HTTP Header & Redirect Checker
Find where a URL redirects, which status it returns and what headers arrive with the final response.
One check, several answers
See the final HTTP status, every redirect hop, response headers, canonical URL, robots directive and page metadata.
Start with where the request ends
After a domain move or HTTPS change, the first question is simple: does the old address reach the right page? Read the redirect chain before investigating individual headers.
/old-page301 · moved/new-page200 · response receivedWhat to check in the report
- Redirects
- Look for unnecessary stops at an old domain or HTTP address before the visitor reaches the final page.
- Page errors
- A 404 means the path was not found; a 5xx response points to a server problem. Check these before adjusting metadata.
- Canonical URL
- Compare the declared address with the final URL and the page you intended visitors to reach.
- Headers
- Review whether a missing policy is needed for this page. A header being present does not prove its policy is effective.
This is a server-side request, not a browser session — it does not sign in, run page JavaScript or follow JavaScript redirects. Private addresses and non-standard ports are blocked. A site may also respond differently to the checker than to a visitor.