What are you checking?
You are checking the key exchange: the step in a TLS connection where the browser and the server agree a secret. If it uses only classical algorithms such as X25519 or ECDHE, someone who records the traffic today could decrypt it once a capable quantum computer exists. If it uses ML-KEM, standardised by NIST as FIPS 203 in August 2024, the recorded traffic stays protected.
Most servers that use ML-KEM today use a hybrid group, X25519MLKEM768, which combines classical X25519 with ML-KEM-768, so the connection is at least as strong as either part. The Australian Signals Directorate's guidance points to ML-KEM-1024 for the longer term.
Three ways to check
1. In your browser
In Chrome or Edge, open the developer tools, choose the Security panel and reload the page. The connection details name the key exchange; X25519MLKEM768 means post-quantum protection for your connection. This shows only what your browser negotiated, not what the server offers to others.
2. With OpenSSL 3.5 or later
OpenSSL added ML-KEM in version 3.5. Ask the server for the hybrid group only:
openssl s_client -connect www.example.com:443 -groups X25519MLKEM768 -brief
If the handshake completes and names the group, the server supports it. Run it again offering both X25519MLKEM768:X25519 to see which one the server prefers.
3. With the free instant check
The Sovereign Q instant check takes one public hostname on port 443, completes the handshake from Cloudflare's network and returns a grade, the exposure and the first fix for the server's software. No account is needed. With a free account, the quantum encryption check gives 10 checks a day of web servers on port 443; SSH, mail and database servers are checked once you prove you control the domain, on a paid plan. Check only systems you own or are authorised to test.
What the result means
- Protected: post-quantum key exchange is negotiated by default.
- Partial: it is offered but not preferred, so many clients still connect classically.
- Exposed: classical key exchange only. Recorded traffic is at risk later.
Key exchange is the urgent part because of harvest now, decrypt later. Certificates and signatures matter too, but a forged signature needs a quantum computer at the time of the attack, while recorded traffic can wait.
After the check
One server is a start. The next step is an inventory of every public endpoint, mail server, VPN and remote-access gateway, then a plan in waves. Our guide to ASD's end-of-2026 milestone explains what that plan contains.
Sources: NIST, FIPS 203; OpenSSL 3.5 release notes. Checked on 17 November 2026.
