Redirect Chain Checker
Give it a URL and it follows each redirect in turn — one hop at a time, up to ten — showing the status code and where each one points.
About
A URL that redirects wastes a round trip and sometimes several. This tool follows each hop in turn, stopping at the final response, so you can see the whole path from the address you typed to the page that actually loads, along with the status code at each stage.
How to use
- Enter the URL, with or without a scheme.
- Submit and let the tool follow the chain up to ten hops.
- Read the final row to see where visitors really end up and how long it took.
Frequently asked questions
Why does a redirect matter for performance?
Every hop is a fresh connection and request before the page even begins to load. On mobile connections a chain of three or four redirects is easily a second of delay.
What status codes will I see?
301 and 308 are permanent, 302 and 307 are temporary, and 303 is used after form submissions. Browsers cache permanent redirects, so a mistake there can be sticky.
What happens if there is a loop?
The tool stops at ten hops and reports the last status, which is usually a redirect rather than a page. A loop means two rules pointing at each other.