Account

What new tool do you want?

Security & Privacy

Website Security Headers Scanner

Get a security grade for any website — HTTPS, HSTS, Content-Security-Policy, clickjacking protection, cookie flags, mixed content and version disclosure — with fixes for each issue.

How to use

  1. 1Enter a website.
  2. 2See your grade and each check, most important first.
  3. 3Add the missing headers in your server or CDN settings.

Frequently asked questions

Is this scan safe to run on any site?

Yes — it's passive. It loads one page like a browser and reads the response; it never sends attack payloads.

What matters most?

HTTPS with an HTTP→HTTPS redirect, HSTS and a Content-Security-Policy give the biggest protection.

Does an A+ mean my site is secure?

No — it means the browser-side protections are set up well. Application bugs need code review and penetration testing.

How this differs from pasting headers yourself

This tool's sibling, the HTTP Security Headers Checker, requires you to run curl or open DevTools yourself and paste the raw headers in — useful for internal or staging sites a public scanner can't reach. This scanner does that fetch for you: type a domain, and a server-side request loads the page exactly like a browser would and reads the response headers, redirect chain, and cookie flags directly, then runs the same category of checks (HSTS, CSP, clickjacking, nosniff, version disclosure) plus a few that need an actual page load to detect — mixed content (HTTP resources loaded on an HTTPS page) and whether HTTP actually redirects to HTTPS.

Why failed checks sort to the top

The results list deliberately sorts failing checks before passing ones, so the first things you see are exactly the items worth fixing — not an alphabetical or arbitrary order you have to scan through. Each failed check also carries its own severity (high, medium, low) shown next to it, which maps to how much weight it carries in the overall score: a missing Content-Security-Policy or HSTS header should jump out as high-priority long before a missing Permissions-Policy does.

Why it's safe to scan a site you don't control

The scan is explicitly passive: it makes one normal page request, reads what the server sends back, and never injects payloads, submits forms, or probes for vulnerabilities the way a penetration-testing tool would. That's why it's safe to point at any public site — your own, a client's, or one you're just curious about — without needing permission the way an active security scan would require. It's a configuration check, not a vulnerability scan.

What an A+ grade doesn't cover

Every check here lives at the HTTP/browser layer — headers, redirects, cookie flags. None of it touches what the application actually does with user input: SQL injection, broken authentication, insecure direct object references and the rest of the OWASP Top 10 require code review, dependency scanning and a real penetration test to find. An A+ here means the browser-facing defenses are configured well; it's a floor worth clearing, not evidence the application logic behind it is secure.

Missing one small header can still be an A+

The score starts at 100. A high failure costs 30 points, a medium failure 12, and a low failure 5, and the score does not go below 0. HTTPS and a missing redirect from plain HTTP to HTTPS are high. HSTS, Content-Security-Policy, clickjacking, cookie flags, and mixed content are medium. X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and version disclosure are low. A+ starts at 95, A at 85, B at 70, C at 55, D at 40, and anything lower is F. Permissions-Policy by itself costs 5 and leaves 95, which is still an A+. A failing HSTS header costs 12 and leaves 88, an A. A site on plain HTTP that also does not redirect costs 60 and lands on 40, the bottom of a D.

HSTS fails unless it lasts at least six months

Strict-Transport-Security passes only when max-age is at least 15,552,000 seconds, which is 180 days. A header that says max-age=86400 — one day — is quoted in the detail and still marked failed. Content-Security-Policy fails if it allows 'unsafe-inline', unless it also uses a nonce, a sha256, sha384, or sha512 hash, or 'strict-dynamic'. Clickjacking passes if either X-Frame-Options or a frame-ancestors rule is set. A cookie fails if it is missing any of Secure, HttpOnly, or SameSite, and up to eight cookie names are listed. Mixed content is checked only on an HTTPS page, and only for ordinary http images, scripts, styles, and fonts, not for localhost. Version disclosure fails if the Server header contains a digit, or if X-Powered-By is present at all.

Related tools

More: Security & Privacy