Redirect Tracer
★★★★★★★★★★5.0(1 votes)
Trace every redirect hop from a URL to its final destination. See status codes and the complete redirect chain.
Redirect Tracer
Traces redirects via a CORS proxy. Up to 10 hops followed.
Redirect Chain0 hops
About This Tool
Why Trace Redirects?
- Performance — each hop adds ~100-300ms latency
- SEO — long chains lose link equity
- Security — verify where short links actually go
- Debugging — find redirect loops or wrong destinations
Best Practice
Keep chains to a single hop. Always use 301 (permanent) not 302 for moved pages.
Frequently Asked Questions
Why do some status codes show as 0?
Status 0 means the proxy couldn't reach the URL — DNS failed, server didn't respond, or connection was blocked. Verify the URL loads in a browser.
What is the maximum chain length?
Browsers follow up to 20 redirects. This tool stops at 10. If you hit 10 hops, your chain is too long and needs consolidation.
Do redirect chains hurt SEO?
Long chains waste crawl budget and can dilute link equity. One or two hops is acceptable; five or more is worth fixing.