Paste any URL and see the full redirect chain hop by hop, with status codes and the final destination.
Loading tool…
Lower stack cost. Back in the inbox. Built to send at any scale.
We rebuild it properly: secondary domains, inboxes, SPF, DKIM and DMARC set to enforcement, warmup and safe sending limits, blacklist monitoring on top. Send-ready in about 17 days. No campaigns, no copy, no lead lists. Infrastructure only.
Almost a decade building cold outreach infrastructure, including his own sending and verification stack built from scratch. 20+ B2B clients at companies worth $10M and above, all in tier one countries.
Free · Written plan + fixed price · No sales call required
Every redirect is an extra round trip: the browser asks for one address, is told to go somewhere else, and has to ask again before the page even starts to load. One clean redirect is fine. Chains of them slow pages down, and speed is part of how search engines judge a site. Long or wrong chains also appear after site migrations, when old addresses point at other old addresses instead of at the final page, and they quietly lose visitors and link value along the way. This checker shows the exact path a URL takes, hop by hop, so you can spot a chain worth shortening and fix it at the source.
A 301 is a permanent move: this page has moved for good, and search engines pass almost all of the old page's ranking value to the new address. Use a 301 when an address is never coming back. A 302 is a temporary move: the page will be back at the old address soon, so search engines keep the old address as the one that counts. Leaving a 302 in place for a move that is really permanent is a common mistake that holds the new address back. A 307 is also temporary, but stricter: the browser must repeat the request exactly as it was sent, so it is used mostly for form posts and APIs rather than page moves. A 308 is the permanent version of the 307, with the same strict rule. For everyday page moves, 301 for permanent and 302 for temporary are the two that matter.
Check http://github.com and you see a tidy two hop result: a 301 hop from http://github.com to https://github.com/, then a 200 at the final address. That is a healthy setup: one permanent hop from http to https, and the page answers. Now picture an old link from an email campaign that still uses http and an old path: it might hop from http to https, then from the old path to a newer path, then once more to the current page before answering 200. Nothing is broken and the visitor still arrives, but the chain is worth shortening: point the old address straight at the final one and the page loads sooner, with less to go wrong.
A redirect loop means two addresses send visitors to each other forever, and the browser gives up with an error; this checker stops and shows you where the chain repeated itself. A chain longer than about three hops is worth fixing even when it works, because every hop adds time and every hop is a place where value and visitors can be lost. A hop from https back to http is a downgrade: the visitor leaves the secure address for an insecure one, and browsers may warn about it. A 302 sitting in the middle of what should be a permanent move is also worth a look, because it tells search engines the move might not be permanent after all.
For more checks on the same domain, run the Domain Health Checker, watch a DNS change spread with the DNS Propagation Checker, see how old a domain is with the Domain Age Checker, and trace the path of an email with the Email Header Analyzer.
A redirect chain is the series of addresses a browser is sent through after it asks for one URL. Each step, called a hop, answers with a redirect status code and the next address, until the final address answers with the page itself. This checker lists every hop in order.
One redirect is normal, and two can be fine, for example http to https and then www to non-www. Once a chain passes three hops it is worth shortening. Very long chains slow the page down, and browsers give up entirely after around twenty redirects.
A 301 is permanent: the page has moved for good, and search engines move the ranking value to the new address. A 302 is temporary: the old address stays the one that counts, because the page is expected back. Using a 302 for a permanent move is a common and costly mistake.
A loop is when address A redirects to address B and B redirects back to A, so the browser bounces between them until it gives up with an error. Fix it by finding the two rules that point at each other, usually in your server config, your .htaccess file or a redirect plugin, and making one of them point at the real final page instead.
A single clean 301 does not meaningfully hurt SEO; search engines pass nearly all of the value through it. What hurts is long chains, loops, and temporary 302s left in place of permanent moves, because they slow pages down and send mixed signals about which address should rank.
Each hop is a full extra request: the browser connects, asks, waits for the redirect answer, then starts again at the next address. On a mobile connection each round trip can add a real delay, and the page cannot start loading until the last hop answers.
Yes, both should load, but one should be the single real address and the other should send visitors to it with one 301 hop. If both serve the full page, you have two copies of your site competing with each other, which splits their value.
Shorteners work by redirecting: the short address answers with a 301 or 302 to the destination, and some add an analytics step in between, which is another hop. That is expected. What matters is that the chain ends at the right page and does not wander through extra addresses first.
It covers what is broken, what we would build, the timeline, and one fixed price. Want it walked through instead? Book a 15 minute plan walkthrough.
Or just reply to the plan email. Either works.
