SSL Certificate Chain Scanner
Performs TLS 1.2/1.3 handshakes against any domain or IP. Flags incomplete trust chains (missing intermediates causing Android/Java failures), SHA-1 deprecations, CAA DNS records, and revocation statuses via CRL and OCSP.
The SSL Certificate Chain Scanner verifies the complete cryptographic trust hierarchy from your server's leaf certificate to trusted root Certificate Authorities. It identifies missing intermediate certificates, imminent expiration cliffs, and insecure cipher suites that trigger browser security warnings.
Diagnostic Inspection Specifications
| What We Scan & Verify | Technical Standard / Threshold |
|---|---|
| X.509 Leaf & Intermediate Chain | RFC 5280 / WebPKI CA/Browser Forum |
| Cryptographic Cipher Suite | TLS 1.3 RFC 8446 / AEAD Ciphers |
| Subject Alternative Names (SANs) | RFC 6125 FQDN Matching |
| Certificate Expiration Window | Minimum 15 Days Remaining |
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 executes a live TLS 1.3/1.2 handshake against target port 443 with SNI (Server Name Indication), inspecting the complete X.509 certificate chain transmitted by the remote host.
It validates the leaf certificate, expiration dates, Subject Alternative Names (SANs), public key bit-depth, and verifies intermediate certificate authority paths up to the trusted root anchor.
It audits cipher suites and reports the exact number of days remaining before certificate expiration cliffs.
Frequently Asked Questions
Why do some clients reject certificates that work in Chrome?
Desktop Chrome caches intermediate CA certificates previously encountered on other sites. Mobile apps, curl, and API clients do not, and will fail if the server omits intermediate certificates.
What are Subject Alternative Names (SANs)?
SANs list all hostnames, subdomains, and wildcard domains that a single certificate is cryptographically valid for.
Does an expired SSL certificate block all website traffic?
Yes. All modern browsers display full-screen security interstitials blocking users from accessing sites with expired or invalid certificates.
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 categoryRedirect & Canonical Chain Scanner
Follows every HTTP hop across 301, 302, 307, 308, and JavaScript meta-refreshes. Correlates HTTP status codes with rel='canonical' declarations to detect SEO leakage.
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.