URL Redirect Chain Checker
Follow a URL's redirect chain hop by hop: status code (301, 302, 307, 308), Location target and final URL. Detects redirect loops and long chains.
https:// is added when no scheme is given.
What is Redirect Checker?
This redirect checker shows every hop a URL goes through before it reaches its final destination: the status code of each response, the Location it points to and the final URL and status. It warns about redirect loops, chains longer than one hop and temporary redirects used where a permanent one is probably intended.
How to use Redirect Checker
- Enter the starting URL, e.g.
http://example.comto test the HTTP→HTTPS and www rules. - Press Check.
- Read the numbered list of hops with their status codes and targets.
- Check the summary (number of redirects, final URL, final status) and any warnings.
When to use Redirect Checker
Use it after a site migration, HTTPS switch or URL restructuring to make sure old URLs reach their new home in one 301/308 hop. It cannot see redirects that depend on cookies, login state or the visitor's country, because the request comes from a Cloudflare data center without cookies.
How Redirect Checker works
AlgoKit's Pages Function requests the URL with automatic redirects disabled, records the status and Location header, resolves the Location relative to the current URL and repeats, up to 10 hops. Every hop is re-validated and its host re-resolved, so a redirect cannot lead the function to a private or local address. A URL that appears twice in the chain is reported as a loop. Only HTTP redirects are followed; meta-refresh and JavaScript redirects are not executed.
Common Use Cases
- Verify that http:// and non-www URLs end on the canonical https://www URL.
- Find and shorten chains like http → https → www → trailing slash.
- Debug an ERR_TOO_MANY_REDIRECTS loop.
- Check where a shortened or tracking link really leads before clicking it.
FAQs
301 or 302 – which should I use?
Use 301 or 308 for permanent moves so search engines transfer the URL. 302, 303 and 307 are temporary. 307/308 keep the request method (POST stays POST); 301/302 may be turned into GET by clients.
Why should chains be short?
Each hop costs a round trip for users, and search engine crawlers follow only a limited number of hops.
Does it follow JavaScript or meta refresh redirects?
No. Only HTTP 3xx responses with a Location header are followed.