Fail

The MTA-STS policy host's certificate isn't trusted

The short version

Install a valid certificate for mta-sts.<your domain>; senders ignore a policy served without one.

What it means

The host mta-sts.<your domain> answered, but its HTTPS certificate isn't one a sending mail server will trust. The detail says why: it has expired, it is issued for other names, it is signed by itself, or its chain doesn't lead to a widely trusted root.

Why it matters

MTA-STS exists to stop someone from tampering with your mail connections, so senders must be sure the policy itself is genuine. They fetch it over HTTPS and check the certificate strictly. If the certificate fails, they treat the policy as missing and deliver without it. A common cause is a CNAME to a hosting service that has no certificate for your mta-sts name.

How to fix it

  1. Find where mta-sts.<your domain> points: your own web server, a static host or a CDN.
  2. Issue a certificate that covers exactly mta-sts.<your domain>. Let's Encrypt and most hosting panels do this automatically once the name is added to the site.
  3. Make sure the server sends the full chain, including the intermediate certificate.
  4. If the certificate expired, check why automatic renewal stopped, so it doesn't happen again.

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. You can also run the SSL checker on the mta-sts host for the certificate details.