Redirect chain tracer

Follows every hop from our server and reports the status, headers, resolved address and timing of each one. Redirects are followed one at a time, and each destination is re-checked before we connect to it.

Why run this on a server

A browser follows redirects itself and shows you only where you landed. The intermediate hops — the ones that reveal a tracking domain, a stale CDN rule, or a chain that briefly drops to plaintext HTTP — are gone by the time the page renders.

Each hop below shows the IP address actually connected to, so you can see when a host resolves somewhere unexpected.