Post-quantum TLS testing
Test the connection, client by client.
Governments have set 2030–2035 deadlines for post-quantum encryption, and most checks look only at what a browser gets. Keyzra tests each kind of client, including RHEL servers in FIPS mode, shows who can fix the gap, and signs every result it publishes.
Real result · U.S.
nist.gov
National Institute of Standards and Technology
Browsers get post-quantum; RHEL FIPS-mode clients get classical.
BrowserX25519MLKEM768✓Post-quantumWho can fix it: No change
RHEL FIPSsecp256r1!Classical fallbackWho can fix it: Cloudflare
CNSA 2.0secp384r1!Classical fallbackWho can fix it: Cloudflare
Next step
Ask Cloudflare to accept SecP256r1MLKEM768 on its edge.
Measured 16 November 2026 · signed with ML-DSA-65Full result
How it works
Nine ordinary TLS 1.3 handshakes per host, about as many as a few page visits.
Connect as four clients
Keyzra offers what a browser, a RHEL server in FIPS mode, a CNSA 2.0 system and a classical client offer.
Record what each one gets
Post-quantum, classical fallback or refused, with the key-exchange group the server chose.
Name who can fix it
Your server configuration, your CDN or cloud provider, or the client itself.
HOST=your-domain.com
# a browser
openssl s_client -connect $HOST:443 \
-groups '*X25519MLKEM768:*X25519:secp256r1:secp384r1' \
</dev/null 2>/dev/null | grep -E 'TLS1.3 group|Temp Key'
Negotiated TLS1.3 group: X25519MLKEM768post-quantum
# a RHEL 10 server in FIPS mode
openssl s_client -connect $HOST:443 \
-groups '*SecP256r1MLKEM768:SecP384r1MLKEM1024:*secp256r1:secp521r1:secp384r1' \
</dev/null 2>/dev/null | grep -E 'TLS1.3 group|Temp Key'
Peer Temp Key: ECDH, prime256v1, 256 bitsclassical
From the latest measurements
Real domains from our signed weekly runs. Each one links to its full result.
Post-quantum for every client
Browsers, RHEL servers in FIPS mode and CNSA 2.0 clients all get it, on every name.
Browsers only
Browsers get post-quantum. A RHEL server in FIPS mode gets classical key exchange.
From the published data
Browsers are mostly covered. FIPS-mode servers are not.
The same U.S. servers that give browsers post-quantum key exchange mostly give RHEL systems in FIPS mode a classical connection. Nothing fails, so nobody sees it.
Hosts that negotiate post-quantum key exchange
Check your own domain
One public host is free, with no sign-up. For all of your domains, weekly monitoring and your own clients, we run pilots with a small number of organizations.