HTTP Header Checker
Enter any URL to inspect its HTTP response headers. Check security headers, caching configuration, CORS policy, and server information.
Why security headers matter
HTTP security headers are your first line of defense against common web attacks. They instruct the browser to enforce security policies before any page content loads. Without them, your site is vulnerable to cross-site scripting (XSS), clickjacking, protocol downgrade attacks, and MIME type confusion.
OWASP lists missing security headers as a common misconfiguration in their Top 10. The fix takes minutes: add a few lines to your web server or CDN configuration. The protection lasts as long as the headers are present.
The most impactful headers to add, in order of priority: Strict-Transport-Security (prevents HTTP downgrade), Content-Security-Policy (prevents XSS), X-Frame-Options (prevents clickjacking), X-Content-Type-Options (prevents MIME sniffing), and Referrer-Policy (controls information leakage).
Caching headers explained
Cache-Control is the primary caching header. It tells browsers and CDNs how long to store a response before requesting a fresh copy. Common values: max-age=3600 (cache for 1 hour), no-cache (revalidate on every request), no-store (never cache).
ETag and Last-Modified enable conditional requests. The browser sends the stored ETag or date back to the server, and the server responds with 304 Not Modified if the content hasn't changed. This saves bandwidth without sacrificing freshness.