Redirect Checker

See where a URL redirects and in how many steps: status code, response time and HTTPS transition for every hop.

What Is a Redirect Checker?

A redirect is when a server sends the browser visiting one address on to another. An http:// address going to its https:// version, a non-www address going to the www version, or a moved page going to its new address are all redirects. When several redirects follow one another, the result is called a redirect chain.

The DNSBil Redirect Checker sends a real request from our server to the address you enter and follows every redirect until it reaches the final page. For each step you see the HTTP status code (301, 302, 307, 308), the response time, the server's IP address, the TLS version and the response headers. At the end you get a short assessment of the chain length, the move to HTTPS, HSTS and temporary redirects.

Redirect Status Codes

CodeTypeWhen to use it
301PermanentWhen a page or domain has moved for good; when moving from HTTP to HTTPS
302TemporaryShort-lived redirects (maintenance page, campaign, redirect after login)
303TemporaryTo take the user to a result page after a form submission; the new request is always a GET
307TemporaryLike 302, but the request method (such as POST) is kept unchanged
308PermanentLike 301, but the request method is kept unchanged

Why Should a Redirect Chain Be Short?

Every redirect makes the browser open a new connection and send a new request, which adds waiting time before any page content arrives. On mobile connections this delay can reach hundreds of milliseconds per step. Search engines also spend crawl budget on long chains and stop following them after a point.

The healthiest setup is for every version of an address (http://, https://, with and without www) to reach the same final address in a single step. If you see an unnecessary intermediate step in the chain, update your server or CDN rule so that the first address points straight at the final one.

Frequently Asked Questions

What is the difference between a 301 and a 302 redirect?

A 301 is permanent and a 302 is temporary. With a 301, search engines index the new address in place of the old one and pass link value on to it. With a 302, the old address may stay in the index. Use a 301 (or 308) for domain changes, moving to HTTPS or any permanent page move.

How many redirects are too many?

A single redirect is ideal; two steps (for example first to HTTPS, then to www) are acceptable. From three steps on, the page load is noticeably delayed. Googlebot follows at most 10 hops in a chain, and browsers give up with an error after about 20 redirects. This tool also follows up to 10 redirects.

What causes the "too many redirects" (ERR_TOO_MANY_REDIRECTS) error?

It usually happens when two rules redirect to each other: for example the server sends HTTP to HTTPS while a CDN or plugin in front of it sends HTTPS back to HTTP. www and non-www addresses pointing at each other create the same loop. This tool detects the loop and shows the step where the chain returns to an earlier address.

Does it also show JavaScript and meta refresh redirects?

No. The tool only follows redirects that the server makes with HTTP response headers (the Location and Refresh headers). JavaScript or <meta http-equiv="refresh"> redirects inside the page run in the browser, so they do not appear in this chain.