Help centre

What's the difference between URL mode and paste mode?

URL mode sends the URL to the Pinpointjson Worker running on Cloudflare. The Worker fetches the URL, inspects the raw response (status code, content-type, body), and returns the analysis. This lets you see what the server actually sent — not just whether the JSON is valid.

Paste mode processes the JSON entirely in your browser. No data touches a server. This is useful for local debugging, logs, or snippets where you want to check validity without sharing the content over the network. Both modes show parse errors with exact line/column position and a plain-language explanation.

Why does my domain show as unreachable?

A Cloudflare Worker cannot open a TCP connection to a host that is itself behind Cloudflare. This is a platform limitation, not a problem with your server. Domains such as example.com, cloudflare.com, and stackoverflow.com will report as unreachable. Verified reachable targets include github.com, wikipedia.org, and news.ycombinator.com. There is no workaround from within the Worker — you would need to fetch from a different infrastructure to reach Cloudflare-backed origins.

How do I read the diagnostic report?

The report is built from several cards, each covering one aspect of the response:

• HTTP response — The status code, declared content-type, body length, final URL after redirects, and a list of redirect hops (up to 5).
• Content-type analysis — Whether the body's content-type matches JSON. A mismatch (e.g. HTML returned as application/json) is flagged as a separate finding.
• JSON parse — The parse verdict. If valid, it shows the structure type, keys, and a preview. If invalid, it shows the exact line, column, and position of the error with a plain-language explanation and the surrounding snippet.
• Error response detection — When the body parses as valid JSON but contains error-like fields (e.g. {"status":"error"}) alongside a 200 HTTP status, a separate warning is shown.
• Raw body preview — Shown when the body is not JSON or when parsing fails, so you can see what the server actually returned.

Is my data stored on the server?

No. Pinpointjson does not have user accounts, databases, or persistent storage. When you diagnose a URL, the URL and response are processed in the Worker's memory and returned to your browser. When you paste JSON, processing happens entirely client-side. Neither data is logged, stored, or retained. See the privacy policy for details.

What is an "error object dressed as success"?

Some APIs return an HTTP 200 status but include a JSON body that indicates an error — for example {"status":"error","message":"Rate limit exceeded"}. The HTTP status says everything is fine, but the body tells a different story. Pinpointjson detects this by looking for error-related fields in parsed JSON and flags it as a separate finding. This is one of the most common causes of "the API returned success but nothing works" and is invisible to standard JSON validators.

Can I use Pinpointjson with a private or internal API?

The Cloudflare Worker that performs URL diagnosis can only reach publicly routable hosts on the open internet. It cannot reach localhost, private IP ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x), link-local addresses, or cloud metadata endpoints. The Worker explicitly blocks these addresses. For internal APIs, you can paste a sample response in paste mode to check whether the JSON structure is valid, but the full forensic report (content-type, headers, redirects) requires the URL to be reachable from the Worker.