What is the Redirect Chain Tracer?
Follows a URL through its HTTP redirect chain on the server side and lists every hop's status code, Location header, and response time, up to 10 redirects.
How it works
The backend requests the URL with `redirect: 'manual'`, so instead of letting fetch silently follow a 3xx response it reads the `Location` header itself, records the hop, and then requests that new URL — repeating until it hits a non-redirect response or reaches 10 hops, whichever comes first.
SysAdmin & security use cases
- Expand a bit.ly or t.co shortened link to see its actual final destination before clicking it.
- Check whether a link is looping (ERR_TOO_MANY_REDIRECTS) instead of resolving.
- Confirm an HTTP link correctly upgrades to HTTPS in one hop instead of several.
- Audit an affiliate or marketing redirect chain to see how many hops it takes and where it lands.