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:

How the Security Headers Checker Works

This tool inspects the HTTP response headers that a web server sends to browsers. Here's the process:

  1. 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).
  2. Header inspection, it checks for 10 critical security headers recommended by OWASP and major browser vendors.
  3. Evaluation, each header is evaluated: present or missing, properly configured or suboptimal, with specific recommendations for improvement.
  4. 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, DENY or SAMEORIGIN, 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

How is the pass, warning, and fail summary calculated?
The server sends a HEAD request and evaluates 10 named response headers. HSTS, CSP, and X-Content-Type-Options can produce failures under the built-in rules. Optional or context-dependent headers usually produce warnings when absent, while X-XSS-Protection is treated as acceptable when absent because modern browsers deprecated it.
Does a pass mean the header policy is secure?
No. Most checks confirm presence, not complete correctness. For example, CSP passes unless it contains both unsafe-inline and unsafe-eval, and X-Frame-Options passes when any value is present. Review the actual value and test the site's behavior with security tooling before treating the policy as complete.
How should I interpret the HSTS result?
Missing HSTS fails. A max-age below 31,536,000 seconds warns. Only deploy HSTS on HTTPS after confirming every affected host works securely, especially before adding includeSubDomains or preload, because a bad rollout can make sites unreachable in supporting browsers.
What should I do with a missing or weak CSP?
Start by inventorying every script, style, image, font, frame, and connection the site needs. Test a restrictive policy in report-only mode, review violations, then enforce it with nonces or hashes where practical. Copying a generic CSP directly into production can break legitimate functionality.
Why does missing X-XSS-Protection still pass?
X-XSS-Protection is a legacy browser filter that modern browsers ignore or retired. The checker considers an absent header or a value of 0 acceptable. A well-designed Content-Security-Policy is the modern control for script-injection risk.
Should I add COOP, CORP, and COEP immediately?
Not blindly. These cross-origin policies can block popups, embeds, fonts, images, payment flows, analytics, and other third-party resources unless those resources opt in correctly. Add them according to the application's isolation needs and test every critical integration.
Why can this result differ from a browser or another scanner?
The tool inspects the final response to a server-side HEAD request with a WebAlohaBot user agent and a ten-second timeout. Some servers omit headers on HEAD, vary policies by route, cookie, geography, CDN edge, or user agent, or block automated requests. Confirm important findings with a normal GET and browser developer tools.
Are the URL and returned headers stored?
The URL is sent to the Web Aloha server for the HEAD request. This endpoint has no cache or database write and does not persist the checked URL or response headers after returning the report.

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.