Free tool
Redirect Checker
Follow a redirect chain hop by hop and see every status code along the way.
The check could not be completed
Redirect results
Redirects
0
Final status
—
Total time
—
| Hop | Status | URL | Time |
|---|
Requests are made from this server, not your browser, so results reflect what a crawler sees rather than your own network. Private addresses, internal host names, and non-standard ports are refused.
What This Tool Does
The redirect checker requests a URL and follows each redirect one hop at a time, reporting the status code, the destination, and the response time for every step until it reaches a final page.
It is the quickest way to see whether a migration left behind a chain, a loop, or an unexpected temporary redirect.
How to Use It
Enter the address you want to trace and run the check. The chain is listed in order, with the final destination highlighted.
How the Tool Calculates or Retrieves Data
The request is made from this website's server, not from your browser, so the result is not affected by your browser cache or extensions. Redirects are followed manually: each Location header is resolved to an absolute URL and then validated again before the next request is made.
The check stops at a fixed hop limit, on a repeated URL, or when a destination fails validation.
Understanding Your Results
A single 301 to the final URL is the healthiest pattern. Several hops in a row waste crawl budget and slow the visitor down, and are worth collapsing into one rule.
- 301 and 308 signal a permanent move, which is what a migration should use.
- 302 and 307 signal a temporary move; permanent changes left on a 302 are a common mistake.
- 4xx means the destination is missing or refused; 5xx means the server failed.
- A loop means two URLs point at each other and no page is ever reached.
Frequently Asked Questions
Chains usually accumulate: a rule adding a trailing slash, another forcing HTTPS, and another moving the old path each add a hop. Combining them into a single rule removes the extra requests.
Use 301 when the change is permanent and you want the new URL to be the one indexed. Use 302 only for genuinely temporary situations, such as a seasonal page.
The checker refuses private and internal addresses on purpose. Allowing them would let anyone use this website to probe the network it runs on.