Info

No MTA-STS policy

The short version

Publish an MTA-STS policy so sending servers refuse unencrypted delivery to you.

What it means

Your domain has no MTA-STS policy: there is no _mta-sts DNS record and no policy file at https://mta-sts.<your domain>/.well-known/mta-sts.txt. This is information, not a fault, and it costs nothing in the email grade.

Why it matters

Mail between servers is usually encrypted, but the encryption is optional. Someone who can interfere with the connection can strip it and read or change your incoming mail, and the sending server will carry on without complaint. MTA-STS tells senders that your mail servers always offer encryption with a valid certificate, so they refuse to deliver any other way.

How to fix it

  1. Make sure every mail server in your MX records presents a valid certificate for its own name. Google Workspace and Microsoft 365 already do.
  2. Create a host mta-sts.<your domain> that serves the policy file over HTTPS with a valid certificate. Start with mode: testing, one mx: line per mail server (wildcards such as *.mail.protection.outlook.com are allowed) and max_age: 86400.
  3. Publish a TXT record at _mta-sts.<your domain> with v=STSv1; id= and a version string of letters and digits, such as today's date.
  4. Add a TLS-RPT record so you get reports while testing.

Check it worked

Run the MTA-STS checker on your domain again. Policy files are fetched fresh on every check, but senders cache the old policy for as long as its max_age says, so give real mail servers that long to notice. The result should show the record, the policy and every mail server matched.