Redirect Checker & HTTP Header Tracer
Follow a URL through every redirect and see each hop's status code, Location, response headers and timing.
Frequently Asked Questions
What is a redirect chain?
It is the sequence of responses a URL goes through before reaching a final page: for example http://example.com → https://example.com → https://www.example.com/. Each hop is a separate request with its own status code and headers, adding latency, so a well-configured site redirects in one hop.
What is the difference between 301, 302, 307 and 308?
301 and 308 are permanent: browsers cache them and search engines move ranking signals to the new URL. 302 and 307 are temporary, so search engines keep indexing the original URL. 307 and 308 also guarantee the request method and body are kept, so a POST stays a POST.
Why can't a browser show me this?
Browser fetch follows redirects silently and hides the intermediate responses, and cross-origin requests cannot read most headers. This tool sends each request from ToolDock's server with automatic redirects turned off, so every hop is visible.
Why test with a different user agent?
Some sites redirect differently for mobile devices, specific browsers or search engine crawlers. Comparing the chain for Chrome, iPhone and Googlebot shows mobile redirects, geo or language redirects, and cloaking that would otherwise be invisible.
What problems does it flag?
Redirect loops, chains longer than three hops, HTTPS to HTTP downgrades, temporary redirects used for what look like permanent moves, HTTP-to-HTTPS upgrades without an HSTS header, redirects missing a Location header, and chains that end in an error.
Does it follow meta refresh or JavaScript redirects?
No. It follows HTTP redirects (3xx status codes with a Location header) only. Redirects done in HTML or JavaScript happen after the page loads in a browser.