HTTP response headers carry instructions from a server to the browser about security, caching, and content handling. A handful of these headers are the front line against attacks like cross-site scripting, clickjacking, and protocol downgrade. This free analyzer scores a pasted header block so you can see your security posture at a glance — without any request being made.
How it works
The tool splits your pasted text into lines, skips any HTTP/... status line, and parses each Header-Name: value pair (case-insensitive, repeated headers comma-joined). It then runs a fixed rubric:
- Content-Security-Policy earns full points when present and clean, and reduced points if it contains
'unsafe-inline'or'unsafe-eval'. - Strict-Transport-Security earns full points when
max-ageis at least about 180 days. - X-Content-Type-Options must be
nosniff. - X-Frame-Options or a CSP
frame-ancestorsdirective protects against clickjacking. - Referrer-Policy, Permissions-Policy, and Cache-Control are checked for presence.
- A
Serverheader that leaks a version number is flagged as information disclosure.
Each check contributes weighted points; the total is converted to a percentage and a letter grade from A to F.
Tips and notes
The fastest way to capture headers is curl -sI https://example.com. Aim to ship CSP and HSTS first — they protect against the highest-impact attacks. Remember that a strong CSP without 'unsafe-inline' requires nonces or hashes for any inline scripts, so plan for that when tightening the policy.