Follow a URL through every redirect to the page it lands on.
Example
Chain
Findings
Capabilities and processing
Enter a URL, or paste the output of curl -sIL. Without http:// or https://, the check starts at http://, so the redirect to HTTPS is part of the chain. Our server requests each hop itself, up to 15, without cookies, and returns each status code, Location header, response headers and time to the first byte. Pasted curl output is read in your browser.
Each hop shows what changed from the one before (to HTTPS, adding or dropping www, a trailing slash, a new path) with the changed part marked. Loops, drops from HTTPS to plain HTTP, temporary codes on permanent moves, chains of more than one hop and chains that end in an error are flagged.
Example workflow
The sample shop goes from http://harbor-supply.example to HTTPS and then to www in two hops, so links should point at the final address. Break it shows a loop, a five-request chain, an HTTPS to HTTP drop, a chain that ends at a 404, a chain that never stops and a host that does not exist.
Limits and interpretation
Only HTTP redirects are followed; a meta refresh or a script redirect inside a page is not. Cookies set along the way are not sent back, so sites that redirect by cookie or by location may behave differently in a browser. Times are measured from our server. Nothing is stored.
Related tools
Security headers grader · Broken link checker · Website down checker · All tools · Privacy