Redirect Checker

The redirect checker follows a URL the way a crawler does and shows every hop: the URL requested, the status code and whether it's a permanent (301, 308) or temporary (302, 303, 307) redirect, the Location it points to and how long each response took. It ends at the final URL and its status, so you can see at a glance whether a link lands on a working page and how many round trips it takes to get there.

Redirect problems are easy to create and hard to see in a browser, which hides the hops and caches permanent redirects. Common ones are chains (http to https, then to www, then to a trailing slash), temporary redirects used for permanent moves, loops that never load, and redirects that drop from HTTPS back to plain HTTP. Google follows up to 10 redirects in a chain, but each extra hop slows visitors down, so the checker warns about every one of these.

Our server requests the URL from the public internet with its own user agent and follows HTTP redirects one hop at a time, checking each target before it goes on; the URL isn't stored or logged. It follows Location headers only, not JavaScript or meta refresh redirects, and only public addresses can be checked. Sites can redirect differently by country, language or device, and times are measured from our server, so treat them as a guide.