A browser hides redirects; a search engine counts every one. This follows an address from this server, station by station, without trusting any client to merge the hops: status code, Location header, time per hop, and the server that answered. With the variants switch it then fetches http and https, with and without www, and reports whether all four end on one canonical address. The final page is read for meta refresh, JavaScript redirects and a canonical link that points elsewhere.
Up to five redirect chains of at most ten hops each are fetched from this server, with a plain GET and no cookies. Requests to private networks, loopback and link-local addresses are refused at every hop. The query is protected by reCAPTCHA v3; the calling IP address and the target are stored for one hour to limit the rate.
Limit worth knowing: only HTTP redirects are followed. A meta refresh or a JavaScript redirect on the final page is reported, not followed. Redirects that depend on cookies, language headers or a mobile user agent may differ from what this server sees.