What is post-quantum key exchange?

Every HTTPS connection starts with a key exchange: the browser and the server agree on the secret key that encrypts everything after it. The classical way to do this, elliptic-curve Diffie-Hellman (X25519, P-256), could be broken by a large enough quantum computer. Such computers don't exist yet, but traffic recorded today could be decrypted once they do, which is why this attack is called "harvest now, decrypt later".

Post-quantum key exchange uses ML-KEM, the algorithm NIST standardized in FIPS 203 in 2024. Websites combine it with a classical curve, so the connection stays safe as long as either one holds. The most common combination is X25519MLKEM768, which current versions of Chrome, Edge, Firefox and Safari offer by default. These hybrids are standardized for TLS 1.3 in RFC 10024.

How to use it

Enter a website's address or host name and press the button. The check connects to its HTTPS server on port 443.

What you see

  • Post-quantum key exchange for browsers: whether the server picks a post-quantum group when it's offered the groups Chrome offers, and which group it picks.
  • TLS version of that connection. Post-quantum key exchange needs TLS 1.3, so a server that only speaks TLS 1.2 can't use it.
  • Key exchange: the group the server picked, such as X25519MLKEM768, or X25519 for a server without post-quantum support.
  • Certificate key: the key in the server's certificate, such as ECDSA P-256 or RSA 2048 bits.
  • Post-quantum groups the server accepts: the result of one TLS 1.3 connection per group, each offering only that group:
    • X25519MLKEM768: X25519 with ML-KEM-768, the hybrid browsers use.
    • SecP256r1MLKEM768 and SecP384r1MLKEM1024: the hybrids with the NIST curves P-256 and P-384.
    • MLKEM768 and MLKEM1024: ML-KEM without a classical curve. The US NSA's CNSA 2.0 guidance asks for ML-KEM-1024.

"Couldn't tell" means that connection failed for another reason than the server turning the group down, such as a timeout or a dropped connection. Some older firewalls and servers drop the larger first message that post-quantum keys need.

What it doesn't cover

The key exchange protects the secrecy of the connection. The certificate proves the server is who it says it is, and on public websites it is still RSA or ECDSA: browsers don't accept post-quantum certificates yet, and a forged certificate would need a quantum computer at the time of the connection, not years later.

The check runs from our server, so a site behind a content delivery network answers from the location nearest to it. Different locations normally share the same settings.

Privacy

The host name you enter is sent to our server, which makes the connections. Nothing is sent to the website besides normal TLS handshakes.