Security Headers Checker Tool Online
Last updated:
Scan any website's HTTP security headers. Check for HSTS, Content-Security-Policy, X-Frame-Options, Permissions-Policy, and more, with actionable recommendations for every finding.
Enter a website to scan its security headers:
Security findings like these are what we monitor daily.
SSL, headers, DNS, uptime, backups — our maintenance plans keep an eye on all of it so you never have to think about it. From $49/mo.
All good — today. Who’s watching tomorrow?
Sites drift: certificates expire, DNS changes, software ages. Our maintenance plans watch it all, from $49/mo.
How the Security Headers Checker Works
This tool inspects the HTTP response headers that a web server sends to browsers. Here's the process:
- Enter a URL, type or paste any website address. The tool sends an HTTP HEAD request to retrieve only the headers (no page content is downloaded).
- Header inspection, it checks for 10 critical security headers recommended by OWASP and major browser vendors.
- Evaluation, each header is evaluated: present or missing, properly configured or suboptimal, with specific recommendations for improvement.
- Summary, results show a pass/warn/fail breakdown with color-coded status for quick assessment.
Why Security Headers Matter
Security headers are your website's first line of defense. They cost nothing to implement and protect against the most common web attacks:
- XSS prevention, Content-Security-Policy controls which scripts can execute on your page. Without it, attackers can inject malicious JavaScript through comments, form fields, or compromised third-party resources.
- Clickjacking protection, X-Frame-Options and CSP frame-ancestors prevent your site from being embedded in a hidden iframe on an attacker's page, where users might unknowingly click on your site's buttons.
- HTTPS enforcement, HSTS ensures browsers always use HTTPS, eliminating the window of vulnerability during the first HTTP request. This protects against man-in-the-middle attacks on public Wi-Fi.
- Data leak prevention, Referrer-Policy controls what URL information is sent to third-party sites. Without it, sensitive query parameters can leak to external services.
- Browser feature control, Permissions-Policy lets you disable browser features (camera, mic, geolocation) that your site doesn't need, reducing your attack surface.
Combine this with the SSL Certificate Checker for a complete security profile, the Redirect Checker to verify HTTPS redirects are properly configured, and the Email Deliverability Checker to verify SPF/DKIM/DMARC for your domain, email security and web security go hand in hand. Also run the PHP Version Checker to ensure your server isn't running an end-of-life PHP version, which is a common source of security vulnerabilities.
Essential Security Headers to Implement
If you're starting from scratch, prioritize these headers in order:
- Strict-Transport-Security,
max-age=31536000; includeSubDomains, enforces HTTPS for 1 year across all subdomains. - Content-Security-Policy, start with
default-src 'self'and add sources as needed. This single header addresses the widest range of attack vectors. - X-Content-Type-Options,
nosniff, one word, zero risk, prevents MIME sniffing attacks. - X-Frame-Options,
DENYorSAMEORIGIN, prevents clickjacking. Takes 30 seconds to add. - Referrer-Policy,
strict-origin-when-cross-origin, sensible default that shares origin but not path to third parties. - Permissions-Policy, disable features you don't use:
camera=(), microphone=(), geolocation=()
For a broader website audit, check your meta tags, schema markup, and broken links alongside security headers for a complete health check.
Key HTTP Security Headers and Recommended Values
Use this reference to understand what each core security header does and a sensible value to start with. Adjust the exact directives to fit your site, but these defaults are a safe, widely recommended baseline.
| Header | Purpose | Recommended value |
|---|---|---|
| Strict-Transport-Security | Forces browsers to connect over HTTPS only, eliminating the insecure first request. | max-age=31536000; includeSubDomains |
| Content-Security-Policy | Restricts which scripts, styles, and other resources can load, the strongest defense against XSS. | default-src 'self' (then add trusted sources as needed) |
| X-Content-Type-Options | Stops browsers from MIME-sniffing a response away from its declared content type. | nosniff |
| X-Frame-Options | Prevents your pages from being embedded in iframes, defending against clickjacking. | SAMEORIGIN (or DENY) |
| Referrer-Policy | Controls how much referrer information is sent to other sites, limiting data leakage. | strict-origin-when-cross-origin |
| Permissions-Policy | Disables powerful browser features (camera, mic, geolocation) your site doesn't use. | camera=(), microphone=(), geolocation=() |
Next steps
Security Headers Checker related tools and articles
Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.
Security Headers: FAQ
What are HTTP security headers?
What does this security headers checker test?
What is Content-Security-Policy (CSP)?
What is HSTS and why is it important?
Do security headers affect SEO?
What is the difference between pass, warning, and fail?
Which headers are most important to fix first?
How do I add security headers to my website?
Is this security headers checker free?
Why does a site I trust still fail some header checks?
Does this tool store the sites I check?
Free 48-Hour Website Audit
Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.
Need Help Securing Your Website?
We help businesses implement security headers, SSL, and web security best practices.