Publish a TLS-RPT record

Why it matters

TLS-RPT sends you daily reports from mail servers that failed to deliver to you over TLS, which is how you find a broken MTA-STS policy or an attack. It costs one DNS record and makes moving MTA-STS to enforce mode much safer.

The fix

1. Create a mailbox (or use an https endpoint or a reporting service) to receive the reports. They are compressed JSON files sent daily.
2. Publish one TXT record at _smtp._tls with v=TLSRPTv1 and an rua address written as mailto:address (or https://url), comma-separated for several.

_smtp._tls.example.com.  IN TXT  "v=TLSRPTv1; rua=mailto:[email protected]"

The examples use example.com. Replace it with your own domain.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the MTA-STS and TLS-RPT check
• Publish an MTA-STS policy, starting in testing mode
• Nothing to do for MTA-STS on a domain that accepts no mail
• Fix the MTA-STS TXT record
• Make the MTA-STS policy file reachable
• Fix the certificate on the MTA-STS policy host
• Fix the MTA-STS policy file
• Switch MTA-STS from testing to enforce
• Turn MTA-STS back on
• Make the MTA-STS policy cover every MX host
• Raise the MTA-STS max_age
• Fix the TLS-RPT record