Cloudflare announced per-domain visibility for post-quantum TLS connections on September 29, 2026. TLS is the protocol that protects data sent between a browser and a website. A key exchange establishes the secrets used for that protection. Post-quantum key exchange is designed to resist future quantum-computer attacks. Cloudflare now surfaces the negotiated method for incoming requests, so a site owner can examine actual traffic instead of relying only on Internet-wide averages. Source
The News, Explained
The new fields are available in HTTP Traffic Analytics, Log Explorer, and Logpush. Logpush exports request records for analysis elsewhere. Cloudflare Radar already offers broad adoption figures, but a domain-specific view answers a different question: what portion of this particular site’s traffic negotiated the post-quantum method under TLS 1.3? Source
Two separate connections
A visitor connects to Cloudflare, and Cloudflare may then connect to the website’s origin server. These two legs can negotiate different cryptographic methods. The announcement says site operators can inspect both through the available telemetry. A high percentage on the browser side therefore should not be read as a measurement of the origin connection. Source
For visitor connections, the TLS Key Exchange card is under Analytics → HTTP Traffic; individual records use ClientTLSKeyExchangeGroup. Origin connections can be inspected through OriginTLSKeyExchangeGroup in Logpush. The source explicitly says the origin value is not shown in the HTTP Traffic Analytics card. Source
OYOPICK’s Take
This makes the post-quantum transition an observable operations question. An owner could first inspect X25519MLKEM768 use in the visitor card, then check the origin log field to identify which connection needs attention. If the visitor value is absent, the source points to TLS 1.3 under SSL/TLS → Edge Certificates. Cloudflare negotiates the method automatically when TLS 1.3 and visitor support allow it, so there is no separate post-quantum switch to find. This proposed sequence connects the published checks; it assesses key exchange rather than certifying that the separate transition for certificates and signatures is complete. Source