Redirect Checker – Check redirects online

See a URL's redirect chain hop by hop: each hop shows its status code, whether the redirect is permanent or temporary, server IP, response time and up to 60 HTTP response headers. Above the chain, you can see the number of redirects, total time, final status and destination URL, plus notices about changes such as switching to HTTPS or www, or a mix of permanent and temporary redirects. In this fictional example, example.com/alt produces the chain http://example.com/alt → 301 → https://example.com/alt → 302 → https://www.example.com/neu (200).

301 and 308 mean “moved permanently”: browsers and search engines remember the new destination, and ranking signals transfer with it. 302, 303 and 307 mean “temporary”: the old URL remains the canonical one. 308 and 307 also require the method and body to remain unchanged; with 301 and 302, POST often becomes GET. Use permanent redirects for domain moves and switching to HTTPS. The checker marks each redirecting hop as permanent or temporary.

Each redirect adds another request and increases load time. Search engines also follow only a limited number of redirects. Avoid more than two or three hops in a row. The checker warns you about chains with more than three redirects. It fetches at most 10 URLs, including the starting URL; if the tenth URL still redirects, the check ends with “Too many redirects”.

Browsers usually show this message when redirects form a loop (A → B → A), for example because of conflicting .htaccess rules or an HTTPS redirect behind a proxy. If a URL appears a second time in the chain, the checker does not fetch it again. It reports “Loop detected” and marks the hop that closes the loop.

Enter the domain without a protocol, and the check starts at http://, just as it would for a visitor who types only the domain. The checker flags the switch to HTTPS and warns you if a redirect leads from HTTPS back to HTTP. To check the HTTPS version directly, include https:// at the start.

No. The checker follows HTTP redirects: 3xx status codes with a Location header. Redirects using <meta http-equiv="refresh"> or JavaScript happen only in the browser and do not appear in the HTTP chain. For SEO, server-side 301 redirects are the better choice anyway.

Some sites redirect mobile devices to a separate mobile version or app page. Under “Fetch as”, select “Mobile browser” to fetch the URL with the user agent of Safari on iPhone, or “Desktop browser” to use the user agent of Chrome on Windows. This lets you compare both chains.

No. The checker fetches the URL live over the public internet from our server. For security reasons, it does not fetch addresses with a private IP or localhost, or blocked service ports such as 22 or 3306, even if a redirect points to them. It rejects URLs containing login credentials when you enter them.

Yes, and you don't need an account. To prevent misuse, there is a 6-second wait after each check, and each IP address can run up to 10 checks per minute.