Redirect checker
When you open an address, the site may send you on to another one: from http to https, from the bare domain to www, or from an old page to a new one. Each step is a redirect, and too many of them slow the page down or break it.
This tool follows the redirects one hop at a time and shows the status code, the next address and how long each step took. Type a full address such as http://example.com to test the step from http to https.
How to read the results
- 301 and 308 are permanent redirects. Search engines pass the old page’s standing to the new address.
- 302 and 307 are temporary redirects. Search engines keep the old address, so use them only for short-term moves.
- More than two or three hops usually means redirects are stacked on top of each other and can be merged into one.
- A loop means the address redirects back to itself, so the page never loads.
Questions
How many redirects are too many?
Browsers stop after about twenty, but each hop adds delay. Aim for one redirect at most between an old address and the final page.
Should http redirect to https?
Yes. Type the http version of your address here and confirm the first hop is a 301 to the https version.
Why does the chain end with a 403 or 429?
The final site may be blocking automated requests. That does not necessarily mean visitors are affected.
Related guides
More free tools
- DNS lookup
- HTTP header checker
- SSL certificate checker
- WHOIS and domain expiry
- MX record lookup
- Robots.txt checker
- Security headers checker
Results are a snapshot taken from our servers at the moment you ask, and can differ from what you see elsewhere. siteupdown.com tests public websites only. Spotted a problem?