TLS has always been a moving target, and the protections that hold today will not necessarily hold tomorrow. That is the reasoning behind Cloudflare's decision to enable the strongest available protections by default rather than waiting for every site operator to choose them. The company introduced Automatic SSL/TLS during Birthday Week 2024: a service that scans the origin configuration of domains sitting behind Cloudflare and upgrades each one to the most secure encryption mode it can support. In the year since, that system has strengthened security for more than six million domains without any customer action.

BLOG-2963 Hero Image

What the Handshake Has to Agree On

Every TLS session starts with a handshake, and before any application data moves, client and server must settle on a shared secret key that protects both confidentiality and integrity. The client opens with a ClientHello, identifying the host it wants via SNI and listing the key agreement methods it supports. The server proves its identity with a certificate, and the two sides derive the shared secret from there.

TLS 1.3 introduced a shortcut. Rather than learning the server's preferred method first, the client guesses and sends one or more keyshares immediately. A correct guess avoids a round trip; a wrong one triggers a HelloRetryRequest (HRR) telling the client which method to try instead. That speculation is a large part of why TLS 1.3 outperforms TLS 1.2.

BLOG-2963 Image 1

For years, most handshakes used elliptic curve cryptography on the X25519 curve. Quantum computers threaten that: ECC algorithms such as X25519 could eventually be broken. The industry's answer is post-quantum key agreement with MLKEM, deployed in hybrid form as X25519 + MLKEM, so that traffic harvested today cannot be decrypted later. According to Cloudflare Radar, X25519 + MLKEM is steadily rising to become the most popular key agreement for connections to Cloudflare.

From SSL's Stumbles to TLS 1.3

The protocol's early incarnations in the 1990s, then called SSL, were undermined by weak keys, poor defenses against man-in-the-middle attacks, and thin adoption. The IETF took over the work and published TLS 1.0, followed through the 2000s by 1.1 and 1.2, which added stronger ciphers and closed new attack vectors but accumulated enough patches and extensions to become bloated and difficult to evolve.

The early 2010s changed direction. After the Snowden disclosures, the Internet embraced encryption by default, with Let's Encrypt, the broad shift to HTTPS, and Cloudflare's own free SSL/TLS making encryption a baseline rather than a costly option. TLS 1.3 arrived in 2018: legacy features removed, modern cipher suites mandatory, and handshakes roughly as fast as the transport underneath — sometimes faster over QUIC.

The Two TLS Layers a CDN Creates

CDNs changed where TLS terminates. A browser no longer talks directly to the distant origin server holding the content; it talks to the nearest edge data center, which may then speak to the origin on the client's behalf.

BLOG-2963 Image 2

That produces two separate TLS layers with different constraints. The edge-to-browser leg is the front door and can chase new security and performance work aggressively: TLS 1.3, QUIC and session resumption all serve latency reduction. The edge-to-origin leg is the backhaul and needs flexibility, because origins may be old, poorly maintained, running legacy TLS stacks, or dependent on custom certificate handling. CDNs therefore act as translators, modernizing the front door while still bridging to whatever the backhaul supports. A phone can get a fast TLS 1.3 session even when the origin behind the CDN has not been upgraded in years. Automatic SSL/TLS exists to address that second leg.

Recommending Was Not Enough

Cloudflare had already invested heavily in the front door with Universal SSL, but upgrading the back door was slower and harder. Cloudflare Tunnel offers one path: a lightweight agent near the origin tunnels traffic back to Cloudflare, guaranteeing modern encryption without touching the origin. Not every customer runs Tunnel, though. For those connecting origins directly, encryption depends on the origin's own configuration, and customers historically had to pick an encryption mode themselves or accept Cloudflare's default.

The SSL/TLS Recommender, launched in 2021, was meant to ease that choice. It scanned origin servers and suggested the most secure mode they supported — for instance, recommending a move from Full to Full (Strict) where the origin used a certificate from a trusted CA such as Let's Encrypt instead of a self-signed one. Based on the origin's responses, it reported whether the configured mode could be improved.

SSL/TLS mode

HTTP from visitor

HTTPS from visitor

Off

HTTP to Origin

HTTP to Origin

Flexible

HTTP to Origin

HTTP to Origin

Full

HTTP to Origin

HTTPS to Origin without certification validation check

Full (strict)

HTTP to Origin

HTTPS to Origin with certificate validation check

Strict (SSL-only origin pull)

HTTPS to Origin with certificate validation check

HTTPS to Origin with certificate validation check

The trouble emerged within three years of launch. Across the more than two million domains using the Recommender, only 30% of its recommendations were acted on. A large share of users never pressed the button that would let Cloudflare talk to their origin under a stricter setting. Settings that could have been upgraded without breaking anything went untouched. The response was to build a system that works alongside the Recommender and applies its findings by default.

Inside the upgrade mechanism

Automatic SSL/TLS determines a domain's ceiling by fetching content over both HTTP and HTTPS and comparing the results, alongside checks on the origin's presented certificate and the content types served. When the two copies match, the system can safely raise encryption to the strongest compatible mode.

The operational sequence looks like this:

  1. Monthly scanning. Each domain is scheduled for a scan once per month, and scanning stops once the domain reaches the maximum supported mode.
  2. Mode evaluation. The scan compares the current encryption mode against what the Recommender concludes from its probes and content scans. Only if the current setting is lower does a gradual upgrade begin.
  3. 1% trial. Traffic is first sent to the origin over the stronger mode for just 1% of requests. Successes are logged; failures are reported to Cloudflare's control plane and the upgrade aborts, with traffic immediately reverted to the prior setting.
  4. Ramping to 100%. With no issues, the new mode extends in 10% increments until it covers all traffic.
  5. Permanent change. After 100% of traffic runs without TLS-related errors, the domain's SSL/TLS setting is updated permanently.

Flexible → Full/Strict transitions get stricter treatment, because they alter cache keys (the origin scheme moves from http to https). Ramping in that case runs from 1% to 10% in 1% steps so customer caches can warm, then resumes the standard 10% increments up to 100%.

Because automated changes need to be visible, a weekly digest goes to account Super Administrators whenever a domain's encryption mode is updated.

BLOG-2963 Image 3

Rollout status and network effects

All Free, Pro, and Business domains have been onboarded to Automatic SSL/TLS, as has every new domain joining Cloudflare regardless of plan. Enterprise onboarding starts soon; Enterprise customers who want early access can turn the feature on in the SSL/TLS dashboard section or via the API. To date the system has upgraded over 6 million domains, and more than 4 million of those moved away from Flexible or Off — both of which use HTTP to origin — to Full or Strict, which use HTTPS.

Teardown remains available for operators who deliberately need a given mode, such as non-production test domains: disable Automatic SSL/TLS and set the mode manually. Today the setting is domain-wide, which means a single underperforming subdomain can hold an entire domain at a weaker TLS level for availability's sake. The stated long-term goal is per-origin or per-subdomain optimization.

Origin-facing connection data collected since onboarding began in late 2024 and early 2025 shows three trends across the network: a 7-8% correlated drop in plaintext origin-bound connections; TLS 1.3 now carrying almost 60% of encrypted origin traffic; and TLS 1.2 shrinking month over month, with TLS 1.0 and 1.1 too rare to register. Cloudflare notes that Automatic SSL/TLS does not control an origin's TLS version support, so these numbers are observational.

The long tail of origins still running outdated packages or configurations remains a concern. SSL Labs can verify a server's TLS setup, but copy-pasting configurations for a high rating carries risk, so origin TLS configurations deserve careful review. Cloudflare origin CA and Cloudflare Tunnel are offered as paths to stronger origin security.

Previous Encryption Mode

Upgraded Encryption Mode

Number of domains

Flexible

Full

~ 2,200,000

Flexible

Full (strict)

~ 2,000,000

Full 

Full (strict)

~ 1,800,000

Off

Full

~ 7,000

Off

Full (strict)

~ 5,000

What upgraded domains show

Looking only at domains upgraded by Automatic SSL/TLS reveals a sharper picture than the network-wide view. By January 2025, enrollment was largely complete and the shift from plaintext to encrypted origin communication was close to total, after which traffic flattened into a stable secure baseline. Part of the dip in encrypted traffic afterward may come from originally upgraded domains turning the feature off manually. July and August 2025 then brought another visible rise in encrypted origin traffic, plausibly from customers updating outdated origin packages and turning on stronger TLS support.

BLOG-2963 Image 4

Splitting out the TLS versions confirms rises in both TLS 1.2 and 1.3 between Cloudflare and origins on upgraded domains. Notably, TLS 1.2 declines network-wide but generally increases on automatically upgraded domains — again suggesting origin TLS stacks that could be updated further. TLS 1.0 and 1.1 were excluded from the comparison because their volumes were low enough to skew the graph.

BLOG-2963 Image 5

For Full (Strict) mode, successful certificate validations on upgraded domains rose dramatically, by roughly 40%.

BLOG-2963 Image 6

Planned features

Three additions are in development, all aimed at more control without weakening safe defaults:

  • Ad-hoc scans let customers re-evaluate an origin ahead of the monthly cadence — useful after certificate rotation or an origin TLS configuration change — so a stronger mode can be applied immediately.
  • Error surfacing will expose origin connection problems in the dashboard with remediation guidance, rather than leaving customers to discover a failed upgrade or a subsequent downgrade after the fact.
  • Onboarding guidance for new domains will clarify when origin configuration should be finished, relative to Cloudflare's first scan and the encryption mode it sets.

All three are expected to roll out by June 2026.

Data protected today with classical key agreement can be recorded now and decrypted later, once quantum attacks become practical. Post-quantum cryptography (PQC) is the industry's answer to that harvest-now, decrypt-later threat. NIST finalized its PQC standards in August 2024: ML-KEM for key agreement, and ML-DSA and SLH-DSA for digital signatures.

Cloudflare's edge already speaks a hybrid key agreement that pairs ML-KEM with X25519. TLS 1.3 traffic to its servers and internal systems is protected by it, and as of mid-September 2025 around 43% of human-generated connections to Cloudflare use the hybrid scheme.

BLOG-2963 Image 7

Origins are a harder problem

When Cloudflare connects to origins, it is the client, and origins are a fragmented mix of hosting providers, software stacks and middleboxes. Not all of them are ready for hybrid post-quantum handshakes, so an aggressive default risks broken connections.

The original workaround was HelloRetryRequest. Cloudflare would only advertise post-quantum support in the ClientHello; an origin that supported the key agreement would ask for it via the retry and the connection would be established. The cost is a full extra round trip, which erases much of TLS 1.3's latency advantage and makes uncached requests feel closer to TLS 1.2.

In 2023 Cloudflare shipped an API endpoint that let customers opt origins into preferring post-quantum connections, skipping the retry by sending the keyshare at the start of the session. Post-quantum protection was also extended to Cloudflare Tunnel.

Automatic from Q4 2025

Starting Q4 2025, the step becomes automatic. As with previous SSL/TLS upgrades, Automatic SSL/TLS will test, ramp and enable post-quantum handshakes with origins where those origins support the key agreement, with no customer action required.

Active origins are already scanned roughly every 24 hours for supported key agreements and preferences, both classical and post-quantum. That scanning is being folded into Automatic SSL/TLS. It brings classical gains too: X25519 is the current default, but scanning data shows more than 6% of origins prefer a different key agreement, producing needless HelloRetryRequests and wasted round trips. Feeding scan results into the default removes those.

The post-quantum side is moving as well. Preliminary scans find that around 4% of origins could benefit from a post-quantum-preferred key agreement today, an 8x increase since scanning began in 2023, and the share is expected to grow as the industry migrates.

BLOG-2963 Image 8

Alongside this, Cloudflare will phase out the pre-standard X25519Kyber768 in favor of the final ML-KEM standard, still hybrid, for edge-to-origin connections. The end state is a default in which origins are scanned proactively and the most preferred keyshare is sent directly, without the extra round trip — improving security and performance together.