SSL/TLS Deep Analyzer
A passive, single-connection TLS assessment — certificate validity, hostname and SAN coverage, chain trust, key strength, signature algorithm, the negotiated protocol and cipher, HTTPS redirect and HSTS — with a documented score and a downloadable PDF.
This is a passive, single-connection analysis. It opens one TLS handshake and reads what the server presents. It does not probe the full protocol/cipher support matrix, is not a penetration test, and never attempts to exploit anything. Checks it can't observe (like whether legacy protocols are disabled) are marked Not Verified rather than assumed.
The URL is sent to Virtual Venture's server to perform the handshake. We don't store the URL or results. Private/internal addresses are refused.
About this tool
What it checks
- Certificate validity: expiry date, not-yet-valid, and renewal headroom
- Certificate identity: hostname / SAN coverage and chain trust
- Certificate cryptography: public-key strength and signature algorithm
- The TLS protocol version and cipher negotiated for this connection
- HTTP → HTTPS redirect behaviour
- HSTS header presence, max-age, and includeSubDomains
How it works
- 1You enter an HTTPS URL; it is sent to Virtual Venture's server (SSRF-hardened, refuses private hosts).
- 2The server opens one TLS handshake to a validated public IP with your hostname as SNI.
- 3It reads what that single handshake and the served certificate/chain reveal — nothing is probed or exploited.
- 4Facts observed are marked Measured; anything a passive check cannot prove is honestly marked Not Verified.
Example output: Overall 100/100 (Excellent) — valid Let's Encrypt certificate, hostname matches, TLS 1.3 negotiated, HSTS max-age 1 year; 'legacy protocols disabled' shown as Not Verified because a passive check cannot prove a negative.
Frequently asked questions
No. This is a passive, single-connection analysis. It opens one TLS handshake, reads the certificate and chain the server presents, and records the protocol and cipher negotiated on that connection. It does not probe every protocol and cipher the server might accept, and it never attempts to exploit anything.
Confirming that old protocols (SSLv3, TLS 1.0, TLS 1.1) are disabled requires deliberately attempting to connect with each of them — many handshakes. A passive single-connection tool cannot prove a negative, so we honestly mark that check Not Verified and point you to an active scanner rather than guessing a pass.
Six categories: Certificate Validity, Certificate Identity & Trust, Certificate Cryptography, TLS Protocol & Cipher, HTTPS Redirect, and Transport Hardening (HSTS). Each category is scored from documented per-check rules (earned ÷ assessable × 100); checks we couldn't observe are excluded rather than counted as failures. The overall is the weight-weighted mean.
It means the chain did not verify against this analyzer's certificate-authority store, often because an intermediate certificate is missing from what the server sends. A specific browser or OS may trust a different set of roots. Sending the full chain (leaf + intermediates) usually resolves it.
No. For safety, the analyzer resolves and validates the target and refuses private, internal, loopback and cloud-metadata addresses. It only analyzes publicly reachable HTTPS hosts.
The URL is sent to Virtual Venture's server to perform the handshake. Running a check does not store the URL, certificate or results — only anonymous usage events. If you download the PDF report, we record the details you enter in the report form together with the tool, URL and score, to issue your report reference. The PDF itself is generated in your browser and is not uploaded.
Related services
Found this tool useful? Help keep it free.
Our tools have no sign-up, no ads and no paywall. A one-time contribution of any amount covers servers and funds new tools.