🔀 Redirect Chain Checker

Trace Every Redirect Instantly 🔁

Follow URL redirects, inspect status codes, detect loops, review query handling, and understand SEO and performance impact — fetched and traced by our own backend, with SSRF protection re-checked on every hop.

🔗

⚡ Real backend trace 🔒 SSRF-protected, re-checked every hop 📈 SEO Friendly 🌐 HTTP / HTTPS Checks

Redirect Report 🛡️

Not scanned yet

Run a trace to see the redirect journey here

🔀 Total Redirects–

✅ Final Status–

⏱️ Total Time–

🔁 Loop Check–

Overall Score–

🔄 Preparing redirect-chain analysis…

🔗

Original URL

–Initial request

🌐

Final URL

–

🔀

Redirect Count

–Total hops

✅

Final Status

–

⏱️

Total Response Time

–All hops combined

🛡️

HTTPS Enabled

–Secure final connection

🧭 A. Redirect Journey

Run a trace to see each hop.

ⓘ Run a trace to see the outcome.Total Time: –

📊 B. Redirect Type Breakdown

ⓘ

301 Moved Permanently

302 Found

307 Temporary Redirect

308 Permanent Redirect

4xx Client Error

Loops Detected

Total Redirects0

💻 C. SEO & Redirect Health

Rule-based, from real signals

–

Chain Length–

–

Destination Quality–

–

HTTPS Consistency–

–

Parameter Handling–

⚙️ D. Technical Details

ⓘ

HTTP to HTTPS–●

WWW Canonicalization–●

Query String Preserved–●

Trailing Slash Consistency–●

HSTS Present–●

Canonical Target Match–●

Loop Detected–●

Mixed Redirect Types–●

💡 E. SEO Recommendations

🧾 F. Final Response Headers

Header	Value
Run a trace to see the final response headers.

🚀 G. Performance Snapshot

Real, measured

DNS Lookup Time–

TCP Connection Time–

TLS Handshake Time–

Redirect Time (Total)–

TTFB (Final)–

⏱ Total Load Time–

⚠️ H. Common Issues Detected

ⓘ

Run a trace to check for common issues.

HOW IT WORKS

A Real Redirect Trace, Not a Demo

Trace follows the URL's redirect chain from our own server with automatic redirects disabled, reading each Location header and requesting the next hop manually — up to 10 hops. Every hop is re-validated against the same SSRF protections used across our tools (private/loopback/link-local/metadata addresses are always rejected), because a safe public URL can redirect into an internal address partway through the chain. Loops are detected by tracking visited URLs. A real DNS + TCP + TLS timing probe against the final destination powers the performance snapshot; nothing is randomly generated.

COMMON QUESTIONS

Redirect Chain Checker FAQ

Why re-check safety on every hop?

A redirect can point anywhere, including into a private network. Checking only the first URL wouldn't catch a chain that redirects into localhost or an internal address partway through, so every hop is independently validated before it's fetched.

How many redirects will it follow?

Up to 10 hops by default. If the chain is still redirecting at that point, the scan stops and says so honestly rather than following indefinitely.

Where do the DNS/TCP/TLS timings come from?

From a real, separate connection-timing probe against the final destination — not an estimate. If a phase can't be measured (for example, TLS timing on a plain-HTTP site), it's left blank instead of guessed.

Can I check internal or private URLs?

No. Requests that resolve to localhost, private IP ranges, link-local addresses or cloud metadata endpoints are rejected before any fetch happens, at every hop.

Is my scanned data stored?

No. Each scan runs live for your request only. The exported report is generated and downloaded entirely in your browser.