Quantum Readiness
Is your browser using post-quantum encryption? We check whether your browser version ships ML-KEM (post-quantum key exchange) by default — and explain your “harvest now, decrypt later” exposure.
—
This is based on your detected browser and version, not a live reading of your TLS handshake — browsers don't expose handshake key-share details to JavaScript. Post-quantum protection also requires the server you connect to to support ML-KEM.
🔐 What is post-quantum crypto?
Future quantum computers could break today's RSA and elliptic-curve key exchange. Post-quantum algorithms like ML-KEM (formerly Kyber) resist that. Major browsers now negotiate it in TLS 1.3 when the server supports it.
⏳ Harvest now, decrypt later
Adversaries can record encrypted traffic today and decrypt it years later once quantum computers mature. Anything sensitive sent over non-PQ connections now is exposed to that future risk.
✅ What to do
- Keep your browser fully updated
- Prefer services/CDNs that have enabled PQ TLS
- For long-lived secrets, assume non-PQ traffic may be harvested