Skip to the tool

Redirect Checker

Trace a URL's redirect chain hop by hop: status codes, timing, loops and what to fix.

How It Works

1

Enter a URL

Type a page address like example.com/old-page. If you leave out the protocol, https is assumed.

2

Follow the chain

The tool requests the URL and follows each redirect, up to 10 hops, without downloading the pages. Every hop shows its status code and response time.

3

Read the notes

Notes flag temporary redirects, long chains, loops and a final URL that errors, and say what each hop changes: http to https, www, or a trailing slash.

FAQ

A 301 (and its modern twin, 308) says the page has moved for good: search engines pass the old URL's signals to the new one. A 302 (and 307) says the move is temporary, so search engines may keep the old URL indexed. Use 301 or 308 for permanent changes.
One is normal, such as http to https. Two or more is a chain: each hop adds a round trip and spends crawl budget. Google follows up to 10 hops, but redirecting the first URL straight to the final one is faster and safer.
Two or more rules that send a URL back to a URL already visited, such as /a to /b to /a. Browsers show 'too many redirects' and the page never loads. The checker stops at the repeated URL and marks it.
No. It reads each response's status and headers and drops the body. Only public http and https addresses on standard web ports can be checked, so private and local addresses are refused.
Redirects can depend on cookies, language, device or login, and a browser may remember a 301 from earlier. This tool sends a clean request with no cookies. To check a link's tags first, build it with the UTM builder.

Built & Maintained by Varstatt

Varstatt is a one-person product studio run by Jurij Tokarski, product engineer since 2011. These tools are free and open — no signup, no catch.