Is KeyBank quantum-safe?
Partly. 9 of 12 public servers under key.com use post-quantum key exchange, the protection against traffic recorded today being decrypted once a large quantum computer exists. Grade B. Scanned October 18, 2026, a partial scan while the certificate logs were unavailable.
3 other servers without post-quantum key exchange
- careers.key.com
- m.key.com
- metrics.key.com
9 servers already protected
- accounts.key.com
- api.key.com
- cdn.key.com
- dev.key.com
- developer.key.com
- developers.key.com
- key.com
- staging.key.com
- www.key.com
What this means
NIST has scheduled the key exchange most servers still use for retirement: deprecated after 2030, disallowed after 2035 (NIST IR 8547). Traffic recorded today can be decrypted once a large quantum computer exists. A server that offers hybrid ML-KEM key exchange closes that today; a server that does not is still open to harvest now, decrypt later.
Hostnames come from public certificate logs plus common service names, kept where the name resolves to a public address, and each is tested from the outside with post-quantum-only TLS 1.3 handshakes. A hostname shows what a server is called, not what traffic it carries; internal systems are out of scope. Method.
Work at KeyBank?
Fleet Watch gives you this scan privately every week, with your suppliers and a report your auditor can verify. The first scan is free.
Scan your own domainBadge
Shows the current grade and updates itself. Anyone may embed it.
<a href="https://latticescan.com/readiness/key.com"><img src="https://latticescan.com/badge/readiness/key.com" alt="quantum readiness"></a>