End-to-end encryption only holds if each party encrypts to the correct public identity key. On 13 April 2023, Meta Engineering said WhatsApp had launched automatic verification of those keys using key transparency, built on an open-source Auditable Key Directory (AKD). Sean Lawlor and Kevin Lewi wrote that users would no longer have to compare a 60-digit security code for a first automated check, while still being able to scan QR codes out of band. An update on that post later stated that key transparency was fully available on WhatsApp for Android and iOS. The problem the system is meant to address is classic: the chat server hands out public keys. If it, or someone who compromised it, served the wrong key, a sender would encrypt to an impostor. WhatsApp already offered a hash of both parties’ keys as a QR code and 60-digit number. Meta wrote that this remains one of the strongest checks, but that it is awkward in one-to-one chats after device changes, worse in small groups, and near-impossible in a group of 100 people, where it counted 4,950 pairs. Key transparency is described as a consistency mechanism: the same public keys everyone else uses for a phone number are the keys your client uses, with inclusion proofs against an append-only directory. The architecture is two-pronged. WhatsApp hosts an AKD mapping accounts to public keys. Changes are batched into epochs because, Meta wrote, the service sees tens of thousands of registrations and re-registrations per minute. Audit proofs of those epoch transitions are published so anyone can check that history is append-only and not rewritten. Public keys cannot decrypt messages; Meta emphasised that private keys stay on devices. When an account is deleted, public keys are removed from the live mapping, but the fact that some key existed at a point in time remains immutable without revealing what the key was. On 24 September 2024, Cloudflare announced that it had begun verifying those audit proofs as an independent auditor. Thibault Meunier and Mari Galicer described the AKD as a tree whose nodes contain hashes of contact details rather than plaintext phone numbers. WhatsApp’s log emits epochs in the form counter/previous-root/current-root. Cloudflare’s auditor timestamps each epoch in a Durable Object so that a given height is globally unique, then separately validates that the tree transformation from the previous digest to the current one is a correct append-only update using Meta’s rust crate, facebook/akd. Signatures and proofs, Cloudflare wrote, do not contain phone numbers, public keys, or other WhatsApp account metadata. Anyone can repeat the check. Cloudflare published a command-line client named plexi and a public auditor endpoint. Its blog walked through verifying namespace whatsapp.key-transparency.v1, showing a successful signature and proof verification for an example epoch. That demonstration is Cloudflare’s own output on that day; it is not a standing certificate that every future epoch will verify. The same post tied the work to Certificate Transparency and to Cloudflare’s earlier Code Verify partnership for WhatsApp Web, in which a browser extension compares a hash of running web code with a hash Cloudflare has of the committed codebase. Meta’s 2023 post is careful about what the system does not replace. Users who want to verify sessions without using WhatsApp servers at all are still told to use the traditional security-code flow. If the automatic check says a connection may not be secure, Meta recommends falling back to that manual comparison. Key transparency can miss a targeted substitution that is consistent across the directory, or a client that never queries the AKD. It also does not encrypt Cloud API business chats that WhatsApp itself excludes from its end-to-end definition. What this means in practice Security-conscious WhatsApp users in Bangladesh and elsewhere can treat automatic “verified” states as WhatsApp’s client checking an auditable log, optionally cross-signed by Cloudflare, not as a magic guarantee. High-risk users should still compare security codes in person or on a second channel after a phone change. Independent researchers can run plexi against published proofs; that is the intended public accountability path. Cyber71 is not a WhatsApp or Cloudflare partner and cannot obtain extra audit material, force a key rotation, or restore an account whose identity key has changed. What is still unclear Neither Meta nor Cloudflare, in the pages loaded for this briefing, publishes a live dashboard of failed epochs or of how many clients actually complete AKD lookups. Latency between a key change and the next epoch is described as tunable, not as a fixed SLA. Whether every unofficial client, business integration, or older app version performs the check is not something an outside newsroom can verify. Cloudflare’s role is to sign and validate tree transitions; it does not see whether a given conversation’s displayed key matches the directory entry on a user’s screen.

Sources

  1. Cloudflare Blog — Cloudflare helps verify the security of end-to-end encrypted messages by auditing key transparency for WhatsApp2026-09-24
  2. Engineering at Meta — Deploying key transparency at WhatsApp2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All research

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help