Redirect & Canonical Chain Scanner
Visualizes multi-hop redirect chains, measuring latency per hop, protocol transitions (HTTP to HTTPS downgrades), cookie dropping behavior, and circular redirect traps that confuse search crawlers and degrade edge caching.
The Redirect & Canonical Chain Scanner follows step-by-step HTTP redirect sequences (301, 302, 307, 308) to detect circular loops, insecure protocol downgrades, and SEO canonical mismatches that divide link equity and drop Google search rankings.
Diagnostic Inspection Specifications
| What We Scan & Verify | Technical Standard / Threshold |
|---|---|
| HTTP Redirect Hop Sequence | RFC 9110 (Max 15-20 Hops Allowed) |
| Insecure Downgrade (HTTPS -> HTTP) | RFC 6797 (HSTS Enforced) |
| Declared Canonical Relation | RFC 6596 rel='canonical' Equality |
| Robots Meta Directives | W3C Robots Exclusion Index/Follow |
Architecture Comparison: OnChainScans vs Legacy Web Checkers
| Diagnostic Capability | OnChainScans (Zero-Telemetry) | Traditional Web Scanners |
|---|---|---|
| File Execution Boundary | 100% Client-Side WebAssembly | Uploaded to third-party server |
| Data Retention & Logs | Zero Logs (Discarded upon tab close) | Stored in database / analytics |
| Execution Engine | Live RFC / Public APIs / Raw Bytes | Simulated / heuristic estimates |
| Subscription / Paywall | 100% Free Forever (Open Tool) | Sign-up gating or credit limits |
How This Scan Works Under the Hood
The scanner initiates an HTTP request and follows 301, 302, 303, 307, and 308 redirect headers sequentially with an 8-second safety timeout, recording status code and latency per hop.
It resolves relative Location headers, monitors for circular redirect loops, and flags protocol downgrades (HTTPS to unencrypted HTTP).
Upon reaching the terminal URL, it parses the HTML payload for <link rel='canonical'> and meta robots directives to ensure search engine equity is correctly directed.
Frequently Asked Questions
How do multi-hop redirects harm SEO?
Googlebot will follow up to 5 redirect hops before abandoning a crawl. Long chains waste crawl budget and cause canonicalization confusion between URLs.
What is the difference between a 301 and a 302 redirect?
A 301 is a permanent redirect that transfers link equity and caching to the new URL. A 302 is a temporary redirect where search engines retain the original URL in index rankings.
What happens if a redirect downgrades from HTTPS to HTTP?
A downgrade exposes query parameters, session tokens, and traffic to plaintext interception over the network, triggering browser security warnings.
What technical standards does this tool enforce?
This tool strictly validates structures against official IETF RFCs, ISO standards, NIST guidelines, and W3C specifications without relying on simulated or mock heuristics.
Related Web, SEO & Network Chains Instruments
View all in categorySSL Certificate Chain Scanner
Dissects the complete X.509 certificate chain from leaf to root authority. Evaluates OCSP stapling, Certificate Transparency (CT) logs, and weak cipher suites.
Dangling CNAME & Subdomain Takeover Scanner
Scans DNS CNAME records for vulnerable pointers to decommissioned AWS S3, GitHub Pages, Vercel, Heroku, or Azure endpoints vulnerable to malicious takeover.
CORS & API Preflight Chain Debugger
Simulates cross-origin OPTIONS requests with custom Origin and Header pairs. Detects catastrophic 'Access-Control-Allow-Origin: *' configurations paired with credentials.