# Security headers checker

Check the HTTP response headers that protect visitors and signal a maintained site: Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, frame protection and HSTS.

Run it at https://crawlwise.dev/tools/security-headers-checker: paste a public URL, no account needed. The scan runs the full CrawlWise audit and returns a private report.

## What this checker tests

- Security headers are present (`trust.headers`)
- HTTPS, HSTS and redirects are correct (`trust.https`)

## What the report shows

- whether the page sends `Content-Security-Policy`, or only `Content-Security-Policy-Report-Only`;
- `X-Content-Type-Options: nosniff`;
- a `Referrer-Policy`;
- frame protection through `X-Frame-Options` or `frame-ancestors` in the CSP;
- HTTPS on the final URL, `Strict-Transport-Security` with its `max-age`, and any scripts,
  styles, images or frames the page loads over plain HTTP.

Headers are read from the response of the final URL, after redirects.

## Common mistakes

- **Headers on the HTML but not on the final URL**, for example when a CDN or redirect layer
  answers first and strips them.
- **A report-only CSP that was never switched on.**
- **`X-Frame-Options: ALLOW-FROM`**, which current browsers ignore. Use `frame-ancestors`.
- **HSTS with a short `max-age`** set during testing and never raised.

## Fix it

Set the headers once, in the web server, CDN or framework, so every response carries them:

```http
Content-Security-Policy: default-src 'self'; frame-ancestors 'none'
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
Strict-Transport-Security: max-age=31536000
```

Start from a strict policy and loosen it for the sources your page needs. The
[redirect checker](/tools/redirect-checker) checks that the HTTPS chain in front of the page is
short and permanent.

## FAQ

### Which security headers does CrawlWise check?

Content-Security-Policy, X-Content-Type-Options: nosniff, Referrer-Policy, and frame protection through X-Frame-Options or a CSP frame-ancestors directive. All four pass, two or three warn and fewer fail. HSTS is checked with HTTPS.

### Is a report-only CSP enough?

No. Content-Security-Policy-Report-Only only reports violations, it does not block them. It counts as present, but a page whose only policy is report-only warns until the policy is enforced.

### Do security headers affect SEO or AI search?

Not directly; no search engine has said it ranks pages by them. They protect visitors from script injection and clickjacking, and they are a cheap sign of a maintained site for anyone who evaluates it.

### Does the check grade the CSP itself?

No. It checks that a policy is present and enforced, not how strict it is. A policy with unsafe-inline or wildcard sources passes here; review it with your framework's CSP guidance.

## Related guides

- [Is your site agent-ready? A practical checklist](https://crawlwise.dev/guides/agent-ready-website-checklist.md)

---

Last updated 19 November 2026.

HTML version: <https://crawlwise.dev/tools/security-headers-checker>

Every CrawlWise page in Markdown: <https://crawlwise.dev/llms.txt>
