Line and column for every JSON error — plus the raw server response.

Paste a URL or a blob of JSON. Rawscope parses it and, when it fails, points at the exact line and column and says what was expected there in plain language — not “unexpected token at position 4471.” For a URL it also reports what the server actually sent: the content-type, whether the body is JSON at all, and whether it is a JSON error object dressed as a 200.

Open the tool Pricing

What you see now

SyntaxError: Unexpected token at position 4471 — no line, no column, no hint about what was expected. If it came from an API, you get the same message whether the server sent malformed JSON, an HTML error page, or an entirely different protocol. The position number tells you nothing useful.

What Rawscope shows

Line 143, column 27. Expected a comma but found }. For a URL response, the tool also reports the Content-Type header, whether the body is JSON at all, and how many bytes the server sent. A surprising share of “my API is broken” is an HTML error page with a 200 status and a JSON content-type, and nothing about that is visible until someone looks at the bytes.

What the tool does

# Paste text — parse a JSON blob in-browser. Shows line, column, expected token, and a human-readable explanation of the error. Valid JSON renders the parsed object.

# Fetch a URL — the Worker fetches the URL (SSRF-safe) and returns the server’s actual response: status, content-type, headers, body. If the body is JSON, it is parsed and checked.

# Server metadata — content-type, HTTP status, body size, and whether the server claims the body is JSON when it is not.

# Redirect tracking — follows up to 5 redirects with SSRF validation at each hop, and reports how many were followed.

# Plain-language errors — replaces “unexpected token at position 4471” with line, column, and expected value in clear terms.

How it works

01 Paste a URL or JSON blob into the tool.

02 If a URL: the Worker fetches it server-side, returns the actual bytes. Parsing happens on the server for URL fetches, entirely in your browser for pasted text.

03 Read the diagnostic report: line, column, expected token, server metadata, and the actual response body.

Known limitations

A host behind Cloudflare cannot be reached from the Worker. Those hosts will report as unreachable, which is a platform restriction — not a result about your host.
The Worker enforces a 15-second timeout. Slow endpoints will time out.
Response bodies over 10,000 characters are truncated in the diagnostic report.
Only HTTP and HTTPS URLs are accepted. No FTP, no file: protocol.
The Worker fetches exactly one URL. It does not crawl, follow links, or retry.