Topic · Transport Security
TLS-RPT rua destination
A TLS-RPT rua destination specifies where aggregated transport-security failure reports should be sent.
How it works
Reporting MTAs use the published reporting URI information to deliver JSON reports through supported methods.
What can go wrong
Incorrect destinations or unsupported report ingestion leave transport failures invisible to administrators.
What to check or do
Validate the TLS-RPT DNS record and verify that actual report files are received and parsed.
How to investigate TLS-RPT rua destination
- Signal to investigate
- TLS-RPT TXT appears correct but no reports reach the configured mailbox.
- Evidence to collect
- Check the rua URI, destination acceptance, aggregate reporting support and any external reporting authorization requirements.
- Common wrong conclusion
- No report received is not proof that all SMTP TLS connections succeeded.
How to interpret the evidence
Reports depend on sender adoption, traffic and reporting windows. Unsupported destination schemes or delivery blocks can prevent reports from arriving.
What to change and how to verify it
Use a supported URI and accepting mailbox or HTTPS collector; verify DNS, monitor reporting volume and handle JSON reports securely.
Put this into practice
Run a focused check, then explore protection if your domain needs it.