Skip to content

How well does your site protect its visitors?

A grade for the security headers a website sends (HSTS, CSP, framing, referrer and more), with a plain-language fix for each gap.

For example https://example.com/. A bare name such as example.com is checked as https://.

Security headers score

Ready to check

Enter an address and press Check.

  • HTTPS only (HSTS)
  • Content security policy
  • Embedding in other sites

A grade for the security headers a website sends (HSTS, CSP, framing, referrer and more), with a plain-language fix for each gap.

How to use

  1. Paste the web address you want to check, such as https://example.com/. A bare name like example.com is checked as https://.
  2. Press Check. The tool reads the headers the site sends and shows a grade from A to F.
  3. Go through the list: each header says in plain words what is set, and what to change when it is not.

How it works

Security headers are short instructions a website sends with every page. They tell the browser to use only https (Strict-Transport-Security), which scripts may run (Content-Security-Policy), whether other sites may show the page in a frame (frame-ancestors or X-Frame-Options), not to guess file types (X-Content-Type-Options), how much of the address to share when a link is followed (Referrer-Policy) and which browser features the page may use (Permissions-Policy). They cost nothing to send and close whole classes of attack.

The grade is points out of 100: CSP 30, HSTS 25, framing 15, and 10 each for nosniff, referrer and permissions. A header that is right earns all of its points and a weak one half. A missing header earns none, except Referrer-Policy and Permissions-Policy, which earn half: leaving them out is a smaller risk, because browsers then use a safe default for referrers and the page simply gets no extra limits. A starts at 90 points, B at 75, C at 60 and D at 40. Example: HSTS for a year (25), a strict CSP (30), framing blocked (15) and nosniff (10), but no Referrer-Policy or Permissions-Policy (5 + 5), scores 90, an A. The weights are this tool’s policy, not a standard. A CSP counts as weak when it allows 'unsafe-inline' scripts without a nonce or hash, 'unsafe-eval', or wildcards. Sources: MDN Web Docs on each header; the OWASP HTTP Headers Cheat Sheet.

The check reads the final response once from our server, after redirects. Headers can differ by page, by country or by browser, and an error page may send different ones. Cross-origin isolation headers (COOP, COEP, CORP) are shown for information only: most sites do not need them.

Sources

Sources and methods

Frequently asked questions

Which header matters most?

Content-Security-Policy does the most against script injection, but it is also the hardest to get right. Strict-Transport-Security is the easiest big win: one line keeps visitors on https.

Is 'unsafe-inline' always bad?

In a script policy it lets any injected inline script run, which defeats much of the point. It is ignored by browsers when the same directive has a nonce or hash, which is how strict policies are built.

Do I need both X-Frame-Options and frame-ancestors?

frame-ancestors in a CSP is the modern way and wins when both are present. X-Frame-Options still covers very old browsers, so many sites send both.

Why is HSTS flagged on a page that ends on http?

Browsers ignore Strict-Transport-Security sent over plain http. Redirect to https first, then send the header there.

Will a good grade make my site secure?

No. Headers are one layer. They do not fix vulnerable code, weak passwords or outdated software.

Why does the grade differ from another checker?

Every checker picks its own weights and strictness. This one explains each point so you can see exactly what it counted.

Send feedback