Redirect Chain Checker

Paste a URL and see every redirect it goes through: the status code, the Location header, the server and how many milliseconds each hop took, with long chains, loops and wrong 302s flagged.

See every redirect between a link and the page it lands on

Full URL or just the domain. Without http:// or https:// we start on http://, so you see the HTTPS redirect too.

Up to 10 hops
Time for every hop
Free, no sign-up

How the check works

1

Paste the URL

An old link, a short link, a campaign URL or just a domain.

2

We follow it hop by hop

Our server asks for each URL without following redirects automatically, then reads the status, the Location header and the time.

3

Fix what is flagged

Long chains, loops, temporary redirects that should be permanent and HTTPS that drops back to HTTP.

Old link going somewhere odd, or a page losing rankings after a migration? Paste the URL below. The checker follows it one hop at a time, up to 10, and shows the status code, where each step points and how long it took, then tells you what to clean up.

What this redirect checker shows you

Paste any URL and the tool asks for it the way a browser would, except it doesn't jump ahead when the server says go somewhere else. It stops, writes down what came back, and then makes the next request itself. So you get the whole chain, hop by hop: the status code (301, 302, 307, 308 and so on), the Location header that points to the next step, the server name, the IP it connected to, and the time each request took in milliseconds.

Most redirect checkers stop at a list of status codes. That's useful, but it doesn't tell you where the slow part is. Here every hop has its own timing, so when a short link takes two seconds to land you can see whether it's the shortener, the tracking domain in the middle or your own server that's dragging.

Why redirect chains matter

One redirect is normal. You moved a page, you switched to HTTPS, you dropped the www. Each of those is a perfectly good reason for a 301. Trouble starts when they pile up. A visitor clicks an old link to http://example.com/blog/post, gets sent to https://example.com/blog/post, then to https://www.example.com/blog/post, then to https://www.example.com/blog/post/ with a trailing slash. Four requests before the page even starts loading.

On a fast connection you barely notice. On a phone with a weak signal, each round trip can easily cost 200 to 500 milliseconds. Search engines notice too. Google and Bing follow a handful of hops, but every extra one uses crawl budget, and long chains are a common reason a moved page takes ages to pick up its old rankings. The tool flags any chain longer than two redirects, because that's usually the point where someone should point the first URL straight at the last one.

301 or 302: the one people get wrong

A 301 (or a 308) says the page has moved for good. Search engines move the ranking signals to the new address and eventually drop the old one. A 302 (or a 307) says it's temporary: keep the old URL in the index, it'll be back. That's right for a sale page, a login bounce or an A/B test. It's wrong for an HTTP to HTTPS switch.

The checker looks at each temporary redirect and compares the two addresses. If the only difference is the scheme, the www or a trailing slash, it's almost certainly a permanent change made with the wrong code, often the default of some plugin or framework. Those get flagged so you can change them to a 301. Other temporary redirects are listed as a note, not a problem, because sometimes they're exactly what you meant.

HTTP, HTTPS and the www question

If you type a bare domain without http:// or https://, the tool starts on plain http:// on purpose. That way you see the first and most important hop: does the site push visitors to HTTPS at all? A green line says it does. A warning says the final page is still served over plain HTTP, which every modern browser labels as not secure.

The worse case is a chain that goes from HTTPS back down to HTTP. It happens more often than you'd think, usually because a CDN talks to the origin over HTTP and the origin builds its redirect from what it sees. With HSTS turned on, that becomes a loop that locks visitors out. The tool calls it out as a failure.

It also watches the www. Going from example.com to www.example.com once is fine. Going www, then non-www, then www again means two rules are fighting each other, typically one in the server config and one in the CMS. Pick one version, put the redirect in one place, and the chain gets shorter.

Loops, dead ends and meta refresh

Redirects that end in a 404 usually come in groups, so once you've fixed one, run the page through our broken link checker to catch the rest.

A redirect loop sends you back to a URL you've already passed through. Browsers give up with a too many redirects error. The tool spots the repeat and stops right there, so you can see exactly which two URLs are bouncing off each other. It also stops after 10 hops no matter what, since nobody needs a chain that long.

A chain can also end badly: a 404 at the end of a redirect, a 500 from the new server, or a redirect with no Location header at all. Each one is shown with the step where it happened.

Some sites still redirect with a meta refresh tag inside the HTML, or with a Refresh header, instead of a real 3xx status. The checker reads the first few kilobytes of the final page to catch that and shows it as its own kind of hop, with the delay in seconds. It works, but search engines treat it as a weaker signal than a 301, and visitors see a blank page while it waits.

Headers, cookies and what gets shown

Open any hop to see its response headers. We only show the ones that are useful for redirect work: Location, Server, Cache-Control, Content-Type, Strict-Transport-Security, X-Robots-Tag, Link, Vary, CDN cache headers and a few more. If the server sets cookies, you'll see how many, but never their values. Some redirects hand out session or tracking cookies, and those have no business showing up on somebody else's screen.

Cache-Control on a redirect is worth a look. Browsers cache 301s hard, sometimes for months. If you set a permanent redirect by mistake, people who already followed it may keep getting sent to the wrong place even after you fix the rule. A short max-age on redirects you aren't sure about saves a lot of pain.

A few times this comes in handy

To get a list of old URLs to test after a migration, pull them out of your previous sitemap with the sitemap URL extractor.

After a site migration, run your most important old URLs through it and make sure each one lands on the right new page in a single hop. Before you print a QR code or send a newsletter, check that the link and its tracking redirects actually reach the page. When a short link from a partner looks fishy, see where it ends up without opening it in your own browser. When Search Console or Bing Webmaster Tools reports redirect errors, paste the URL here to see exactly which hop breaks. And when a page feels slow only for visitors who come from ads, check the click tracker chain in front of it.

How the check runs

Our server makes every request itself, one hop at a time. It never lets the HTTP client follow redirects on its own. Before each request it looks up the host name and refuses anything that points to a private, loopback or reserved address, then connects only to the address it just checked. It asks with HEAD first, which returns headers without the page, and only falls back to GET when the server refuses HEAD. Even then it stops reading after a few kilobytes. Each hop gets 8 seconds and the whole chain gets 25.

Only http and https on the standard ports 80 and 443 are followed, and URLs with a user name or password in them are turned away. Results are cached for 10 minutes, so if you just changed a redirect rule and still see the old chain, give it a few minutes. There's also an hourly limit on checks from each connection to keep the service fair. The User-Agent identifies itself honestly as a redirect checker, so a few sites that serve bots differently may show a slightly different chain than your browser gets.

Redirect Checker Questions

Similar tools to explore

Broken Link Checker

Scan web pages for broken hyperlinks, 404 status codes, redirect loops, and crawl errors.

Scan Now

Google Search Console Data Downloader

Export, format, and filter Google Search Console performance data for advanced SEO keyword analysis.

enable SEO Insights

Sitemap URL Extractor

Extract clean URL lists, last modified dates, and change frequencies from XML sitemaps and sitemap indexes.

Extract URLs

XML Sitemap Generator

Generate clean, schema-compliant XML sitemaps with custom lastmod dates and priority weighting.

Generate Sitemap

Sitemap Validator

Validate XML sitemaps and sitemap indexes against official sitemaps.org XML schema protocols.

Validate Sitemap

Website URL Extractor

Crawl any website and extract all internal links, external links, and image URLs. Export to TXT or CSV for SEO audits and analysis.

Extract URLs