Network

Redirect Checker

A redirect checker traces every hop a URL takes before it reaches its final destination, showing the status code at each step. It reveals 301 versus 302 mistakes, chains that waste crawl budget, and loops that never resolve, all of which cost link equity and slow the page down for real visitors.

Last updated · Free, no signup

Loading interactive Redirect Checker…

What does a redirect checker trace?

A redirect checker follows the Location header from one URL to the next and lists the status code at every hop. The chain exposes temporary-versus-permanent mistakes, HTTP-to-HTTPS detours, tracking intermediaries, loops, and unnecessary hops that add latency and complicate crawling.

The protected server-side client tries HEAD before GET, caps each response body, uses an eight-second timeout, and stops after fifteen hops. It does not carry a user's cookies or login state, so personalized and geographic redirects can differ. Review both the final target and every intermediate host before trusting a shared link.