Info

No TLS reporting record

The short version

Publish a TLS-RPT record at _smtp._tls so senders tell you when encrypted delivery fails.

What it means

Your domain has no TLS-RPT record at _smtp._tls.<your domain>. Without one, mail servers that fail to deliver to you over an encrypted connection have nowhere to report it. On its own this is information. While MTA-STS is in testing mode it becomes a warning, because testing without reports tells you nothing.

Why it matters

Large senders such as Google and Microsoft send a daily summary of every connection to your mail servers: how many were encrypted, and why any failed. That is how you find an expired certificate on a backup mail server or a policy that forgets a host, before it costs you mail. The record is free and changes nothing about delivery.

How to fix it

  1. Choose where reports should go: a mailbox, such as tls-reports@<your domain>, or a reporting service that turns the JSON into charts.
  2. At your DNS host, add a TXT record named _smtp._tls with the value v=TLSRPTv1; rua=mailto:tls-reports@example.com, using your own address.
  3. To send reports to several places, separate the addresses with commas. https: addresses work too.
  4. Expect the first reports a day or two later.

Check it worked

Run the MTA-STS checker on your domain again once the old record's TTL has passed, usually within an hour. The TLS-RPT section should say reports are requested and list your address.