Traces a URL's full redirect chain, hop by hop, from our server - showing each status code and destination up to the final page.
Every extra redirect hop adds latency and, more importantly, can silently break things: too many hops triggers browsers' "too many redirects" error, a redirect loop makes a URL permanently unreachable, and long chains between HTTP/HTTPS or www/non-www variants can dilute SEO signal that a direct redirect wouldn't. This traces the full path a browser would actually follow, one hop at a time.
Known limitations: the check runs from our server rather than your own browser or location, so geo-based or device-based redirects (for example, mobile vs. desktop redirects) may show a different path than what you'd personally see. Redirects to private or internal addresses are not followed, for safety.
Read more: Tracing a Redirect Chain: Why Every Hop Matters.