Turn a raw block of HTTP headers into something readable. Paste request or response headers from DevTools, curl or a log, and get a searchable table with the status line separated, repeated headers like Set-Cookie kept, and a short explanation of what each common header does. Missing security headers are pointed out. Copy everything as JSON. It's free, runs in your browser, and nothing is sent anywhere.
| Header | Typical value |
|---|---|
| Strict-Transport-Security | max-age=31536000; includeSubDomains |
| Content-Security-Policy | default-src 'self' |
| X-Content-Type-Options | nosniff |
| Referrer-Policy | strict-origin-when-cross-origin |
| Permissions-Policy | camera=(), geolocation=() |
In Chrome or Firefox DevTools open the Network tab, select a request and copy the headers, or run curl -I https://example.com.
Each cookie needs its own Set-Cookie line. They're kept separate here, and become an array in the JSON.
At minimum Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options: nosniff and a Referrer-Policy. The tool lists any that are missing.
Yes, including pseudo-headers such as :authority and :path.
No. Parsing happens in your browser.
The parser reads a raw header block as copied from browser DevTools, curl -I or a server log. The first line is checked for an HTTP start line — a response status line such as HTTP/1.1 404 Not Found, or a request line such as GET /path HTTP/1.1 — and shown separately. Each following line is split at its first colon into a field name and value; HTTP/2 pseudo-headers like :authority are kept, and the obsolete line folding of old HTTP/1.1, where a continuation line starts with whitespace, is joined to the header above. Repeated headers are preserved in order rather than merged, because Set-Cookie in particular must never be combined into one line. About fifty common headers carry a one-line explanation. For responses, the tool notes which basic security headers are missing — Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options and Referrer-Policy — flags framework banners such as X-Powered-By and the CORS combination of a wildcard origin with credentials, which browsers reject. Lines that aren't headers are reported by number.