Redirect Checker

The check shows the full chain of hops from the address you enter to the final page: the status code of each step, whether it is permanent or temporary, the address, and the time. The chain unfolds up to ten steps.

Besides response headers, the tool detects meta refresh and script-based redirects. Those steps are invisible in headers, so checkers that read only headers miss them. For a permanent move, a server-side 301 is the safer option.

Canonicalizing mirrors

Four variants of the site root are checked separately: with and without https, with and without www. You can see whether all four converge on a single address. If they diverge, the home page ends up with duplicates.

What the tool flags in its output

A temporary 302 where a move calls for a permanent 301. Loops. Chains that are too long. A hop from the secure protocol back to plain http.

Batch of addresses

Up to 200 addresses can be checked in one run: for each one you get the chain of codes, the number of hops, and the final address. The tool queries a single site no more than once per second. Results can be exported to CSV.