Keyzra

Post-quantum TLS testing

Test the connection, client by client.

A browser and a RHEL server in FIPS mode can get different key exchange from the same host. Keyzra tests each kind of client, shows who can fix the gap, and signs the result.

Free check of one public host. No sign-up.

Sample result

shop.example.com

FIPS paradox

1 of 4 client classes gets post-quantum key exchange from this host.

BrowserX25519MLKEM768Post-quantumWho can fix it: No change

RHEL FIPSP-256, classicalClassical fallbackWho can fix it: CDN provider

CNSA 2.0Needs ML-KEM-1024RefusedWho can fix it: CDN provider

ClassicalX25519ClassicalWho can fix it: Client owner

Next step

Ask the CDN to accept SecP256r1MLKEM768 and SecP384r1MLKEM1024 next to X25519MLKEM768.

Illustrative example · real results are signedHow we test

How it works

Nine ordinary TLS 1.3 handshakes per host, about as many as a few page visits.

  1. 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.

  2. Record what each one gets

    Post-quantum, classical fallback or refused, with the key-exchange group the server chose.

  3. Name who can fix it

    Your server configuration, your CDN or cloud provider, or the client itself.

What you get

One host, measured the way your clients connect to it.

A result per client

Each client class gets its own outcome and negotiated group, instead of one “ready” label for the whole host.

Check a domain

Who can fix it

The provider, your organization or the client, with the exact server setting when the fix is yours.

Provider readiness

Signed evidence

Every result is signed with ML-DSA-65. Anyone can verify it offline, without trusting Keyzra.

Verify a result

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

Browsers77.7%

77.7%

RHEL FIPS-mode clients13.5%

13.5%
3,462 U.S. hosts with TLS 1.3: federal, S&P 500, top 100 banks and FedRAMP providers. Signed runs, 16–17 November 2026.

Check your domain in ten seconds.

  • Four client classes, nine handshakes
  • The FIPS-paradox verdict
  • The exact fix for your server or provider
  • A shareable result link
Check a domain Request access

Monitoring, client replay and audit exports are in early access.