What this tool checks
It runs the 10 HTTPS and header tests from our free scan, the same code with the same rules:
- #19 HTTP redirects to HTTPS Free
- #20 SSL certificate valid Free
- #21 Certificate expires in more than 14 days Free
- #22 HSTS header Free
- #23 Content-Security-Policy present Free
- #24 Clickjacking protection Free
- #25 X-Content-Type-Options Free
- #26 Referrer-Policy Free
- #27 No mixed content Free
- #28 Server version hidden Free
The full free scan runs these plus leaked keys, exposed files, CORS, error pages, redirects and malware: 46 tests in all. Pro adds cookie flags, older TLS versions, a weak CSP and more.
Why these headers matter
Security headers are instructions your server sends with every page. They cost nothing to add and they close whole classes of attack in the visitor's browser. The OWASP HTTP Headers Cheat Sheet is the reference we follow.
HTTPS, the certificate and HSTS
Every page should load over HTTPS, plain HTTP should redirect to it, and the certificate must be valid and not about to expire. Strict-Transport-Security (HSTS) then tells browsers to use HTTPS for your site from now on, so a visitor on a hostile Wi-Fi network can't be quietly kept on plain HTTP. OWASP warns to read how HSTS works before setting a long lifetime: once browsers remember it, they won't load your site without valid HTTPS.
Content-Security-Policy
A Content-Security-Policy lists where scripts, styles and frames may come from. If an attacker manages to inject a script, a good policy stops the browser from running it. It's the most powerful header here and the one that takes the most care.
Clickjacking protection
Without frame-ancestors in your CSP (or the older X-Frame-Options header), another site can load yours in an invisible frame and trick people into clicking your buttons.
The smaller ones
X-Content-Type-Options: nosniff stops browsers guessing file types. A Referrer-Policy controls how much of your URLs other sites see. Mixed content (HTTP files on an HTTPS page) weakens the page. And a Server or X-Powered-By header with a version number tells attackers exactly what to look up.
How to fix what it finds
Most headers are set in one place: your host's configuration (for example a headers file or your framework's config), or a proxy in front of your site. Change it once and every page gets the header. Then run the check again to confirm.
Each run uses one of your 2 free scans for the day. To see everything at once, run the full free scan.
Questions
Is this the same as the full free scan?
No. It runs only the HTTPS and header tests. The full free scan runs all 46 free tests and uses the same daily allowance.
Why does a header I set not show up?
Often a proxy, CDN or the host's own settings replace or drop headers. We check the response your visitors actually get, so test the address they use.
Does the checker change anything on my site?
No. It loads your page the way a browser does, plus a request over plain HTTP to check the redirect and one TLS handshake for the certificate.