Free Tool

HTTP Header Checker

Inspect response headers from any website. Check security headers, caching policies, and server configuration instantly.

Privacy-First Analytics

Recommended Tool

Affiliate

Stop sacrificing visitor privacy for data. Fathom Analytics is a simple, privacy-focused alternative to Google Analytics. It's GDPR compliant and doesn't require those annoying cookie banners. Get clean data while respecting your users.

No cookie banners required
GDPR, CCPA, and PECR compliant
Bypass ad-blockers for accurate data

Disclosure: We may earn a commission if you sign up through our link, at no extra cost to you. Sign up via our link and you'll also get $10 credit towards your first invoice. We only recommend tools we genuinely believe in.

Why HTTP Headers Matter

HTTP response headers are instructions your server sends to every browser and crawler that requests a page. They control caching behavior, enforce security policies, dictate content types, and influence how search engines process your responses. Misconfigured headers can expose your site to XSS attacks, prevent efficient caching, or leak server version information to attackers. Inspecting headers regularly is a fundamental part of web security and performance hygiene.

Security Headers Overview

Security headers are your first line of defense against common web attacks. They instruct browsers to enforce protections like blocking cross-site scripting, preventing clickjacking, and restricting which external resources can load. Major security headers include Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, and X-Frame-Options. Sites missing these headers are significantly more vulnerable to injection attacks and data theft.

Common Security Headers

  • Content-Security-Policy (CSP) — Controls which scripts, styles, images, and other resources a browser is allowed to load. A strong CSP prevents most XSS attacks by blocking inline scripts and unauthorized external sources.
  • Strict-Transport-Security (HSTS) — Forces browsers to use HTTPS for all future requests to your domain. Once set, even if a user types http://, the browser upgrades to HTTPS before making the request, preventing SSL-stripping attacks.
  • X-Content-Type-Options — When set to 'nosniff', prevents browsers from MIME-type sniffing responses. This stops attackers from disguising executable files as harmless content types.
  • X-Frame-Options — Controls whether your page can be embedded in iframes on other sites. Setting it to DENY or SAMEORIGIN prevents clickjacking attacks where malicious sites overlay invisible frames on your content.

Frequently Asked Questions

What are HTTP response headers?
HTTP response headers are metadata fields that a server sends back alongside the page content when a browser or crawler requests a URL. They contain instructions about caching, security, content encoding, cookies, and more. Every response includes headers, even if you never see them as a user.
Which security headers should every site have?
At minimum, every site should set Strict-Transport-Security (HSTS), X-Content-Type-Options: nosniff, X-Frame-Options, and a Content-Security-Policy. These four headers protect against the most common web attacks including XSS, clickjacking, and MIME-type confusion.
How do caching headers affect performance?
Headers like Cache-Control, ETag, and Expires tell browsers and CDNs how long to store a response before re-fetching it. Proper caching headers can eliminate redundant requests entirely, reducing server load and dramatically improving page load times for returning visitors.
What is the CORS header used for?
The Access-Control-Allow-Origin header controls which external domains can make requests to your server from client-side JavaScript. Without proper CORS headers, browsers block cross-origin API calls. Misconfigured CORS can either break legitimate integrations or expose your API to unauthorized access from any website.