Cost
Free
Hops
Up to 10
/ Free tool

Redirect checker

Paste a URL and the checker requests it, then follows each redirect itself, so you see every hop: the status code (301, 302, 307, 308), the Location it points to, and the final answer at the end of the chain. It names loops, chains longer than one hop, redirects from HTTPS back to HTTP, temporary redirects used for permanent moves, and pages that are down.

Status and headers only, up to ten hops. Nothing is stored.

/ Redirect guide

What each status code means, and what a clean redirect looks like

A redirect is the server answering "not here, over there". Done well it is one hop with the right code. Done badly it is a chain of four, a loop, or a temporary redirect that search engines keep treating as temporary.

How to read the result

Each row is one answer from a server, in order. A 3xx row carries a Location header, which is where the next request goes. The last row is the final answer: 200 means a page was served, 4xx means the address is wrong or refused, 5xx means the server failed. The time shown is the whole trace from our server, not a speed test of your site.

The checker sends an ordinary GET with no cookies, reads only the status and headers of each answer, and stops after ten redirects. On the final page it reads the start of the HTML to spot a meta refresh, which is a redirect done in the page instead of by the server.

301, 302, 307 and 308

RFC 9110 defines the redirect codes. 301 Moved Permanently and 308 Permanent Redirect say the resource has a new permanent address. 302 Found and 307 Temporary Redirect say it lives somewhere else for now. 303 See Other sends the client to a different resource, usually after a form is posted. With 307 and 308 the client must not change the request method; with 301 and 302 a client may change POST to GET, for historical reasons.

For search, the difference matters. Google's documentation says its systems treat 301 and 308 as a strong signal that the redirect target should be indexed, and 302 and 307 as a weak one. A move from http:// to https://, or from the bare domain to www, is permanent and should use 301 or 308.

Chains: why one hop is the target

A chain happens when redirects are added one at a time over the years: http to https, then the bare domain to www, then an old path to a new one. Every hop is another request and another wait before the page starts loading, and crawlers give up eventually: Google's crawlers follow up to 10 redirect hops by default.

The fix is to point every old address straight at the final one. If http://example.com/old goes through three hops to https://www.example.com/new, change the first rule so it answers with the last address directly. Internal links, canonical tags and sitemaps should use the final address too, so they never start a redirect at all.

Redirect loops

A loop is a chain that comes back to an address it already visited, so it never ends. RFC 9110 says a client should detect and intervene in cyclical redirections, which is why browsers stop and show an error such as too many redirects. MDN notes that a loop can be spread over several servers, so no single one of them sees it.

Common causes are two rules that undo each other, such as one adding a trailing slash and another removing it, or a proxy or CDN that talks to the origin over plain HTTP while the origin redirects every HTTP request to HTTPS. Read the hops above: the address that repeats tells you which two rules are fighting.

Is the site down, or just down for me?

This check runs from our server, not from your network, so it is a second opinion. If the trace ends in a 200 here but the site will not load for you, the problem is likely on your side: DNS cache, a local network or a browser extension. If it ends in a 5xx, or nothing answers at all, the server or something in front of it has a problem for everyone who reaches it the way we do.

A 403 can mean the site refuses automated clients rather than people, so treat a 403 here as a hint and check in a browser too. Google's documentation notes that persistent 5xx answers make its crawlers slow down and eventually drop the URLs from the index, which is why an outage that lasts days costs more than the days themselves.

Meta refresh and JavaScript redirects

A redirect can also be written into the page: a meta refresh tag in the HTML, or a script that sets window.location. MDN says HTTP redirects are the best way to redirect, and to use them and not add meta element redirects when possible. Page-level redirects only work for clients that read the HTML or run the script, and they run after the page has already been downloaded.

If the checker finds a meta refresh on the final page, it shows where it points. Replacing it with a server-side 301 or 308 is usually a one-line change in the server or CDN configuration.

/ Questions

Questions people ask

What is the difference between a 301 and a 302 redirect?
301 says the page has moved for good; 302 says it is somewhere else for now. Search engines treat a 301 as a strong signal to index the new address and a 302 as a weak one. Use 301 or 308 for permanent moves, 302 or 307 only when the original address will come back.
How many redirects are too many?
More than one is worth fixing. Each hop adds a request before the page loads, and Google's crawlers follow at most 10 hops by default. This checker stops at ten too.
How do I fix "too many redirects"?
Find the address that repeats in the chain above; the two rules that send traffic back and forth are the ones that produce those hops. A frequent cause is a CDN reaching the origin over HTTP while the origin forces HTTPS. Make one place responsible for the HTTPS redirect and remove the other rule.
Is a site down if the checker gets an error?
A 5xx answer or no answer at all from our server means it is down for at least some visitors. A 403 may only mean the site blocks automated clients. If the trace ends in a 200, the site answers and the problem is more likely on the visitor's side.
Does the checker follow meta refresh or JavaScript redirects?
It reports a meta refresh on the final page and shows its target, but does not follow it, and it does not run JavaScript. HTTP redirects are followed hop by hop, up to ten.
Is the result stored?
No. The URL is fetched when you ask, the result is returned to this page, and nothing is saved.
/ Sources

Where each statement comes from

Checked against the sources on .