The third edition of the PQC Vendor Scorecard covers 53 vendor products in six categories: cloud infrastructure, browsers and CDNs, networking, HSM and key management, databases, and SaaS and collaboration. 35 of the products are measured on their customer-facing hosts, 123 hosts in all. The other 18, among them the four browsers, the firewall and router firmware and the end-to-end encryption layers, have no host that a customer's data crosses; they are read from vendor documentation alone and marked not measured. The measured figures come from five consecutive daily scans by the production scheduler, 30 October to 3 November 2026. The Q1 and Q2 editions were read from vendor material only.
Two readings per product
Each product carries a status and a measurement. The status is deployed, available, announced or none, read from the vendor's own dated material with the URL given; a press article or a third-party tracker is not material. The measured columns are the key exchange group each host negotiates by default and the post-quantum groups it accepts on request, the signature algorithm of the leaf certificate, the weakest protocol version or cipher suite the host still offers, who serves the host, and the grade, which is the worst grade across the product's hosts. A host is in a product's row when a paying customer's data or credentials cross it in normal use: sign-in, API, data plane, mail for mail products, tunnel and client-connect endpoints. Marketing sites, documentation, status pages and corporate mail are not.
Deployed requires post-quantum key exchange negotiated by default on every host in the row. A product whose material says deployed but whose hosts negotiate a classical group by default reads available, is marked as such, and moves on that reading. Two products read that way in this edition. AWS core services negotiate ML-KEM on STS and EC2 and x25519 on the SES submission host. Internxt Drive negotiates ML-KEM on its gateway and drive hosts and x25519 on its API host.
Results
11 measured products carry vendor material saying post-quantum key exchange is deployed. 9 of them negotiate ML-KEM by default on every host scanned. Of the 35 measured products, 15 negotiate it by default on every host and 27 on at least one. Every post-quantum negotiation in the cohort is X25519MLKEM768. No host negotiates another post-quantum group by default, and no host presented a post-quantum certificate: every leaf certificate is signed with RSA or ECDSA. Seven products still accept the pre-standard X25519Kyber768Draft00 on request beside the standard group. Twelve products negotiate ML-KEM on some hosts and not others; the hosts that do not are most often mail hosts and API endpoints.
| Category | Measured | ML-KEM by default on every host | On some hosts | On none | Documentation-only |
|---|---|---|---|---|---|
| Cloud infrastructure | 9 | 4 | 3 | 2 | 0 |
| Browsers and CDNs | 3 | 3 | 0 | 0 | 4 |
| Networking | 4 | 0 | 3 | 1 | 4 |
| HSM and key management | 2 | 2 | 0 | 0 | 3 |
| Databases | 5 | 2 | 3 | 0 | 2 |
| SaaS and collaboration | 12 | 4 | 3 | 5 | 5 |
Juniper Mist counts among the products negotiating on some hosts because one of its four hosts did not answer a plain TLS connection in the window; the three that answered negotiate ML-KEM.
Findings by category
In cloud infrastructure, AWS negotiates ML-KEM by default on STS, EC2, every S3 endpoint and KMS, with SecP256r1MLKEM768 accepted on request. Google negotiates it on every Cloud, Workspace and Gmail host, the MX and the SMTP relay included. Microsoft's Azure hosts negotiate classical groups except the portal, which moved to ML-KEM in September. Dropbox and Box negotiate classical groups on every host and accept no post-quantum group on request.
All three edges, Cloudflare, Akamai and Fastly, negotiate ML-KEM by default on every host, Cloudflare's Tunnel endpoint on port 7844 and its WARP client API among them. The four browsers are read from release notes: Chrome, Firefox and Edge enable the hybrid group by default, and Apple's platform statement covers Safari on iOS 26 and macOS 26.
In networking, the appliance rows are documentation-only: Fortinet and Palo Alto ship ML-KEM in firmware a customer enables, Cisco has dated targets for FTD 10.5 and ASA 9.25, and Junos documents RFC 8784 pre-shared keys, which are not NIST post-quantum cryptography. On the vendors' own services, Juniper Mist negotiates ML-KEM on its API, console and device-connect host, Palo Alto's SASE API and WildFire negotiate it while Prisma Access's API and the app portal do not, Cisco's Meraki API and Webex negotiate it while the Meraki dashboard and Umbrella do not, and Fortinet's cloud services negotiate classical groups on every host.
In HSM and key management, AWS KMS negotiates ML-KEM on its standard and FIPS endpoints in both regions, and Google Cloud KMS on its endpoint. Thales Luna ships ML-KEM and ML-DSA, and Entrust nShield ML-KEM, ML-DSA and SLH-DSA, in firmware a customer installs and enables; by both vendors' own release notes, the firmware that carries them is not the FIPS 140-3 validated firmware. Azure Key Vault and Managed HSM have no Microsoft material naming a post-quantum key type or a date.
In databases, DynamoDB's endpoint negotiates ML-KEM by default and is the one product in the cohort whose every host accepts SecP384r1MLKEM1024 on request. The RDS control plane negotiates it too; the RDS and Aurora data planes are per-instance and read from AWS's material, which makes the hybrid group an opt-in on PostgreSQL 18 and MySQL 8.4. MongoDB Atlas's three cluster hosts on port 27017 negotiate ML-KEM and accept all three hybrid groups; the Atlas control plane negotiates x25519. Oracle's identity and IaaS endpoints and the console negotiate ML-KEM, the Autonomous Database endpoint and the OCI email submission host do not. Snowflake's web application negotiates ML-KEM; the trial account's data plane negotiates x25519. No Microsoft material names SQL Server or Azure SQL.
In SaaS and collaboration, Proton Mail negotiates ML-KEM by default on its sign-in, webmail, API and both mail exchangers and reads A on all five hosts, with no vendor material on the transport. Zoom's three service hosts and Signal's three service hosts negotiate it. Workday negotiates it on four of five hosts and ServiceNow on its sign-in host. Microsoft 365 negotiates classical groups on all six hosts, Exchange Online's MX and submission included. Salesforce, Slack and SAP's Cloud Foundry hosts negotiate classical groups on every host and accept no post-quantum group on request. Apple's identity host negotiates ML-KEM; its push host and iCloud Mail's IMAP, submission and exchanger hosts negotiate x25519. mailbox.org's two mail exchangers and submission host negotiate ML-KEM; its sign-in, webmail and IMAP hosts do not. Tuta's app host negotiates secp256r1 and its mail exchanger x25519. The end-to-end rows, TutaCrypt, Proton's post-quantum OpenPGP, Signal's PQXDH, iMessage's PQ3 and Zoom's end-to-end encryption, state each vendor's description of its own protocol; the scorecard does not assess key custody or verify the protocol.
Grades
The grade is set by the weakest thing a host still offers. Nine products read F because at least one host still accepts TLS 1.0, TLS 1.1 or a 3DES cipher suite; six of those nine negotiate ML-KEM by default on every host. Google's endpoints, Cloudflare's WARP client API, Signal's storage and CDN hosts, Fortinet's FortiGuard services, Apple's iCloud Mail exchangers and Tuta's mail exchanger are in that group. Across the 34 products with a grade, two read A, one B, six C, sixteen D and nine F.
Movement since Q2
Movement is read on the status scale against the Q2 edition's status, corrected where it rested on no vendor source. Three products improved and one degraded on the effective status. Google Workspace and Google Cloud KMS moved to deployed on Google's August statement and negotiate ML-KEM on every host. RDS and Aurora moved to available on the PostgreSQL 18 announcement. Internxt reads available because its API host negotiates x25519, although its material says deployed. Of the sixteen measured products new to this edition, Google Cloud, Fastly, Zoom, Signal, Juniper Mist and Proton Mail negotiate ML-KEM by default on every host that answered; Fortinet's cloud services, SAP Business Technology Platform and Tuta's mail hosts negotiate it on none; the other seven negotiate it on some hosts.
Transitions in the series
Thirteen of the hosts have been in the scanner's other cohorts since June 2026, and their series show when a host moved. Five hosts carry both a classical and a post-quantum reading after measurement began: Oracle's console in July, Akamai's control host in July, ServiceNow's sign-in host in August, the Azure portal in September, and Proton's webmail in September. The Oracle, Akamai and Azure hosts alternated between the two groups for some weeks before settling on ML-KEM.
Download
The report carries the full results table per category, the per-product status with the vendor material and date, the post-quantum-by-default reading against each CNSA 2.0 class year, the transitions, the movement table, the regulatory dates and 138 sources.
Download the [PQ]probe PQC Vendor Scorecard: Q3 2026 Edition
Per-host results are not published. A vendor or operator may ask for a re-test of a listed host at hello@pqprobe.com; the answer comes within five business days. The scored products' hosts are scanned once a day, and the Vendor Monitor shows each product's current standing beside what its dated vendor material says.