Where does this address really go?
Type a web address and we’ll follow each redirect one by one, then tell you in plain words whether http goes to https, whether www and the bare name agree, and whether the redirects are permanent. Free, no sign-up, and we don’t keep what you type.
Nothing checked yet
Your report shows up here: every hop with its status code, where the address ends up and what to change.
What this checks
- Every hop, with its status code, the address it sends you to and how long it took.
- Whether http moves to https, and whether anything moves you back to http.
- Whether each redirect is permanent (301, 308) or temporary (302, 303, 307).
- With all 4 versions, whether www and the bare name end up at the same address.
- Loops and chains of more than 10 redirects.
- A meta refresh in the final page. We report it but never follow it, and we never run JavaScript.
Each hop is one GET request to port 80 or 443 of a public address, checked again before every hop. Private addresses, other ports and bare IP addresses are never contacted.
What we keep
Only a daily count of how many checks ran and how they ended. Not what you typed, not your address, no cookies.
Questions people ask
What’s the difference between a 301 and a 302 redirect?
A 301 says the page has moved for good: browsers remember it and search engines move the old address’s standing to the new one. A 302 says the move is temporary, so they keep the old address. 308 and 307 mean the same, but keep the request method.
Should my site use www or not?
Either works. What matters is choosing one and redirecting the other to it with a 301, so every visitor and search engine ends up at one address. Test all 4 versions to check.
Why does the checker start with http://?
Many visitors and old links still use http. Starting there shows whether the site upgrades them to https. Type https:// yourself to start from the secure address instead.
What is a redirect loop?
Two or more addresses that keep sending visitors to each other, so the page never loads. It often happens when a host and a CDN each have their own rule for www or https. Browsers stop after a few rounds and show an error.