Is your domain using post-quantum encryption? Now you can see for yourself
Cloudflare adds per-domain post-quantum TLS telemetry to Logpush, Log Explorer, and HTTP Traffic Analytics dashboards.
Cloudflare introduced post-quantum visibility tools that surface the negotiated TLS 1.3 key exchange algorithm for every request, letting customers audit PQ posture, assess compliance ahead of 2030 deadlines, and find cryptographic gaps. Cloudflare Radar shows about 70% of browser-generated traffic to Cloudflare uses hybrid ML-KEM (FIPS 203), while only about 15% of origins Cloudflare connects to support it. X25519MLKEM768 is the only recommended PQ key exchange group in TLS 1.3, and Cloudflare targets full post-quantum security by 2029.
- Per-connection telemetry exposes negotiated key exchange algorithm in three Cloudflare products
- Radar: ~70% of browser traffic to Cloudflare uses hybrid ML-KEM vs ~15% of origins
- X25519MLKEM768 is the only recommended PQ group; unavailable in TLS 1.2 or earlier
- Cloudflare targets 2029 for full post-quantum security; NIST deprecates RSA/ECC by 2030
From the original article
8 min read at blog.cloudflare.com
Cloudflare has added visibility into post-quantum (PQ) encryption in TLS 1. 3 directly into HTTP Analytics, Log Explorer, and Logpush. Learn how to make sure your domain is protected with PQ encryption.
By Andrew Depke · blog.cloudflare.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.