Account

What new tool do you want?

Security & Privacy

HTTP Security Headers Checker

Paste a site's HTTP response headers to grade its security headers — HSTS, CSP, X-Content-Type-Options, clickjacking protection, Referrer-Policy and Permissions-Policy.

How to use

  1. 1Get the headers: run curl -sI https://example.com, or open DevTools → Network → click the page → Response Headers → copy.
  2. 2Paste them here to see the grade and what to fix.

How it's calculated

Each header is weighted (HSTS 25, CSP 25, clickjacking 15, nosniff 10, Referrer-Policy 10, Permissions-Policy 10, no version leaks 5). Grade: A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 40, otherwise F.

Frequently asked questions

Why paste headers instead of entering a URL?

Browsers block pages from reading other sites' headers. Pasting keeps the check private and works for internal sites too.

Which header matters most?

A strict Content-Security-Policy and HSTS give the biggest protection — against script injection and HTTPS downgrade attacks.

Is X-XSS-Protection still needed?

No — modern browsers removed the XSS auditor. Use a Content-Security-Policy instead.

Why you paste headers instead of entering a URL

A browser-based tool can't just fetch another site's headers for you — the Same-Origin Policy blocks JavaScript running on this page from reading response headers from a different origin unless that server explicitly opts in with CORS, which most sites don't do for arbitrary third-party scripts. Getting the headers yourself with curl -sI https://example.com or DevTools' Network tab sidesteps that restriction entirely, and as a side benefit this also works for internal, staging or localhost sites that a public scanner could never reach.

Worked example: HTTP Security Headers Checker

Headers with a proper Strict-Transport-Security (max-age ≥ 15552000), a Content-Security-Policy free of unsafe-inline/unsafe-eval/wildcards, frame-ancestors or X-Frame-Options set, nosniff, a safe Referrer-Policy and a Permissions-Policy add up to the full 100 points and a grade of A. Drop in just "Server: Apache/2.4.1" and "X-Powered-By: PHP/8.1" with nothing else and every weighted check fails except the trivial ones — that scores 0 and grades F, with the information-leakage check specifically calling out the exposed version numbers, which matter because a published Apache or PHP version tells an attacker exactly which known vulnerabilities to try.

Which header to fix first

HSTS and CSP are weighted 25 points each because they address the two biggest categories of real-world attack: HSTS stops a user's first connection from being silently downgraded to plain HTTP where it can be intercepted, and CSP is the main defense against injected scripts (XSS) actually executing even if an attacker manages to get them onto the page. The other headers matter but are narrower in scope — clickjacking protection stops your site being framed invisibly, nosniff stops a browser from executing a file as a different MIME type than declared. If you can only fix two things, HSTS and CSP move the grade the most.

An empty box is not the same as a bad paste

Leave the box empty and you get no grade and no error. Paste text that has no header lines and the message says no headers were found, with an example of a strict-transport-security line. A real header is a name, a colon, and a value. Names are matched without caring about capitals, and a repeated name keeps the last value. The grade uses the score out of 100, shown beside the letter: A at 90 or above, B at 75, C at 60, D at 40, and F below that. The placeholder already includes a short HSTS line, a content-security-policy line, and nosniff, but nothing is graded until you paste and run it.

Related tools

More: Security & Privacy