Workspace

Post-quantum TLS, Encrypted Client Hello and Early Hints

3 day streakD

Post-quantum TLS, Encrypted Client Hello and Early Hints

What changed in the last two years: hybrid post-quantum key exchange in most TLS traffic, encrypted server names, and preload hints that replaced server push.

CurrentLesson 6 of 616 min

A large enough quantum computer could break the elliptic-curve key exchanges TLS uses today. None exists yet, but traffic recorded now could be decrypted later: harvest now, decrypt later. Protecting key exchange cannot wait for the computer to arrive.

Hybrid key exchange

The deployed answer is a hybrid: run classical X25519 and the post-quantum ML-KEM-768 side by side and combine both secrets. An attacker must break both. The named group X25519MLKEM768 carries this in ordinary TLS 1.3 key shares. Per the syllabus sources, RFC 10024 standardised it in August 2026, and it carried over two-thirds of human TLS traffic to Cloudflare by April 2026.

Figure 6.1

The post-quantum ClientHello no longer fits in one packet

Classical (X25519)≈ 482 B
Hybrid (X25519MLKEM768)≈ 1,666 B
Fields and extensions (varies by client)X25519 share, 32 BML-KEM-768 key, 1,184 BOne TCP segment ≈ 1,460 B
A classical ClientHello with an X25519 key share fits easily in one packet. ML-KEM-768 adds a 1,184-byte encapsulation key, making the hybrid client share 1,216 bytes and pushing the ClientHello past a typical 1,500-byte packet.

Bigger first messages have consequences. Middleboxes that assumed a ClientHello fits in one packet broke; some servers needed bigger buffers; QUIC's anti-amplification limits interact with larger first flights. These were found and fixed through years of experiments before the default switch.

Encrypted Client Hello

TLS 1.3 encrypts almost everything after ServerHello, but the ClientHello itself, including the SNI naming the site, travels in plaintext. Anyone on the path can see which site you visit. Encrypted Client Hello encrypts the real ClientHello with a key published in the site's HTTPS DNS record, inside an outer ClientHello that names only a shared front-end.

103 Early Hints

While a server computes a response, the browser sits idle. HTTP/2 server push tried to fill that time by pushing resources unasked, but servers pushed things browsers already had, wasting bandwidth, and browsers removed it. 103 Early Hints sends an informational response first, with Link: rel=preload headers. The browser decides what to fetch, using its own cache knowledge.

early-hints.txtText
HTTP/1.1 103 Early Hints
Link: </app.css>; rel=preload; as=style
Link: <https://api.example.com>; rel=preconnect

HTTP/1.1 200 OK
Content-Type: text/html
…
Go deeperMASQUE and multipath QUIC

MASQUE defines how to proxy UDP and IP over HTTP/3, so a single QUIC connection to a proxy can carry other QUIC connections inside it. It powers privacy relays and modern VPN-like services that look like ordinary HTTPS to the network.

Multipath QUIC extends connection migration: instead of moving from one path to another, a connection uses several at once, like Multipath TCP. The aim is seamless handover and combined bandwidth on phones with Wi-Fi and cellular.

Where you will meet it

Browsers and CDNs

Chrome, Firefox and major CDNs negotiate the hybrid group by default. Your own TLS library may need an upgrade to offer it.

Compliance

Organisations with long-lived secrets prioritise post-quantum key exchange now, because recorded traffic is the threat.

Page speed

Sites with slow server-side rendering send 103 responses to start CSS and font downloads during the wait.

Words to know

Harvest now, decrypt later
Recording encrypted traffic today to decrypt once quantum attacks exist.
ML-KEM
A standardised post-quantum key encapsulation mechanism.
ECH
Encrypted Client Hello: hides the real ClientHello and SNI.
Early Hints
A 103 response suggesting resources to preload before the final response.

Check yourself

Answer out loud before you open each one.

What does X25519MLKEM768 protect, and what not?

Key exchange, so recorded traffic stays confidential. Not certificate authentication, which still uses classical signatures.

Why is the hybrid used rather than ML-KEM alone?

An attacker must break both algorithms, so a flaw in the newer one does not leave traffic exposed.

What does Encrypted Client Hello hide?

The real ClientHello, including the SNI naming the site you are connecting to.

Try it

Run openssl s_client -connect cloudflare.com:443 -groups X25519MLKEM768 -brief </dev/null with an OpenSSL 3.5 or later build and check the negotiated group.

A good place to start

Explore a pattern

A little guidance

Start with a pattern, read through a problem, and mark it solved when the idea clicks. Save anything you want to revisit.

New tutorials are added one at a time. Your bookmarks and solved checkmarks stay in this browser.

Explore the roadmap