Free tool

Free security headers checker — test any website instantly

Check which HTTP security headers your website is sending and get copy-paste fixes for each one. No account required.

We check the headers your server sends — no malware scanning, no active probing. Instant. Free.

Want to go deeper? Scantinel’s Full scan runs an active OWASP Top 10 vulnerability test, port scan, and CDN origin check against your verified domain — not just headers. See pricing

What are HTTP security headers?

HTTP security headers are configuration instructions your web server sends to browsers along with every page response. Missing or misconfigured headers are one of the most common and easiest-to-fix security issues found in web audits.

Content-Security-Policy

Restricts which sources can load scripts, styles, and resources. Prevents XSS attacks.

Strict-Transport-Security

Tells browsers to always use HTTPS, preventing SSL-stripping attacks.

X-Frame-Options

Prevents your pages from being embedded in iframes on other domains (clickjacking protection).

X-Content-Type-Options

Prevents browsers from MIME-type sniffing, reducing drive-by-download risk.

Referrer-Policy

Controls how much referrer information is sent with cross-origin requests.

Permissions-Policy

Restricts browser feature access (camera, microphone, geolocation) for your page.

Cross-Origin-Opener-Policy

Prevents cross-origin documents from gaining references to your window.

Cross-Origin-Resource-Policy

Restricts which origins can load your resources, preventing Spectre-style attacks.

Read our security blog  |  Check your SPF and DMARC records

Frequently asked questions

Is this tool free?
Yes, completely free. No account required. You can check any domain you own (or any public domain, for reference) and see the results immediately.
What's the difference between this and a full Scantinel scan?
This tool checks HTTP response headers only — one layer of your website's security posture. A Full scan checks headers plus TLS/SSL, DNS, email authentication, exposed files, port-level services, and the full OWASP Top 10 active vulnerability suite.
My CSP header says 'unsafe-inline' — is that bad?
Yes, unsafe-inline in your Content-Security-Policy significantly weakens its protection against XSS attacks. The recommended fix is to remove unsafe-inline and use nonces or hashes for any legitimate inline scripts.
Can I share my results?
Yes. After your check runs, the URL updates to include your domain as a query parameter (e.g., /tools/security-headers-checker?domain=example.com). You can share that URL and anyone opening it will see the same results.