A visual redirect checker that maps the whole chain
When a URL redirects, it often doesn't go straight to its destination — it can pass through several hops, each returning its own HTTP status code. This redirect checker follows that chain one step at a time and draws it out visually, so you can see exactly how a request travels from the URL you entered to where it finally lands. Enter a domain or a full URL and you'll get a step-by-step trace: every hop, every status code, and the final destination.
301 redirect lookup for site migrations
Redirects are the backbone of a clean site migration. When you move a domain or restructure URLs, a permanent 301 redirect tells search engines the old address has moved for good and passes its ranking signals to the new one. This 301 redirect lookup shows you whether a URL returns a 301 (permanent) or a 302 / 307 (temporary) — a distinction that matters enormously for SEO, since temporary redirects don't pass authority the same way. If you've just bought an expired domain, tracing its redirects tells you where its old traffic is being sent.
HTTP status code checker, hop by hop
Every hop in the chain is also an HTTP status code checker in its own right. A healthy chain ends in a single 200 OK; a chain that ends in a 404 or 500 means the redirect is sending visitors to a dead page. We label each status plainly — 301 Moved Permanently, 302 Found, 200 OK — and colour-code redirects, successes, and errors so problems jump out. The classic case we always check is http:// to https://: enter a bare domain and we start on plain HTTP, so you can confirm the secure redirect is in place.
Check the redirect chain for loops
The most damaging redirect problem is a loop — URL A sends you to B, and B sends you back to A, forever. Browsers give up and search engines can't index the page at all. When you check a redirect chain here, we track every URL visited and stop the moment one repeats, flagging it clearly as a loop. We also cap unusually long chains, since a trace that runs past ten hops usually signals a misconfiguration worth fixing. The goal is simple: a fast, honest picture of what your redirects actually do.