Redirect Checker
Trace redirect chains for any URL.
Loading…
About Redirect Checker
Redirect chains build up quietly: http to https, then non-www to www, then a trailing slash, then a moved page. Enter an address and our server requests it, follows each Location header, and returns the whole path as a numbered list with the status code of every hop and a Final tag on the last URL. When there are more than two redirects, a long-chain note appears, so you can tell when it is worth collapsing the chain into a single step.
Features
- Numbered list of every URL in the chain with its status code
- Final tag on the last URL reached
- Follows 301, 302, 303, 307 and 308 redirects
- Long-chain note when there are more than two redirects
- Total time for the whole chain in milliseconds
Limitations
- Only HTTP redirects are followed. A meta refresh tag or a JavaScript redirect inside the page is not detected, because the tool reads headers only.
- The trace stops after 10 hops, and a redirect that points to an internal or reserved address is not followed.
- Public http and https addresses only, and each IP address is limited to 20 traces per minute.
- Our server sends its own plain request, so the chain can differ from what a browser sees when cookies, language or device change the redirect.
How it works
- Enter the address to trace; https:// is added if you leave the scheme out.
- Press Trace Redirects and wait while our server follows the chain.
- Read the summary line, which says whether there were no redirects or how many were found, and the total time.
- Follow the numbered list: each hop shows its status code and URL, and the last one is tagged Final.
- Use Re-check after you change a redirect rule, or New URL to start over.
Example input
http://example.comFrequently asked questions
- A 301, like a 308, says the page has moved permanently, while a 302, like a 307, says the move is temporary. A 303 means See Other. Each hop in the list shows its code, so you can check that a permanent move uses a permanent code.
- The tool adds a long-chain note when there are more than two. Every hop costs a round trip, so aim to send visitors straight to the final address, for example from http://example.com directly to https://www.example.com/ in one step.
- It stops after 10 hops, when a redirect response has no Location header, or when a hop points to an internal or reserved address. The last row shows where it ended, so a loop appears as a chain that never reaches a 200.
- Both make the same server check. This page lists every hop as a numbered chain, while the status checker leads with the final code, its name and the final address, and shows the chain only underneath.
- Yes. The trace is made by our server, so the address you enter goes there first. The request leaves from our infrastructure with the AuraTools-SEO-Checker/1.0 user agent, and your own browser is not involved in the chain.
Related tools
- HTTP Status CheckerCheck HTTP status codes and redirect chains.
- Canonical URL GeneratorGenerate a canonical <link> tag for any URL.
- Website SEO CheckerFree SEO audit tool — analyze any website's technical and on-page SEO.
- XML Sitemap GeneratorGenerate an XML sitemap from a list of URLs.
- Full Site AuditAudit a page plus a few of its internal pages at once.