Security · response headers
Security headers analyzer.
Paste the raw response headers from your browser dev tools or curl -I. The page never requests your site; it only reads the text you paste.
Paste response headers
Paste only headers you are authorized to inspect. Remove cookie values if you prefer; only attribute names are checked.
Findings
Your findings will appear here.
What this checks
- Content-Security-Policy: presence, unsafe-inline / unsafe-eval, wildcard sources, frame-ancestors
- Strict-Transport-Security: max-age (one year, 31536000 seconds, is the preload minimum) and includeSubDomains
- X-Content-Type-Options, Referrer-Policy, Permissions-Policy, X-Frame-Options
- Cross-Origin-Opener-Policy and Cross-Origin-Resource-Policy
- Set-Cookie: Secure, HttpOnly, SameSite and __Host- / __Secure- prefix rules
Limits: This checks the header text you paste. It cannot see redirects, other pages, or what a browser actually enforces, and a clean result is not a security audit. HSTS is only honoured over HTTPS. Some OWASP recommendations (for example COEP require-corp or Cache-Control no-store) suit specific apps and are not flagged here.
Sources: OWASP Secure Headers Project · MDN HTTP headers · MDN HSTS · MDN Referrer-Policy · MDN Set-Cookie
Worked example: reviewing four response headers
Paste this response (from curl -I or browser dev tools): strict-transport-security: max-age=300, x-content-type-options: nosniff, content-security-policy: default-src *; script-src 'unsafe-inline' and set-cookie: sid=abc123; Path=/.
| Level | Header | Finding |
|---|---|---|
| warn | Strict-Transport-Security | max-age=300 is under one year (31536000), the minimum for HSTS preload |
| warn | Content-Security-Policy | 'unsafe-inline' allowed with no nonce or hash, and a wildcard (*) source in the default or script list |
| ok | X-Content-Type-Options | nosniff |
| missing | Referrer-Policy, Permissions-Policy, COOP, CORP, X-Frame-Options | Not present |
| warn | Set-Cookie (sid) | missing Secure; missing HttpOnly; no SameSite attribute |
The findings are prompts for review. Choose headers for the application: for example, cross-origin isolation can affect embeds, and a suitable CSP frame-ancestors directive may replace X-Frame-Options.
Next steps: CSP generator, Permissions-Policy generator, Set-Cookie inspector, or Cache-Control analyzer.
Common mix-ups
-
Often assumedAdding X-XSS-Protection: 1; mode=block protects my site from cross-site scripting.
What the source saysMDN marks X-XSS-Protection as deprecated and non-standard, and warns it can create XSS vulnerabilities in otherwise safe sites. It recommends a Content-Security-Policy instead of browser XSS filtering. [1]
-
Often assumedOnce I send a Strict-Transport-Security header, every visitor is always on HTTPS.
What the source saysMDN explains that a browser that has not yet seen the header makes its first request over plain HTTP, which is open to network attacks. Only HSTS preloading closes that gap, and it requires a max-age of at least one year. [2]
Checked against these sources on .
Frequently asked questions
Does the analyzer request my site?
No. It reads only the header text you paste, so it never contacts your server.
Why is one year the HSTS threshold?
The HSTS preload list requires a max-age of at least 31536000 seconds (one year) along with includeSubDomains and preload.
Should I add every header it lists as missing?
Not blindly. Some, such as Cross-Origin-Resource-Policy: same-origin, break embedding that you may want. Add each one deliberately.
Is a clean result a security audit?
No. It checks the pasted header text only, not redirects, other pages or what a browser enforces.