Free tool
Is your website quantum-safe?
Enter a domain and find out in seconds whether its encryption already uses post-quantum key exchange, or could be recorded today and decrypted later.
We only start a TLS handshake and read the server's first reply. No data is sent, nothing is stored, and results are cached for an hour.
You're here from my email. These are the same public checks I ran on your domain, live. If it helps, I'll walk you through the fixes for your setup in 20 minutes, or simply reply to my email with any question. Deepanshu, founder
PQScope inventories the cryptography in your code and every endpoint, writes a CycloneDX CBOM, and gives you a migration plan matched to the 2026, 2030 and 2035 milestones.
Why quantum computers matter for your website
Almost every website protects its traffic with public-key cryptography: RSA or elliptic curves agree the keys and sign the certificate. A large enough quantum computer, running Shor's algorithm, would break both. Nobody has one yet, but encrypted traffic can be recorded today and decrypted later. That threat is called "harvest now, decrypt later", and it's why key exchange is the first thing to fix. Passwords, health records and contracts sent today may still need to stay secret in 10 or 15 years.
What "post-quantum key exchange" means
In August 2024, NIST published ML-KEM (FIPS 203), a key-encapsulation method designed to resist quantum attacks. Browsers and servers now combine it with the classical X25519 exchange in a hybrid called X25519MLKEM768, so a connection is safe as long as either part holds. Current versions of Chrome, Edge and Firefox support it, and Cloudflare and Google offer it by default. Many other servers, load balancers and CDNs still only speak classical key exchange.
How this check works
We start a TLS 1.3 handshake that offers the post-quantum hybrids first and sends no keys. The server has to reply with the group it wants, which tells us whether it supports post-quantum key exchange, without completing a connection or sending any data. A second, older-style handshake lets us read the certificate, which is still classical everywhere: public certificate authorities don't issue post-quantum certificates yet. For sites behind Cloudflare, which we can't probe directly, the result is inferred from Cloudflare's defaults and labelled as such.
How to turn it on
- Behind a CDN: Cloudflare enables it by default. On other CDNs and cloud load balancers, look for a post-quantum or hybrid key exchange option in the TLS settings.
- nginx or Apache with OpenSSL 3.5 or later: list X25519MLKEM768 first in the key-exchange groups, for example ssl_ecdh_curve X25519MLKEM768:X25519:prime256v1 in nginx.
- Go 1.24 or later: X25519MLKEM768 is on by default in crypto/tls.
- Keep the classical groups in the list, so older clients still connect.
Deadlines that are coming
The EU's coordinated roadmap asks member states to have national plans and first steps in place by the end of 2026, to protect high-risk systems by 2030, and medium-risk systems by 2035. The US has similar targets for federal systems. Regulators and enterprise buyers are starting to ask suppliers for a cryptographic inventory, and the website is the easiest place to start.
FAQ
Questions
Is this check safe to run on my site?
Yes. It sends one handshake request, the same first message every browser sends, and reads the reply. No connection is completed and no data is exchanged.
My site says 'Not yet'. Is it insecure?
Not today. Classical key exchange is still secure against today's computers. The risk is that recorded traffic could be decrypted in the future, so plan the change now.
Why is my certificate shown as classical?
Every public website certificate is classical today: certificate authorities and browsers haven't started using post-quantum signatures yet. Key exchange is the part you can fix now.
What's X25519MLKEM768?
A hybrid of the classical X25519 key exchange and ML-KEM-768, the post-quantum standard NIST published as FIPS 203. The connection stays safe if either part holds.
Can I check my API or mail server?
This page checks port 443 of one domain. PQScope, our command-line tool, checks any host and port and scans your code too.
Do you store the domains I check?
Results are cached for an hour to avoid repeat probes; we keep only daily usage counts.