Network & DNS
Redirect Checker
See the redirect chain for a URL, hop by hop, including status codes.
Meta refresh and JavaScript redirects are out of scope.
Results appear here.
What the result means
The Worker starts at the URL you enter and reads the first response without letting the platform follow redirects on its own. If the status is a redirect and Location is present, the next URL is resolved against the current one, including relative paths. Each hop is checked with the same private-address rules before it is requested. The chain stops on a loop, a missing Location, a non-redirect status, or after ten redirects. The table shows the URL, the status, and the Location of every hop that was actually requested, plus the reason the walk stopped. Meta refresh and JavaScript redirects are not followed. They live in the body or in a script, and this check never reads the body. A timeout on a later hop is reported as the stop reason rather than as a completed chain.
Related tools
Questions
What is a redirect loop?
A loop is the same URL appearing again in the chain. The checker stops instead of walking it forever. The hop list shows where the repeat started.
Does this follow JavaScript redirects?
No. Only HTTP Location headers are followed. A meta refresh tag or a script that sets window.location is outside this check, because the body is not read.
Why did the chain stop at ten hops?
Ten redirects is the cap. A longer chain is reported as a hop limit so a misconfigured site cannot make the checker chase URLs without end.