Skip to content
CheckerGoogleRank Version française
  1. Home
  2. Technical and performance
  3. Security Headers Checker

Security Headers Checker

Check the five HTTP headers that protect your visitors — and get the lines to add.

Direct measurement of the HTTP response headers your server actually sends, with no intermediary and no cache. Assessment follows current OWASP recommendations, including the ones that changed — X-XSS-Protection is deliberately not required. No usage limit.

What this tool is for

Every response your server sends carries headers alongside the page itself. A handful of them instruct the browser to refuse certain attacks: do not run this, do not frame that, never come back over plain HTTP. They cost nothing, they are invisible to visitors, and most sites have none of them.

Their absence is rarely a decision. Hosting panels do not add them, content management systems do not add them, and nothing in a browser signals that they are missing. A site can run for a decade, perfectly functional, entirely unprotected on this front.

This tool reports what your server actually sends — not what a plugin claims to set — and gives the exact lines to add for anything missing. Start with the easy ones. Three of the five take under a minute and carry no risk of breaking anything.

How to read your results

Strict-Transport-Security forces HTTPS for a duration you choose. It also removes a redirect on every repeat visit, which is a genuine speed gain. The important caution is that it cannot be undone before it expires: begin with a short max-age and raise it once your certificate renewal is proven reliable.

X-Content-Type-Options: nosniff stops the browser guessing a file's type from its contents rather than trusting the declared type. It is the header to add first — a single line, no configuration, no way to break a working site.

X-Frame-Options prevents your pages being embedded in someone else's frame, which is how clickjacking works. SAMEORIGIN suits nearly everyone. Use DENY only if you never embed your own pages anywhere.

Referrer-Policy controls how much of the current URL is sent when a visitor follows a link away. strict-origin-when-cross-origin is the sensible default: full detail within your site, domain only to the outside — which stops query strings leaking to third parties.

Content-Security-Policy is the most powerful and the most demanding. It declares which sources may load scripts, styles and images, and blocks everything else. Deploy it in report-only mode first, live with the reports for a week, then enforce.

The most common mistakes

Setting a one-year HSTS on day one. The instruction is irrevocable for its duration. If the certificate lapses, every browser that saw the header refuses to connect at all — no warning to click through, no way to reach the site. Start at a day.

Enforcing a CSP without observing first. The policy will block something you forgot: an analytics script, an embedded font, a payment widget. In report-only mode you learn this from a report. In enforcing mode you learn it from customers.

Trusting a plugin's dashboard instead of the response. Plugins frequently set headers that a server-level configuration then overwrites, or that only apply to pages the plugin renders. Only the actual HTTP response settles the question, which is what this tool reads.

Adding X-XSS-Protection because an old article said so. Browsers removed the feature and it could create vulnerabilities of its own. Advice from 2016 is actively wrong here. Omit it.

Setting the headers only on the homepage. Attacks target whatever page they can reach, and often the least maintained one. Configure them at server level so every response carries them, including error pages and file downloads.

Related tools

Frequently asked questions

Do security headers affect SEO?

Not directly — no header is a ranking factor. The connection is indirect but real: HSTS removes a redirect hop on every visit, which improves load time, and a site compromised through an attack these headers would have blocked loses far more than a few positions. Treat them as insurance, not as optimisation.

Which header should I add first?

X-Content-Type-Options: nosniff. One line, no configuration, no possible side effect. Then Referrer-Policy, then X-Frame-Options. Leave Content-Security-Policy for last: it is by far the most effective and by far the easiest to get wrong.

Why is CSP so difficult?

Because it inventories everything your pages load — scripts, styles, fonts, images, frames — and blocks the rest. Any omission breaks something visible. Deploy it with Content-Security-Policy-Report-Only first: it reports violations without blocking, letting you find the gaps before users do.

What max-age should HSTS use?

Start low, around 86400 — one day. HSTS tells browsers to refuse plain HTTP for the duration you set, and that instruction cannot be recalled: if your certificate breaks, visitors are locked out for as long as the max-age you published. Raise it to a year once you are confident the certificate renews reliably.

Is X-XSS-Protection still useful?

No. Modern browsers removed the feature, and the header could itself introduce vulnerabilities in some configurations. It is now recommended to omit it, or set it to 0. A checker still demanding it is out of date.

Do these headers slow the site down?

No, in any measurable sense. They add a few hundred bytes per response. HSTS actually makes things faster by eliminating the HTTP-to-HTTPS redirect on repeat visits. Only a badly written CSP has real cost, and that cost is breakage rather than latency.