Toolsky

Free Online Tools & Utilities for Every Task.

Security Headers Auditor

Audit the security headers of any website for better SEO and protection.

How it works?

Security headers are HTTP response headers that a website's server sends to the browser. These headers tell the browser how to behave when handling the content of your site.

A high security score indicates that your website has implemented modern defensive measures against common attacks like Cross-Site Scripting (XSS) and Clickjacking, which improves both user safety and search engine trust.

Your site can have perfect passwords, patched plugins and an encrypted connection, and still leave its visitors exposed — because a separate layer of protection lives in HTTP response headers, the short instructions your server sends with every page that tell browsers what they may and may not do with your content. Most sites send few or none of them, simply because nobody ever checked. This security headers auditor does the checking: give it a website address and it inspects the headers the site actually returns, grading what is present, what is missing, and what each gap means for the people browsing.

What Security Headers Do Behind the Scenes

Headers are the browser's rulebook for your pages, and a handful do most of the protective work. Strict-Transport-Security (HSTS) orders browsers to only ever use HTTPS for your domain, closing the door on downgrade attacks. Content-Security-Policy (CSP) whitelists where scripts, styles and images may load from — the single strongest defence against cross-site scripting, because injected scripts from unlisted sources simply refuse to run. X-Frame-Options (and CSP's frame-ancestors) decide whether other sites may embed yours in a frame, which is the whole mechanism of clickjacking. X-Content-Type-Options: nosniff stops browsers guessing file types, preventing a uploaded image from being executed as script. Referrer-Policy controls how much of your URLs leak to other sites through referrer data, and Permissions-Policy switches off browser features — camera, microphone, geolocation — that your pages never use, so a compromised script cannot use them either. MDN's HTTP headers reference documents each one in full.

What the Auditor Checks

  • Presence of the core headers — HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, checked on the site's real responses.
  • Value sanity, not just existence — a CSP of * or an HSTS with a trivially short max-age technically "exists" while protecting almost nothing; the audit looks at what the values actually enforce.
  • Information-leaking headers — server banners advertising exact software versions, which hand attackers a shopping list of known vulnerabilities to try.
  • A readable verdict per item — what is missing, why it matters in plain language, and how urgent the fix is, so the report works for site owners and not only for security engineers.
  • A companion to the rest of the hardening toolkit — generate a policy with the CSP Header Generator, inspect raw responses yourself in the HTTP Headers Parser, and confirm the HTTPS layer underneath with the SSL Checker.

How to Audit a Site's Headers

  1. Enter the full address of the site, using the version visitors actually see — https, and with or without www exactly as the live site resolves.
  2. Run the audit and wait for the response collected from the site.
  3. Read the findings top-down: missing HSTS or clickjacking protection usually outranks cosmetic items.
  4. Note the current values of any headers that are present but weak — you will need them to recognise the change later.
  5. Apply fixes at the right layer: server configuration, CDN settings, or your platform's security settings — not inside page HTML.
  6. Re-run the audit after each change to confirm the new headers are being served, and test your site thoroughly after adding a CSP in particular.

Reading a Real Audit Result

Picture a small business site that scores poorly. The audit shows HTTPS works, but there is no HSTS, so a visitor's first-ever request could still be intercepted and downgraded. There is no X-Frame-Options and no frame-ancestors rule, meaning any site on the internet can embed this shop's pages inside its own and overlay fake buttons — textbook clickjacking exposure. X-Content-Type-Options is absent, and the Server header cheerfully reports an exact version number of outdated software. None of these gaps required an attacker to "hack" anything; they are configuration defaults the owner never saw. The fixes, in this case, were four lines of server configuration, verified by re-running the audit the same afternoon — which is the normal pattern: headers are the cheapest security improvements a website can make.

Header Fixes That Break Sites (and Other Traps)

Enthusiasm has one famous casualty: the Content-Security-Policy. A strict CSP switched on without testing will block your own analytics, fonts, chat widget and payment scripts, because to the browser they look exactly like the injected scripts the policy exists to stop. Roll CSP out in report-only mode first, watch what it would have blocked, whitelist your real services, then enforce. Second trap: setting headers in the wrong place — rules added to a staging config or a single page do nothing for the rest of the site. Third: treating a good header score as complete security. Headers restrain browsers; they do not patch your application, and an unpatched plugin behind a perfect CSP is still an unpatched plugin. Finally, re-audit after migrations and CDN changes, because headers configured on an old server routinely vanish in a move.

Frequently Asked Questions About the Security Headers Auditor

Do security headers affect SEO?

Indirectly at most. HTTPS itself is a known ranking signal, and headers protect the visitors you already win — but no header is a ranking shortcut. Their real value is protection and trust, not positions.

Which single header should I add first?

If you serve HTTPS, HSTS is the quick, low-risk win. CSP is more powerful but needs careful rollout; clickjacking protection via X-Frame-Options or frame-ancestors is another safe early fix.

Where do I set these headers?

In your web server configuration (Apache .htaccess or httpd config, Nginx server blocks), in your CDN's settings, or through your hosting platform's security panel — never in individual page files.

Can headers make my site slower?

Negligibly. Headers are a few hundred bytes of text per response. A CSP can even speed a site up slightly by blocking junk third-party requests you never authorised.

Why does my report show headers I never set?

Your host, CDN or CMS adds some by default. That is normal — the audit reports what browsers receive, whoever configured it, which is the only view that matters.

How often should I audit?

After any server move, CDN change, or platform update, and on a routine schedule a few times a year. Header configuration is exactly the kind of thing that silently disappears in a migration.

Does a perfect score mean my site cannot be hacked?

No. Headers govern how browsers treat your pages; they do not fix vulnerable code, weak passwords or outdated software. They are one strong layer of a defence that needs the others too.

Small Headers, Serious Protection

No visitor will ever praise your Referrer-Policy, and that is the point: headers work invisibly, on every request, for every visitor. One audit shows you which of those silent instructions your site is failing to give — and most fixes take minutes once you know they are missing.