What is checked?
The check examines the TXT record at _smtp._tls and its reporting destinations. One unambiguous record must contain v=TLSRPTv1 and at least one rua destination. Reports can identify problems involving MTA-STS, DANE or certificates.
Worked example
Synthetic example using a reserved domain and documentation addresses. Adapt the domain, addresses and services to your infrastructure before using it.
_smtp._tls.example.test. TXT "v=TLSRPTv1; rua=mailto:tls-reports@example.test"This example directs reports to tls-reports@example.test. A suitable report receiver must exist there in production. For Sendequelle, use the address assigned in your account.
Common mistake
A valid TLS-RPT record is mistaken for proof that the server has no problems. Missing reports do not prove that every connection succeeded either.
Recommended next step
Set up the intended receiver, publish a single record and watch for incoming reports. Investigate reported problems by period, receiving MX and failure type, comparing them with stored monitoring measurements.
What the result does not prove
Aggregate reports arrive with a delay and cover only participating senders. They replace neither a current certificate measurement nor alerts from your own monitoring.