TLS report destination is not usable
ATTENTIONWhat it means
the offending value is neither a mailto: address nor an https: endpoint, so the reports have nowhere to go.
How to fix it
Use rua=mailto:tlsrpt@example.com, or an https: endpoint if your provider collects reports that way.
Check your own domain
This page describes the condition. To find out whether your domain has it, run the TLSRPT test or the full checkup, which examines every record at once.
Understand it properly
This page covers one condition. For the whole picture, TLS-RPT, defined, or start at the Health Library.
Where this comes from
We judge this against RFC 8460 section 3. Every finding on this site cites the specification behind it so you can check the work rather than take our word for it.
Other TLSRPT conditions
TLSRPT_RUA_INVALID
Every fix on this site is yours to implement. If you would rather someone did it, I take this work directly.