Security headers check: CSP, HSTS and friends
Security headers are instructions your server sends to the browser to switch on built-in protections. A missing one rarely causes a breach on its own, but it removes a safety net. ScanAnt reads your response headers and tells you which ones are absent, weak or too permissive.
Free, no signup. We only read what your site already shows every visitor.
What we check
Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.
Strict-Transport-Security (HSTS)
Quick scanTells browsers to use HTTPS only for your domain, so a downgrade to plain http cannot succeed.
Content-Security-Policy
Quick scanReports a missing policy, and a weak one that still allows inline and eval scripts, which makes it much less useful against XSS.
Clickjacking protection
Quick scanWhether other sites can embed yours in a frame, through X-Frame-Options or the frame-ancestors directive.
X-Content-Type-Options
Quick scanThe nosniff value stops browsers from guessing a file type and running an upload as a script.
Referrer-Policy
Quick scanWhether full page addresses, which may hold tokens or ids, leak to other sites in the Referer header.
Cookie flags
Quick scanSecure, HttpOnly and SameSite on the login cookie. They are set in headers too, so we check them here.
Permissions-Policy and COOP
Deep scanWhether camera, microphone and cross-window isolation are restricted. These extras are part of the deep scan.
Version disclosure
Deep scanServer and framework versions announced in headers such as Server or X-Powered-By, which help attackers pick exploits.
- Quick scan: No signup. Reads only what every visitor receives.
- Deep scan: After you prove ownership and tick the deep option.
No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.
Common mistakes
A CSP that allows unsafe-inline and unsafe-eval
It looks like protection but permits the injected scripts it should block.
HSTS only on the home page or with a tiny max-age
Browsers forget the rule quickly and the first visit stays exposed.
Setting headers in the app but not on static files
Responses served directly by nginx or a CDN skip your application middleware.
Copying a CSP from a blog without testing it
A strict policy can break your own scripts, so teams switch it off and never come back.
How to fix it
Add the headers at the edge (nginx, your CDN or hosting config) so they cover every response, not only app routes.
Start with Strict-Transport-Security: max-age=31536000 and X-Content-Type-Options: nosniff, which rarely break anything.
Roll out Content-Security-Policy in report-only mode first, remove inline scripts, then enforce it.
Use frame-ancestors 'none' (or 'self') for clickjacking and a Referrer-Policy such as strict-origin-when-cross-origin.
Rescan to confirm each header arrives on the final, redirected page.
Questions
Do I need all of these headers?
HSTS, nosniff, a framing rule and a Referrer-Policy are cheap and safe for most sites. CSP gives the most protection but takes the most care. Pick by effort and risk, and start from the first four.
Why does my header show as missing when I set it?
Often it is set on one route, one subdomain or only the http:// address. We read the final page after redirects, so check the response that real visitors actually receive.
Do headers make a site secure by themselves?
No. They reduce the damage when another bug exists. They do not fix XSS, broken access control or leaked keys.
Is a header check passive?
Yes. The main headers are read from one normal page load, so no signup or ownership proof is needed. Permissions-Policy, COOP and version disclosure are part of the deep scan.
Related checks
Check your website security for free
A free first look at any site: HTTPS, headers, cookies and leaked keys.
Open →Next.js security scanner for production apps
NEXT_PUBLIC secrets, middleware bypass, source maps and unprotected routes.
Open →Laravel security scanner: debug leaks and exposed files
Public .env, APP_DEBUG, Debugbar, Horizon and log files on Laravel sites.
Open →
Run the scan now
Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.
Choose a scan level →