Redirect checker

Trace a URL hop by hop: every status code, every Location header, and how long each step took. Catches chains, loops, temporary redirects and HTTPS downgrades.

Redirect status codes at a glance

CodeTypeKeeps method?Use it for
301PermanentNo (POST may become GET)Moved pages, domain changes, HTTP→HTTPS
308PermanentYesPermanent moves of forms or APIs
302TemporaryNoShort-term moves, A/B tests
307TemporaryYesTemporary moves that must keep POST; also shown by browsers for HSTS upgrades
303See otherBecomes GETAfter a form submission

Keeping redirects healthy

  • After a migration, update internal links to the new URLs instead of leaning on redirects forever.
  • Collapse chains: http:// → https://www. should be one hop, not three.
  • Keep old redirects in place for at least a year; Google’s site-move guidance recommends keeping them as long as possible.
  • Never redirect every old URL to the home page. Google treats mass redirects to an irrelevant page as soft 404s.

Questions people ask

What does a redirect checker do?

It requests a URL without following redirects automatically, records the status code and Location header of each response, then follows the Location to the next hop, until it reaches a final page, an error or the 10-hop limit. You see the whole chain, not just the destination.

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

301 (and 308) mean the move is permanent, so search engines should index the new URL and transfer signals to it. 302 (and 307) mean temporary: the old URL is expected to come back. Google says it treats long-lived 302s like 301s eventually, but a 301 is the clear signal for a permanent move.

What is a redirect chain?

Two or more redirects in a row, e.g. http://example.com → https://example.com → https://www.example.com → https://www.example.com/home. Each hop adds a network round-trip. Fix by making the first URL redirect straight to the final one.

What is a redirect loop?

A chain that returns to a URL it has already visited, so it never ends. Browsers show “too many redirects”. The checker stops as soon as it sees a repeated URL and marks it as a loop.

Can it check JavaScript or meta refresh redirects?

No. It reports HTTP-level redirects (3xx status codes with a Location header), which are the ones search engines handle most reliably. Meta refresh and JavaScript redirects only run in a browser.

Can I use it as an HTTP status checker?

Yes. Any URL returns its status code even if it does not redirect. To check the status of many links on one page at once, use the broken link checker.

More link tools on this bench