Redirect checker

What this redirect checker does

The tool requests the address you enter and follows each redirect one step at a time, recording the status code and location of every hop until it reaches a final page or a limit. You get the full chain, not just the end, which is what you need to find loops, double hops, and http-to-https-to-www detours.

Requests go through the same validated fetcher that Vector uses: public http and https only, private and internal addresses refused, every hop re-checked, and a cap on redirects and response size.

Why redirect chains matter

Each hop is a round trip before the visitor sees anything, and search engines pass slightly less signal through every extra redirect. Two hops are common after a migration, for example http to https and then non-www to www. The fix is to redirect straight to the final address in one step and to update internal links so they point at the destination directly.

Reading the status codes

301 and 308 are permanent and are the right choice for moved pages. 302 and 307 are temporary and tell search engines to keep the old URL indexed. A 200 at the end means the chain resolved. A 404 or 500 at the end means the redirect points at a broken page.