Skip to content
Email basics November 4, 2026 · 3 min read · By Smailor Team

Also in FrançaisEspañolDeutsch

Is email encrypted? TLS, STARTTLS and end-to-end

Usually yes, but only part of the way. Most email today is encrypted while travelling between servers, and it sits readable on each server it passes through. Two different things are called "encrypted email", and they protect against different people.

Encryption in transit: TLS

TLS protects the connection, the same way HTTPS does for a website. Someone spying on the network sees scrambled data. It works hop by hop: from your app to your provider, then between each pair of SMTP servers, and from your provider to your app.

The server at each end can read the message. Your provider has it in clear text, and so does the recipient's. TLS protects from the network, not from the providers.

Why TLS between servers can be weak

Between mail servers, TLS is opportunistic. A server offers STARTTLS, and if that works the session is encrypted. If it does not, most servers send in clear text rather than not at all. An attacker on the network can remove the offer and force the downgrade. Two standards close that gap:

  • MTA-STS lets a domain publish, over DNS and HTTPS, that its servers require TLS with a valid certificate. Senders that support it then refuse a downgrade.
  • DANE does similar work with signed DNS records, and needs DNSSEC.
  • TLS-RPT sends you daily reports of TLS failures.

Gmail shows a red open padlock on messages that arrived without TLS. It does not mean the message is dangerous, only that this hop was not encrypted.

End-to-end encryption

End-to-end means only the sender and the recipient hold the keys, so servers carry something they cannot read.

TLS S/MIME OpenPGP
Protects The connection The content The content
Provider can read Yes No No
Setup for users None Certificates Keys to exchange
Used by Nearly everybody Large companies Technical users

Their shared weakness is that both people need a compatible setup, which is why so few use it for everyday mail. Subject lines and headers also often stay unencrypted, since servers need them for delivery.

Services such as Proton Mail make it automatic among their own users. Mail to outsiders falls back to TLS or a link to a protected message.

What each one does not do

  • DKIM is not encryption. It signs a message and leaves it readable.
  • TLS does not prove the sender is honest. A phishing message can arrive perfectly encrypted.
  • A padlock on your webmail protects the connection between your browser and the provider. It says nothing about the rest of the route.

Frequently asked questions

Is it safe to send a password or a bank detail by email?

Avoid it. The message stays readable in several mailboxes for years. Use a one-time link or a password manager's sharing feature.

How do I check that my provider uses TLS?

Send yourself a message from an outside address and read the headers. A line such as by mx.google.com with ESMTPS or a mention of TLS1_3 shows that this hop was encrypted.

Do I need to do anything for TLS on my domain?

If you use a mail provider, no. If you run a server, install a valid certificate and enable STARTTLS. Port 465 or 587 is then used for apps, and port 25 between servers.

Can a company read its employees' mail?

On the company's own server or account, generally yes technically. The legal side depends on your country and on what your staff were told.

Smailor uses TLS on its web app and on mail client connections, and hosts your mail in the EU. Your messages are readable by the service that delivers them, as with any standard mailbox. The privacy policy says who can access what.