Skip to main content
ToolSmartly

Security Header Checker: Audit Your Website Security

Website security starts with rigorous HTTP header configuration, yet identifying misconfigurations can be a complex challenge. Our HTTP security headers analyzer instantly inspects your domain to evaluate the protection provided by CSP, HSTS, and other essential security policies. Completely free and 100% client-side, this tool provides a detailed security score and actionable recommendations without any data being transferred or stored, helping you strengthen your site against modern threats with total privacy.

Examples: toolsmartly.com github.com mozilla.org cloudflare.com
The scan uses a public CORS proxy to bypass browser restrictions. Only public HTTP headers are read — no page content is sent.
Load example: ✅ Secure config ❌ Insecure config ⚠️ Partial config
↵ Enter to analyze
Enter a URL or paste your headers to get the security analysis.

Scan history

No scans yet.

Why are HTTP security headers important?

HTTP security headers are directives sent by the web server in the HTTP response, instructing the browser on how to handle page content. A misconfigured or absent header leaves the door open to XSS, clickjacking, content injection, MITM and session theft attacks. Their correct configuration is one of the first recommendations in the OWASP guide.

The most critical headers

Content-Security-Policy (CSP) is the most powerful header: it defines allowed sources for scripts, styles, images and iframes, effectively blocking XSS attacks. Strict-Transport-Security (HSTS) enforces HTTPS connections for a defined period, protecting against MITM attacks on HTTP connections.

Security grade A+ → F

Our analyzer assigns a score out of 100 based on the presence and configuration quality of 12 headers. Critical headers (CSP, HSTS) count more than secondary headers. An A+ grade means all required headers are present and correctly configured according to OWASP and Mozilla Observatory recommendations.

Analysing and fixing your security headers

Two modes: enter a site’s URL, or paste headers copied from your browser’s developer tools (Network tab). To read another site’s headers, URL mode goes through the public corsproxy.io service, which browser restrictions make necessary: the requested address is sent to it, and results depend on its availability. Paste mode runs entirely in your browser.

How to use it

  1. Enter the full URL (https://…) or paste the response headers.
  2. Read the overall grade (A+ to F), then the detail for each header: present, missing or misconfigured, with the recommendation.
  3. Fix your server configuration, then run the analysis again.

A solid baseline to adapt

Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Security-Policy: default-src 'self'; frame-ancestors 'self'
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()

The CSP is the trickiest: list every domain you really use (analytics, ads, fonts), or the site will break. Start with the Content-Security-Policy-Report-Only header, which reports what would be blocked without blocking it. X-XSS-Protection is obsolete: modern browsers ignore it, and CSP replaces it.

Where to set them

  • Apache: Header always set X-Content-Type-Options "nosniff" in .htaccess or the site configuration.
  • Nginx: add_header X-Content-Type-Options "nosniff" always;
  • Cloudflare Pages, Netlify: a _headers file at the site root.
  • WordPress or a hosted CMS: depending on the host, a security plugin or the admin panel.

Frequently asked questions

Why does a URL scan sometimes fail?

The site may block requests coming from the proxy, or the proxy may be briefly unavailable. Copy the headers from your browser’s Network tab instead (click the first request, “Response headers” section) and use paste mode.

Is an A+ grade enough to be secure?

No. Headers are one layer of defence among others: they limit the impact of some attacks but do not fix vulnerable code, outdated plugins or weak passwords.