TinyPingTinyPing

Redirect Checker

Trace every redirect a URL goes through: each hop's status code, Location header and time, plus the final status. Loops, long chains and temporary redirects are flagged. Try http://example.com.

Common redirect problems

Redirect loop (too many redirects)

Two rules send the visitor back and forth, often HTTP to HTTPS on the server while a proxy such as Cloudflare talks to the origin over HTTP. On Cloudflare, set SSL/TLS mode to Full (strict) instead of Flexible. On WordPress, check that the site URL settings match the URL you serve.

Too many hops

http://example.com to https://example.com to https://www.example.com to /en/ is three redirects before any content loads. Each hop costs a round trip. Point every old URL straight at the final one.

No redirect from HTTP to HTTPS

The HTTP version still serves the page instead of redirecting. Visitors who type the domain without https stay on an unencrypted connection. Add a permanent redirect for every path on port 80.

302 used where 301 is meant

A 302 or 307 tells browsers and search engines the move is temporary, so they keep the old URL. For a permanent move (a new domain, HTTPS, a renamed page) use 301 or 308.

www and non-www both redirect, or neither does

Pick one hostname as canonical and redirect the other to it. A chain that goes www to non-www and back to www is a sign two systems (DNS host, CDN, app) each enforce a different rule.

Chain ends in an error

The redirects work but the final page returns 404 or 500. Usually the target path was renamed or the new server does not have the page yet.

How to check redirects

  1. Enter the URL to start from, for example http://example.com or an old page path.
  2. Click Trace redirects.
  3. Read each hop: status code, where it points and how long it took.
  4. Fix flagged loops, long chains or temporary redirects at their source.

What is an HTTP redirect?

A redirect is a response that tells the client to fetch a different URL. The server answers with a 3xx status code and a Location header, and the browser requests that new URL. If the new URL also redirects, you get a chain.

The status code says what kind of move it is. 301 Moved Permanently and 308 Permanent Redirect mean the old URL is gone for good, so browsers may cache the redirect and search engines move ranking signals to the new URL. 302 Found and 307 Temporary Redirect mean the old URL is still the real one. 307 and 308 also require the client to keep the same method, so a POST stays a POST.

Browsers stop following after a fixed number of redirects and show an error such as ERR_TOO_MANY_REDIRECTS. Long chains also slow down every visit that starts at an old URL, so keep each one to a single hop where you can.

GET / HTTP/1.1
Host: example.com

HTTP/1.1 301 Moved Permanently
Location: https://www.example.com/

When to use a redirect checker

Moving to a new domain

Check that old URLs land on the matching new page with a single 301, not on the home page or a 404.

ERR_TOO_MANY_REDIRECTS after enabling Cloudflare

See the loop hop by hop and confirm it is the Flexible SSL setting fighting a server-side HTTPS redirect.

Checking marketing and short links

Trace a campaign link or shortener URL to see every tracking hop it passes through before it reaches your page.

nginx or .htaccess changes

After editing rewrite rules, confirm HTTP goes to HTTPS and www to your canonical host in one step.

Check something else

Frequently asked questions

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

A 301 says the page has moved permanently, so browsers can cache it and search engines index the new URL. A 302 says the move is temporary and the original URL stays the one to index.

When should I use 307 or 308?

Use them when the request method must not change, for example an API endpoint that receives POST requests. 308 is the permanent version, 307 the temporary one.

How many redirects are too many?

One is ideal and two is acceptable. This checker flags chains of more than three hops. Browsers give up entirely after a fixed limit and show a too many redirects error.

Why does my browser still redirect after I removed the rule?

Browsers cache 301 and 308 redirects. Test in a private window or clear the cache. This checker does not cache, so it shows what the server sends now.

Does the checker follow JavaScript or meta refresh redirects?

No. It follows HTTP redirects (3xx with a Location header), which is what servers, crawlers and most HTTP clients rely on.

Catch broken redirects early

A server move or a new CDN rule can break redirects without anyone noticing. TinyPing checks the final page every 5, 15 or 30 minutes and alerts you when:

  • the redirect chain ends in an error
  • the site times out
  • an expired certificate breaks HTTPS
Start monitoring free for 7 days

US$6.99 a month or US$47 a year per 50 monitors, team members free. 7-day free trial, no card needed.

Want alerts in team chat? Follow the guide for Slack or Google Chat.