Our Apps FAQ Blog
Security Tool

HTTP Security Headers Analyzer

Paste raw HTTP response headers from DevTools, cURL, or Postman for an instant security, caching & cookie audit.

Runs in your browser. Nothing is uploaded.
Response headers 0 lines · 0 chars
Drop text or log file here
Security Report Heuristic Analysis

No headers analyzed yet

Paste headers in the left editor or load a sample configuration to generate a full security audit.

Why HTTP Response Headers Matter for Modern Web Security

HTTP security response headers are the first line of defense in modern browser-based security. When a web client loads an application, the server's HTTP response headers define critical security boundaries. They govern whether external scripts can execute, restrict framing inside malicious IFrames, enforce encrypted HTTPS transport, and protect sensitive authentication tokens stored in cookies.

How to Use the Security Headers Checker

  1. Capture Your Headers: Open your browser's Developer Tools (F12) > Network tab, select any document request, and click "Copy response headers". Alternatively, run curl -I https://example.com in your terminal.
  2. Paste into the Workspace: Paste the text into the left pane. Leading HTTP status lines (such as HTTP/2 200 OK) are automatically parsed.
  3. Review Audit Findings: The right pane renders an overall security score and categorized findings for CSP, HSTS, Cookies, CORS, Caching, and Info Leaks.
  4. Deploy Immediate Fixes: Click the server tabs (Nginx, Apache, Express/Helmet, Cloudflare) next to any warning or missing header to copy ready-to-paste configuration directives.

Sample Audit Comparison

# Vulnerable / Default Header Configuration: HTTP/1.1 200 OK Server: Apache/2.4.41 (Ubuntu) X-Powered-By: PHP/7.4.3 Set-Cookie: sessionid=xyz123; path=/ # Hardened Defense-in-Depth Configuration: HTTP/2 200 OK Strict-Transport-Security: max-age=31536000; includeSubDomains; preload Content-Security-Policy: default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; X-Content-Type-Options: nosniff Referrer-Policy: strict-origin-when-cross-origin Permissions-Policy: camera=(), microphone=(), geolocation=() Set-Cookie: sessionid=xyz123; Secure; HttpOnly; SameSite=Lax; Path=/

Detailed Security Explanation

Content Security Policy (CSP)

A Content Security Policy restricts the resources (such as JavaScript, CSS, Images, and Fonts) that the browser is allowed to load. By forbidding 'unsafe-inline' and 'unsafe-eval', a robust CSP neutralizes the vast majority of Cross-Site Scripting (XSS) attack vectors.

HTTP Strict Transport Security (HSTS)

HSTS informs browsers that the domain must only be accessed over HTTPS. This eliminates man-in-the-middle SSL-stripping attacks by preventing insecure HTTP fallbacks. Best practice dictates a max-age of at least one year (31,536,000 seconds), accompanied by includeSubDomains and the preload directive.

Secure Cookies and SameSite

Cookies containing session tokens or authentication credentials must always include the HttpOnly attribute (preventing client-side JavaScript theft via XSS) and the Secure attribute (preventing cleartext transit over unencrypted channels). The SameSite attribute defends against Cross-Site Request Forgery (CSRF).

Frequently Asked Questions

What are security headers?

Security headers are specialized HTTP response parameters sent by a server to a client web browser. They activate built-in browser security mechanisms that guard against Cross-Site Scripting (XSS), clickjacking, drive-by downloads, protocol downgrade attacks, and unauthorized cross-domain data leakage.

What should my CSP be?

A sensible starter policy is: default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none';. Applications requiring third-party analytics or CDNs can add specific trusted hostnames, or implement cryptographic nonces ('nonce-...') for inline script validation.

Does this scan my website?

No. Many online header checkers perform an outbound network fetch to your website, which fails on internal dev environments, staging servers, or password-protected intranets. This tool runs 100% locally in your browser: you paste the text, and JavaScript analyzes it offline.

What does SameSite do?

The SameSite cookie attribute specifies whether cookies are attached to cross-origin requests. Setting SameSite=Lax prevents the browser from sending cookies on third-party cross-site POST requests, protecting against CSRF attacks while maintaining a seamless user experience on top-level incoming links.

Can I run this offline?

Yes. The entire tool is completely standalone, has zero external script or CDN dependencies, and does not require an active internet connection once loaded.