Trace a complete redirect chain
Enter a public URL to see every 301, 302, 307, or 308 hop and the final HTTP response.
| Hop | Status | URL | Location |
|---|
Why redirect chains matter
A redirect is normal when a page moves or HTTP becomes HTTPS. A chain such as old URL → intermediate URL → another domain → final page adds latency and makes analytics, crawling, and link maintenance harder. The cleanest link points directly to the final destination.
Check health after the chain
Use the dead link checker for a batch of URLs, or inspect the final page’s social and SEO metadata with the Open Graph checker.
Frequently asked questions
Which redirect status codes does it show?
The checker records every 300-range response that supplies a Location header, including 301, 302, 303, 307, and 308, followed by the final response.
How many redirects are too many?
One intentional redirect is common. Several hops add latency and create more places for a chain to break. This tool stops after 10 redirects and reports the limit.
Why does this need a server request?
Browser CORS rules prevent a page from reliably reading cross-site response statuses and Location headers. Marqly’s server performs the limited check and returns only the chain.
Can it check private or local network URLs?
No. Localhost, private IP ranges, credentials, custom ports, and redirects toward blocked addresses are rejected for safety.