TLS Version Checker
See which TLS versions a server accepts (1.0 to 1.3), the cipher suite it negotiates and whether that cipher is strong, plus a quick check of its certificate.
What This Checker Does
- Orbit2x's server connects to the hostname and port you enter, offering the same TLS versions and cipher suites as a modern client, and records what the server chooses: TLS version, cipher suite and ALPN protocol (h2 means HTTP/2).
- With version testing on, it makes one more connection for each of TLS 1.0, 1.1, 1.2 and 1.3, allowing only that version, to see which ones the server accepts.
- It checks the certificate (trusted issuer, matching hostname, validity dates) using the same rules as the SSL certificate checker.
Findings are labelled OK, Fix or Note. Fix items are worth acting on; Notes are suggestions. Nothing here is a vulnerability scan.
TLS and SSL Versions
| Version | Published | Status |
|---|---|---|
| SSL 2.0 / 3.0 | 1995 / 1996 | Broken and prohibited (RFC 6176, RFC 7568). Should never be enabled. |
| TLS 1.0 | 1999 | Deprecated by RFC 8996 in 2021. Browsers stopped accepting it in 2020. |
| TLS 1.1 | 2006 | Deprecated by RFC 8996 in 2021, together with TLS 1.0. |
| TLS 1.2 | 2008 | Still secure when used with forward-secret AEAD cipher suites. Widely needed for compatibility. |
| TLS 1.3 | 2018 | Current version (RFC 8446). Faster handshake, and only strong cipher suites are allowed. |
PCI DSS hasn't allowed SSL or early TLS for protecting payment card data since June 2018. A sensible configuration for most sites today is TLS 1.2 and 1.3 only.
How Cipher Suites Are Rated
- Strong: all TLS 1.3 suites, and TLS 1.2 suites with ECDHE or DHE key exchange plus AES-GCM or ChaCha20-Poly1305 encryption.
- Legacy: RSA key exchange, which has no forward secrecy (a stolen server key can decrypt recorded traffic), or CBC-mode encryption, which has had padding-oracle attacks such as Lucky 13.
- Weak: RC4 (prohibited by RFC 7465), DES and 3DES (Sweet32), NULL, export-grade, anonymous or MD5-based suites.
The rating applies to the suite the server chose for a modern client. A server may still accept weaker suites for older clients; this checker doesn't list every suite the server accepts.
Turning Off Old Versions
nginx
ssl_protocols TLSv1.2 TLSv1.3;
Apache (mod_ssl)
SSLProtocol -all +TLSv1.2 +TLSv1.3
Reload the server and run the check again. Mozilla's SSL Configuration Generator produces complete, maintained settings, including cipher lists, for most web servers. If a CDN or load balancer terminates TLS, change the setting there instead.
Testing a Version Yourself
openssl s_client -connect example.com:443 -servername example.com -tls1_1 </dev/null
Replace -tls1_1 with -tls1, -tls1_2 or -tls1_3. A completed handshake means the version is accepted. Recent OpenSSL builds may refuse TLS 1.0 and 1.1 themselves; adding -cipher 'DEFAULT:@SECLEVEL=0' lets them try.
How the Check Is Made
The hostname you enter is sent to Orbit2x's server, which makes up to five TLS connections to it. No web page is requested and nothing is stored. Private and local network addresses are refused. See the privacy policy for general data practices.
Frequently Asked Questions
Is it safe to turn off TLS 1.0 and 1.1?
For public websites, almost always. Current browsers don't use them, and the clients that still need them are very old (for example Android 4.4 and earlier, and Internet Explorer 10 and earlier). If you run an API with older embedded or industrial clients, check your logs for the negotiated version before switching them off.
Why does my server negotiate TLS 1.2 instead of 1.3?
TLS 1.3 needs OpenSSL 1.1.1 or newer (or an equivalent library) and has to be enabled in the server configuration, for example ssl_protocols TLSv1.2 TLSv1.3; in nginx. A load balancer or CDN in front of the server can also be the part that's limiting the version.
What's the difference between this and the SSL certificate checker?
This page looks at the connection: which protocol versions are accepted and which cipher suite is chosen. The SSL certificate checker looks at the certificate in detail: trust chain, covered domains, expiry and fingerprint. Both run the same certificate checks, so they agree on whether a certificate is valid.
Why is my cipher suite rated Legacy?
Legacy means it still works but isn't the best option: either RSA key exchange, which has no forward secrecy, or CBC mode, which has had padding-oracle attacks. Prefer ECDHE with AES-GCM or ChaCha20-Poly1305. TLS 1.3 cipher suites are always rated Strong.
Does this test for vulnerabilities like Heartbleed or ROBOT?
No. It reports versions and the negotiated cipher, not every cipher the server accepts or implementation bugs. For a full audit, use a dedicated scanner such as SSL Labs' Server Test or testssl.sh.