- Published on
Automatic Key Exchange: faster, post-quantum secure origin handshakes for 45 billion daily connections (and counting)
- Authors
- Name
- DeepHorus
Cloudflare has announced Automatic Key Exchange, an extension of Automatic SSL/TLS designed to remove a costly guess from TLS 1.3 handshakes between its edge and origin servers. The launch targets the roughly 45 billion origin connections Cloudflare handles each day, turning a single extra network round trip into a meaningful performance problem. It combines faster negotiation with a path toward post-quantum protection, without requiring website operators to reconfigure their origins.
Cloudflare’s reverse-proxy role creates two separate TLS sessions for a typical website: one between visitor and edge, and another between edge and origin. Automatic Key Exchange affects the second session, in which Cloudflare acts as the client. Its first ClientHello includes a hostname, supported key-agreement algorithms, and one or more key shares. If the origin accepts the choice, encryption can be established in one round trip; otherwise, it may send a HelloRetryRequest and force a second attempt.
For years, Cloudflare generally led with X25519, a widely supported classical algorithm. Measurements showed that this fixed choice was suboptimal for roughly 30% of origin connections. When the initial key share did not match the origin’s preference, the origin returned a HelloRetryRequest, and Cloudflare generated a new share and repeated the exchange. The connection still succeeded, but an avoidable round trip delayed the first content request.
Automatic Key Exchange replaces the blanket assumption with a per-origin measurement. Cloudflare probes each origin to learn which key-agreement algorithms it supports and prefers, then puts that choice in the first ClientHello. When supported, the post-quantum hybrid X25519MLKEM768 becomes the preferred option. The design preserves TLS 1.3’s predictive fast path while making the opening packet more likely to be accepted immediately.
Cloudflare reports that, during the ongoing rollout, HelloRetryRequests fell from approximately 52% to 3.7%. At the 90th percentile, the company says the change removed more than 150 milliseconds from origin handshake latency. That gain can matter for dynamic pages, API calls, and transactions where a few hundred milliseconds influence user experience. The improvement comes from avoiding a full network round trip, not from relaxing authentication or encryption.
The security motivation may be even more significant than the speed gain. Attackers can record encrypted traffic today and try to decrypt it later if a powerful quantum computer breaks the classical protections used to capture it, a strategy known as harvest-now, decrypt-later. X25519MLKEM768 combines a classical component with a post-quantum mechanism, helping compatible origins defend against that future risk while remaining part of TLS. Cloudflare says hundreds of thousands of domains now have post-quantum origin connections through the rollout, with no manual configuration required, and the number is growing daily.
The timing reflects pressure to prepare for Q-Day, which some industry experts estimate could arrive as early as 2029 if classical encryption is broken. Previously, post-quantum origin negotiation generally required a manual Cloudflare setting or cooperation from the origin server. Making the process automatic turns a specialized migration into a default network behavior. Operators are likely to welcome that model because it reduces deployment work and the risk of inconsistent configuration.
Looking ahead, Cloudflare expects the feature to expand as probing, algorithm support, and telemetry improve. The system still requires ongoing cryptographic maintenance and coordination among CDNs, hosting providers, and origin operators. Future updates may support additional preferred algorithms as hybrid standards mature. If the reported gains hold at internet scale, predictive, post-quantum-ready handshakes could become a practical baseline rather than an opt-in setting.
