Redirect Checker

A redirect checker follows HTTP redirects (3xx responses) and displays the chain: each hop with status code, Location header, and response time. It helps you verify that URLs redirect correctly, debug redirect loops, and understand SEO implications (301 vs 302).

This tool uses fetch() with redirect: 'manual' to capture each response without automatically following. Due to CORS, only URLs that allow cross-origin requests will work in the browser. For unrestricted checking, use the generated curl command in your terminal.

301 (Moved Permanently) — Use the new URL permanently. Search engines transfer link equity. 302 (Found) — Temporary redirect. Original URL may be used again. 307 (Temporary Redirect) — Like 302 but preserves HTTP method (POST stays POST). 308 (Permanent Redirect) — Like 301 but preserves HTTP method. Use 301/302 for most cases; 307/308 when you need to preserve the request method.

Browsers block JavaScript from reading response headers of cross-origin requests unless the server sends CORS headers. Many sites do not expose redirects to cross-origin scripts. The tool explains this and generates a curl command: curl -vL <url>. Run it in your terminal to follow redirects for any URL. curl is not subject to CORS and shows the complete redirect chain with headers.