Audit

Free tool · No sign-up

Redirect and status checker

Updated 17 November 2026

Enter a URL or domain to see every redirect hop with its status code and destination, the final URL and its status, the total time, and plain-language flags: long chains, loops, a missing http to https upgrade, a www versus non-www split and temporary redirects where a permanent one belongs.

We follow the redirects of this address, plus its http:// version and its www / non-www twin, 3 chains at most. Chains are cut after 3 redirects. 20 checks an hour.

What it checks
Every redirect hop (up to 3), the final status, the http:// version and the www or non-www twin of your address.
What you get
Each hop as a record with its status code and URLs, then findings such as chains, temporary redirects and loops.
What it costs
Free, no sign-up. 20 checks per hour per IP address. We follow up to 3 redirects per address, 8 second limit.

Sample result

  • warn

    http:// version

    Send http:// straight to the final https address in one 301.

    http://example.com/ -> https://www.example.com/ (2 hops)
  • pass

    This address

    301 https://example.com/old -> https://example.com/new

A static example. Run the check above to see the records for your own address.

How do I use it?

Enter the old address and press Trace redirects. The tool follows every hop, shows each status code and the final URL, then tests the http:// and www or non-www versions. Use the result to collapse chains, so the first URL points straight at the final one with a single permanent 301 or 308.

  1. Type the old address you want to trace.

  2. Press Trace redirects. We follow each hop, then try the http:// and www or non-www versions.

  3. Read each hop's status code. 301 and 308 are permanent, 302 and 307 are temporary.

  4. Point the first address straight at the final URL, then run it again.

What does the redirect checker show?

For the address you enter, the checker requests it like a crawler, without running JavaScript, and follows each redirect by hand so you can see every step:

  • Each hop. The status code, whether it is permanent (301, 308) or temporary (302, 303, 307), and where it points.
  • The final URL and its status. The page that finally answers, and whether it returns 200 or an error.
  • Total time. How long the whole chain took from our server. Every extra hop adds a full round trip.
  • Flags. A chain longer than one hop, a redirect loop, no http to https upgrade, www and non-www ending on different URLs, and temporary redirects where a permanent one is expected.

Which redirect status code should I use?

A 301 and a 308 say the move is permanent, so search engines carry the old URL's signals to the new one and eventually drop the old address. A 302 and a 307 say it is temporary, so the old URL stays indexed. Use a temporary redirect for things that really are temporary, such as a login, a language choice or a short campaign, and a permanent one for HTTPS, a preferred host and any page you moved for good. The difference between 301 and 308 (and 302 and 307) is only that the newer codes keep the request method, which matters for forms.

Why do redirect chains and loops hurt?

Every hop is a separate request, so a chain such as http://example.com to https://example.com to https://www.example.com is slower than one direct redirect. Googlebot follows only a handful of hops, and some tools and apps give up sooner. A loop never ends: the browser shows "too many redirects". This checker stops after 3 redirects and tells you if it saw the same URL twice, which means a loop.

How do I check https and www versus non-www?

Your site should have one preferred address. The http:// version should redirect to https:// in one step with a 301, and www.example.com and example.com should both end at the same final URL. If they end at different URLs, search engines may treat them as two sites. The checker loads both variants to test this. If the counterpart host does not resolve at all, it tells you that instead.

What does it not do?

It sees only HTTP redirects. Redirects done with JavaScript or a meta refresh tag are not followed, and a site can answer differently to a browser than to our request, for example by country.

Frequently asked questions

What is a redirect chain?

A chain is when one redirect leads to another before the final page, such as http to https and then to www. Each hop adds delay. Point the first address straight at the final URL instead.

Should I use 301 or 302?

Use 301 (or 308) when a page has moved for good, and for http to https and www moves. Use 302 (or 307) only when the move is temporary, because search engines keep the old URL indexed.

Why does the checker stop after 3 redirects?

To keep the check fast and safe. A site that needs more than 3 redirects, or that loops, has a problem worth fixing, and the checker reports it with the hops it saw.

Does this follow JavaScript or meta refresh redirects?

No. It follows HTTP redirects only, which are what search engines and crawlers act on first.