Enter a public HTTP or HTTPS address. You can omit https://.
DigestSEO · Free SEO Tools
URL Redirect Checker: See Every 301, 302 & Redirect Hop
Follow a public link through every HTTP redirect, up to 10 hops. Inspect 301, 302, 303, 307 and 308 status codes, detect loops and reveal the final URL. Free, no signup.
HTTP · 301 / 302 / 307 / 308
Redirect chain
0 Redirects
This URL does not return an HTTP redirect.
Last URL checked
Results come from DigestSEO's Cloudflare infrastructure using GET requests. Worker-origin fetches may bypass certain Cloudflare edge redirects, so an external browser can see a different chain. This checks HTTP responses, not JavaScript or meta-refresh navigation. It never opens a destination in your browser.
01 — 03
How does the URL redirect checker work?
DigestSEO requests each hop without automatically following redirects.
Inspect every status code, destination and Location header; spot loops and broken endpoints.
301 · 302 · 303 · 307 · 308
301 / 308
301 and 308: permanent moves. Confirm the target is the right replacement page.
302 / 307 / 303
302 and 307: temporary moves. A 303 explicitly switches clients to a GET request.
3xx → 3xx → 404
Multiple redirects add requests. A loop, a missing Location or a final 404 needs investigation.
URL redirect checker FAQ
What is the difference between a 301 and a 302 redirect?
A 301 announces a permanent move and a 302 indicates a temporary one. Google treats 308 like 301 and 307 like 302. Choose the code that reflects the intended move.
Why does a URL show 200 with no redirects?
A 200 response means that HTTP request returned content directly. A JavaScript redirect or meta refresh may still move a browser after the response, but this server-side checker cannot observe those.
Can this checker find redirect chains and loops?
Yes. It records each HTTP hop in order, stops when a URL repeats and caps the trace at ten redirects to avoid unbounded requests.
Is this tool free and does it check every URL?
It is free without an account for up to 20 single-URL checks per network address per UTC day. Only public HTTP(S) addresses are accepted; some sites block automated fetches or return responses that differ from a browser.