What the result means
The tool reads the headers of the final response (after any redirects) and checks six common protections. Each one is marked Good, Review (present but weak), or Missing. There is deliberately no letter grade or score: a header count says little about how secure a site really is.
| Header | What it does |
|---|---|
| Strict-Transport-Security | Tells browsers to use HTTPS only. We flag a max-age under 180 days. |
| Content-Security-Policy | Limits where scripts and other resources can load from. We flag unsafe-inline and unsafe-eval. |
| X-Content-Type-Options | nosniff stops browsers from guessing file types. |
| Referrer-Policy | Controls how much of the URL is shared with other sites. |
| Permissions-Policy | Restricts browser features such as camera or geolocation. |
| X-Frame-Options or frame-ancestors | Controls whether other sites can embed the page in a frame. |
Example
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
These three would be marked Good. The tool also lists headers such as X-Powered-By that reveal the software in use.
Limits
- This is a quick look at six headers, not a security audit. A missing header is not automatically a vulnerability, and a full set does not make a site safe.
- Only the final response is analysed. Different pages or paths can send different headers.
- A Content-Security-Policy is judged only for unsafe-inline and unsafe-eval. Its overall strength needs a manual review.
- Only http and https on ports 80 and 443 are supported, and private addresses are blocked.
FAQ
Which header should I add first?
Start with HTTPS and Strict-Transport-Security, then X-Content-Type-Options and Referrer-Policy, which are low risk. Add Content-Security-Policy gradually, because a strict policy can break pages.
Why is there no score?
A single grade hides context. Knowing which protection is missing is more useful than a letter.
Can I run this on any website?
Only on sites you are allowed to test, for your own checks. We only read public response headers.