HTTP Header Analyst
Parse and analyze HTTP headers for security best practices.
Parse and analyze HTTP headers for security best practices. Enter your numbers and get an instant result.
Paste raw HTTP headers, one per line, and the page parses each into its parts and counts how many it recognises as security headers.
This page executes on the tool server: the pasted text is sent for that one request, the analysis runs there, and nothing is stored. An empty paste is refused with the reason, and nothing is ever fetched from any server on your behalf.
The output is an inventory, not a grade: every header parsed, the security-relevant ones flagged, and their count reported beside the full parse.
What the analysis covers
Each line is split into name and value and checked against the page's list of security headers. Recognised names are marked with their role, and the security count totals them at the end of the response.
Unrecognised headers are still parsed and shown; they simply do not add to the security count. The page describes what arrived, never what should have.
- Every pasted header parsed by name
- Security headers flagged by role
- Security count beside the full parse
What is sent and what is kept
The request carries the pasted headers, and the response carries the parse. Neither is written to disk or logged; a second paste is a second request with no memory of the first.
The page never requests the URL the headers came from. Analysis reads only your paste, so private response headers stay between you and the page.
How to use the headers box
Paste the raw HTTP headers, one per line, and press Execute Tool Engine. Each line is split into name and value and checked against the page's security header list; recognised names are marked with their role, unrecognised ones still parsed and shown, and the security count totals them at the end.
Empty pastes are refused with the reason, and nothing is ever fetched from any server on your behalf: the page never requests the URL the headers came from, so private response headers stay between you and the page.
What to Expect
Best for
- Inventorying a response's security headers
- Checking a paste for a specific header
- Learning which headers carry security roles
Not ideal for
- Grading a site's overall security
- Fetching headers from a live URL
- Judging header values as safe or unsafe
What this tool keeps
- Every header line you pasted
- The same parse for the same paste
- Your paste private beyond the single request
What may need cleanup
- Checking values the page does not judge
- Comparing against a hardening guide
- Re-pasting after the server changes its headers
Common errors
- Reading the count as a security score
- Expecting the page to fetch a URL
- Pasting request headers and reading them as response policy
Example use cases
- Auditing a deployment's response headers
- Confirming a new header shipped
- Teaching what each security header does
Sample input
A pasted response header block with content-type, strict-transport-security and x-frame-options lines.
Sample output
Each header parsed with the security names flagged and their count reported, analysed on the tool server.
Who this is for
- Developers hardening responses
- Security reviewers auditing headers
- Anyone learning HTTP header roles
Frequently asked questions
What do I paste?
Raw HTTP headers, one per line, exactly as the response carried them. An empty paste is refused with the reason.
What does the security count mean?
How many of the pasted headers the page recognises as security headers. It is a count of recognised names, not a grade of the site.
Does the page fetch the URL itself?
No. It analyses only the text you paste, so nothing is requested from any server on your behalf.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.