HTTP Headers
Inspect response headers and redirects.
HTTP headers are the metadata a server returns with every response: status code, content type, caching rules, cookies and security policies. This fetches a URL and shows those headers along with each step of any redirect chain.
Start a check
Public internet targets onlyResults
Ready when you are
Enter your details above and run the tool.
How HTTP Headers works
What it does
Inspect response headers and redirects.
What you get
HTTP status and the headers returned by the website.
Live data sources
The target is sent to a network provider. Results include their source; timeouts and unavailable data are clearly marked.
What if a check cannot finish?
Confirm your input and try again. A timeout, blocked request, or unavailable provider is not proof that a domain is broken. Internet measurements and third-party services have limits.
HTTP Headers — frequently asked questions
Why does my redirect chain matter?
Every hop adds a round trip before anything renders, and long chains dilute link signals. Redirect to the final URL in one step wherever you can.
Which security headers should I have?
At minimum Strict-Transport-Security, X-Content-Type-Options: nosniff and a Content-Security-Policy. Referrer-Policy and a frame policy are worth adding too.
What is the difference between a 301 and a 302?
301 is permanent: clients and search engines update to the new URL and may cache the redirect indefinitely. 302 is temporary and keeps the original URL authoritative.