Back to Articles
Guide2026-09-15•5 min read•CSR.plus Team

TLS 1.2 Deprecation 2026: Status and Upgrade Path

TLS 1.2 Deprecation 2026: Status and Upgrade Path
2026-07
RFC 9851
IETF 冻结 TLS 1.2 功能开发
73.1%
TLS 1.3 请求占比
Cloudflare Radar,2026-08
2020 年
TLS 1.0/1.1 浏览器弃用
主流浏览器全部移除支持
2021-03
RFC 8996
IETF 正式废弃 TLS 1.0/1.1

加密请求的 TLS 版本构成(2026-08)

加密请求的 TLS 版本构成(2026-08)100100%TLS 1.3 — 73%TLS over QUIC(HTTP/3) — 21%其他(主要为 TLS 1.2) — 6%来源:Cloudflare Radar,2026-08 全月,按经过 Cloudflare 网络的请求统计;「其他」为余量推算,主要为 TLS 1.2。

来源:Cloudflare Radar,2026-08 全月,按经过 Cloudflare 网络的请求统计;「其他」为余量推算,主要为 TLS 1.2。

TLS 1.2 Deprecation 2026: Real Status, RFC 9851 and Your Upgrade Path

TLS 1.2 is not deprecated, and as of November 2026 no major browser has published a removal date. What has happened is quieter but significant: in July 2026 the IETF published RFC 9851, putting TLS 1.2 (still commonly called SSL) into feature freeze — outside urgent security fixes, no further changes will be approved. The actual deprecation already happened to TLS 1.0 and 1.1, which browsers dropped during 2020 and RFC 8996 formally retired in March 2021. The right move now: enable TLS 1.3 — 73.1% of encrypted requests on Cloudflare's network already use it (Cloudflare Radar, 2026-08) — and treat TLS 1.2 as a monitored compatibility fallback instead of waiting for a removal date nobody has announced.

TLS 1.0/1.1: the completed deprecation

Browsers removed TLS 1.0/1.1 support during 2020, and the IETF made it official with RFC 8996 in March 2021. These versions rely on outdated MD5/SHA-1 primitives and static RSA key exchange, and they are helpless against downgrade attacks like BEAST and POODLE. If your server still offers TLS 1.0/1.1 today, security scanners will fail you — that part of the cleanup is uncontroversial.

TLS 1.2: not deprecated, but frozen

In July 2026 the IETF published RFC 9851 ("TLS 1.2 is in Feature Freeze"): outside urgent security fixes, new TLS Exporter Labels and new ALPN protocol IDs, no changes will be approved for TLS 1.2, and the constraint does not apply to DTLS. The rationale is blunt — TLS 1.3 fixes most known deficiencies of TLS 1.2 and keeps growing. Importantly, a freeze is not a deprecation: TLS 1.2 remains the minimum baseline for compliance regimes such as PCI DSS, and servers may keep offering it to legacy clients.

TLS 1.3 is the direction

TLS 1.3 (RFC 8446, 2018) compresses the handshake to one round trip, makes forward secrecy mandatory and deletes all legacy cipher suites. It already carries 73.1% of encrypted requests on Cloudflare's network, with another 20.5% over TLS/QUIC (HTTP/3) (Cloudflare Radar, 2026-08). New capabilities — including post-quantum key exchange — arrive only in TLS 1.3, which is exactly why RFC 9851 froze the old version.

What this means for site owners

There will be no "off switch" day in the short term: no removal date exists. The risk is long-term — a frozen protocol gains no new features, and the ecosystem will increasingly treat TLS 1.2 as legacy. The playbook: enable TLS 1.3 today, keep TLS 1.2 as a fallback, monitor its traffic share in your logs, and let data — not rumors — decide when to tighten.

Step 1: Confirm TLS 1.3 is enabled

Run your domain through the SSL Checker and read the negotiated protocol list. If TLS 1.3 is missing, move on to the configuration changes below.

Step 2: Inspect the handshake

The SSL/TLS Tracer shows the full handshake and cipher suites, so you can verify forward secrecy settings and protocol preference order.

Step 3: Update the server configuration

Nginx:

ssl_protocols TLSv1.2 TLSv1.3;

Apache:

SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1

Keep both TLS 1.2 and TLS 1.3 first, confirm everything works, then tighten based on data. Always syntax-check and reload after editing (for example nginx -t && nginx -s reload).

Step 4: Monitor the TLS 1.2 share before disabling it

Log the protocol version:

log_format tls '$ssl_protocol';  # protocol only — no client IP, no URL
access_log /var/log/nginx/tls.log tls;

After a few days, aggregate the TLSv1.3 vs TLSv1.2 split. When the TLS 1.2 share approaches zero, remove it safely; if it remains noticeable, real clients still depend on it — keep it and re-check periodically.

Troubleshooting checklist

SymptomLikely causeFix
Client reports a protocol mismatchServer is TLS 1.3-only and the client is oldRe-enable TLS 1.2 as a temporary fallback
TLS 1.3 has no effect after enablingOpenSSL older than 1.1.1Upgrade OpenSSL, rebuild or restart
Handshake fails after config changeTypo in ssl_protocols or config not reloadedRun nginx -t, then reload
Legacy clients cannot connectUnpatched Windows 7 etc. only support TLS 1.2Keep 1.2 during transition, monitor logs
Scanner flags TLS 1.0/1.1 still openProtocols not explicitly disabledExplicitly disable TLSv1 and TLSv1.1
Certificate valid but handshake failsIncomplete chain combined with old protocolsInspect chain and validity with the Certificate Decoder

FAQ

Is TLS 1.2 deprecated now?

No. As of November 2026 no major browser has published a TLS 1.2 removal date. But the IETF froze TLS 1.2 feature development in July 2026 via RFC 9851: outside urgent security fixes, no new changes are approved.

Do I need a new certificate for any of this?

No. RFC 9851 targets protocol development, not certificates. Enabling TLS 1.3 is a server configuration change; your existing certificate keeps working.

When must TLS 1.2 be removed?

There is no official date. Track your own logs: measure the TLS 1.2 share of traffic, and disable it once that share approaches zero. Until then, keep it as a compatibility fallback.

What about clients that cannot do TLS 1.3?

Unpatched Windows 7, old Android builds and many IoT devices only speak TLS 1.2 or older. If you must serve them, keep TLS 1.2 enabled through a transition period, monitor the logs, and remove it once the traffic disappears.

How do I verify that my server supports TLS 1.3?

Enter your domain in the SSL Checker — the protocol list shows exactly what your server negotiates. For deeper detail, the SSL/TLS Tracer walks through the full handshake.

Take action

Related: Fix TLS Protocol Mismatch, Fix SSL Protocol Error, 2026 SSL/TLS Statistics.

FAQ

Is TLS 1.2 deprecated now?

No. As of November 2026 no major browser has published a TLS 1.2 removal date. But the IETF froze TLS 1.2 feature development in July 2026 via RFC 9851: outside urgent security fixes, no new changes are approved.

Do I need a new certificate for any of this?

No. RFC 9851 targets protocol development, not certificates. Enabling TLS 1.3 is a server configuration change; your existing certificate keeps working.

When must TLS 1.2 be removed?

There is no official date. Track your own logs: measure the TLS 1.2 share of traffic, and disable it once that share approaches zero. Until then, keep it as a compatibility fallback.

What about clients that cannot do TLS 1.3?

Unpatched Windows 7, old Android builds and many IoT devices only speak TLS 1.2 or older. If you must serve them, keep TLS 1.2 enabled through a transition period, monitor the logs, and remove it once the traffic disappears.

How do I verify that my server supports TLS 1.3?

Enter your domain in the [SSL Checker](/check) — the protocol list shows exactly what your server negotiates. For deeper detail, the [SSL/TLS Tracer](/tools/ssl-tracer) walks through the full handshake.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles