Follow a URL hop by hop through every 301, 302, 307 and 308 to its final destination. See the status codes, the final URL and any loops. Free, instant, no signup.
Enter a URL or host. A bare host defaults to http:// so you can see the HTTPS upgrade hop. Redirects are followed on the server.
The redirects command follows the chain hop by hop and reports every status code, where each hop points and the final URL.
# human readable hop-by-hop chain
python cli.py redirectshttp://github.com# full structured JSON (hops, status codes, final_url, hop_count)
python cli.py redirectshttp://github.com--json
THE BIG DIFFERENCE
Trace redirects from inside your AI
This tool speaks the Model Context Protocol (MCP) and ships a REST API. Connect it once, then just ask your assistant where a link ends up or why a URL takes so many hops.
A redirect checker follows a URL's HTTP redirects one hop at a time and shows you the whole journey: each intermediate URL, the status code it returned, where it pointed next, and the final destination and its status. It is the fastest way to see exactly where a link ends up, how many hops it takes, and whether any of those hops are slow, broken or looping. This tool traces the chain on the server, so it sees the real status codes a browser would never expose to a web page.
How to trace a redirect chain
Type the URL or host (for example http://github.com) into the box above.
Select Trace. The full chain appears in a few seconds.
Read each hop, its status code and where it redirects to, from the first request to the final URL.
Check the hop count and the final status to spot chains that are longer than they need to be.
301 vs 302 vs 307 and 308
301 Moved Permanently: the resource has moved for good. Search engines pass ranking signals to the new URL and browsers may cache the redirect. Use this for permanent moves.
302 Found: a temporary redirect. The original URL keeps its ranking and nothing is cached long term. Some clients change the method to GET on the way.
307 Temporary Redirect: like a 302 but the HTTP method and body are preserved exactly, so a POST stays a POST.
308 Permanent Redirect: like a 301 but, like 307, it preserves the method and body. It is the modern permanent redirect for APIs and forms.
Why redirect chains hurt SEO and performance
Every hop is an extra round trip that adds latency before the page even starts to load, which is especially painful on mobile networks. Each hop can also dilute the ranking signals passed to the final URL, and long chains waste crawl budget and risk breaking if any hop in the middle fails. The best practice is simple: redirect straight to the final URL in a single hop, and never chain a 301 into another 301 into a third.
Redirect loops
A redirect loop happens when URLs point back at each other, so A sends you to B and B sends you back to A. The request never reaches a real page, and browsers give up with an error like ERR_TOO_MANY_REDIRECTS. This checker tracks the URLs it has already visited and stops as soon as it sees one repeat, so you can find the exact pair of URLs that are bouncing the request between them.
Frequently asked questions
What is a redirect checker?
A redirect checker follows a URL's HTTP redirects one hop at a time and shows the whole chain: each intermediate URL, the status code it returned (such as 301, 302, 307 or 308), where it pointed next, and the final destination URL and its status. It is the fastest way to see exactly where a link ends up and how many hops it takes to get there.
What is the difference between a 301 and a 302 redirect?
A 301 is a permanent redirect: the resource has moved for good, so search engines pass ranking signals to the new URL and browsers may cache it. A 302 (and 307) is a temporary redirect: the move is not permanent, so the original URL keeps its ranking and nothing is cached long term. Use 301 for permanent moves and 302 or 307 only for genuinely temporary ones.
Why do redirect chains hurt SEO and performance?
Every hop in a redirect chain is an extra round trip that adds latency before the page loads, and each hop can dilute the ranking signals passed on to the final URL. Long chains waste crawl budget, slow down users on mobile networks, and risk breaking if any hop in the middle fails. Best practice is to redirect straight to the final URL in a single hop.
What is a redirect loop?
A redirect loop happens when URLs point back to each other, for example A redirects to B and B redirects back to A, so the request never reaches a real page. Browsers stop after too many hops and show an error such as ERR_TOO_MANY_REDIRECTS. The redirect checker detects loops by tracking the URLs it has already visited and stops instead of following them forever.
Can I trace redirects inside Claude, ChatGPT or Gemini?
Yes. It ships an MCP server and a REST API, so you can connect it to Claude, ChatGPT, Gemini, Kimi, Cursor and any MCP client, then ask your assistant to trace a URL's redirect chain and tell you where it ends up. See the connection guide.