Redirect checker — see every hop between a link and its destination.
Paste a URL to trace the whole redirect chain: each HTTP status code, where every hop points, how long it took, and where you finally land.
Check a URL
Live checkTurn any long URL into a short, trackable link.
Once the destination checks out, shorten it with click analytics by source, location and device, all in one dashboard.
What happens when a URL redirects?
A redirect is a server answering "not here — go there instead".
When a browser requests a page, the server can reply with a status code in the 3xx range and a Location header. The browser then requests the new address automatically, and the visitor only sees the final page.
Redirects are everywhere: http:// to https://, the bare domain to www, a renamed page to its new URL, and every short link to its destination. Each hop costs a full network round trip, so long chains make pages slower and make links harder to debug.
This checker repeats that process step by step and shows you what each server said, which is exactly what you need when a link lands on the wrong page, a migration loses traffic, or a campaign link doesn't track.
Redirect status codes
The four you will see most, and what each one tells clients.
| Code | Name | Meaning | Method preserved |
|---|---|---|---|
| 301 | Moved Permanently | The resource has a new permanent address. Clients and search engines should use it from now on. | Not guaranteed (POST may become GET) |
| 302 | Found | Temporary move. Keep using the original URL for future requests. | Not guaranteed (POST may become GET) |
| 307 | Temporary Redirect | Temporary move that must repeat the request with the same method and body. | Yes |
| 308 | Permanent Redirect | Permanent move that must repeat the request with the same method and body. | Yes |
Common questions
What is the difference between a 301 and a 302 redirect? +
A 301 says the move is permanent, so browsers and search engines can cache it and treat the new URL as the real address. A 302 says the move is temporary, so the original URL stays the one to use.
How many redirects are too many? +
There is no hard rule, but every hop adds a round trip. More than two or three hops is worth fixing, and browsers stop after about 20. This tool stops after 10 and tells you when it does.
Does this follow JavaScript or meta refresh redirects? +
No. It follows HTTP redirects, the ones sent in response headers. Redirects performed by JavaScript or by a <meta http-equiv="refresh"> tag happen after the page loads and aren't visible at the HTTP level.
Why does my URL work in a browser but fail here? +
Some sites treat server requests differently from browsers, for example by blocking unknown user agents, requiring cookies, or only answering from certain countries. The tool reports exactly what the server returned to our request.
Can I check internal or localhost URLs? +
No. The check runs from our servers, so only publicly reachable addresses can be tested. Private IP ranges and localhost are blocked on purpose.