HTTP Redirect Chain Checker
Trace the full sequence of HTTP redirects from any URL to the final destination — with status codes.
Quick answer: Trace the full sequence of HTTP redirects from any URL to the final destination — with status codes.
Last updated
Frequently asked questions
- Why do I care about a redirect chain?
- Each redirect adds round-trip latency and is a SEO penalty. Long chains (3+) often indicate stale URLs that should be collapsed. Mixed http→https→http chains can leak referrer data.
- Why does this run on a server?
- Browser fetch follows redirects automatically and won't tell you the intermediate hops. Our server uses 'redirect: manual' to capture each step and report it back.
- Will you fetch private URLs?
- We refuse private IP ranges and localhost. Use only against public URLs or your own infrastructure.
- What's the redirect cap?
- 10 hops. Beyond that we abort and report a likely loop. RFC 7231 suggests 5 as a sensible limit; 10 leaves headroom for legitimate edge cases.
- Is the URL logged?
- Per-request stats only (status, duration). The URL itself is not stored.