Why does this need a server, unlike most tools here?

Following someone else's redirect chain means fetching an arbitrary domain from scratch, which your browser blocks via CORS — so this check runs through Tool4U's own server, which follows each hop on your behalf. Nothing about the URL or its chain is logged or stored.

Why would I have more than one redirect?

Common causes: an HTTP→HTTPS redirect, a www vs. non-www redirect, a URL shortener, or a marketing/tracking link that hops through an analytics domain before the real destination — each is its own hop in the chain.

What happens if there are too many redirects?

The check stops after 10 hops and reports a redirect-loop error.

Redirect Chain Viewer

See every hop a URL redirects through before landing on its final destination.

URL

The URL is fetched from our server (an arbitrary cross-origin fetch isn't possible directly from your browser) — the target site sees this server's request, not your IP, and nothing about the check is stored.

Related tools

How it works

1
Enter a URL
Including the protocol.
2
Each hop is followed
Up to 10 redirects, in order.
3
See the full chain
Every intermediate URL and status code, plus the final destination.

FAQ

Why does this need a server, unlike most tools here?: Following someone else's redirect chain means fetching an arbitrary domain from scratch, which your browser blocks via CORS — so this check runs through Tool4U's own server, which follows each hop on your behalf. Nothing about the URL or its chain is logged or stored.
Why would I have more than one redirect?: Common causes: an HTTP→HTTPS redirect, a www vs. non-www redirect, a URL shortener, or a marketing/tracking link that hops through an analytics domain before the real destination — each is its own hop in the chain.
What happens if there are too many redirects?: The check stops after 10 hops and reports a redirect-loop error.