SSL vs TLS — what the difference is and what you're actually buying

Funny thing: the SSL protocol hasn't existed on the internet for over a decade. In June 2015 RFC 7568 landed with no room for interpretation — "SSLv3 MUST NOT be used." And yet the word stayed: "SSL certificate" on your host's price list, ssl_protocols in the nginx config, the OpenSSL library.
So if you're buying an "SSL certificate," you're buying TLS. Let's sort out what actually differs and what follows from it for you.
Short version: it's one protocol that got renamed
SSL (Secure Sockets Layer) was invented at Netscape in the nineties. In 1999 it moved to the IETF, was reworked, and shipped under a new name — TLS 1.0. Then came TLS 1.1, 1.2 and 1.3.
So these aren't two competing protocols but one, with a new name and several generations. "SSL" caught on before the rename — and stuck in marketing, docs and file names.
The useful consequence: there is no "choice between SSL and TLS." If your hosting panel says "enable SSL," it enables a current version of TLS. The only real choice is between TLS versions.
What's alive and what's officially dead
The timeline is short but worth keeping in your head:
- SSL 2.0 and 3.0 — dead. RFC 7568 (June 2015) forbids SSLv3 outright, including falling back to it from any TLS version.
- TLS 1.0 (1999) and TLS 1.1 — deprecated by RFC 8996 in March 2021. The reasons are technical: they're wired to old cryptography, SHA-1 included. Browsers had already dropped them in 2020.
- TLS 1.2 — the workhorse, supported everywhere.
- TLS 1.3 — published in August 2018 (RFC 8446) and now the default. Shorter handshake, a 0-RTT mode for repeat connections ("saving a round trip," as the spec puts it), and a pile of legacy machinery removed — including outdated key exchanges and the old TLS 1.2 session tickets.
Compressed: TLS 1.2 and 1.3 are alive, everything else is history.
How 1.3 actually differs from 1.2
No tables, just the substance:
- Speed. The 1.3 handshake is shorter — the connection is established in fewer exchanges, and repeat visits can use 0-RTT. On mobile networks you feel it.
- Fewer choices, fewer mistakes. TLS 1.2 has dozens of cipher suites, some weak; 1.3 keeps five, all modern. Accidentally configuring something insecure became almost impossible.
- Legacy dropped. The mechanisms behind the famous attacks of the last decade are simply gone from 1.3.
- Compatibility. TLS 1.2 is understood by absolutely everything, including ancient clients and corporate proxies. So the normal production setting is both: 1.2 and 1.3.
Who should do what
A site on Vercel, Netlify, Cloudflare Pages or a panel host. Do nothing. The platform picks the versions, and it already picked well. "SSL" in the UI is just the familiar signboard.
Your own server (nginx, Caddy, your container). Enable exactly two versions and stop worrying:
ssl_protocols TLSv1.2 TLSv1.3;
The directive is called ssl_protocols for historical reasons — there's no SSL left in it. If an inherited config mentions TLSv1 or TLSv1.1, delete them: they only widen the attack surface, and in 2026 practically nobody needs them.
Talking to a bank, a government service or an old corporate API. The one case where you may have to keep TLS 1.2 as a floor and read the partner's requirements carefully. Even there, SSL is out of the question.
How to check what you have
Quickly, with curl:
curl -Iv https://kodiq.ai 2>&1 | grep -i "SSL connection using"
You'll get something like SSL connection using TLSv1.3 — the same wording confusion again: curl says "SSL" and shows a TLS version.
In more detail, with openssl: try connecting with a specific version and see whether you're let in:
openssl s_client -connect kodiq.ai:443 -tls1_1 </dev/null
If the connection fails — good, the old protocol is off. What the server actually presents during that handshake is covered in what is a TLS certificate; why any of it sits on top of plain HTTP is in what is HTTPS.
Then why does everyone say "SSL"?
Because the word is older. It got baked into product names, books and settings before the rename, and nobody rewrites an established term on a price list. Treat "SSL" as colloquial for "encryption on the web."
Should I disable TLS 1.2 since 1.3 exists?
No. TLS 1.2 isn't broken, it's just older. Turning it off costs you clients and buys you no security. The right pair is 1.2 plus 1.3.
Does the TLS version affect site speed?
A little, and only when establishing a connection. TLS 1.3 saves one network round trip — tens of milliseconds per new connection on mobile. A CDN that terminates TLS closer to the user will do far more.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





