HTTP Redirect Checker — Trace Any URL Chain

An HTTP redirect (301, 302, etc.) tells the browser to go to a different URL. This happens automatically and is often invisible to the user.

301 is a permanent redirect (search engines transfer link equity). 302 is temporary (original URL keeps its SEO value).

Google recommends no more than 3 redirects. Each hop adds latency and can lose link equity.

Yes — paste any shortened address and the whole chain is followed for you, so you see the final destination and every hop in between. The hops matter as much as the end: a link that passes through three different shorteners before landing somewhere is telling you something about who built it, and a chain that ends on a login page for a service you were not expecting is the shape a phishing link usually has. Two limits worth knowing. A shortener that decides what to show based on who is asking can send us somewhere different from where it would send you. And a link that has already expired resolves to the shortener's own error page, which is an answer in itself.

The chain is followed on our server, not in your browser, so the destination is never loaded on your machine and never gets to run anything there — that is the whole reason to check a link somewhere else before opening it. Addresses that match known-bad patterns are flagged in the result. What this cannot do is tell you a link is safe: a clean chain means nothing suspicious was found in the redirects, not that the page at the end is harmless, and a page can change between our request and your visit. Treat a clean result as one reason less to worry, not as permission.