Observed facts: Cloudflare says it added visibility into post-quantum (PQ) encryption in TLS 1.3. It names HTTP Analytics, Log Explorer, and Logpush as the surfaces where that visibility is available. The company frames the feature as a way for users to check whether their domains are using PQ encryption.
Mechanism: The mechanism is exposure of encryption-related status in existing analytics and log products, rather than a claim that a new cryptographic protocol has been introduced. Mechanism: Customers can use Cloudflare’s HTTP Analytics, Log Explorer, and Logpush to inspect whether TLS 1.3 connections use PQ encryption.
Why now: Why now: As organizations evaluate post-quantum readiness, a visible signal can help them move from assumptions about protection to checking their observed traffic. This is an operationally useful step even though the announcement does not establish universal deployment.
Implications: First implication: Teams can use the newly surfaced information to identify whether PQ encryption is in use for relevant domains and connections, then decide what further checks are needed. The announcement provides visibility, not evidence of automatic remediation or full estate coverage.
Evidence boundary: Evidence boundary: The public announcement excerpt establishes the named products and TLS 1.3 scope, but does not specify eligibility, rollout timing, configuration requirements, or how the signal is calculated. It should not be read as proof that every Cloudflare customer or every connection is covered.
Watch conditions: First watch condition: Watch for Cloudflare documentation clarifying availability, configuration, and the precise meaning of the PQ indicator in each product. Those details would determine how reliably teams can use the signal for readiness tracking.
New branch: This begins a distinct analytical record because no prior New Runtime record was supplied; no relationship to another record is asserted.