Post-quantum TLS: what X25519MLKEM768 protects and how to turn it on
By TechCompare · Updated · How we check
X25519MLKEM768 is the post-quantum key exchange browsers already offer. A server that picks it keeps today's traffic safe from a future quantum computer, and it only needs TLS 1.3 and a TLS library with ML-KEM.
A large quantum computer could break the elliptic curve math behind today's TLS key exchange. Nobody has one yet, but traffic recorded now could be decrypted once someone does. X25519MLKEM768 guards against that. It pairs the classic X25519 exchange with ML-KEM-768, the algorithm NIST standardized as FIPS 203 in 2024, so the connection stays safe as long as either one holds.
How this is calculated
The threat has a name: harvest now, decrypt later. Someone records encrypted traffic today and waits. The key exchange is the weak spot, because that's what a quantum computer running Shor's algorithm could undo to recover the session keys. Certificates are a different matter. Forging one would take a quantum computer at the moment of the connection, so post-quantum certificates can come a little later.
Browsers moved first. Chrome 131 and Firefox 132 on desktop offer X25519MLKEM768 by default, and Apple turned it on for Safari and its system networking in iOS 26 and macOS Tahoe 26. Cloudflare reports that well over half of the browser traffic reaching its network now uses it. The IETF published the hybrid groups for TLS 1.3 as RFC 10024 in August 2026.
On servers, OpenSSL 3.5 and later include ML-KEM and prefer X25519MLKEM768 by default, and Go 1.24 and later do the same. Older OpenSSL versions don't support it at all, so many servers need an operating system or package update first. A config that pins its own list of curves, like an nginx ssl_ecdh_curve line, also has to add it.
The key share is much bigger, about 1.2 KB instead of 32 bytes, so the browser's first message often no longer fits in one packet. Some old firewalls and servers can't handle that and drop the connection. The checker calls that refused: TLS 1.3 works with a classic hello but fails when the hello carries the post-quantum share.
The SSL Checker offers X25519MLKEM768 the way a browser does and reports whether the server picks it, picks a classic group instead, or refuses the hello.
Verdict
Update the TLS library first. OpenSSL 3.5 or later gets you X25519MLKEM768 with no extra setup in most servers, unless the config pins a list of curves. Behind a CDN, check both the edge and the link to your origin. A refused result points at a server or middlebox that can't handle the bigger hello, and that's worth fixing soon.
More SSL scenarios
Related guides
Frequently asked questions
Does post-quantum TLS slow a site down?
Do I need a new certificate for post-quantum TLS?
What's the difference between No and Refused?
Related tools
DNS Lookup
Look up a domain's DNS records on Cloudflare or compare several resolvers at once, and read its SPF, DMARC and DKIM records in plain words.
Use toolOpen Graph Visualizer
Preview how your website links will look when shared on Google, Twitter, Facebook, and Discord.
Use toolPassword Generator
Generate secure, random passwords locally in your browser.
Use tool