Practical example
For a cached API response, inspect Cache-Control, Age, ETag, Vary, and Content-Type together instead of reading one header in isolation.
HTTP Headers Parser
Paste raw HTTP headers and instantly parse them into structured JSON.
You can paste raw request or response headers, with or without the HTTP status line.
0 headers
What is an HTTP headers parser?
HTTP headers carry metadata about requests and responses, such as content type, caching, security rules, and server behavior.
This tool helps you convert raw HTTP headers into structured JSON and a readable key-value list directly in your browser.
How to use the HTTP Headers Parser
- Paste raw HTTP request or response headers into the input field.
- Click Parse.
- View the headers as JSON and as a readable list.
Tips
- You can paste headers copied from browser DevTools, curl, Postman, or server logs.
- Duplicate headers are grouped into arrays.
- Security-related headers are highlighted for quick review.
Related guides
Learn the workflow behind this tool and what to check next.
HTTP debugging
How to debug redirects and HTTP status codes
A practical workflow for checking redirect chains, understanding 301 vs 302, diagnosing 404 and 500 responses, and confirming the final URL.
Read guide
DNS and domains
How to troubleshoot DNS records for a domain
A practical DNS checklist for website hosting, email records, domain verification, nameserver changes, SSL certificates, and reverse DNS.
Read guide
HTTP header checks for debugging requests and responses
Headers explain caching, negotiation, security, proxies, and authentication behavior that is not visible in the response body.
Caching rules
Read Cache-Control, Expires, ETag, Vary, and Age together to understand browser and intermediary cache behavior.
Content handling
Confirm Content-Type, charset, Content-Encoding, and Content-Disposition match the bytes and download behavior you expect.
Proxy evidence
Inspect Via, Forwarded, X-Forwarded-* and vendor headers when CDN or reverse-proxy behavior differs from the origin.
Sensitive values
Redact cookies, authorization headers, internal hostnames, request IDs, and infrastructure details before sharing a capture.
A practical example, an edge case, and a maintainer note
Edge case
Headers may repeat, and Set-Cookie must not be combined like an ordinary comma-separated header. Preserve every occurrence.
Maintainer note
The same response can be changed by an origin, reverse proxy, and CDN, so identify which layer added each surprising header.
Related tools
You may also find these tools useful.
HTTP Status Code Lookup
Look up HTTP response codes such as 404, 301, 302 and 500 instantly.
Network & Web
›
cURL Parser
Parse cURL commands into method, URL, headers, query parameters, and body instantly.
Network & Web
›
User-Agent Parser
Parse browser, OS, device, engine, and bot info from User-Agent strings.
Network & Web
›
Meta Tags / Open Graph Preview
Preview Google and Open Graph snippets and generate meta tags.
SEO & Webmaster
›
HTTP Headers Parser FAQ
Are my HTTP headers sent anywhere?
No. The raw headers are parsed in the page — cookies, authorization tokens, and internal hostnames stay local.
Can I paste a full HTTP response?
Yes. The status line like HTTP/1.1 200 OK is ignored during parsing.
What happens with duplicate headers?
They are grouped into arrays in the parsed JSON output.