Redirect Chain Fixer

Follow your redirect chain hop by hop. Detects loops and your stack — generates the exact config to fix ERR_TOO_MANY_REDIRECTS.

Try: www redirect chain  ·  3-hop redirect

Enter any URL — follows every redirect hop in real time
and generates the exact fix if a loop is detected.

Works with Cloudflare · Vercel · Nginx · Apache · Netlify

Or paste curl output

Run this in your terminal, then paste the output below:

curl -sIL --max-redirs 15 https://yoursite.com | grep -E "^HTTP|^Location|^location|^server|^cf-ray|^x-vercel"

See also: Redirect loop fix guide  ·  SSL Chain Visualizer

You might also need
⚖️Header Diff
Compare headers between staging and production
🔒HeadersFixer
Scan security headers and get stack-specific fixes
📋Pre-Launch Checklist
20 HTTP checks before you ship
Done with this tool?
20 HTTP checks before you ship — security, CORS, cache, redirects, staging.
Pre-Launch Checklist →
📖 HttpFixer Blog — fix guides, explainers, and references →

About Redirect Chain Fixer

What does Redirect Chain Fixer check?

Redirect Chain Fixer follows HTTP redirects from your URL in real time, recording each hop — status code, location header, and response time. It flags redirect loops, chains longer than 3 hops, and mixed HTTP/HTTPS redirects.

What causes ERR_TOO_MANY_REDIRECTS?

ERR_TOO_MANY_REDIRECTS occurs when the browser follows more redirects than its limit without reaching a final destination. Common causes include misconfigured Cloudflare SSL settings, conflicting redirect rules in Nginx and a CDN, or a redirect loop between www and non-www versions.

How many redirects are too many?

More than 3 hops is worth investigating. Each redirect adds a round-trip latency penalty. Browsers typically abort after 20 consecutive redirects. The ideal chain is a single 301 from HTTP to HTTPS with no further hops.

Is my URL stored or logged?

No. The redirect chain is followed via a stateless Cloudflare Worker. Your URL is not stored or associated with any account.