Redirect chain checker
Paste a link and see every hop it takes before a browser lands — status codes, time per hop, protocol and host changes, and whether it loops. Useful for old links, affiliate links and anything that "sometimes works".
20 of 20 free runs left this hour. Used them up? An extra run is $1.49 and works for every tool here, no account needed.
How it works
- We request the address without following anything, and read the status and the Location header.
- Then we request the next address, up to 10 hops, stopping at a loop or a final page.
- A page that redirects with a meta refresh or JavaScript instead of a status code is caught too.
- Each hop is graded: one permanent redirect is fine, chains and temporary redirects cost speed and ranking.
Questions people ask
Why do redirect chains matter?
Every hop is a round trip before the visitor sees anything — on a phone often 200–500 ms each. Search engines also pass less signal through long chains and may stop following after a few hops.
Is a 302 bad?
Not by itself. A 302 says "temporary", so search engines keep the old address in their index. For a page that has moved for good, use a 301 (or 308) — that is the one that transfers the ranking.
What is a redirect loop?
Address A sends to B and B sends back to A. Browsers give up with "too many redirects" and the page is unreachable. It usually comes from two rules fighting — one forcing www, one removing it, or HTTPS rules on both the CDN and the server.
Why does the tool show a hop my browser does not?
Browsers hide the hops. A common surprise is http → https → www → trailing slash: three hops where one 301 straight to the final address would do.
Does it check affiliate or shortened links?
Yes — paste the short link and you see the whole path to the final destination, including the parameters that are added on the way.
Free, no signup. Runs on our servers, nothing is installed. Want all of it at once? The full site check runs 30+ tests in one go.