Redirect Checker
Paste a URL to follow it hop by hop. You will see every redirect, the status code at each step and where the chain finally ends.
- Web & SSL
- Live check
- Free, no sign-up
- Results are not published
Run Redirect Checker
At a glance
- What it checks
- Follow a URL hop by hop and see every redirect, status code and final destination, with loop detection.
- Data source
- Each redirect hop requested and validated before it is followed.
- Freshness
- Live check; results are cached for up to 5 minutes
- Limits
- JavaScript or meta-refresh redirects inside pages are not executed. Methodology
- Cost
- Free, no account needed
Understanding the result
How the chain is followed
The checker requests the URL you enter and, whenever the response is a redirect, reads the Location header and requests the next address. Relative locations are resolved against the current URL. If you enter a URL without a scheme, http:// is assumed, which is useful for testing how a bare address behaves.
Each hop is listed with its URL, status code, IP address, HTTP version and response time. Following stops when a non-redirect response arrives, when the same URL appears twice (a loop), when a redirect points to an unsupported target, or after 10 redirects.
Understanding the result
The main finding is a PASS when the chain ends in a normal response, and shows the number of redirects and the final status code. It is a FAIL if the chain loops, exceeds the redirect limit, points to a blocked address or uses an invalid redirect.
Additional findings help you tidy the chain:
- More than three redirects (WARNING): each hop costs a round trip, which is noticeable on mobile connections.
- HTTPS to HTTP downgrade (WARNING): a hop sends the visitor from a secure URL to an insecure one, exposing the rest of the journey.
- Temporary redirects (INFO): the chain contains 302, 303 or 307 responses. That is fine for short-term moves, but permanent moves should use 301 or 308 so browsers and search engines update their records.
Common redirect mistakes
- Chains that grow over time:
http://example.comtohttps://example.comtohttps://www.example.comtohttps://www.example.com/en/. Point each old address straight at the final one. - Loops: two rules sending traffic back and forth, often between a CDN setting and a server rule, or between
wwwand the bare domain. - Lost paths: a site migration that sends every old URL to the new home page instead of the matching page.
- Query strings dropped: tracking parameters or search terms that disappear during the redirect.
For a quick overview of a hostname's HTTPS setup rather than a specific URL, use the HTTP Status & HTTPS Checker.
Limits and safety
Only http and https URLs on ports 80 and 443 are accepted, and credentials in URLs are not allowed. Every hop is resolved and checked before it is requested, so a redirect that points to a private or internal address is stopped and reported rather than followed. Response bodies are not downloaded. Redirects performed by JavaScript or HTML meta refresh tags happen inside a browser, so they are not visible to this tool.
Frequently asked questions
Why doesn't the tool follow my JavaScript redirect?
JavaScript and meta refresh redirects require loading and running the page, which this tool deliberately does not do. Only HTTP-level redirects with a Location header are followed.
How many redirects are too many?
There is no strict rule, but one redirect is ideal and more than three is a sign the chain should be simplified. Browsers give up after a much larger number, and this tool stops at 10.
Is a 302 bad for SEO?
Not in itself. Search engines treat a long-lived 302 much like a permanent redirect over time, but using 301 or 308 for permanent moves states your intent clearly and avoids ambiguity.
Why did the chain stop at a "blocked" hop?
The redirect pointed to an address in a private or reserved range, such as a local network. For security, the tool never sends requests to those destinations.