HTTP Headers Checker
Fetch and display full HTTP request and response headers for any URL — inspect caching, cookies, redirects and server details.
About HTTP Headers
Fetches the full set of HTTP request and response headers for any URL, showing exactly what the server sends back before any browser rendering or JavaScript execution touches it. This is the ground-truth view for debugging caching behavior, redirect chains, content negotiation, cookie flags, or CDN behavior, since browser dev tools sometimes show headers after they've been modified client-side. Response headers alone often explain browser behavior that otherwise looks unexplainable.
Common things to check first: Cache-Control and ETag explain why a page won't update after a deploy; Set-Cookie flags (Secure, HttpOnly, SameSite) explain login/session bugs across subdomains; a Vary header that doesn't match your CDN's cache key is a frequent cause of one visitor seeing another visitor's cached page. If a header you expect is missing entirely, check whether a reverse proxy or CDN in front of your origin is stripping it.
Security Headers
Related Tools
The headers that explain most problems
| Header | What it tells you |
|---|---|
Cache-Control | How long browsers (max-age) and CDNs (s-maxage) may cache the response, or no-store for never. |
Age, cf-cache-status, x-cache | Whether the response came from a CDN cache (HIT) or the origin (MISS), and how old it is. |
ETag / Last-Modified | Used for revalidation; a 304 Not Modified answer means "your cached copy is still good". |
Location | The target of a redirect. Follow full chains with the redirect checker. |
Set-Cookie | Cookie flags: Secure, HttpOnly, SameSite. SameSite=None only works together with Secure. |
Content-Type | Media type and charset. See the MIME type lookup. |
Server, X-Powered-By | Software and versions. Better hidden on production servers. |
"Why doesn't my change show up?"
If Age is high or the cache status says HIT, you are seeing a cached copy at the CDN. Purge the URL in the CDN, and keep HTML on a short cache lifetime so deploys appear quickly. If the origin itself sends an old ETag or Last-Modified, the problem is on the server.
The same check from your own machine
- Response headers:
curl -sI https://example.com - Follow every redirect:
curl -sIL https://example.com - Some servers answer HEAD requests differently from GET. To see the headers of a real GET:
curl -s -D - -o /dev/null https://example.com
Grading security headers specifically? Use the security headers checker.