See every header your server really sends
One URL, every redirect hop, every response header, checked against the specs and explained in plain English. Nothing is followed automatically and nothing is collapsed.
Headers are read exactly as they came off the wire: original casing, duplicates and order all preserved.
Get found on Google and AI
Ex-Google Search engineers show you what to fix. Book a free, no-obligation call.
searchbrothers.com →What this checks
Enter a URL and httpheader.com requests it through a proxy in the country you pick, walks the redirect chain by hand, and lints every response header it sees. Each finding says what the server did, why it matters, and what to change.
The report also shows the HTTP/2 view of the final hop and what the origin advertises in Alt-Svc. For a real HTTP/3 test, use http3test.com; for certificates, ssltest.com.
Frequently asked questions
- Why does the report show each redirect separately?
- Because the headers on a 301 are not the headers on the page it points at. Caching, security and cookie problems usually live on a hop nobody looks at, so the chain is never collapsed.
- Why is header casing shown for HTTP/1.1 but not HTTP/2?
- HTTP/2 and HTTP/3 lowercase field names at the protocol level, so original casing only exists on HTTP/1.1. An h2 view that looks tidy has not been fixed, it has been normalised by the protocol.
- Do you honour robots.txt?
- Yes. The target's robots.txt is fetched through the same proxy first, and a disallowed URL is not checked.
- Can I check a list of URLs?
- Not here, by design. http.app does batch checking.
Disclaimer
This website is developed by technical SEO consultant and ex-Google engineer Fili.
Bugs will happen and despite best efforts to maintain the code base and data quality, no guarantees can and/or will be given. Data may be incomplete, lost and/or errors may occur. This is a personal website and for-fun project. Use at your own risk.