Security Headers Checker
Grade a site's HTTP security headers and get the exact line to add for each one that's missing.
How to use it
- Paste your site's address.
- See which of the six key security headers are set, and your grade.
- Add the missing ones in your host's settings (Cloudflare, Netlify, Vercel, nginx or your framework).
The six headers we check
- Strict-Transport-Security (HSTS): makes browsers always use HTTPS.
- Content-Security-Policy: controls where scripts can load from, the main defence against cross-site scripting.
- X-Content-Type-Options: stops browsers guessing file types.
- X-Frame-Options (or CSP
frame-ancestors): stops other sites framing your pages to trick clicks. - Referrer-Policy: limits what your URLs reveal to other sites.
- Permissions-Policy: switches off browser features you don't use.
Where to add them
On Netlify and Cloudflare Pages, add a _headers file. On Vercel, use headers in vercel.json. On nginx, use add_header. Start with a looser Content-Security-Policy and tighten it later, because a strict one can block your own scripts if you don't test it.
Frequently asked questions
Do security headers affect SEO?
Not directly. HTTPS is a ranking signal, and a hacked site loses rankings fast, so headers protect your SEO indirectly. Visitors and partners also check them.
Which header should I add first?
Strict-Transport-Security, X-Content-Type-Options and Referrer-Policy are safe one-line additions. Content-Security-Policy needs testing, so add it last.
Why does it say my server version is visible?
Headers like "Server: nginx/1.18.0" tell attackers exactly which software to look up. Most servers can hide the version number.
More free tools
Related guides
Check everything at once
RankHoot runs 60+ SEO, AI search, speed and security checks on your page and gives you copy-paste fixes.
Scan my site free