Signal Can Now Check the Key Before You Trust the Chat

You open Signal, tap a contact’s name, choose View Safety Number, and find a new button marked Verify automatically. If the check succeeds, Signal shows a green tick and the words Encryption verified. That small result answers a question most people never knew their phone had to ask: did the app receive the right encryption key for this person?

Signal introduced Automatic Key Verification on 11 August 2026. The feature adds several independent checks around the directory that connects a phone number or username to an encryption key. Signal, Cloudflare, and Trail of Bits each watch the record for inconsistent changes, while Signal apps check their own entries and can check a contact when the user asks. (Signal, Trail of Bits)

This is a useful security improvement, especially because it turns a difficult manual ritual into a button ordinary people may actually press. It does not prove that the person holding the other phone is who they claim to be. It cannot rescue a contact whose whole Signal account and phone number have been taken over. Think of the green tick as a check on the route to the mailbox, not a passport check on the person opening it.

The good news comes first. You do not need to verify every Signal conversation or learn how cryptographic trees work. Update Signal, switch on Automatic Key Verification if it has not arrived enabled for you, and use it for the few conversations where a hidden substitution would cause real harm. For an everyday family chat, encryption still works without turning every message into an inspection.

What Signal changed in August 2026

Every encrypted Signal conversation depends on a key held by each participant’s device. Your contact’s public key is the address your app uses when it locks a message for them. Their private key stays on their device and opens it. Before your app can send the first locked message, it has to ask Signal’s directory which public key belongs to that contact.

That directory is necessary because people change phones, reinstall apps, add linked devices, and update phone numbers. A paper address book in your pocket cannot keep up. Signal therefore acts rather like a post office directory: your app asks where Alice’s locked mailbox is, then uses the listed address. The message remains unreadable to Signal, but the accuracy of the directory still matters.

The hard case appears if somebody powerful enough to alter that directory gives Bob a false address for Alice. Bob then locks the message with an attacker’s key, believing it belongs to Alice. The attacker could open the message, read or alter it, lock it again with Alice’s real key, and forward it. Both ends might continue to see an encrypted conversation while the unexpected person sits between them. Security people call this a man-in-the-middle attack; Signal uses the friendlier name “Mallory in the middle.” (Signal)

Signal describes that attack as advanced and unlikely. It would require an outsider to get past the security of major cloud providers or a privileged insider to target a specific account. There is no claim in Signal’s announcement that such a compromise has happened. The new feature addresses the design possibility before it becomes a known incident, which is exactly when good security engineering should act.

Until August 2026, Signal’s strongest answer was its safety number. Every one-to-one conversation has a long numeric code and a QR code derived from the participants’ keys. You and your contact can compare those codes in person, scan each other’s QR displays, or compare through another trusted route. A match gives strong evidence that both of you see the same keys rather than keys supplied by somebody in the middle.

The mathematics worked, but the human ceremony stood in the way. Two people had to understand why the comparison mattered, find the screen, and arrange a second trustworthy contact route. Many careful people never did it, while those facing a serious risk could still make a mistake by comparing through the same potentially compromised conversation.

Automatic Key Verification adds a second route. Signal records public-key associations and changes in a tamper-evident history. Apps and independent auditors check that history for consistency. When you tap Verify automatically, your app checks whether the key it received for your contact agrees with that shared record. The old safety number remains available because the two checks answer related but different questions.

That distinction gives the feature its real value. Strong protection that sits behind a ritual almost nobody performs has limited reach. A clear button brings the check into normal use without weakening the manual option for journalists, sources, activists, executives, families handling a crisis, or anyone else who needs stronger proof.

Why encrypted messages still need a directory

End-to-end encryption is often explained as a sealed envelope that only the recipient can open. That picture is useful, but it skips the address. Before you can seal the envelope for Alice, you need a reliable way to obtain the lock that belongs to Alice rather than one quietly supplied by Mallory.

Public-key encryption splits the job between two related keys. The public key can be handed out widely and used to lock information for its owner. The private key stays secret and unlocks it. Signal’s real protocol uses several kinds of keys and changes some of them over time, but the mailbox model is enough to understand the directory problem. (Signal)

Suppose your sister replaces her phone. Signal has to associate her account with keys from the new device. Your app has to learn about the change before the next conversation can proceed normally. A directory handles that update, yet any central directory creates a narrow point of trust: the app must believe that the answer it receives is the answer everyone else receives.

The obvious fix would be to publish every change in a permanent ledger. If an address changes, another entry is appended. Old pages cannot be silently rewritten. Your sister can inspect the entries about her, and your phone can inspect the current entry when it needs to send her a message.

A giant ledger brings a practical problem. Millions of registrations, device changes, and account updates make a page-by-page search absurd. Signal adds index structures that let an app obtain a small proof about one account without downloading the full history. The app can check that proof against a summary of the whole structure, rather like using an index to find the relevant pages while also checking the book has not been swapped.

There is one more trap. A dishonest directory might keep two books. It could show a clean history to auditors and most users, then show a private, altered history to one targeted pair. Each version could look internally neat. The lie lives in the fact that different people received different versions.

Independent auditors make that split harder to sustain. Signal runs one auditor, while Cloudflare and Trail of Bits run two others. Each follows the sequence of updates and signs a summary after checking that the new state grows consistently from the state it already accepted. Signal clients currently require recent signatures from all three auditors for the verification system to succeed. (Trail of Bits)

Cloudflare says its auditor periodically fetches batches of updates, checks that each one is consistent with the history before it, and signs the result. The auditor works on cryptographic proofs rather than plain user records. According to Cloudflare, it does not see phone numbers, usernames, public keys, or message contents while doing this job. (Cloudflare)

Trail of Bits built its auditor separately from Signal’s reference implementation. That independence matters. Three copies made from the same code could share one mistake. A separate implementation based on the public specification offers a better chance of catching disagreement in how the rules are interpreted.

The result is called key transparency. The name sounds abstract, but its promise is plain: a service should have a much harder time giving one person a secret, altered map of everybody’s keys while showing a clean map to everybody else. Changes leave evidence, and outside witnesses keep copies of the sequence.

What the green tick actually proves

A successful automatic check says that Signal’s key-transparency system found a consistent association between the account identifier and the public key being used by the conversation. The result gives you evidence against a quiet substitution of a special key that differs from the shared record. That is the narrow, useful claim behind Encryption verified.

The check adds value even though Signal conversations were already end-to-end encrypted. Encryption protects a message after the right key has been chosen. Key verification helps answer whether the app chose the expected key in the first place. A perfectly sealed parcel sent to a substituted address still reaches the wrong door.

Your Signal app also checks its own entries periodically. That means your device can notice if the shared record contains keys for your account that do not belong to your devices. If the app cannot verify the log or sees an unexpected key, Trail of Bits says it presents a warning that Automatic Key Verification is unavailable for the device. Other technical or availability problems can produce the same warning, so failure should prompt a manual check rather than an instant conclusion that somebody attacked you. (Trail of Bits)

The timing has an honest limit. Trail of Bits says clients require each tree summary to belong to a history endorsed by all registered auditors within the previous seven days. A fully malicious server could therefore maintain a separate view for as long as one week before client applications began displaying warnings. That window does not make the system pointless. It defines how quickly the witnesses force a long-running lie into view. (Trail of Bits)

The auditors do not read messages. They are checking the consistency of the map, not sitting in the conversation. Cloudflare says it sees cryptographic proofs rather than the plain identifiers and keys in the log. Signal says identifiers are obscured before they enter the structures the auditors inspect, and lookups are unauthenticated rather than tied to a particular Signal account. (Signal, Cloudflare)

A green tick also does not mean the conversation will remain safe regardless of what happens next. If your contact adds a device, reinstalls Signal, or changes the account in a way that updates its keys, the record may legitimately change. Signal’s checks follow those changes. Your job is to pay attention when the app reports an unexpected change or when the stakes make identity important.

For most people, the button should be treated like checking the address before sending an important parcel. You do not inspect the route for every joke, recipe, or family photograph. You check when the content would hurt if misdirected, when a contact has just changed devices under strange circumstances, or when somebody asks you to act on sensitive instructions.

The Digital Fortress uses the idea of spending patience where it buys the most safety. This feature fits that rule nicely. Verify the lawyer handling a transfer, the family member asking for urgent money, the colleague sending recovery information, or the source discussing something dangerous. The football chat can carry on without a ceremony.

The important limits

Key transparency checks a relationship between an identifier and a key. It does not verify the flesh-and-blood identity behind the identifier. Signal states this plainly: Alice and Bob can check that they have the key recorded for an account, but they still need another verification step if Mallory has taken full control of Alice’s account. (Signal)

Imagine that a criminal takes over a person’s phone number, registers Signal again, and controls the resulting account. The transparency record may accurately show the new key associated with that account. Everybody can see one consistent history, while the wrong person now controls the endpoint. A ledger can expose a hidden fork; it cannot decide whether a legitimate-looking account change happened under coercion or theft.

A stolen and unlocked phone creates a similar boundary. If somebody can read messages directly on the device, the network encryption has already done its job and delivered them to that device. Automatic verification cannot eject the person holding it. Screen locks, device updates, remote-loss controls, and quick action after theft still matter.

Malware on either endpoint sits outside the feature’s main promise too. Software that can read a message after Signal decrypts it does not need to substitute a directory key. The route can be clean while the room at the end is compromised. Keep phones updated and be careful with unofficial Signal builds, strange accessibility permissions, and apps installed from links in messages.

The current feature also has a phone-number limitation. Signal says your app can automatically check another person’s key only when it has that person’s phone number. If you began the conversation through a username and never exchanged phone numbers, automatic verification may be unavailable. That limitation protects some of the privacy benefit of usernames, but it means the easy check cannot cover every contact. (Signal)

An out-of-date number can cause trouble as well. Your contact may change numbers while your address book still holds the old one. Signal says that does not damage the underlying encrypted conversation or the contact’s public key, but it can prevent automatic verification because your phone is asking about stale information. Updating the saved number may restore the check.

Group conversations deserve another small warning. The announcement and support flow focus on checking a Signal connection through that person’s safety-number screen. A group name and picture can be copied, and an unexpected member can still be added if group permissions allow it. Before sharing something sensitive in a group, check the member list rather than treating one verified contact as proof about everybody present.

A green tick cannot tell whether a message itself is truthful. A verified family member can still have their phone borrowed, be pressured into sending a message, or simply be mistaken. If “your brother” asks for a bank transfer to a new account, verification reduces one technical route for impersonation. Calling him on a known number remains a sensible check on the request.

These limits do not diminish the feature. They keep its promise usable. Security tools become dangerous when people credit them with powers they never claimed, then stop checking the risks left outside the box.

When safety numbers still matter

The manual safety number remains Signal’s strongest direct comparison between two participants. When you scan each other’s QR codes in person, both phones compare information derived from the conversation keys without relying on a third route to tell you that the match is correct. For people with a real chance of targeted interception, that ceremony earns its place.

Journalists meeting a confidential source should still compare safety numbers when they can do so safely. Activists operating under state pressure, lawyers exchanging privileged material, executives authorising large payments, and administrators passing recovery secrets have similar reasons. The automatic check is a strong baseline, while direct comparison adds evidence that reaches beyond the directory’s shared history.

Distance makes the choice harder. Two people may be unable to meet, and comparing the number inside the same Signal conversation is circular. If the conversation had an unexpected party, that party could influence what each side sees or says. Use a second route you already trust, such as a known phone call, a video conversation where you recognise the person, or a previously established contact method.

Do not send a safety-number screenshot through the unverified chat and treat its arrival as independent proof. That is the digital version of asking the person at the suspicious front desk whether the front desk is honest. A second channel earns its value by failing differently.

Safety numbers can change for ordinary reasons. A contact may replace a phone or reinstall Signal. Treat a change as a prompt, not a siren. Ask the person through a known route whether they changed devices, then compare again if the conversation matters.

Automatic verification is particularly helpful between those high-stakes moments. It lets the app and outside auditors keep watching the shared record rather than asking two people to repeat a long number every week. Manual verification can then be reserved for first contact, a surprising change, or a decision with serious consequences.

Here is a useful household rule: use the automatic check for an important conversation today, and use a direct safety-number comparison when identity itself is part of the risk. If a parent receives an urgent request for money from a child, call the child on the saved number. If a solicitor sends new bank details, confirm through the office number you already know. Encryption protects the conversation; verification protects the route; human confirmation protects the decision.

Nobody needs to do this for every chat. A security habit that demands constant suspicion will be abandoned. Pick the few relationships where a substituted identity could move money, expose somebody, or open another account, and give those relationships the extra minute.

What to do in Signal now

The new feature is meant to reduce work, so keep the setup proportionate. You need a current Signal app, the privacy setting enabled where necessary, and a simple rule for which contacts deserve a check. The steps below should take less time than explaining the phrase “key transparency” at the dinner table.

1. Update Signal from the normal app store: Install the current release from Apple’s App Store, Google Play, or Signal’s official download route. A friend forwarding an installation file is the wrong way to obtain a security update. Open Signal after updating and let it finish any normal migration work.

2. Find the Automatic Key Verification setting: Trail of Bits gives the path as Settings > Privacy > Advanced > Automatic Key Verification. Turn it on if the option is present and disabled. Rollouts and platform versions can differ, so update first if the setting has not appeared. (Trail of Bits)

3. Test it on one important contact: Open the conversation, tap the person’s profile, choose View Safety Number, then tap Verify automatically. A successful check shows a green tick with Encryption verified. Start with somebody whose messages could lead you to send money, disclose private information, or reset an account. (Signal)

4. Treat an unavailable result as a reason to pause: Failure can have harmless causes, including an unsupported username-only contact, an old phone number, a rollout gap, or a temporary service problem. Check the number in your address book, update both apps, and try later. For an urgent and sensitive conversation, compare safety numbers through another trusted route.

5. Keep manual verification for the highest stakes: Scan QR codes in person when practical. At a distance, compare through a known second channel. Once you have verified somebody, pay attention if Signal later reports a safety-number change.

6. Verify requests as well as keys: A green tick does not make an unusual demand sensible. Call before sending money to a new account, sharing a recovery code, or acting on a sudden story that removes your chance to pause. Use a number you already had rather than one supplied in the request.

7. Protect the phone at both ends: Use a screen lock, install operating-system updates, and remove apps you no longer trust. Turn on Signal’s Registration Lock and keep your Signal PIN private if those options fit your setup. Verification works best when the devices holding the private keys are cared for too.

That is enough for most households. You do not need to photograph every safety number, keep a spreadsheet of keys, or inspect the public code. Update, enable, verify the contacts that carry consequences, and keep a second route for unusual requests.

For a small business, write one sentence into the payment process: “Changes to bank details are confirmed by a call to the supplier using the number already on file.” Signal verification strengthens the message route, while that sentence protects the money decision. The two controls cover different mistakes.

Families can use an equally simple version. Choose a phrase or callback habit for urgent money requests, and never let urgency cancel the callback. Automatic verification makes silent key substitution harder; a familiar voice and a known number help when the account or phone itself may be in somebody else’s hands.

What to ignore

Ignore claims that Signal has only now become encrypted. Signal says its service remains end-to-end encrypted as before. Automatic Key Verification adds a check around the public keys used to start and maintain those encrypted relationships. It strengthens one edge of the system rather than switching encryption on for the first time. (Signal)

Ignore claims that the feature makes interception impossible. Trail of Bits documents a potential period of up to seven days before warnings appear if a completely malicious server maintains a split view, because clients require auditor endorsements from within that window. Endpoint compromise and full account takeover also sit outside the green tick’s narrow claim. (Trail of Bits)

Ignore anybody telling ordinary families to compare every safety number before sending a message. That standard sounds pure and fails in real life. Reserve the manual ritual for conversations where identity has consequences, and let the automatic system lower the floor everywhere else it is available.

Ignore the idea that Cloudflare or Trail of Bits can now read Signal chats. Their role is to check cryptographic summaries for a consistent history. Cloudflare says its auditor does not see users’ phone numbers, usernames, public keys, or message contents. Signal describes the user data in the log as cryptographically obscured. (Cloudflare, Signal)

Ignore the pressure to understand every component before pressing the button. You already rely on tamper-evident records elsewhere. A bank statement gives you a sequence of transactions so a vanished payment leaves a discrepancy. A parcel-tracking history records handoffs so two parties cannot quietly tell incompatible stories forever. Signal’s implementation uses harder mathematics, but the useful instinct is familiar: keep a history and ask independent witnesses whether everybody received the same version.

Be cautious with screenshots of green ticks. A screenshot proves very little because it can be old, edited, or taken from another conversation. Perform the check on your own device. If the decision matters enough to need evidence, use direct safety-number comparison and confirm the request separately.

The calm position is also the technically honest one. Signal has reduced a subtle trust problem and made the check easier to use. The remaining limits are reasons to use the feature correctly, not reasons to dismiss it.

A better default, with an honest boundary

Automatic Key Verification improves Signal where security often fails: the gap between a strong design and a human being with dinner on the stove. Safety numbers already gave users a direct way to catch substituted keys, but they asked two people to coordinate a careful comparison. The new button brings a meaningful part of that assurance into the ordinary flow.

The mechanism deserves credit. Signal keeps a tamper-evident history of key associations. Its app checks entries. Three auditors, operated by Signal, Cloudflare, and Trail of Bits, sign consistent states. A targeted directory lie becomes harder to hide because the attacker must maintain conflicting histories against clients and independent witnesses.

The boundary deserves equal attention. The system verifies a key association, not a person’s identity, honesty, physical control of a phone, or freedom from malware. Username-only contacts may not support the automatic check today. A completely malicious service could sustain a split view for a limited period before the auditor-signature window causes warnings. Serious users should retain direct safety-number comparison.

For everyone else, the action is pleasantly small. Update Signal. Turn on Automatic Key Verification if needed. Check one or two contacts whose messages can move money or expose something private. Pause on warnings and unusual requests. Keep the football chat out of your security project, and you have my blessing to skip verifying the family meme group.

That is how useful security should feel. The machinery works in the background, the warning has a clear meaning, and the person holding the phone has one sensible next step.

If you want calm, practical security notes without the daily panic cycle, the newsletter is one email per month.

Sources

• Signal: Introducing Automatic Key Verification, accessed 2026-08-13
• Trail of Bits: How Trail of Bits helps verify the integrity of your Signal chats, accessed 2026-08-13
• Cloudflare: Signal Taps Cloudflare to Help Protect the Privacy of Hundreds of Millions of Users Through Key Transparency, accessed 2026-08-13
• BleepingComputer: Signal adds new security feature to thwart man-in-the-middle attacks, accessed 2026-08-13