Understanding Email Encryption

Email encryption protects against different risks depending on where and when it is applied, so users should start by identifying what they need to defend against. Common concerns include account takeover, malware, mistaken spam filtering and accidental deletion; network interception, data breaches and stolen hardware are less frequent, while journalists or activists may also need protection from provider insiders or government demands. TLS secures the connection between a device and its email provider, with certificates and Certificate Transparency helping verify the provider’s identity. Between mail servers, encryption is usually opportunistic: it is widely used, especially by major providers, but can be downgraded by an active attacker. MTA-STS and DANE can enforce stronger protections, though DANE’s reliance on DNSSEC brings significant outage risks.

Encryption at rest protects stored mail if disks are stolen or improperly discarded, but providers hold the keys and can decrypt data when compelled by a valid court order; it also does not help if an attacker controls a server. Zero-access services keep stored-message keys out of the provider’s hands, which can help against insiders, breaches and legal demands, but the protection has limits. Incoming messages may be exposed before encryption, metadata such as contacts and timestamps can remain visible, and browser-based services may be vulnerable if compromised code is altered to capture credentials. The central argument is that no single method protects against every threat: confidentiality must be weighed alongside availability, integrity and practical trade-offs.