Help Centre

1. I pasted JSON and the tool says "INVALID" with a line and column — what does that mean?

The diagnostic points at the exact character where the JSON parser stopped and says what it was expecting there. Common causes:

• Trailing comma — JSON does not allow a comma before } or ]. Remove the last comma before the closing brace or bracket.
• Missing closing brace/bracket — the input ends before the structure is closed. Look at the highlighted position: the parser was expecting } or ] there.
• Unquoted key or value — all property keys and string values must be wrapped in double quotes ("). Single quotes are not valid JSON.
• Extra text after root value — JSON only permits one value at the top level. Check for stray characters or a second JSON document after the first one.

The error message in the result panel gives a plain-language explanation of each case.

2. My URL fetch returned an "ERROR" badge or a non-2xx status — is my API really broken?

Not necessarily. The tool reports exactly what the server sent back. If the status code is not in the 200-299 range (e.g. 404, 500, 403, 502), the response is flagged as an error and every derived verdict (e.g. whether the body is valid JSON) is marked as unreliable. A 200 response with a JSON Content-Type but an HTML body is also flagged — this is a common pattern where an API returns an error page dressed as a successful JSON response.

Tip: always check the body preview to see what the server actually sent. If it is HTML when you expected JSON, the API gateway or reverse proxy is probably catching the error before your application handler runs.

3. The tool says "unreachable" but the URL works in my browser — what's happening?

The server-side fetch runs on Cloudflare Workers. Hosts that are themselves behind Cloudflare cannot be reached from a Worker — the platform refuses to open a connection back into its own network. This is a documented platform limitation of the Worker runtime. The tool shows a note about this next to the input field so you know the unreachability is expected rather than a network fault.

If you are certain the target host is not behind Cloudflare and the fetch still fails, the server may have been unable to resolve the DNS name or connect for other network reasons (DNS failure, timeout, firewall block). Try pasting the response body directly instead of fetching the URL.

4. Does Jsonprobe store my data?

No. Pasted JSON is parsed entirely in your browser — the text never leaves your device. URL fetch requests are sent to the server, processed, and the result is returned to your browser. The server does not store, log, cache, or share URLs, response bodies, or any part of the request. There are no user accounts, no cookies, no analytics scripts, and no tracking mechanisms on this site. See the privacy policy for the full detail.

5. How do I subscribe to Pro or Enterprise?

The Pro ($9/month) and Enterprise ($49/month) tiers are planned but not yet available. The Free tier is fully functional today and includes everything listed on the pricing page. No payment infrastructure is wired on this site — the checkout form on the pricing page is a demonstration only and does not process any real payment. There is no way to subscribe today.

6. How do I report a bug or request a feature?

Support is not yet reachable by email — no mailbox is maintained on this domain. The best route to report a genuine bug or suggest a feature is to open an issue in the repository that publishes this code. If you do not have access to a repository and your concern is urgent, see the Contact us section below for the current limitations on support reachability.