Category: Developer tools
HTTP Headers Parser
Parse pasted response headers and spot security and cache headers
Paste raw HTTP response headers from DevTools or curl -I and see each name, value and category, with security and cache headers highlighted. Parsed in your browser.
| Name | Value | Category |
|---|---|---|
Content-Type | text/html; charset=utf-8 | General |
Cache-Control | no-cache, must-revalidate | Cache |
Strict-Transport-Security | max-age=63072000; includeSubDomains | Security |
X-Content-Type-Options | nosniff | Security |
X-Frame-Options | DENY | Security |
ETag | "33a64df551" | Cache |
Server | nginx | General |
Everything on this page is processed in your browser. Nothing is uploaded.
What this tool does
Paste raw HTTP response headers — copied from your browser's network panel or a curl -I output — and see them split into a name, value and category, with common security and caching headers highlighted. Parsed entirely in your browser; nothing is fetched over the network.
How to use it
- Get the raw text first: copy the response headers from the network panel in your browser's DevTools, or run curl -I against the URL and copy the command output.
- Paste that raw text into the input; the parser works line by line in your browser and splits each line into a header name and its value.
- Read the parsed table: security headers such as Strict-Transport-Security and X-Frame-Options and cache headers such as Cache-Control and ETag are marked separately from general headers like Content-Type and Server, so you can jump straight to the ones you came to check.
Privacy
This tool runs entirely in your browser. Your input is never uploaded, stored or shared — closing the tab removes it.
Frequently asked questions
- Does this tool fetch the headers for me?
- No. It makes no network request and never visits a URL on your behalf. You bring the headers yourself — copy them from the DevTools network panel or run curl -I and copy the output — and paste that text in to have it parsed.
- Why is the status line ignored?
- The parser reads each line as a header name and a value. A status line such as HTTP/1.1 200 OK has no header name, so it does not become a row. You can still paste a whole curl -I output; the table shows the actual headers from it.
- Which headers count as security headers here?
- Common security controls such as Strict-Transport-Security and X-Frame-Options are flagged as security headers, caching controls such as Cache-Control and ETag are flagged as cache headers, and routine fields like Content-Type and Server stay general. The categories help you find headers faster; they are not a verdict on whether your configuration is correct.
- Is my input, file, or result uploaded?
- No. Your input, settings and parsed results stay in the browser and are not uploaded to LocalTools. Response headers can contain sensitive values such as Set-Cookie, which is why the parsing happens locally.
- What does this tool not support?
- It only parses response header text that you paste. There is no server upload or cloud processing, no accounts, sync or cloud history, and no crawling, third-party APIs or automatic external lookups. Formats, algorithms and batch features that are not described on this page are not available.