HTTP Redirect Checker
Trace redirect chains and analyze HTTP status codes
Redirect Chain
Final Destination
-
Summary
Status Codes
Actions
Learn more & FAQ
What does a redirect checker do?
When a URL redirects, your browser usually follows the chain silently and shows only the final page - hiding how many hops it took, what status code each one used, and whether the chain loops. This tool follows the same chain a browser would and shows every hop explicitly, so you can see exactly what's happening between the URL you entered and where it finally lands.
How to read your results
Each hop in the chain shows its HTTP status code (301, 302, 307, etc.), the URL it redirected from, and where it pointed next. A clean result ends in a single 200 after one or two hops. A long chain, a loop, or an unexpected status code at any step is worth fixing - each extra hop costs load time and, for 301s specifically, a little SEO value passed through to the final URL.
Frequently asked questions
What's the difference between a 301 and a 302 redirect?
A 301 is permanent - it tells browsers and search engines to use the new URL going forward and transfers most of the original page's SEO value. A 302 is temporary and signals the old URL may return, so search engines generally keep indexing the original.
Why would a URL have multiple redirects in a row?
Each redirect in a chain adds latency and a small amount of lost SEO equity. Chains build up over time from things like an old HTTP-to-HTTPS redirect, a www normalization redirect, and a URL restructure all stacking on top of each other instead of pointing straight to the final destination.
What causes a redirect loop?
A redirect loop happens when a chain of redirects eventually points back to a URL already visited earlier in the chain, so the browser or crawler never reaches a final page. It's usually caused by conflicting rules at different layers (CDN, server config, application code) each redirecting the same URL differently.
How many redirects are too many?
There's no hard rule, but each hop adds a full round-trip of latency, so more than two or three in a chain is usually worth collapsing into a single direct redirect, both for page speed and because search engines reduce the ranking weight passed through long chains.
Why does my redirect work in a browser but look broken here?
Browsers follow redirects automatically and only show you the final page, hiding the chain in between. This tool follows the same chain but shows every hop and its status code, which is often how a slow or looping redirect gets noticed in the first place.