Web & Dev

SSL/TLS Versions

SSL and TLS protocol versions — release dates, current status, and what to deprecate.

Protocol timeline

VersionReleasedStatusNotes
SSL 1.0never❌ Never releasedInternal Netscape design; flaws found before public release.
SSL 2.01995❌ Deprecated (2011)Numerous weaknesses; RFC 6176 prohibits use.
SSL 3.01996❌ Deprecated (2015)POODLE attack; RFC 7568 prohibits.
TLS 1.01999 (RFC 2246)❌ Deprecated (2021)BEAST-era weaknesses; removed from major browsers.
TLS 1.12006 (RFC 4346)❌ Deprecated (2021)Removed from major browsers.
TLS 1.22008 (RFC 5246)✓ AllowedStill common; minimum acceptable for most profiles.
TLS 1.32018 (RFC 8446)✓ Recommended1-RTT handshake, cleaner cipher list, 0-RTT (with caveats).

What the version changes in practice

The big practical difference between TLS 1.2 and 1.3 is the handshake. A full TLS 1.2 handshake takes two round trips before the application can send data; TLS 1.3 needs one (RFC 8446). On a connection with an 80 ms round-trip time, opening the TCP connection costs 80 ms, then TLS 1.2 adds 160 ms for a total of 240 ms before the first HTTP request goes out. TLS 1.3 adds 80 ms for a total of 160 ms. On a mobile link with 200 ms round trips the saving is 200 ms per new connection. Resumed sessions and connection reuse reduce the cost further.

Deprecation dates have a precise source. RFC 8996, published in March 2021, formally deprecated TLS 1.0 and 1.1. Earlier RFCs prohibited SSL 2.0 (RFC 6176, 2011) and SSL 3.0 (RFC 7568, 2015). “Deprecated” in an RFC means a compliant client or server must not negotiate that version, though old devices may still try.

Checking and configuring a server

  • Test a version with OpenSSL: openssl s_client -connect example.com:443 -tls1_3 shows whether the handshake succeeds. Repeat with -tls1_2 and -tls1_1; the last should fail on a modern server.
  • Allow TLS 1.2 and 1.3 only. Disabling 1.2 breaks older clients, while keeping 1.0 and 1.1 exposes known weaknesses and fails most compliance scans.
  • The certificate and the protocol version are separate things. People still say “SSL certificate”, but a certificate works with any TLS version the server enables.
  • TLS 1.3 0-RTT early data can be replayed by an attacker, so allow it only for requests that are safe to repeat, such as simple GETs.
  • After changing settings, re-test from the outside; a load balancer or CDN in front of the server may set its own minimum version.

Notes

  • Disable SSLv3 and TLS 1.0/1.1 on servers you control — they expose known-vulnerable ciphers.
  • TLS 1.3 dropped RSA key exchange, CBC modes, and SHA-1.
  • PCI-DSS, NIST, and most modern compliance frameworks require TLS 1.2+.
Was this article helpful?