Redirect chain checker
Follow every hop a URL takes — status codes, http/https, timing and the final address. Catch redirect chains, loops and downgrades before they cost you rankings or clicks.
Check a URL
Why the redirect chain is worth checking
Every hop between a link and its destination adds latency and a chance of failure, and each one can dilute or drop a signal — link equity, the click id on a tracking URL, UTM parameters, the referrer. Search engines follow a few hops but treat long chains as a quality problem; ad networks may reject a destination that bounces through several redirects. This tool follows the chain server-side and shows every hop: the URL, the status code, the scheme, timing and the final address. A single 301 straight to the canonical https URL is ideal; two or more hops, a 302 where a 301 belongs, an http step after an https one, or a loop are all worth fixing.
What it does and does not follow
The check uses HEAD requests from our server. Only HTTP-level redirects (3xx with a Location header) are followed — a page that redirects via a meta-refresh tag or client-side script shows as a 200 here. Because the request comes from a server with a bot user agent, a link that cloaks on user agent or geo can resolve differently than it would for a real click, and some servers return 403 or 405 to HEAD while serving a browser fine. For safety the checker refuses any URL whose hostname resolves to a private, loopback or reserved IP range, so it cannot be used to probe internal networks.