Warning

An MTA-STS policy is served but no DNS record announces it

The short version

Publish a v=STSv1 TXT record at _mta-sts so senders know to read the policy.

What it means

A valid-looking policy file is served at https://mta-sts.<your domain>/.well-known/mta-sts.txt, but there is no _mta-sts TXT record announcing it. Senders look for the DNS record first and only then fetch the file, so as things stand nobody reads your policy.

Why it matters

Without the record, MTA-STS is switched off for your domain no matter what the file says. This usually happens when the file was set up first and the DNS step was forgotten, or when the record was removed during a DNS move while the website kept serving the file.

How to fix it

  1. At your DNS host, add a TXT record named _mta-sts (the full name is _mta-sts.<your domain>).
  2. Set the value to v=STSv1; id= followed by a version made of letters and digits, for example v=STSv1; id=20261114.
  3. Check that the policy file's mx: lines list every mail server in your MX records before you publish, especially if the file says mode: enforce.
  4. Keep the id in mind: change it every time you edit the policy file, so senders know to fetch the new one.

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 record row should now say present, and the MTA-STS verdict should follow the policy's mode.