Redirect Chain Checker - Trace 301/302 Hops and Loops
Resolve short links and inspect redirect chains hop by hop: status codes, targets and timings, with loop and max-hop detection so you know exactly where a campaign link lands. Copy the result or export CSV.
The chain is fetched hop by hop by our server. Your target URL is relayed but never logged or stored.
About This Tool
The redirect chain checker requests the target hop by hop, reading response headers only, and lists every 301/302 with its status code, destination and timing so you know exactly where a short link lands.
It also detects redirect loops and max-hop overflow, re-validating each hop's target so redirects cannot be abused to reach private networks. Useful for campaign link audits, domain migrations and incident triage.
Key Features
Hop-by-hop detail
Every hop shows its request URL, status code, Location and elapsed time.
Loop detection
Repeated destinations are flagged immediately so infinite redirects are easy to spot.
Max-hop guard
Set a limit between 1 and 20 hops and receive the partial chain when exceeded.
Timing breakdown
Compare per-hop and total latency to find the slow redirect.
Result export
Copy the full JSON or export the hop table as CSV for your report.
When to Use It
Campaign link audits
Confirm an ad short link lands on the right page rather than the homepage or an error page.
Domain migration checks
Verify an old domain 301s directly to the new one instead of chaining multiple hops.
Incident triage
Diagnose login or payment callback loops and hop-limit failures.
How to Use It
- 1Paste the short link or any URL and optionally adjust the max hops.
- 2Click Analyze and wait for the server to walk the chain.
- 3Review the summary cards and hop table, paying attention to loop and overflow badges.
- 4Copy the JSON result or export the chain as CSV.
Frequently Asked Questions
Why does this need a server?
Browsers cannot read the Location header across origins, so a server must walk the chain hop by hop.
Can it reach private addresses?
No. Loopback, private and reserved ranges are rejected on every hop to prevent abuse.
How many hops are supported?
Between 1 and 20, defaulting to 10. When exceeded, the partial chain is returned.
Is there a rate limit?
Yes, 10 requests per minute per IP; you will be asked to retry after the limit.
