1. Home
  2. Free tools
  3. Security headers checker

Security headers checker

Paste a page address to grade its HSTS, Content-Security-Policy, clickjacking, referrer and permissions headers, then copy the fix for your server.

No sign-up.Try:
Check several addresses at once (up to 10)
0 of 10

How to use it

  1. Enter the address of a page, for example https://example.com/.
  2. Read the grade and the table. Each header is marked Set, Weak or Missing, with one line on what to do.
  3. Pick your server in the snippet box, copy the lines, add them to your configuration and run the check again.

What it checks

  • Strict-Transport-Security (HSTS) and its lifetime
  • Content-Security-Policy, including unsafe-inline and wildcard sources
  • Clickjacking protection through frame-ancestors or X-Frame-Options
  • X-Content-Type-Options, Referrer-Policy and Permissions-Policy
  • Cross-Origin-Opener-Policy (optional extra)
  • Server and X-Powered-By headers that reveal version numbers

Limits

  • Reads the headers of one response. Different pages, paths or file types on the same site can send different headers.
  • Checks that headers are present and sensibly set. It does not test whether a Content-Security-Policy would break your site, or find vulnerabilities.
  • The grade is a simple weighted score for comparison over time, not a security certification.

Public pages only, one page at one point in time. See the methodology and terms.

Frequently asked questions

How is the grade calculated?

Each header carries a weight: CSP 30, HSTS 20, clickjacking protection 15, and 10 each for X-Content-Type-Options, Referrer-Policy and Permissions-Policy, with 5 for COOP. A weak setting earns part of the points. The total maps to A+ (95 and up) through F. A page served over plain HTTP is capped at F.

Will adding these headers break my site?

Most are safe. The Content-Security-Policy is the exception: a strict policy can block scripts, styles or images you rely on. Deploy it as Content-Security-Policy-Report-Only first, review what it would have blocked, then enforce it.

Why does the tool only look at one page?

Headers are usually set for the whole site, but not always. Static files, an API, or a login page can differ. Check the pages that matter most, including one behind your CDN.

Does a good grade mean my site is secure?

No. Headers are one layer. They reduce the damage from common browser-side attacks, but they do not fix vulnerable code, weak passwords or outdated software.

Where do I see raw headers or the SSL certificate?

Use CheckDomainHealth for raw HTTP headers, certificate details, DNS and email records. This tool focuses on grading the security headers and giving you the fix.

↑ ↓ to moveEnter to openEsc to closeAll results