URL Redirect Checker

Trace a URL's full 301/302/307/308 redirect chain to its final destination.

Follows each hop (up to 15) and re-checks every host for safety. Nothing is stored.

Related tools

HTTP HeadersView a URL's response headers and follow its redirect chain.Security HeadersGrade a site on HSTS, CSP, X-Frame-Options and other security headers.SSL CertificateInspect a site's TLS certificate: issuer, validity, SANs and expiry.Meta Tags CheckerInspect a page's title, meta description, canonical and Open Graph / Twitter Card tags.

Frequently asked questions

What does the redirect checker show?

It follows a URL through every HTTP redirect — 301, 302, 307 and 308 — and lists each hop with its status code until it reaches the final page, so you can see the complete chain.

What is the difference between a 301 and a 302?

A 301 is a permanent redirect and passes SEO ranking signals to the destination; a 302 (and 307) is temporary and generally does not. Use 301 when a page has moved for good.

Why are long redirect chains bad?

Each hop adds latency and a chance of failure, and search engines may dilute or drop ranking signals across many hops. Aim to redirect straight to the final URL in a single step.

Does it follow HTTPS upgrades and www changes?

Yes. Redirects from http to https, or between the apex and www, appear as ordinary hops in the chain so you can confirm your canonical setup.

Is there a limit to how many redirects it follows?

It follows up to 15 hops and re-checks each host for safety. If a site loops or exceeds that, it reports the chain it saw rather than looping forever.