Fail

The MTA-STS record points to a policy we couldn't fetch

The short version

Serve the policy at https://mta-sts.<your domain>/.well-known/mta-sts.txt, or remove the DNS record.

What it means

Your domain publishes an _mta-sts DNS record, so senders expect a policy file, but we couldn't fetch it from https://mta-sts.<your domain>/.well-known/mta-sts.txt. The detail says what happened: the host doesn't exist, it refused the connection, or it answered with an error such as 404.

Why it matters

Senders that support MTA-STS see the record, try to fetch the policy and fail. They then deliver without the policy, so you get none of the protection, and some log the failure on every message. A record pointing nowhere often means the policy host was removed during a website move or a DNS clean-up.

How to fix it

  1. Check that the host name mta-sts.<your domain> has an A or AAAA record (or a CNAME to your hosting service).
  2. Make sure it serves HTTPS with a valid certificate for exactly that name.
  3. Put the policy file at the path /.well-known/mta-sts.txt, served directly with status 200 and Content-Type: text/plain. Many teams use a static host or a small CDN rule for this.
  4. If you no longer want MTA-STS, delete the _mta-sts TXT record instead, or publish a policy with mode: none first so senders drop their cached copy.

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.