Trace any redirect chain, hop by hop

Each hop is individually defensible. The stack is the problem. Paste a URL. Redirectdepth follows the chain and tells you each step — what changed, what was avoidable, and whether the chain could have been compressed.

Trace a URL Pricing

How it works

  1. Paste any URL — with or without a scheme. Redirectdepth prepends https:// if needed.
  2. The tool follows the redirect chain server-side using the HTTP HEAD method, capturing each 3xx response raw.
  3. Every hop is reported: status code, destination URL, what URL component changed (scheme, host, trailing slash, path, query), and whether the hop was avoidable.
A hop is avoidable if all its changes are cosmetic — scheme change, www prefix, trailing slash, tracking-parameter removal. These could have been combined with another redirect into a single hop.

What you see

0 start https://github.com
1 302 https://github.com/ trailing_slash: added — avoidable
2 200 https://github.com/ final

Features

  • Follow chains up to 20 hops (50 with Pro)
  • Detect redirect loops and stalled chains
  • Component-level diff: scheme, host, port, path, trailing slash, query, fragment
  • Identify avoidable hops that could be collapsed
  • No account needed — paste a URL and get results instantly

Limitations

Redirectdepth uses Cloudflare Workers to follow redirect chains. A Cloudflare Worker cannot open a connection to a host that is itself behind Cloudflare (e.g. example.com, cloudflare.com). Those hosts will report as unreachable — this is a platform limitation, not a result about your target server. The following hosts are verified reachable: github.com, wikipedia.org.

The tool uses HEAD requests. Some servers may differ on HEAD vs GET redirects, though the HTTP specification treats them identically for redirect behavior.