Blog / How the internet works /
Email encryption basics
Email was designed in a friendlier internet. It was built to get a message from A to B, not to keep it secret on the way. Privacy was bolted on later, in pieces, and the pieces don’t all do the same job.
So when someone says “my email is encrypted”, the honest reply is: which part? Between your phone and your provider? Between your provider and the recipient’s? Sitting on a server? Or readable only by the person you wrote to? Those are four different answers, and most of us only get the first two for free.
Here are the basics, in plain words.
The postcard problem
Think of an unencrypted email as a postcard. Anyone who handles it between sender and recipient could, in theory, read it. Email passes through several hands: your device, your provider’s server, maybe a relay or two, the recipient’s provider, and finally their device.
Encryption is the envelope. The question is whose hands the envelope protects you from, and where it comes off.
Layer 1: encryption in transit (TLS)
This is the one that happens mostly without you noticing. When your email app talks to your provider, the connection is encrypted with TLS, the same technology behind the padlock on websites. I covered the web version in HTTPS and the padlock: what it does and does not promise.
Between mail servers, it works through an upgrade step usually called STARTTLS. Server A says “can we encrypt this?”, server B says yes, and the message travels inside an encrypted tunnel.
Two honest limitations:
- It’s often opportunistic. If the other server doesn’t support TLS, many servers will still deliver the message unencrypted rather than fail. Stricter policies exist, but they aren’t universal.
- It protects the journey, not the destination. Once the message arrives, your provider and the recipient’s provider can read it in the clear.
For most everyday mail, TLS in transit is a perfectly sensible baseline. It stops casual snooping on public networks and in the pipes between servers.
Layer 2: encryption at rest
This means the message is encrypted while stored on a server or your device. Big providers encrypt their disks, and your phone or laptop probably encrypts its storage too (I wrote about the laptop side in BitLocker and device encryption explained).
Useful, but be clear about what it protects against: someone stealing a disk, or a server decommissioned badly. It does not stop the provider itself from reading your mail, because the provider holds the keys. Same for anyone who gets into your account with your password.
Layer 3: end-to-end encryption
Here the message is encrypted on your device and only the recipient’s device can decrypt it. The provider in the middle sees scrambled data. This is what messaging apps like Signal do by default, and I compared a few in encrypted messaging: Signal, WhatsApp and Telegram compared.
For email, the long-standing options are PGP (or OpenPGP) and S/MIME. Both use a pair of keys: a public key you share, and a private key you keep. People encrypt to your public key; only your private key opens it.
Some newer providers offer end-to-end encrypted mailboxes, and some business plans offer client-side encryption features. They work, with trade-offs.
Why email end-to-end encryption is awkward
It’s the reason most people never use it:
- Both sides need to set it up. If the person you’re writing to has no key, you can’t encrypt to them.
- Keys are your problem. Lose the private key and your old messages are gone. Share it carelessly and the protection is gone too.
- Search and previews suffer. A server that can’t read your mail can’t search it for you.
- Metadata stays visible. Even with the body encrypted, who wrote to whom, when, and often the subject line can still be seen by the servers handling it.
That last point matters. Encryption hides the content; it doesn’t hide the fact that a conversation happened.
Encryption is not the same as sender checks
People mix these up constantly. SPF, DKIM and DMARC don’t encrypt anything. They help receiving servers decide whether a message really came from the domain it claims. That’s about trust and spoofing, not secrecy. If you want the full picture of how a message is verified on its way, read how email actually gets delivered: SPF, DKIM and DMARC in plain words.
And “encrypted” doesn’t mean “safe to click”. A phishing email can arrive over a perfectly encrypted connection. The padlock tells you the pipe is private, not that the sender is honest.
What this means if you run a website
If your site sends email (order confirmations, contact-form notifications, password resets), a few things follow:
- Use a proper mail service or SMTP connection with TLS rather than relying on the server’s default mail function. Most reputable providers do this already; it’s worth knowing it’s on.
- Don’t put secrets in email. Passwords, API keys and one-time recovery links shouldn’t be sent in plain messages if you can avoid it. Send a link to a secure page instead, and make the link expire.
- Protect the mailbox itself. The strongest encryption in the world doesn’t help if someone logs into your account. Use a password manager and two-factor authentication. I made the case in email security settings worth turning on.
- Tell your visitors the truth. If your contact form says “your message is encrypted”, make sure you can back that up. Usually the honest claim is “sent over a secure connection”.
Common myths
“Gmail/Outlook email is end-to-end encrypted.” Not by default. It uses TLS in transit and encryption at rest, but the provider can process your messages.
“If I delete it, it’s gone.” Copies may exist in the recipient’s mailbox, backups and anywhere it was forwarded.
“Encryption means nobody can ever read it.” It means the specific attacker you were worried about can’t, as long as you handled keys and accounts properly.
“Only people with something to hide need it.” Medical details, contracts, ID scans and invoices are ordinary things that deserve an envelope.
Key takeaways
- Three layers: in transit (TLS), at rest, and end to end. Most email gets the first two, not the third.
- End-to-end email encryption works but needs effort from both sides.
- Encryption hides content, not metadata.
- It’s separate from SPF, DKIM and DMARC, which are about sender trust.
- For most people, a strong password, two-factor login and a sensible habit about what goes into email do more than any extra tool.
FAQ
Is normal email secure enough?
For everyday messages, yes, if your account is well protected. For anything sensitive, such as IDs or financial documents, consider sharing a link to a protected file instead, or using an end-to-end encrypted option.
Do I need PGP?
Probably not. If you handle sensitive material and your contacts are willing to use it, it’s worth learning. Otherwise it creates more friction than it removes.
What’s the single best step?
Lock the account. A strong unique password and two-factor authentication close the door that attackers actually use most.
Related reading
- Online privacy basics for normal people
- Tor explained
- VPNs explained: when you need one and when you do not
Next time you’re about to email something sensitive, ask one question first: who could read this on the way, and who could read it once it lands? If the honest answer bothers you, send it another way.