Redirect checker: follow a URL hop by hop
Paste up to 10 addresses, one per line. For each one you get every redirect on the way, its status code and where it points, and what the address finally answers.
- 301http://harbor.example/docs
- 308https://harbor.example/docs
- 301https://www.harbor.example/docs/
- 200https://www.harbor.example/docs/latest/
Reading the result
Each line is one request. A 3xx answer sends you to the address in its Location header, and the next line is that address. The last line is what a reader finally gets.
| Code | What it means for a link |
|---|---|
301, 308 | Moved for good. Update links to the new address. |
302, 307 | Moved for now. Fine for logins and A/B tests, wrong for a page that moved for good. |
404, 410 | Gone. Google treats both the same way. |
5xx | The server failed. Check again later before you change the link. |
999, 429, a challenge 403 | A bot wall answered, not the page. It usually works in a browser. |
More than one redirect is a chain. It still works, but every hop adds a round trip, and Google stops after 10. If the addresses start repeating, the result says it’s a loop: the page never loads, and browsers show “too many redirects”. Redirect chains and loops explains how to cut a chain to a single hop and how to break a loop, and why checkers see 403 and 429 covers bot walls.
Find where a short link goes
Paste a short link, a tracking link from an email or an ad, and the last line is where it lands. The request comes from our server, so you see the destination without opening the link in your own browser. That helps when you don’t trust a link, or when you want the real address to link to instead of the short one.
The checker follows the redirects a server sends: a 3xx answer with a Location header. Some pages forward you with JavaScript or a <meta http-equiv="refresh"> tag instead. For those, the last line is that forwarding page with a 200, and only a browser will show you the rest. The request also carries no cookies, so a redirect that depends on a login, your country or your device can end somewhere else for you.
Check an HTTP to HTTPS redirect
Paste the http:// address of a page, and the www or non-www form you don’t use. Each one should reach the final address in a single permanent redirect:
301 http://example.com/pricing
200 https://example.com/pricingTwo hops, such as http to https and then to www, is a chain made of two rules that each fire on their own. Merge them so every variant goes straight to the final address. Flattening chains at the server has the rules for nginx, Apache, Cloudflare, Netlify and Vercel. A 302 or 307 on the first line means the move is marked temporary; for https it should be a 301 or 308. The result also notes a plain http:// hop in the middle of a chain, where the redirect can be read or changed on the way.
More than 10 addresses
The bulk URL checker takes up to 100 at once. For each one it shows the first status code and the last, where the redirects end, and how many there were, with a CSV you can sort. To check every link on a site rather than a list, run the free broken link scan. Moving a site? Checking redirects after a migration walks through the whole list.
