Tools Redirect checker

Redirect checker

Follow a web address hop by hop: every redirect, its status code, where it goes and how long it took. Spots loops, https-to-http slips and chains that are too long.

What is a redirect?

A redirect is a page saying "this has moved, go here instead". Browsers follow it without asking. Sites use them to send http:// to https://, to choose between www and the bare domain, and to keep old links working after pages move.

What good looks like

One hop, straight to the final address, using a permanent redirect (301 or 308) for moves you mean to keep. If you type the bare domain over http, a good site takes you to its https address in one step, two at most.

Common mistakes

  • A loop: two settings that disagree, such as Cloudflare's Flexible SSL with a host that forces https. Browsers show "too many redirects".
  • A redirect that drops from https back to http, even for a moment.
  • Long chains (http → https → www → a trailing slash…), each one a little slower for visitors and search engines.
  • Temporary redirects (302) for permanent moves, so search engines keep the old address.

Questions people ask

What's the difference between 301 and 302?
301 (and 308) mean "moved for good": search engines move the page's ranking to the new address. 302 (and 307) mean "for now": they keep the old one. Use 301 unless the move really is temporary.
Why do you start at http:// when I type only the domain?
Because that's what happens when someone types your domain into a browser, and it shows whether you're sent to https.
Do you follow redirects to any address?
Up to 10 hops, on the normal web ports only, and never to private network addresses. We stop and tell you if a redirect points somewhere we don't check.