Post-Quantum Readiness Checker
Test your browser's support for post-quantum cryptography (PQC). Check WebCrypto API capabilities, TLS algorithm support, and get a quantum-readiness score. All tests run locally in your browser.
How Post-Quantum Readiness Checker Works
Check if your browser supports post-quantum cryptography Test TLS algorithms, WebCrypto APIs, and get a quantum readiness score. Provide your input in the form above and the tool analyzes it instantly in your browser, giving you actionable results without sending data to any server.
What Is Post-Quantum Cryptography?
Post-quantum cryptography (PQC) refers to cryptographic algorithms that are resistant to attacks by quantum computers. Current encryption standards like RSA and elliptic curve cryptography (ECC) could be broken by a sufficiently powerful quantum computer using Shor's algorithm. NIST finalized its first PQC standards in 2024: ML-KEM (Kyber) for key encapsulation, ML-DSA (Dilithium) for digital signatures, and SLH-DSA (SPHINCS+) for stateless hash-based signatures.
This tool checks whether your browser and its WebCrypto implementation support these new algorithms, and assesses your overall readiness for the post-quantum transition.
Why Post-Quantum Readiness Matters Now
The threat is not just future — it is present. Nation-state actors are conducting "harvest now, decrypt later" attacks, intercepting encrypted data today to decrypt it once quantum computers become powerful enough. Sensitive data with long shelf lives (medical records, financial data, state secrets, intellectual property) is at immediate risk. Wavestone reports that organizations should begin cryptographic inventory and migration planning now, even before quantum computers reach cryptographic relevance.
Chrome 124+ and other Chromium browsers already support ML-KEM (Kyber) in TLS 1.3 handshakes, making post-quantum key exchange available today. This tool checks if your browser is among them.
The NIST PQC Standards
NIST selected four primary algorithms after an 8-year evaluation: ML-KEM (formerly CRYSTALS-Kyber) for key encapsulation, ML-DSA (formerly CRYSTALS-Dilithium) for digital signatures, SLH-DSA (formerly SPHINCS+) as a conservative signature backup, and FN-DSA (formerly FALCON) for size-optimized signatures. These algorithms are based on lattice problems and hash functions that are believed to resist both classical and quantum attacks.
How to Prepare for Post-Quantum
Start with a cryptographic inventory — identify every system, protocol, and certificate that uses RSA, ECC, or DH key exchange. Prioritize systems handling long-lived sensitive data. Test hybrid PQC modes (classical + PQC) in non-production environments. Update TLS libraries to versions supporting ML-KEM. Plan certificate and key rotation timelines. The transition will take years — starting now gives you time to test, validate, and roll out changes incrementally rather than in a crisis.
Frequently Asked Questions
What is post-quantum cryptography (PQC)?
Post-quantum cryptography refers to encryption algorithms designed to resist attacks from quantum computers. Current algorithms like RSA and ECC could be broken by quantum computers using Shor's algorithm. NIST standardized the first PQC algorithms in 2024: ML-KEM (Kyber), ML-DSA (Dilithium), and SLH-DSA (SPHINCS+).
When will quantum computers break current encryption?
Estimates vary from 10-20 years for cryptographically relevant quantum computers. However, the "harvest now, decrypt later" threat is real today — adversaries collect encrypted data now to decrypt later. NIST recommends beginning migration immediately for long-lived sensitive data.
Does my browser already support post-quantum?
Chrome 124+ and Chromium-based browsers (Edge, Brave, Opera) support hybrid ML-KEM/X25519Kyber768 key exchange in TLS 1.3. Firefox and Safari are working on PQC support. This tool tests your specific browser's capabilities.
What is ML-KEM (Kyber)?
ML-KEM (Module-Lattice Key Encapsulation Mechanism), formerly known as CRYSTALS-Kyber, is NIST's primary post-quantum key encapsulation standard. It enables two parties to establish a shared secret key that is resistant to quantum attacks. Chrome uses it in hybrid mode (X25519Kyber768) combined with classical key exchange for defense-in-depth.
What should developers do to prepare?
Start with a cryptographic inventory of all systems using RSA, ECC, or DH. Update TLS libraries to support TLS 1.3 with PQ extensions. Test hybrid PQC modes in staging environments. Plan certificate rotation timelines. For web apps, ensure servers support X25519Kyber768 in TLS 1.3 negotiation.
Are symmetric algorithms like AES quantum-safe?
Yes, symmetric algorithms (AES-128/256, SHA-256/384/512) are considered quantum-resistant. Grover's algorithm provides only a quadratic speedup against symmetric crypto, meaning AES-256 provides 128-bit security against quantum attacks — still very strong. Only asymmetric algorithms (RSA, ECC, DH) are at risk.