Deployment analysis / Scenario explorer
What breaks, and when?
Choose which cryptographic assumptions weaken or fail. Follow the effects on trusted keys, recorded traffic and the next connection.
Impact on
Public TLS certificate authorities
How the keys are counted
Distinct subject public keys are identified by their SPKI fingerprint. A key counts once if any matching certificate is unexpired at the evaluation instant. A cross-signed key can appear in both roles. The Chrome TLS cohort was frozen on 16 November 2026. Later issuance, early distrust, private anchors, leaf keys and dependent signatures fall outside the count. Locally trusted roots can remain accepted past their encoded expiry. Population and source data
Consequences by system
Cost of changing profiles
TLS measurements · SLH-DSA parametersWhat the scenario assumes
Reduced margin means the selected profile falls below a deployment’s security target and needs migration. Practical break means the relevant key can be recovered, accepted signatures forged, or the negotiated secret derived within its useful lifetime. Dates are your inputs. A threshold includes the listed smaller profiles in that family. Each mathematical claim applies independently.
Each result describes a specific configuration. An independent secret can preserve a correctly combined hybrid exchange. A composite signature can still authenticate when verification requires both components and one remains sound. A separately accepted weak credential can still permit impersonation. Assume uncompromised endpoints and sound symmetric encryption, hashes and combiners. Except for the dated CA inventory, there is no measured denominator for how many systems use each profile.
Measured handshake costs · Recent issuance and migration plans · Project overview