News2026-08-14•6 min read

TLS 1.2 Deprecation 2026: The Countdown Has Started

· CSR.plus Team

•Apple removes TLS 1.2 trust in December 2026; Chrome, Edge and Firefox follow with default disablement in early 2027.
•Roughly 8% of the top sites still negotiate TLS 1.2 by default — and tens of millions of domains overall.
•No new certificate is needed: upgrade your server configuration to TLS 1.3 and keep TLS 1.2 only as a short-term fallback.

2026-12

Apple cutover

TLS 1.2 trust removed from roots

2027-03

Browser default

Chrome/Edge disable TLS 1.2

Sites still on 1.2

of top sites default to TLS 1.2

80%

TLS 1.3 adoption

already supported by top sites

Share of top sites still defaulting to TLS 1.2 (%)

Top 1M domains, handshake-based scan.

Default protocol distribution, August 2026

Share of scanned domains per negotiated default.

The background

In September 2025, Apple, Google and Mozilla jointly announced the end of TLS 1.2 in their trust stores. TLS 1.2 has served the web for 18 years, but its old cipher suites, weaker hash usage and aging 2008-era design make it a growing liability. The browser vendors committed to removing TLS 1.2 trust from their root stores by the end of 2026, with default disablement in browsers following in early 2027.

The timeline

Firefox began the phase-out in November 2026, gradually marking TLS 1.2 connections as insecure. Apple removes TLS 1.2 trust from its root store in December 2026, affecting Safari and all Apple platforms. Google and Microsoft disable TLS 1.2 by default in Chrome and Edge in the first quarter of 2027. Operators with certificates that are still valid can no longer rely on them after these dates.

Why TLS 1.2 is being retired

TLS 1.2 was designed in 2008. Its ciphers still allow 3DES and RC4 in some configurations, it needs explicit configuration for forward secrecy, and the ecosystem has spent years patching downgrade attacks such as BEAST, POODLE, DROWN and ROBOT. TLS 1.3 removed the legacy cipher machinery, cut the handshake to one round trip and made forward secrecy mandatory — there is no reason to keep the old protocol alive.

What this means for site owners

Your certificate can still be valid for months, yet clients will stop trusting the TLS 1.2 handshake that serves it. About 8% of the top sites still default to TLS 1.2 today; every one of them must ship TLS 1.3 before the cutover dates. The good news: enabling TLS 1.3 is a configuration change, not a certificate re-issuance.

How to check your site

Use the free SSL Checker on csr.plus: enter your domain and it reports which protocol versions your server negotiates, including whether TLS 1.3 is enabled. For a detailed view, the SSL/TLS Tracer shows the exact handshake and the offered cipher suites. The Certificate Inspector verifies the full chain and its validity period.

Upgrade steps and compatibility

On Nginx, set "ssl_protocols TLSv1.2 TLSv1.3;" (drop TLS 1.2 once your analytics confirm no legacy traffic). On Apache, set "SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1" and remove TLSv1.2 later. Keep in mind older clients — Windows 7 without updates, ancient Android, some IoT devices — cannot speak TLS 1.3; if you must serve them, keep TLS 1.2 enabled during a transition period and monitor logs before disabling it.

FAQ

Why is TLS 1.2 being deprecated?

TLS 1.2 is an 18-year-old protocol with legacy ciphers and a history of downgrade attacks. Browsers want a single, modern baseline — TLS 1.3 — for security and simpler configuration.

What happens to my site if it still uses TLS 1.2 after the cutover?

Browsers will refuse to connect: the TLS 1.2 handshake is no longer trusted, even if your certificate is valid. Users see connection errors, and traffic drops to near zero for modern clients.

Do I need a new certificate?

No. The deprecation targets the protocol, not certificates. Upgrade your server configuration to enable TLS 1.3; your existing certificate keeps working.

What about old clients that cannot do TLS 1.3?

Windows 7 (unpatched), very old Android and many IoT devices only support TLS 1.2 or older. If you must support them, keep TLS 1.2 enabled as a fallback during a transition period, monitor the logs, and disable it once the traffic disappears.

How do I verify that my server supports TLS 1.3?

Enter your domain in the free SSL Checker on csr.plus — the protocol list shows exactly what your server negotiates. For a deeper look, the SSL/TLS Tracer walks through the whole handshake.

UptimeRobot