Help Centre

Getting started, common questions, and known limitations for the Rawscope JSON diagnostic tool.

Getting started

What is Rawscope?
Rawscope is a diagnostic tool for developers debugging JSON parsing issues. Paste a JSON blob and it tells you the exact line, column, and expected token where the parse failed. Or enter a URL and it fetches the response server-side, showing you the HTTP status, content-type, headers, body, and whether the response is actually JSON — or an HTML error page masquerading as one.
How do I use the tool?

There are two modes on the App page:

Pasted text (default): Paste or type a JSON blob into the text area and click Parse JSON. The parsing happens entirely in your browser — nothing is sent to any server.

URL fetch: Switch to the URL tab, enter an HTTP or HTTPS URL, and click Fetch & parse. The tool fetches that URL from a server-side Worker and returns a full diagnostic report including the response body, headers, status code, content-type, and redirect chain.

What does a successful result look like?
For valid JSON, the verdict box shows a green Valid JSON message and the parsed object is displayed. For a URL fetch, you additionally see the server metadata table and the response body preview. For invalid JSON, the verdict shows the exact line number, column, and a plain-language description of what was expected — instead of an opaque "unexpected token at position 4471".

Frequently asked questions

The tool says "This host is behind Cloudflare and cannot be reached from this Worker." What does that mean?
Rawscope’s URL fetch runs on a Cloudflare Worker. Cloudflare Workers cannot make outbound requests to IP addresses that are themselves behind Cloudflare. This is a platform restriction, not a bug in Rawscope or an issue with your target host.

If you need to inspect a Cloudflare-fronted endpoint, try pasting the response body into the Pasted text mode instead (obtain the body via curl, a browser’s network inspector, or an alternative tool).
My fetch returned "timed out after 15 seconds". Can I increase the timeout?
Not on the Free tier. The Worker enforces a hard 15-second timeout for outbound requests to prevent slow endpoints from blocking the service for other users. A longer timeout is a planned Pro tier feature, but it is not built or buyable yet. For now, if your endpoint consistently takes longer than 15 seconds, consider inspecting it locally with curl or another tool and pasting the result.
The response body says "truncated" — where is the rest?
Response bodies over 10,000 characters are truncated in the diagnostic report to keep the tool responsive. The truncation is clearly marked in the report. A Pro tier with untruncated response bodies is planned but not yet available.
Is my data stored or logged when I use Rawscope?
No. Text you paste in Pasted text mode is parsed entirely in your browser and never sent anywhere. URLs you fetch are transferred to the Worker only to perform the fetch and return the result; no request history is retained server-side.

Rawscope has no accounts, no user profiles, no tracking cookies, and no analytics SDKs. See the Privacy Policy for full details.
Does Rawscope follow redirects?
Yes — the Worker follows up to 5 redirects per request, validating each hop against the same SSRF (Server-Side Request Forgery) protection rules (no loopback, link-local, or private-network addresses). The report shows how many redirects were followed. If more than 5 redirects are needed, the tool reports the endpoint as unreachable.
Can I buy Pro yet?
No. Pro is planned but not yet built or available for purchase. No payment processor is connected, and the checkout form on the Pricing page is a demo only. When Pro launches, it will be announced on this site. There is no mailing list to notify you — the only way to know is to check back.

Known limitations

How to contact us

No mailbox configured

Rawscope does not yet have a support mailbox, contact form, or any other channel through which to receive user messages. There is no registered legal entity behind the service and no email address on any domain in this fleet that can receive mail.

If you have found a bug or have a feature request, the operator is aware of the lack of a contact channel and will establish one as a priority. Check back on this page for updates.

Until then, please do not assume any address you see elsewhere on this site is reachable. If a contact address is shown on any page, it has not been verified to receive mail.