Redirect Checker

Page details

Trace a URL's full redirect chain hop by hop: every status code, the final destination, and a loop flag. Export JSON or CSV. Free, no signup.

Paste one URL and see every hop, its status code, and where it ends.

Built for the crawlers and assistants that read your redirects

No configuration and nothing to install. The trace runs server-side and returns the full path.

Use the exact address you want traced — an old page, a shortened link, an affiliate URL or the http version of a domain. One URL per run.

Each request is sent without letting the HTTP client follow redirects on its own, so every intermediate hop is captured rather than silently collapsed into the destination.

You get every hop with its status, the final URL, the hop count and a loop flag. Export the result as JSON or CSV to attach it to a migration ticket.

Choosing the wrong code is the most common redirect mistake. This is what each status actually signals to a browser and to a crawler.

The page has moved for good and you want ranking signals to consolidate on the new URL.

The move is genuinely temporary. This is the most commonly misapplied code — a permanent move sent as 302 keeps signals split.

After a form submission, to send the browser to a result page that must not be re-posted.

A temporary move where the request method and body must survive. Also what HSTS produces internally.

A permanent move that must keep the method — the modern counterpart to 301 for non-GET requests.

304 Not Modified is a 3xx but is not a redirect — it is a caching response and will not appear as a hop.