Skip to content
Workspace/Sample full report · github.com
Live platformالعربية
QA

Sample full report

This is a real, complete report for github.com, exactly as a buyer receives it after payment, from a scan run on 2026-11-03. The result changes if the site changes its configuration.

Scan your site and get your report

B

Post-quantum readiness report

github.com

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

Scanned at: 2026-11-03T08:58:57+00:00 · IP 20.26.156.215

What we found

Warning Classical key exchange only (x25519)

We offered X25519MLKEM768, as Chrome and Firefox do, and the server chose x25519. That is secure today, but traffic recorded now could be decrypted once a quantum computer can run Shor's algorithm ("harvest now, decrypt later"). This is the most important item to fix for quantum readiness.

Info Certificate signature (ECDSA-256) is breakable by Shor's algorithm

Every certificate algorithm in use today (RSA, ECDSA, EdDSA) falls to a large quantum computer at any key size; moving to RSA-4096 does not help. It is less urgent than key exchange because impersonation needs the quantum computer at connection time and cannot be done retroactively. The long-term fix is ML-DSA (FIPS 204) certificates once CAs and browsers support them; until then, automate certificate renewal to ease the switch.

How to fix

You need a TLS library with ML-KEM. Quickest routes: upgrade to OpenSSL 3.5 or newer, use a server built with Go 1.24+, or put a proxy such as Cloudflare in front of your site.

nginx (OpenSSL 3.5+)

# check first: nginx -V 2>&1 | grep -o 'OpenSSL [0-9.]*'   (needs 3.5 or newer)
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;

Apache httpd (OpenSSL 3.5+)

SSLProtocol -all +TLSv1.2 +TLSv1.3
SSLOpenSSLConfCmd Groups X25519MLKEM768:X25519:prime256v1

Caddy / Go 1.24+

# X25519MLKEM768 is enabled by default in Go 1.24+ crypto/tls.
# Upgrade Caddy (or your Go server) to a build made with Go 1.24 or newer.

Cloudflare / CDN

# Cloudflare negotiates X25519MLKEM768 with browsers by default.
# Proxy the domain through it (orange cloud) and scan again.

After changing the configuration, scan again here to confirm the grade is A.

Technical details

TLS (probe)TLSv1.3
Key exchange groupx25519
Cipher suite (probe)TLS_AES_128_GCM_SHA256
Post-quantum ClientHello acceptedTrue
TLS (standard handshake)TLSv1.3 · TLS_AES_128_GCM_SHA256
Certificate keyECDSA-256 (secp256r1)
Signature algorithmecdsa-with-SHA256
Subject / Issuergithub.com / Sectigo Limited
Valid until2027-01-27T23:59:59+00:00 (85 days)
Chain verifiedTrue
SANs (2)github.com, www.github.com
Scannerv2.0

Timeline context

  • In August 2024 NIST published ML-KEM (FIPS 203), ML-DSA (FIPS 204) and SLH-DSA (FIPS 205).
  • Draft NIST IR 8547 (2024): RSA and ECC at 112-bit security deprecated after 2030 and disallowed after 2035.
  • Latest published estimate for breaking RSA-2048: under one million noisy physical qubits in under a week (Gidney, 2025). Today's quantum computers are far from that, but data recorded today may stay sensitive for years.
  • Symmetric encryption (AES-128/256, ChaCha20) is not practically affected: per NIST, Grover's speed-up is not a practical threat.

What this scan does not cover

  • Grade A does not mean your site is fully "quantum-safe" or free of vulnerabilities. We measure the public TLS connection on port 443 only.
  • If your site is behind a CDN or proxy (such as Cloudflare), we test the visitor-to-CDN connection, not the CDN-to-origin connection.
  • We do not test the web application itself, email, VPNs, internal systems or how your data is stored.
  • Certificates are still classical (RSA/ECDSA) on every site today, because browsers do not accept ML-DSA certificates yet. That is not a mistake in your setup.
  • The result is a snapshot at scan time; any change to the server or CDN can change it.