Enter a URL to see which of six key security headers it sends (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) and get a simple coverage score.
Security Headers Scanner
Enter a URL to see which of six key security headers it sends (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) and get a simple coverage score.
When a browser loads a page, the server sends a set of HTTP response headers before the HTML. A handful of them tell the browser to switch on extra protections: only use HTTPS, refuse to load scripts from unexpected places, refuse to be framed by another site, and so on. If they are missing, the browser falls back to its permissive defaults. This scanner requests the URL you enter from the Toolspedia server, reads the raw response headers, and reports whether six specific headers are present:
| Header | What it does | Reference |
|---|---|---|
| Strict-Transport-Security (HSTS) | Tells the browser to use HTTPS only for this host for max-age seconds, blocking downgrade and cookie-stealing attacks on plain HTTP. | RFC 6797 |
| Content-Security-Policy (CSP) | Lists which sources scripts, styles, images, frames and connections may load from. The main browser-side defence against cross-site scripting (XSS). | MDN |
| X-Frame-Options | Stops other sites putting your page in an iframe (clickjacking). Values: DENY or SAMEORIGIN. | MDN |
| X-Content-Type-Options | With the only valid value nosniff, stops the browser guessing a file's type, so an uploaded text file can't be run as a script. | MDN |
| Referrer-Policy | Controls how much of the current URL is sent to other sites in the Referer header, which matters when URLs contain tokens or search terms. | MDN |
| Permissions-Policy | Switches browser features such as camera, microphone and geolocation on or off for your page and any embedded frames. | MDN |
Run it after launching a site, moving host or CDN, changing server or security-plugin settings, or when an auditor asks whether security headers are in place.
https:// (for example https://www.yoursite.com/). The field rejects input that doesn't start with http:// or https://. You can also click one of the example chips (example.com, github.com, cloudflare.com) to see how a result looks.We ran the scanner on three addresses in October 2026. Headers change whenever a site redeploys, so your results may differ, but the pattern is what matters.
| URL scanned | Headers found | Score | Missing |
|---|---|---|---|
| https://github.com | 5/6 | 83% | Permissions-Policy |
| https://cloudflare.com | 1/6 | 17% | Everything except HSTS |
| https://www.cloudflare.com/ | 6/6 | 100% | None |
The score is simply headers present divided by six: 5 / 6 = 0.833, shown as 83%. GitHub sends a long HSTS policy (max-age=31536000; includeSubdomains; preload, which is one year), a strict CSP, X-Frame-Options: deny, nosniff and a Referrer-Policy, but no Permissions-Policy.
The Cloudflare pair is the more useful lesson. https://cloudflare.com answers with a 301 redirect to https://www.cloudflare.com/, and that redirect response carries only HSTS, so it scores 17%. The scanner does not follow redirects; it reports the headers of exactly the URL you typed. Scan the final address and the same company scores 100%. Always scan the URL your visitors actually end up on, and scan the bare domain separately if you want to check that the redirect itself sends HSTS.
Because every header counts the same, the percentage only moves in steps of about 17 points. It is a checklist, not a risk rating: a site missing only CSP scores 83% but lacks the header that does the most against XSS, while a missing Permissions-Policy matters little on a page that never uses the camera or location.
The scanner checks that each header exists, not whether its value is strong. In our test www.cloudflare.com scored 100% while its CSP includes 'unsafe-inline' and 'unsafe-eval' in script-src, which weakens XSS protection. So after the scan, look at the values yourself:
max-age should be long; 31536000 (one year) is the common choice and is the minimum for the HSTS preload list. A value like max-age=300 counts as present here but protects for only five minutes. Our HSTS Header Checker pulls out max-age, includeSubDomains and preload for you.'unsafe-inline', 'unsafe-eval', wildcards like * or https: in script-src, and a missing default-src. A header named Content-Security-Policy-Report-Only does not enforce anything and is not counted.DENY or SAMEORIGIN. MDN points to CSP's frame-ancestors directive as the modern replacement; sending both does no harm.strict-origin-when-cross-origin or stricter. unsafe-url leaks full URLs. The Referrer Policy Checker shows the exact value.Headers are added on the web server, CDN or application, not in the HTML. A reasonable starting set for nginx looks like this (the always flag makes nginx send them on error pages too):
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
add_header Content-Security-Policy "default-src 'self'; frame-ancestors 'self'" always;
On Apache the equivalent is Header always set Name "value" with mod_headers enabled. Two cautions: only add includeSubDomains once every subdomain works over HTTPS, and roll CSP out with Content-Security-Policy-Report-Only first, because a strict policy copied from elsewhere will usually block your own analytics, ads, fonts or embedded videos. The OWASP HTTP Headers Cheat Sheet lists recommended values for each header.
/api/ or on static files), so scan a few representative URLs.You can get the same raw data with curl -sI https://www.yoursite.com/ in a terminal or the Network tab of your browser's developer tools (click the document request and look at Response Headers). That shows every header and lets you follow redirects with curl -sIL, but you have to know which six names to look for and spot the missing ones yourself. The scanner is quicker for a yes/no checklist on any device; DevTools or curl is better when you need full values or are debugging a specific path.