The most visible progress in post-quantum migration has been in TLS, the protocol behind HTTPS. Major browsers and content delivery networks already negotiate a hybrid post-quantum key exchange for a large and growing share of connections. If you run websites or APIs, you may already be using it, or be one configuration change away.
What X25519MLKEM768 is
In TLS 1.3, the client and server agree a shared secret using a key exchange group. Traditionally that is an elliptic-curve group such as X25519. X25519MLKEM768 is a hybrid group that does two key exchanges at once:
- X25519, classical elliptic-curve Diffie–Hellman, and
- ML-KEM-768, the NIST post-quantum key encapsulation mechanism (FIPS 203),
and combines both results into the session secret. An attacker has to break both to recover the keys. If quantum computers break X25519, ML-KEM still protects the session. If an unexpected flaw is found in ML-KEM, X25519 still does.
It protects against harvest now, decrypt later: traffic recorded today can't be decrypted later with a quantum computer.
What it doesn't do
Hybrid key exchange protects confidentiality. It does not change authentication: certificates are still signed with RSA or ECDSA. Post-quantum certificates (ML-DSA) are a separate, harder migration because of their size and the ecosystem of certificate authorities and clients that must support them.
Who supports it
- Browsers: Chrome and Edge have enabled X25519MLKEM768 by default since late 2024 (after an earlier experimental Kyber version). Firefox and Safari have added support too.
- CDNs and cloud edges: major CDNs and cloud load balancers support hybrid key exchange, often by default at the edge.
- Libraries: OpenSSL 3.5 (April 2025) added ML-KEM, ML-DSA and SLH-DSA and includes hybrid groups by default. BoringSSL and AWS-LC support them, and Go's standard library enables hybrid key exchange by default in recent versions. Java added ML-KEM and ML-DSA in JDK 24.
- SSH: OpenSSH 10.0 made the hybrid
mlkem768x25519-sha256key exchange the default.
Versions and defaults move quickly, so check your own stack's release notes.
How to check
In a browser: open developer tools, go to the Security panel (Chrome and Edge), and look at the connection's key exchange. It shows X25519MLKEM768 when hybrid is in use.
From the command line (OpenSSL 3.5 or later):
openssl s_client -connect example.com:443 -groups X25519MLKEM768 </dev/null 2>/dev/null | grep -i "group"
If the server supports it, the output names the negotiated group. If the handshake fails or falls back, it doesn't.
At scale: scan your external endpoints and record the negotiated group for each. Track "percentage of internet-facing endpoints supporting hybrid key exchange" as a programme metric.
Enabling it
- Behind a CDN or managed load balancer: check whether hybrid is enabled at the edge, often a simple setting or already the default. Remember the connection from the edge to your origin may still be classical.
- Your own servers: upgrade to a TLS library with hybrid support and add the group to your configuration's preferred list. Keep classical groups as fallbacks for older clients.
- Internal services: service meshes and internal load balancers often lag behind public edges. Include them in your plan.
Pitfalls
- Bigger handshakes. The client's first message grows by over a kilobyte, which can push it over a single network packet. Most networks cope, but some middleboxes (old firewalls, TLS inspection appliances, buggy proxies) have mishandled larger ClientHello messages. Test through your corporate network paths.
- TLS inspection. Inspection proxies must support the new groups, or they may force downgrades or break connections. Ask your vendors.
- Old clients. Keep classical groups available. Negotiation falls back gracefully when both sides follow the standard.
- False reassurance. Hybrid TLS at the edge is a great start, not the end. VPNs, internal traffic, PKI and signatures still need attention. See the migration roadmap.
Learn more
Read post-quantum cryptography explained and the NIST standards field guide. For TLS, PKI and network security fundamentals, see the free CISSP track.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
Strengthen your crypto fundamentals
Cryptography lessons and practice questions in the free CISSP track.
Create a free account