FreeAudit / Guides / Security headers checker
Security headers checker
Security headers are short instructions your server sends with each page. They tell the browser to stay on HTTPS, not to run your page inside another site, and not to guess file types. FreeAudit reads them from outside, marks each one pass or fail, and gives the fix. It is free and needs no login.
The headers FreeAudit looks at
| Header | What it does |
|---|---|
| Strict-Transport-Security (HSTS) | Tells browsers to use HTTPS only. FreeAudit wants a memory time of at least 31,536,000 seconds (one year) |
| Content-Security-Policy | Limits where scripts and images can load from. FreeAudit treats it as advice, not a fail |
| X-Frame-Options | Stops other sites from showing your page in a frame |
| X-Content-Type-Options | Set to nosniff, so the browser trusts the file type you send |
| Referrer-Policy | Controls how much of your address is shared when someone clicks a link |
More than headers
The same security part also checks that plain http:// goes to https://, the CAA record, DNSSEC, OCSP stapling and a security.txt file.
Adding a header
You can add headers at your server or in Cloudflare. In Cloudflare they go under Rules, then Transform Rules, then Modify Response Header. The Cloudflare setup guide explains the rest of the setup.
FAQ
What is the most important security header?
HSTS is a good first one. It keeps visitors on HTTPS after the first visit.
Can a wrong CSP break my site?
Yes. A strict policy can block your own scripts. Test it before you switch it on.
Does a good score mean my site is safe?
No. Headers close some doors. They do not fix weak passwords or old software.