google.com
12 endpoints tested · 533 hostnames found in public certificate logs · scanned Jul 14, 2026
Every endpoint we tested uses post-quantum key exchange. Traffic to google.com is safe from someone recording it now and decrypting it later.
Findings
- info
12 endpoints already negotiate post-quantum key exchange
Hybrid ML-KEM is active (X25519MLKEM768). Traffic to these endpoints is protected against retroactive decryption.
android.clients.google.com · google.com · aistudio.google.com · calljoy.area120.google.com · colab.research.google.com · antigravity.google.com · console.au.cloud.google.com · cert-test.sandbox.google.com · console.ch.cloud.google.com · console.ca.cloud.google.com · console.eu.cloud.google.com · console.il.cloud.google.com
- medium
All 12 certificates use classical signature keys
Certificate keys (RSA/ECDSA) are broken by Shor's algorithm, but unlike key exchange this is not retroactively exploitable — a signature only needs to resist forgery while it is still trusted. No publicly-trusted CA issues ML-DSA certificates yet, so there is no action available today. NIST deprecates these algorithms after 2030 and disallows them after 2035.
android.clients.google.com · google.com · aistudio.google.com · calljoy.area120.google.com · colab.research.google.com · antigravity.google.com · console.au.cloud.google.com · cert-test.sandbox.google.com · console.ch.cloud.google.com · console.ca.cloud.google.com · console.eu.cloud.google.com · console.il.cloud.google.com
Endpoints
| Host | Key exchange | TLS | Certificate key |
|---|---|---|---|
| android.clients.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| aistudio.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| calljoy.area120.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| colab.research.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| antigravity.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| console.au.cloud.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| cert-test.sandbox.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| console.ch.cloud.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| console.ca.cloud.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| console.eu.cloud.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
| console.il.cloud.google.com | X25519MLKEM768 | TLSv1.3 | ECDSA prime256v1 |
Compliance evidence
No security questionnaire asks about quantum yet. They do ask what cryptography you run and how you manage it, and most companies struggle to answer that with anything solid. A scan gives you something to point to.
CEK-04 CSA Cloud Controls Matrix | Encryption Algorithm Observed key exchange, cipher suite and certificate key algorithm for every reachable endpoint (12/12 endpoints on post-quantum key exchange). |
CEK-05 CSA Cloud Controls Matrix | Encryption Change Management Baseline of algorithms in use, so any cryptographic change is detectable against a known-good snapshot. |
CEK-07 CSA Cloud Controls Matrix | Encryption Risk Management Quantum exposure assessed per endpoint, separating retroactively-exploitable key exchange from forward-only signature risk. |
CEK-21 CSA Cloud Controls Matrix | Key Inventory Management 100 certificates and 533 hostnames enumerated from public Certificate Transparency logs. |
A.8.24 ISO/IEC 27001:2022 | Use of cryptography Documented, dated record of which cryptographic algorithms are actually deployed — the evidence this control asks for. |
Crypto Inventory US EO 14412 / OMB M-26-15 | Automated Cryptographic Inventory Machine-generated inventory of cryptographic assets, exportable as a CycloneDX CBOM. |
This is only the outside view
A scan like this sees your public endpoints. The rest of your cryptography lives in your code, your internal services, your key stores, and the software you buy from other people. If you run cryptography at the scale of a bank, an airline, or a retailer and want the full picture, or a walkthrough for your security team, get in touch.
Talk to us