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.

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.

Enter a valid value or use one of the quick examples above.
Live analysis is enabled where server-side checks are available. A few tools still fall back to readiness mode when they need external network services or third-party APIs.

What this scanner checks

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:

HeaderWhat it doesReference
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-OptionsStops other sites putting your page in an iframe (clickjacking). Values: DENY or SAMEORIGIN.MDN
X-Content-Type-OptionsWith 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-PolicyControls 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-PolicySwitches 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.

How to use it

  1. Type the full address into the URL field, including 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.
  2. Click Scan Security Headers. The request is made from our server, so it usually returns in a second or two.
  3. Read the result panel: the summary badge shows the score as a percentage, three tiles show Security Score, Headers Found (for example 4/6) and whether HSTS is on, and below them each of the six headers is listed as Present or Missing.

Worked example: three real sites

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 scannedHeaders foundScoreMissing
https://github.com5/683%Permissions-Policy
https://cloudflare.com1/617%Everything except HSTS
https://www.cloudflare.com/6/6100%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.

How to read the score

  • 83-100% (green): five or six of the headers are present. Now check their values (see below), because presence alone doesn't prove they're configured well.
  • 50-67% (amber): three or four present. Usually HSTS and nosniff are there and CSP or Permissions-Policy is missing.
  • 0-33% (red): two or fewer. Common on default shared hosting and on static sites served straight from a CDN with no header rules.

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.

What "Present" does not tell you

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:

  • HSTS: 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.
  • CSP: watch for '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.
  • X-Frame-Options: DENY or SAMEORIGIN. MDN points to CSP's frame-ancestors directive as the modern replacement; sending both does no harm.
  • Referrer-Policy: strict-origin-when-cross-origin or stricter. unsafe-url leaks full URLs. The Referrer Policy Checker shows the exact value.

Fixing missing headers

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.

Limits worth knowing

  • Public URLs only. The request comes from the Toolspedia server, so it can't reach localhost, staging sites on a private network, or pages behind a login.
  • One URL at a time. Different paths can return different headers (an app may set CSP on pages but not on /api/ or on static files), so scan a few representative URLs.
  • Six headers only. It does not score X-XSS-Protection (OWASP advises against relying on it; modern browsers have removed the XSS auditor), the Cross-Origin-Opener/Embedder/Resource-Policy headers, CORS, or cookie flags such as Secure, HttpOnly and SameSite. To see every header the server returned, use the HTTP Headers Checker.
  • Headers are one layer. A perfect score doesn't mean the site is secure; it says nothing about outdated software, weak passwords or vulnerable plugins.

Scanner vs checking by hand

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.

Frequently Asked Questions

It is the number of the six checked headers that are present, divided by six. Each header is worth about 17 points, so 5 of 6 shows 83%. Scores of 80% and above show green, 50-79% amber and below 50% red.

The scanner does not follow redirects. If https://example.com redirects to https://www.example.com/, the redirect response often carries few or no security headers. Scan the final URL your visitors land on.

No. The tool checks that each header exists, not that its value is strong. A CSP containing 'unsafe-inline' or an HSTS max-age of a few minutes still counts as present, so review the values after scanning.

It is not part of this score. The OWASP HTTP Headers Cheat Sheet advises against relying on it because modern browsers removed the feature it controlled; a Content-Security-Policy is the current defence against XSS.

No. The request is sent from the Toolspedia server, so it can only reach publicly accessible URLs. For localhost or staging sites, check the headers in your browser's developer tools or with curl -I.