Skip to main content
ToolsHub

Security Headers Checker

Enter a URL to grade browser security headers and get a fix list for anything missing or weak.

Updated

Grades HSTS, CSP, clickjacking, MIME sniffing, Referrer-Policy, and Permissions-Policy. This is ToolsHub’s grader, not Mozilla Observatory.

No grade yet

Enter a URL to grade HSTS, CSP, X-Frame-Options, and the other browser security headers.

How to use Security Headers Checker

The Security Headers Checker fetches a URL and grades the HTTP response headers that tell browsers how to treat your site: HSTS, Content-Security-Policy, clickjacking protection, MIME sniffing, Referrer-Policy, and Permissions-Policy. You get an A–F grade, a score out of 100, and a fix line for each failing check. The grader is ToolsHub’s own model — simpler than Mozilla Observatory, aimed at webmasters who need a punch list rather than a research paper.

  1. Enter the page URL (https is required for a meaningful HSTS result).
  2. Click Grade. We GET the URL with SSRF protections and read the response headers.
  3. Read the letter grade and the table. Fail and warn rows are the ones to fix first.
  4. Apply the recommended header on your origin or CDN, then re-run the check.
  5. Use Analyze deeper if you also need the certificate, redirect chain, or on-page SEO.

How the ToolsHub grade is calculated

Every site starts at 100. Missing HSTS on HTTPS costs 20, missing CSP costs 25, missing clickjacking protection costs 15, missing nosniff costs 10, and missing Referrer-Policy or Permissions-Policy cost 5 each. Unsafe-inline in script-src is a warning (-12), not a full fail. Strong HSTS with preload and COOP can add a few bonus points. Scores map to A (90+), B (80–89), C (70–79), D (50–69), and F (below 50). The model is documented so you can disagree with a weighting — it is guidance, not a pentest.

Grade bands
ScoreGrade
90–100A
80–89B
70–79C
50–69D
0–49F

What to set first

If the site is already on HTTPS, add Strict-Transport-Security with max-age of at least 15552000 (180 days) and includeSubDomains once every subdomain is ready. Add X-Content-Type-Options: nosniff and X-Frame-Options: DENY (or CSP frame-ancestors) the same day — they rarely break pages. CSP is the high-value, high-effort header: start in report-only, lock default-src and script-src, then enforce. Referrer-Policy: strict-origin-when-cross-origin and a tight Permissions-Policy are quick wins after that. Do not rely on X-XSS-Protection; browsers have dropped it.

Glossary

HSTS
HTTP Strict Transport Security — tells browsers to use HTTPS only, including on later visits.
CSP
Content-Security-Policy — restricts which scripts, styles, and origins a page may load.
Clickjacking
A UI-redressing attack that embeds your page in a hidden iframe; X-Frame-Options and CSP frame-ancestors mitigate it.
MIME sniffing
When a browser guesses a response type instead of trusting Content-Type; nosniff disables that guess.
COOP
Cross-Origin-Opener-Policy — isolates the browsing context from cross-origin popups.

Related reading

Free · No spam

Get weekly tool tips & updates

New tools, power-user tips, and productivity hacks — delivered free every Friday.

No spam, ever. Unsubscribe with one click.

Related Network & DNS

Explore all Network & DNS.