Independent annual measurement of post-quantum cryptography adoption across the public internet. Reproducible methodology, open data.
-
Updated
Oct 2, 2026
#
x25519mlkem768
Here are 5 public repositories matching this topic...
Which classes of TLS client can still handshake with your endpoint? pqprobe dials it as a classical client and as a post-quantum one (ML-KEM), and tells a civil refusal apart from a ClientHello it choked on. One static Go binary, zero dependencies, no request ever sent.
tls cli golang security devops monitoring cdn load-balancer handshake sre ansible-inventory observability post-quantum tls13 clienthello zero-dependencies pqc ml-kem x25519mlkem768 tls-intolerance
-
Updated
Sep 22, 2026 - Go
How quantum-safe is .nl? A weekly scan of ~19,000 Dutch domains for post-quantum TLS key exchange (X25519MLKEM768), published as a report
go tls cryptography netherlands post-quantum security-research github-actions internet-measurement ml-kem x25519mlkem768
-
Updated
Oct 5, 2026 - Go
Browser-based TLS 1.3 handshake simulation using the X25519MLKEM768 hybrid post-quantum key exchange (codepoint 0x11EC) per draft-ietf-tls-ecdhe-mlkem-04. Byte-level framing, full key schedule, side-by-side vs. classical X25519.
cryptography hkdf x25519 post-quantum-cryptography key-schedule tls-handshake tls13 kyber crypto-lab ml-kem ml-kem-768 x25519mlkem768 noble-curves rfc8446 ietf-draft hybrid-key-exchange noble-post-quantum pq-migration
-
Updated
Oct 1, 2026 - TypeScript
Add this topic to your repo
To associate your repository with the x25519mlkem768 topic, visit your repo's landing page and select "manage topics."