HTTP & IP

Redirect Tracer & Checker

Follow every HTTP redirect hop and display the full chain with status codes.

About Redirect Tracer

Follows every hop in an HTTP redirect chain from a starting URL to its final destination, showing the status code (301, 302, 307, etc.) and target at each step. Redirect chains that are too long hurt page load time and can trip up crawlers or link-checking tools. The distinction between a 301 (permanent) and 302 (temporary) redirect matters for SEO and caching behavior, and this surfaces exactly which type is in use at each hop.

A redirect chain that loops back on itself will exhaust normal browser/crawler retry limits and fail outright — if a chain here doesn't reach a final destination, check for a loop before assuming it's just unusually long.

📖 Read more in our Knowledge Base →

What this checks

Follows 301, 302, 303, 307, 308 redirects up to 15 hops. Useful for debugging URL shorteners, canonical chains, and misconfigured redirects.

Related Tools

Which redirect code to use

CodeMeaningMethod kept?Use for
301Moved permanentlyNot guaranteed (POST may become GET)Permanent page moves, HTTP→HTTPS, www↔non-www
308Permanent redirectYesPermanent moves of API or form endpoints
302Found (temporary)Not guaranteedShort-term redirects, login flows
303See otherAlways becomes GETAfter a form submission
307Temporary redirectYesTemporary moves that must keep POST

Browsers cache 301 and 308 redirects, sometimes for a long time. Test a new permanent redirect as 302 first, then switch.

Keep chains short

Each hop costs a new request, often a new DNS lookup and TLS handshake. A typical bad chain: http://example.com → https://example.com → https://www.example.com → https://www.example.com/. Point every variant straight to the final URL in one step. Search engines follow several hops but chains slow crawling, and some clients stop after a few.

How this tracer works

It requests each URL with HEAD, reads the status and Location header, and follows only 301, 302, 303, 307 and 308, up to 15 hops. JavaScript and <meta http-equiv="refresh"> redirects happen inside the page and are not shown. A chain that ends early on a 4xx or 5xx code shows where it breaks; a chain that hits the hop limit is usually a loop, for example HTTPS forced at the origin and HTTP forced at a CDN. To check only the final status, use the HTTP Status Checker.