Post-quantum key exchange · Norway micro companies

What share of Norway micro companies have tls-pq-readiness?

50.86%

50.86% of Norway micro companies (95% CI 44.47–57.23%), measured across 232 companies on 2026-10-01.

hybrid post-quantum: 49.14%classical only: 50.86%
hybrid post-quantum · 49.14%classical only · 50.86%
Trend

Measured every Wednesday since 2026-08-01 — 1 observation to date. Last measured 2026-10-01.

How this is measured

Tier 2. One TLS handshake offering X25519MLKEM768 ahead of the classical curves, then read which group the server actually chose. TLS 1.2 endpoints are excluded, not counted as classical — they have no post-quantum key exchange to decline, and "not on TLS 1.3" is already tls-legacy against a different denominator. Denominator: has_web.

Passive measurement: a single DNS lookup, TLS handshake, or homepage GET per domain. Aggregate-only; no individual company is named. 95% Wilson confidence intervals. Population: national company registries (Companies House, Brreg, SIRENE), sampled by size band and resolved to email-active domains. Parked domains excluded. Snapshot: brreg-norway-per600-seed20260730.

Licensed CC BY 4.0 — reuse with attribution to Quiet Failures. Download: JSON · CSV.

Why it matters

The failure with no symptom at all. The padlock is green, the grade is an A, the protocol is current, and the key exchange is the one part that does not survive contact with a quantum computer — retrospectively, because traffic captured today can be decrypted years later once the capability exists. Nothing about the site will ever look wrong, and by the time it matters the recording has already been made. The 47-day certificate clock has a deadline; this one has a countdown nobody can see.

Limits of this measurement

Measures the key exchange only — a hybrid group protects the session key, not the certificate's signature, so hybrid_pq is not "quantum-safe" end to end and must not be reported as such. Server support is read as offered to our client: a server may prefer a PQ group with a browser that offers a different one. The rate reflects hosting and CDN defaults far more than any decision made by the domain's owner, which is much of the story. Capped at 2,000 domains per run because it needs its own handshake rather than sharing the one the certificate metrics already make.

The same check, other segments

Show the remaining 7 segments

Share or cite this figure

Reuse is free under CC BY 4.0 — attribution to Quiet Failures is all we ask.

Post on X

Embed this stat

Free to reuse under CC BY 4.0 — the card links back and updates as the data does.

<iframe src="https://quietfailures.com/embed/tls-pq-readiness/no-micro" width="380" height="210" style="border:0;max-width:100%" loading="lazy" title="What share of Norway micro companies have tls-pq-readiness?"></iframe>