Skip to main content

Which of your TLS servers use post-quantum key exchange?

· 3 min read
CertAutoPilot Team
CloudNativeWorks

Post-quantum migration has two very different halves. Replacing certificate signatures (RSA, ECDSA) with post-quantum ones is still years away for public TLS. Key exchange is already here: browsers and current TLS libraries negotiate the hybrid group X25519MLKEM768 by default, and every connection that uses it is protected against traffic recorded today and decrypted by a future quantum computer.

The question for an operator is simple: which of my servers already do this, and which do not?

Checking one server​

OpenSSL 3.5 and later name the negotiated group. Against a server that supports hybrid key exchange:

echo | openssl s_client -connect www.example.com:443 -servername www.example.com 2>&1 | grep -i group
# Negotiated TLS1.3 group: X25519MLKEM768

When the server only offers classical groups, there is no such line; OpenSSL prints the classical key instead:

Peer Temp Key: X25519, 253 bits

Two things to know when reading the result:

  • Hybrid key exchange needs TLS 1.3. A server that negotiates TLS 1.2 is classical, whatever its library supports.
  • The server's preference wins. A server can support the hybrid group and still choose X25519 when the client offers both. Supporting a group and using it are different facts.

What usually decides the answer​

In our measurements, a server built on a current TLS library negotiates the hybrid group out of the box: Node.js 24 with OpenSSL 3.5, and an openssl s_server from OpenSSL 3.5 or later, both chose X25519MLKEM768 with no configuration. Servers come out classical when they are pinned to an explicit group list that predates ML-KEM, when they are limited to TLS 1.2, or when they run an older library. Appliances and load balancers follow their own firmware schedule.

Measuring a whole estate​

Checking servers one by one does not scale, and the answer changes as libraries are upgraded and configurations drift. CertAutoPilot's discovery records the key exchange of every TLS server it scans and shows it on a quantum readiness page:

  • how many servers use hybrid or pure ML-KEM key exchange, how many are classical, and how many are still on TLS 1.2;
  • optionally, which groups each server supports beyond the one it chose, to find servers that could be hybrid with a configuration change;
  • a daily trend, and a notification when a server that used to negotiate a post-quantum group falls back to a classical one.

It also classifies certificate keys, so the second half of the migration, signatures, is visible in the same place when the time comes.