Redirect Checker
Trace every hop in a URL's redirect chain, from the first request to the final page.
What this tool does
Follows a URL's full redirect chain and lists every hop — the URL requested, the status code it returned, and the Location header it pointed to — up to the final response.
How to use it
Enter a public URL. The checker requests it, and for every 3xx response with a Location header, requests the next URL in turn, recording each hop, until it reaches a non-redirect response or 10 hops.
Example
A URL that goes through an HTTP-to-HTTPS redirect and then a www-prefix redirect shows two hops in the chain, each with its own status code, before the final 200 response.
Validation and safety
Every hop in the chain is checked against the same rules as a single request: only http/https, and private, internal or cloud-metadata addresses are blocked at each step, not only for the first URL — a redirect cannot be used to reach an internal address the direct request would have been blocked from reaching.
How to interpret the result
A short, clean chain (ideally zero or one hop) is generally better for SEO and page-load speed than a long chain — each hop adds latency and search engines may not follow very deep chains reliably.
Limitations
The check stops after 10 hops and flags this as a possible redirect loop rather than following indefinitely. It reflects one request at one moment, uses a generic bot user agent, and does not simulate a real browser's cookie or JavaScript-based redirect handling.
Privacy
This tool sends the address you enter to Quiklio's own server, which makes the network request on your behalf — the target address is not sent to any third party beyond what a normal request to that address would reveal.
Frequently Asked Questions
- What does Redirect Checker do?
- Follows a URL's full redirect chain and lists every hop — the URL requested, the status code it returned, and the Location header it pointed to — up to the final response.
- Can this be used to probe internal or private addresses?
- Yes, this is blocked. Requests to localhost, private IP ranges and cloud metadata addresses are refused before any check runs, and the resolved IP is re-checked after DNS lookup to prevent bypassing this with a hostname that points to a private address at request time.
- Is the checked address shared with anyone else?
- This tool sends the address you enter to Quiklio's own server, which makes the network request on your behalf — the target address is not sent to any third party beyond what a normal request to that address would reveal.