Redirect Checker
See each hop between a URL and its final destination, with status codes and response times.
Este conteúdo está em inglês.
Exemplos resolvidos
Checking an old HTTP link
http://example.com/old-page entered in the address box
Hop 1: 301 Moved Permanently, http://example.com/old-page to https://example.com/old-page Hop 2: 200 OK at https://example.com/old-page Final address: https://example.com/old-page
This is an illustrative result for a typical HTTP to HTTPS redirect; the hops shown for a real site will depend on its own setup.
Spotting a temporary redirect
https://example.com/sale entered, which sends visitors to a seasonal page
Hop 1: 302 Found, https://example.com/sale to https://example.com/sale-2026 Hop 2: 200 OK at https://example.com/sale-2026 Final address: https://example.com/sale-2026
A 302 signals a temporary move, so search engines usually keep the original address; use a 301 if the move is permanent.
Sobre Redirect Checker
A redirect checker follows a web address from start to finish and records each step along the way. Every hop shows the HTTP status code the server returned, the next location it pointed to and how long the response took. This makes it easy to see whether a move is permanent, temporary or looping, and whether a long chain is adding delay before visitors reach the content.
Redirects are a normal part of running a site, whether you have moved a page, changed domains or forced HTTPS. Problems creep in when several hops stack up, or when one redirect points back to an earlier address and traps the browser. Checking the chain after a migration helps you catch these issues early, before they affect visitors or how search engines crawl your pages.
Como usar Redirect Checker
- Paste the full URL, including https://, into the checker.
- Run the trace and wait for every hop to load.
- Read the status code for each step, such as 301 or 302.
- Check the final destination and its response time.
- Fix any loops or extra hops in your server or content management system settings, then trace again.
Usos comuns
- Confirming an old page sends visitors to its new address after a site move
- Finding redirect chains that add delay before a page loads
- Diagnosing a 'too many redirects' error that a visitor reported
- Checking that HTTP links reach the HTTPS version in one step
Perguntas frequentes
What is the difference between a 301 and a 302 redirect?
A 301 redirect tells browsers and search engines that a page has moved permanently, so the new address should replace the old one. A 302 signals a temporary move, and the original address is expected to return. A 307 is also temporary, but it keeps the original request method. Use 301 for lasting moves and 302 or 307 for short-term changes.
What causes a redirect loop?
A redirect loop happens when a series of redirects sends the browser back to an address it has already visited, so it never reaches a final page. Common causes include conflicting HTTP and HTTPS rules, or a www rule that clashes with a non-www one. The browser usually stops with an error such as too many redirects. Trace the chain to find the step that points back.
How many redirects are too many?
There is no single official limit, but browsers give up after a set number of hops, and each extra hop adds a full round trip before the page loads. Aim for one redirect where possible, going straight from the old address to the final one. Long chains are worth fixing even when they still load, because they slow every visit.
Will a redirect checker change my site's redirects?
No. The checker only requests each address and reports what the server returns, so it does not alter any settings or content. To change a redirect, you need access to your server, hosting control panel or content management system. After you make a change, run the trace again to confirm the new chain behaves as expected.
Why does my browser show a different final address?
Browsers may cache permanent redirects, and some sites serve different responses depending on cookies, location or the user agent. Saved preferences and extensions can also change the route a browser takes. The checker requests the address directly, so its result gives a cleaner view of what the server returns. If the results still disagree, clear your browser cache and trace again.