TLS Scanner
Read the negotiated TLS protocol version, cipher suite, ALPN, and OCSP stapling, and flag downgrade-prone and deprecated configurations.
High9Medium5Low3Info5
High9 checks
- TLS Certificate ExpiryAsync check: opens a TLS connection to :443 and reports the certificate validity window, expiry, self-signing, and incomplete chains.
- Weak TLS Protocol VersionAsync check: reports whether the negotiated TLS protocol is TLS 1.2+ or older (TLS 1.0/1.1/SSLv3).
- RSA Key Size Below 2048 BitsThe TLS certificate uses an RSA key smaller than 2048 bits. Keys below this threshold are practically factorable with modern compute resources.
- Self-Signed Certificate in ProductionThe TLS certificate is self-signed (issuer equals subject with no trusted CA chain). Browsers display a hard error and require users to manually bypass the warning.
- Subject Alternative Name (SAN) MissingThe TLS certificate does not include a Subject Alternative Name (SAN) extension. Modern browsers and APIs only trust certificates that list hostnames in SAN. The legacy CN field is ignored.
- Expired Certificate in CA ChainOne or more intermediate or root certificates in the TLS chain have expired. An expired CA certificate in the chain causes strict verifiers to reject the entire chain even if the leaf certificate is still valid.
- Certificate signed with a broken hash algorithmA certificate in the chain the server presents is signed with SHA-1, MD5, MD2, or an ECDSA/DSA variant of SHA-1. The scan reads the signature algorithm OID out of the DER of each certificate the server sent, skipping the self-signed root.
- Certificate is not yet validThe certificate the server presents has a notBefore date later than the time of the scan, so it has not started being valid.
- Certificate requires OCSP stapling but none was stapledThe certificate carries the RFC 7633 TLS Feature extension requesting status_request. That is OCSP Must-Staple, and the handshake returned no stapled OCSP response.
Medium5 checks
- Plain HTTP Does Not Redirect to HTTPSAsync check: for an http:// target, opens a raw connection to :80 with redirect-following disabled and inspects only the first response. Reports when the server answers directly (or redirects to a non-HTTPS location) instead of redirecting straight to HTTPS.
- TLS Certificate Chain Missing Intermediate CertificateAsync check: opens a TLS connection and inspects the certificate chain the server actually sent (via the peer certificate's issuer-certificate links), independent of whether the connecting client's own trust store happens to already have the missing intermediate cached. Reports when the handshake verified successfully but the server sent only the leaf certificate.
- Negotiated cipher suite has no forward secrecyThe handshake settled on a static-RSA key-exchange suite at a protocol version below TLS 1.3. The session key is encrypted directly to the certificate's public key rather than derived from an ephemeral exchange.
- Weak ephemeral key exchange parametersThe handshake completed with an ephemeral key below a safe size for its key-exchange type. That is a finite-field Diffie-Hellman group smaller than 2048 bits, or an elliptic curve below 224 bits.
- Server still accepts TLS 1.0 or TLS 1.1A second handshake offering only TLS 1.0 and TLS 1.1 completed successfully against this host. That proves the server still accepts a deprecated version even when it prefers a modern one with a modern client.
Low3 checks
- Certificate validity period exceeds 398 daysThe leaf certificate's notBefore to notAfter window is longer than 398 days. That is the maximum the CA/Browser Forum Baseline Requirements have imposed on publicly trusted certificates since September 2020.
- Certificate serial number has too little entropyThe leaf certificate's serial number is shorter than sixteen hexadecimal digits. That is below the 64 bits of CSPRNG output the CA/Browser Forum has required since ballot 164 in 2016.
- Negotiated cipher suite uses CBC modeThe handshake settled on a CBC-mode cipher suite below TLS 1.3, rather than an AEAD suite such as AES-GCM or ChaCha20-Poly1305.
Info5 checks
- TLS 1.3 Not SupportedThe server does not offer TLS 1.3. Connections fall back to TLS 1.2, which lacks TLS 1.3's 0-RTT resumption, reduced round-trip handshake, and mandatory forward-secrecy-only cipher suites.
- ECDSA Key Size Below P-256The TLS certificate uses an ECDSA key on a curve smaller than P-256 (secp256r1). Curves below P-256 provide less than 128-bit equivalent security and should be avoided in new certificates.
- OCSP Stapling Not EnabledAsync check: opens a TLS connection requesting OCSP status (requestOCSP) and listens for a stapled OCSP response during the handshake. Reports when an otherwise validly-verified certificate has no stapled response.
- Certificate covers an unusually large number of namesThe leaf certificate lists more than fifty Subject Alternative Names on one key. A single certificate and a single private key therefore cover a large set of hostnames.
- Certificate carries no embedded Certificate Transparency SCTsThe leaf certificate contains no embedded Signed Certificate Timestamp list extension. That extension is the most common way a certificate proves it was submitted to public Certificate Transparency logs.
About the TLS checks
- What does the TLS category check?
- Read the negotiated TLS protocol version, cipher suite, ALPN, and OCSP stapling, and flag downgrade-prone and deprecated configurations. Protocol version, cipher suite, ALPN negotiation, OCSP stapling.
- How many tls checks are there?
- VulnRadar runs 22 checks in this category, ranging across high, medium, low, info severity.
- Do I need to install anything to run the tls checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the tls checks on your site
VulnRadar runs all 22 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.