About this tool
Each hop is requested separately; the tool reads the status code and the Location header, then requests the next address — up to 10 hops. Every destination is re-checked before it is requested, so redirects to private or internal addresses are not followed.
How to read the results
- 301 / 308 — permanent; search engines transfer ranking to the target. 308 keeps the request method.
- 302 / 303 / 307 — temporary; search engines keep the original URL indexed.
- Loops — the chain returns to an address already visited; browsers stop with "too many redirects".
- HTTPS → HTTP — a downgrade exposes the request; always flagged.
Best practice: one hop from any old or http:// address straight to the final https:// URL.
Limitations
- Only HTTP redirects (3xx + Location) are followed. JavaScript and <meta http-equiv="refresh"> redirects are not detected, because page bodies are not downloaded.
- Only ports 80 and 443 and public addresses are followed.
- Some sites redirect differently depending on the visitor's country, language or device.
Frequently asked questions
How many redirects are too many?
Keep it to one where possible. Each hop adds latency, and search engine crawlers stop following after a handful.
301 or 302 for moving to HTTPS?
Use 301 (or 308). The move is permanent, and you want search engines to index the https:// address.
Why does www and non-www matter?
Pick one as canonical and redirect the other to it in a single hop, keeping HTTPS throughout.
Why does the checker show a different result than my browser?
Browsers cache 301 redirects and HSTS, and may send cookies or a different language. This tool always starts fresh, like a first-time visitor.
What is a 301 redirect?
A permanent redirect; search engines move ranking to the new URL.
What is a 302 redirect?
A temporary redirect; the original URL stays indexed.
What causes "too many redirects"?
A loop, often between http/https or www/non-www rules.