See every redirect hop.
Name the waste.
Paste a URL. Redirectdepth follows the redirect chain hop by hop and reports each one: status code, destination, and what changed at that step. Then it names the hops that were avoidable.
The cost of a chain
Each hop is individually defensible and the stack is the problem. http to https is correct. Apex to www is correct. Adding a trailing slash is correct. Lowercasing the path is correct. Do all four in sequence and a visitor waits four round trips before the first byte of HTML — on a mobile connection where each one costs real time.
Redirectdepth shows which hops could be collapsed into a single redirect and which cannot, and it flags a loop or a chain that exceeds what browsers will follow.
What it reports
Status code per hop
301, 302, 307, 308 — each redirect type reported with its semantic colour. A chain that terminates without reaching a destination is flagged immediately.
What changed
Scheme (http → https), host (apex → www or arbitrary), trailing slash (added or removed), path case change, and tracking parameters (utm_*, fbclid, gclid, etc.) that appeared mid-chain.
Avoidability verdict
Each redirect hop is marked as avoidable or unavoidable based on what it accomplishes. A chain with zero avoidable hops is performing exactly as configured.
Loop detection
If the chain revisits a URL, Redirectdepth stops and reports the loop with every hop collected before it.
Max-hops guard
Most browsers stop at 20 redirects. Redirectdepth follows the same limit and shows every hop it collected before hitting it.
What it does not do
No configuration changes. Redirectdepth does not change any server or DNS setting. It reads the chain and reports the result. No accounts, no stored history, no saved data — every trace is ephemeral.
No real-user latency measurement. Hops are counted from the Cloudflare edge, not from a browser on a mobile connection. Actual user-perceived latency may be higher.
No inference. If the platform cannot reach a host, it says so with the reason. It never guesses at server software or configuration.