MTA-STS explained: stop email being read in transit
MTA-STS tells other mail servers to deliver your email only over an encrypted, verified connection. What it stops, its limits, and what to ask.
You ran a domain check and it says “MTA-STS not found”. Your email works, your SPF and DMARC look fine, so does this one matter?
Short answer: MTA-STS protects the road your email travels on between mail servers. It is a sensible extra layer for businesses that email contracts, invoices or personal data, but it is not the first thing to fix. Here it is in plain English.
What MTA-STS means
MTA-STS stands for Mail Transfer Agent Strict Transport Security. A “mail transfer agent” is just a mail server. The idea is simple: your domain publishes a rule that says “anyone sending email to us must use an encrypted connection, and must check they are talking to the real us.”
Sending servers that understand the rule follow it. Those that do not understand it carry on as before.
The problem it solves
When one mail server sends a message to another, the two servers usually agree to encrypt the connection. But that agreement is often only “if both sides want to”. The standard that defines MTA-STS, RFC 8461, describes two ways an attacker on the network can spoil this:
- Stripping the encryption. The attacker removes the offer to encrypt, so the two servers quietly fall back to sending the message in plain text.
- Pointing the mail at the wrong server. The attacker redirects the connection, for example by tampering with the answer that says which server receives your mail, so the message goes to a server they control.
Without a rule, the sender has no way to know something is wrong. With MTA-STS, a sender that supports it refuses to deliver the message in these cases, rather than handing it over.
How it works, without the jargon
Your domain publishes two things:
- A short public note that says “we have an MTA-STS policy”.
- The policy itself, a small text file served from a web address on your domain over https. It says which mail servers are allowed to receive your email and how long senders should remember the rule.
A sender that supports MTA-STS fetches the policy, remembers it, and from then on only delivers to the listed servers over a verified, encrypted connection.
The three modes
The standard defines three modes, and the order you use them in matters:
- Testing. Problems are reported but email is still delivered. This is where to start.
- Enforce. Senders must not deliver if the check fails. This is the protection you want.
- None. A polite way to switch the policy off.
Going straight to enforce is the classic mistake. If the policy lists the wrong mail server, or the certificate on the policy address expires, legitimate email can be held back or bounce.
What it does not do
Be realistic about its limits:
- It protects email in transit between servers. It does not protect a mailbox that someone breaks into with a stolen password.
- It only helps when the sender supports it. Many large providers do, but not every server.
- The standard itself notes it relies on trusted certificate authorities, and that it cannot stop an attacker who blocks the very first lookup of the policy.
- It does nothing against fake emails sent in your name. That is the job of SPF, DKIM and DMARC, covered in our guide to stopping email spoofing.
A simple picture
Think of a courier delivering a sealed parcel. Normally the courier trusts whatever address and door they are given. MTA-STS is a note on your door that says: “Deliver only to this exact address, and only if the lock and the sign match what I told you. If anything looks different, bring the parcel back.” The courier loses a little time, but the parcel never ends up in the wrong hands.
Do you need it?
Think about who writes to you and what they send. If clients email you contracts, IDs, medical or financial details, it is worth having. If your email is mostly general enquiries, do SPF, DKIM and DMARC first, then come back to this.
What to ask your email provider or developer
You do not need to touch any settings yourself. Ask:
- Do you support MTA-STS for our domain, and can we start in testing mode?
- Who will watch the reports, and who renews the certificate on the policy address?
- When will we move to enforce, and how will we know it is safe?
- Is our SPF, DKIM and DMARC already in good shape?
If the answers are vague, that is a sign the job needs someone who does it regularly.
Want a second opinion?
Our free domain security checker looks at your email and domain setup from the outside and lists what is missing, in plain English. If you would rather have us set it up and keep it healthy, see our domain and email security service.
- Email hello@wpfoss.com
- WhatsApp +254 118 271 160
- Tell us what you need
Sources and further reading
- RFC 8461: SMTP MTA Strict Transport Security (MTA-STS), IETF. Source for the two attacks it addresses, the policy and DNS note, the testing, enforce and none modes, and its stated limits.
