Needs: OpenSSH 10.1 or later prints the warning; servers need OpenSSH 9.9 or later for mlkem768x25519-sha256 · Not yet tested on a real server

"connection is not using a post-quantum key exchange algorithm"

Newer OpenSSH clients print "connection is not using a post-quantum key exchange algorithm" when the server they connect to can't agree on a post-quantum key exchange. The session still works, but someone recording it today could decrypt it with a future quantum computer. (check: the exact wording and the first OpenSSH version that prints it.)

Why you see it

Fix it on the server

  1. Check the version: ssh -V on the server.
  2. Upgrade OpenSSH to 9.9 or later (10.0 or later makes mlkem768x25519-sha256 the default).
  3. If sshd_config sets KexAlgorithms, put the post-quantum ones first:
KexAlgorithms mlkem768x25519-sha256,sntrup761x25519-sha512,curve25519-sha256
  1. Check and restart: sshd -t && systemctl restart sshd.

Our scanner checks your HTTPS endpoints; the SSH check is planned. Scan your domain below for the web side.

Check the change

Scan your domain to see whether every host now uses post-quantum key exchange.

Related check: Is my site post-quantum?