Screen Resolution Checker
Your screen size, viewport, pixel ratio and which breakpoint is active.
Paste raw HTTP headers and get them parsed, explained and checked.
The HTTP Header Parser turns a pasted header block into a readable table, pulls apart the start line, comments on the security headers, flags version leaks and calls out duplicates that matter.
Copy a block of headers out of your browser's network panel or a curl -I output and paste it here. They are parsed into a readable table, with the start line pulled apart into its method and target, or its status code and reason.
Beyond formatting, the parser comments. Security headers are noted as present or missing — Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, Referrer-Policy. Headers that leak version information, such as Server and X-Powered-By, are flagged. Duplicates are called out, because a repeated Set-Cookie is normal and a repeated Content-Length is a request-smuggling risk. Folded continuation lines are rejoined the way a server would.
HSTS, CSP, nosniff and Referrer-Policy are reported as present or missing, rather than simply listed if they happen to be there.
Server and X-Powered-By tell an attacker exactly what to target, and the parser says so.
A repeated Set-Cookie is normal; a repeated Content-Length is a request-smuggling risk. Both are surfaced.
A status line gets its code explained, a request line its method and target separated.
Obsolete continuation lines are joined the way a server would read them, so a wrapped header is not misread.
From developer tools, curl -I, or a raw request log.
A status line shows the code and its meaning; a request line shows the method and target.
Missing protections and version-leaking headers are both called out.
Repeated headers are listed, since some are fine and some are a problem.
In Chrome or Firefox developer tools, open the Network tab, click a request and use "Copy response headers" or "Copy request headers". On the command line, curl -I gives you response headers directly.
Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options: nosniff and a Referrer-Policy cover most of the ground. The parser says which are present and which are not.
It depends which. Set-Cookie repeats by design. A repeated Content-Length or Transfer-Encoding is a serious problem, because different servers in a chain may disagree about which one to honour.
No. The tool parses what you paste. Fetching a URL from the browser would be blocked by CORS anyway, and this site does not make requests on your behalf.
What people who use the HTTP Header Parser think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the HTTP Header Parser. It takes half a minute and no account.
Write the first reviewYour screen size, viewport, pixel ratio and which breakpoint is active.
Build a frosted glass panel with backdrop blur, over a real background.
Encode and decode Base58 in the Bitcoin, Ripple or Flickr alphabets.
Every HTTP status code, searchable, with what it actually means.
Tidy a TOML file: consistent quoting, ordered tables, keys before headers.
Run JSONPath expressions against a document and see every match live.
See a float’s sign, exponent, mantissa and its exact decimal value.
Reveal tabs, non-breaking spaces and zero-width characters in your text.