Practical guide
How to inspect HTTP headers
Use this page to see the status, redirect path, and response headers a server sends before a browser renders the page.
What this tool checks
The HTTP header inspector requests a URL and reports the status code, redirect chain, and response headers. Headers can reveal caching rules, content type, compression, cookies, CDN behavior, and security policies such as HSTS, CSP, X-Frame-Options, COOP, and Referrer-Policy.
When to use it
Use it after deploying a site, changing redirect rules, moving behind a CDN, or tightening browser security headers. It is especially helpful when a page works in one browser but fails in another, or when SEO tools report redirect, canonical, mixed-content, or header-related warnings.
How to read the result
Start with the status code. A 200 response means the final URL returned content, 3xx responses show redirects, 4xx responses usually indicate a client or permission problem, and 5xx responses usually indicate a server-side failure. Then review the redirect chain and security headers to confirm the final URL is the one users and crawlers should see.
Example HTTP header check
- Example input
https://example.com- Example result
status: 200 content-type: text/html; charset=UTF-8 strict-transport-security: max-age=31536000 cache-control: max-age=604800
Security and caching headers are only useful when they are present on the final response users actually receive.
Related tools
Related guides
FAQ
Why does the tool show a different URL than I entered?
Which security headers matter most?
Why do headers differ between tools?
Last reviewed: 2026-05-20.