How to fix: TLS-RPT Record Missing rua= Reporting URI
Async check: a v=TLSRPTv1 TXT record exists at _smtp._tls.<domain>, but it has no rua= tag specifying where to send reports. Without rua=, the record has no effect.
Why it matters
Without a working rua= reporting address, TLS-RPT reports cannot be delivered, so you have no visibility into SMTP TLS failures even though the TXT record looks present.
TLS-RPT is a companion to MTA-STS: it tells receivers where to send aggregate reports about SMTP TLS negotiation failures. The rua= tag specifies that destination; a record without it publishes the protocol version but never actually receives reports.
How to fix it
- 1Add rua=mailto:tls-reports@<domain> (or an HTTPS reporting endpoint) to the existing _smtp._tls.<domain> TXT record.
Code examples
DNS TXT
_smtp._tls.example.com. IN TXT "v=TLSRPTv1; rua=mailto:[email protected]"References
Detected automatically by VulnRadar. The check id is email-tls-rpt-rua-missing, stable across every scan so you can filter or diff on it.
More email checks
Questions
- How severe is TLS-RPT Record Missing rua= Reporting URI?
- VulnRadar rates this low severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id email-tls-rpt-rua-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does TLS-RPT Record Missing rua= Reporting URI map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.