B

Post-quantum TLS readiness

github.com

Secure today, exposed to harvest-now-decrypt-later

Short answer

No. As of 2026-11-04, github.com does not negotiate post-quantum key exchange; it uses x25519 over TLSv1.3 (Quantum Aether grade B), so recorded traffic is exposed to harvest-now-decrypt-later.

GradeB
Key exchangex25519
Post-quantumno (classical)
TLSTLSv1.3
Hosting networkMicrosoft Corporation

From a live scan on 2026-11-04T15:52:44+00:00

Show your readiness on your site

post-quantum TLS: B

Markdown
[![Post-quantum TLS grade by Quantum Aether](https://ather-quatum.cloud/badge/github.com.svg)](https://ather-quatum.cloud/?domain=github.com)

Related sites