Free Tool
Redirect Checker
Trace the full HTTP redirect chain for any URL. See every hop, status code, Location header, and response time. Free, no signup required.
What You Get
Here's an example of a redirect chain this tool reveals. Try it above with any URL.
Redirect Chain Complete
http://example.com — 2 redirects to final destination
http://example.com
Location: https://example.com
https://example.com
Location: https://www.example.com
https://www.example.com
Final destination — Total time: 203ms
The redirect chain shows every hop from the initial URL to the final destination. Each hop displays the HTTP status code (301 for permanent, 302 for temporary), the Location header that tells the browser where to go next, and the response time for that individual hop.
In this example, the URL goes through two redirects: first from HTTP to HTTPS (enforcing a secure connection), then from the bare domain to the www subdomain. This is a common and healthy redirect pattern. Chains with more than 3 hops may indicate misconfiguration and can slow down page loads.
How It Works
Enter URL
Type any URL you want to trace. We'll follow every redirect from the starting point.
We Follow the Chain
Our server follows each redirect hop, recording the status code, Location header, and response time.
See Every Hop
View the complete redirect chain from start to finish, with every status code, header, and timing detail.
HTTP Redirect Glossary
The terms that show up in any redirect chain — explained without the spec-speak.
301 vs 302
301 = permanent (search engines transfer link equity, browsers cache aggressively). 302 = temporary (search engines keep the old URL, browsers do not cache). Mixing these up is one of the most common SEO mistakes.
307 and 308
Modern method-preserving versions. 307 = temporary like 302 but the request method survives. 308 = permanent like 301 but method-preserving. Use these for API endpoints.
Location header
The HTTP response header that tells the client where to go next. Can be absolute (https://...) or relative (/new-path). The browser follows it automatically when paired with a 3xx status code.
Redirect loop
A→B→A or any chain that returns to a URL it has already visited. Browsers give up after ~20 hops and show ERR_TOO_MANY_REDIRECTS. Common causes: HTTP→HTTPS rule plus an HTTPS→HTTP rule, or trailing-slash mismatches.
Canonical URL
The single URL you want search engines to treat as authoritative. Redirects help enforce this — bare-domain → www, HTTP → HTTPS, /path/ → /path. The canonical URL should always be the final destination, not an intermediate hop.
Link equity (PageRank)
The SEO value passed from one page to another via a link or redirect. 301 redirects pass nearly all of it. 302 redirects historically passed less, though Google has narrowed that gap. Each extra hop in a chain still dilutes equity slightly.
Redirect Status Codes & Common Issues
What each redirect code means, when to use it, and the chain problems to watch for.
ERR_TOO_MANY_REDIRECTSRedirect loop detected
The server is redirecting in a circle — usually a misconfigured load balancer, a missing trailing slash rule, or a CDN-level redirect that conflicts with an origin redirect. Trace the chain above to see exactly where the loop closes.
301 Moved PermanentlyPermanent redirect
The original URL is gone for good. Search engines transfer link equity to the destination. Use this when content has permanently moved or for HTTPS upgrades.
302 FoundTemporary redirect (legacy)
The redirect is temporary — search engines keep the original URL indexed. Often misused where 301 was intended, which loses SEO equity. Some clients also change the request method on a 302; use 307 if you need to preserve POST.
307 Temporary RedirectMethod-preserving temporary redirect
Like 302 but guarantees the HTTP method is preserved. A POST stays a POST after the redirect. The right choice for temporary moves of API endpoints.
308 Permanent RedirectMethod-preserving permanent redirect
The modern equivalent of 301 that preserves the HTTP method. Recommended over 301 for API endpoints that accept POST/PUT/PATCH.
Mixed redirect chainHTTP and HTTPS hops together
If your chain bounces between HTTP and HTTPS along the way, you have a configuration problem. The redirect from HTTP should go directly to the final HTTPS URL — bouncing exposes a window for downgrade attacks and adds latency.
Frequently Asked Questions
Last updated · Built and maintained by exit1.dev — uptime, SSL, and domain monitoring with instant alerts.
Need Continuous Redirect Monitoring?
Stop checking manually. exit1.dev monitors your URLs automatically and alerts you when redirect chains change or break. 10 free monitors. Unlimited with Nano.
Start Free Monitoring