No headers analyzed yet
Paste headers in the left editor or load a sample configuration to generate a full security audit.
Paste raw HTTP response headers from DevTools, cURL, or Postman for an instant security, caching & cookie audit.
Paste headers in the left editor or load a sample configuration to generate a full security audit.
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.
curl -I https://example.com in your terminal.HTTP/2 200 OK) are automatically parsed.
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.
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.
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).
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.
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.
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.
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.
Yes. The entire tool is completely standalone, has zero external script or CDN dependencies, and does not require an active internet connection once loaded.