The internet has moved half of its encryption to post-quantum key exchange, mostly through browser and server updates nobody had to think about. It has not moved its signatures at all: not on certificates, DNSSEC, mail or routing. This is what Witnessory measured this month, and why the second number is the one to watch.
| Top 10,000 websites negotiating it with a browser-grade client | 58.9% |
| SSH servers on those domains offering it | 51.3% |
| Mail servers of the top 1,000 sites, after STARTTLS | 45.1% |
| Public encrypted DNS resolvers on our list | 5 of 13 |
| Certificates in Certificate Transparency logs, post-quantum key or signature | 0 |
| DNSSEC-signed domains in the top 10,000 using a post-quantum algorithm | 0 |
| DKIM keys of the top 1,000 sites that are post-quantum | 0 |
| Routing security (RPKI) objects signed post-quantum, of about 576,000 | 0 |
Medians across networks, one network one vote; the range across networks is given where it matters
below. View c15ae91fb82d, 2026-10-30.
The two halves defend against different attacks, on different clocks.
Key exchange defends against record now, decrypt later: someone stores today's encrypted traffic and opens it once a large enough quantum computer exists. The fix only needs the two ends of a connection to agree, so it ships as a software update. Browsers, large CDNs and OpenSSH did exactly that, and the web reached 59% without most site operators doing anything.
Signatures defend against impersonation: a forged certificate, a forged DNS answer, a forged route, a forged update. Recorded traffic is of no use for that, so the danger starts only when the machine exists. But the fix is far slower. A post-quantum certificate is useless until browsers trust a post-quantum root; a post-quantum DNSSEC zone needs an algorithm number that does not exist yet; DKIM has no post-quantum key type registered. Each needs a standard, then the ecosystem that relies on it, then every operator. And it has to be finished before the machine exists, because a signature that can be forged on that day protects nothing.
So the 0% is not neglect: in most of these systems there is not yet a standard to deploy. It is the measure of how much is still to come, and the reason to watch it from the first non-zero reading.
c15ae91fb82de16ad92971c7de2552291c2eed10079ac9d1a4ce657b6ff436e0, as of
2026-10-30 07:01 UTC. The view is published; the readings and the aggregator are to be
published, and until then the hash is the record.Preliminary: the probes are younger than the 30 days after which they carry full weight. Five networks is a thin basis, and the ranges will move as probes on more networks join.
The view is only as wide as the networks it is measured from. A probe takes a few minutes to install, measures only public servers' handshakes, and never reports where it runs beyond its network and country: run a probe. To see where your own site stands, check it.
Data: Witnessory, CC BY 4.0. Corrections and questions: hello@witnessory.org.