TLS-RPT Builder: Get Daily Reports When Email to Your Domain Fails TLS

When another company’s mail server can’t deliver to you securely, you usually never find out. The failure happens on their side: an expired certificate on one of your MX hosts, a security gateway that stopped offering encryption, a policy file your web host started redirecting. Their server logs it, maybe retries, maybe delivers in plaintext, and nobody on your team ever sees a thing.
TLS-RPT fixes that blind spot. You publish one TXT record at _smtp._tls that tells sending servers where to send a daily report on their attempts to reach your domain over TLS. Google and Microsoft send those reports today, and each one counts the successful encrypted sessions, the failed ones, and exactly why each failure happened.
The builder below creates the record, validates every destination, and checks what any domain publishes today, along with whether it pairs the record with MTA-STS.
TLS-RPT Builder v1.0.0Last Update: Nov 18, 2026
Enter your domain and where reports should go to build the TLS-RPT TXT record for _smtp._tls, or check what the domain publishes today.
What TLS-RPT Does
TLS-RPT is the IETF reporting standard for SMTP transport security, published in 2018 as RFC 8460 alongside MTA-STS. It does one job: it gives senders a standard address to report TLS results for your domain and a standard JSON format to report them in.
TLS-RPT doesn’t change how anyone delivers mail to you. It never blocks a message, never requires encryption, and can’t break delivery. That makes it the safest email security record you can publish and the one to publish first.
Reports cover two kinds of problems:
- Negotiation failures: a server that doesn’t offer STARTTLS, a certificate that’s expired, untrusted, or issued for the wrong name, or another TLS handshake error.
- Policy failures: an MTA-STS policy the sender couldn’t fetch or parse, an MX host your policy doesn’t list, or a DANE TLSA record that doesn’t match when you use DNSSEC-based DANE.
Why TLS-RPT Matters
Email between servers is encrypted only opportunistically. STARTTLS can be stripped by a MITM attacker, and certificate problems on your side silently push senders back to plaintext or, under an enforced policy, stop delivery entirely. Without reports, you learn about either problem from a customer who says your team never got their email.
- It makes MTA-STS safe to enforce. Testing mode exists so you can see failures before you require encryption. Without TLS-RPT, testing mode tells you nothing.
- It catches outages early. An expired certificate on an MX or on your policy host shows up in the next day’s report, not weeks later in a support ticket.
- It reveals attacks. A sudden spike in
starttls-not-supportedfrom one network, while other senders connect fine, can point to downgrade interference on the path. - It documents your posture. Daily evidence that inbound mail arrives encrypted is useful for security reviews, audits, and vendor questionnaires.
Government guidance puts reporting first. The UK government’s TLS-RPT and MTA-STS guidance tells departments to set up TLS-RPT and start monitoring before they begin an MTA-STS deployment, and Google’s own Workspace MTA-STS documentation pairs the two.
Adoption of the record has grown, but only a handful of senders generate reports, so the reports you receive come from the largest mailbox providers.
TLS reporting adoption rose three to four times between October 2021 and September 2024, from 11,531 .com domains (0.02%) to 52,641 (0.07%), and from 1,527 .org domains (0.03%) to 7,192 (0.12%). The researchers note that only two major providers, Google and Microsoft, currently send TLS reports.
Md. Ishtiaq Ashiq, Tobias Fiebig, and Taejoong Chung, Unraveling the Complexities of MTA-STS Deployment and Management in Securing Email, ACM Internet Measurement Conference, 2025
Among the top 1 million domains that publish MTA-STS, about 45% use testing mode, the mode that relies on TLS reports to show what would fail under enforcement.
Freddie Leeman, URIports, MTA-STS Adoption: Three Years of Steady Growth, January 6, 2026
What the TLS-RPT Record Looks Like
Host: _smtp._tls.example.com
Type: TXT
Value: v=TLSRPTv1; rua=mailto:tls-reports@example.com v=TLSRPTv1identifies the record and must come first.rualists where reports go. Usemailto:for an inbox orhttps://for an endpoint that accepts a POST. Plainhttp://isn’t allowed.- Separate multiple destinations with commas, as in
rua=mailto:tls@example.com,https://reports.example.net/tlsrpt. - Characters with special meaning in the record, such as
,,!, and;, must be percent-encoded inside a URI. The builder encodes them for you. - Publish exactly one record at
_smtp._tls. Two records make the policy invalid and senders ignore both.
Unlike DMARC, TLS-RPT doesn’t require an external destination to publish an authorization record, so you can send reports straight to a reporting service’s address. A subdomain that receives mail needs its own record, just as it needs its own MTA-STS policy.
How TLS Reporting Works
- A sender delivers to your domain. Throughout the day it records each SMTP session to your MX hosts: whether TLS succeeded, and if not, why.
- It finds your record. The sender looks up
_smtp._tls.yourdomainand reads theruadestinations. - It aggregates a full day. The RFC asks senders to cover one UTC day, 00:00 to 24:00, and deliver after a delay of a few hours so receivers aren’t flooded at midnight.
- It sends the report. Over email, the report is a gzip-compressed JSON attachment on a message that must carry a valid DKIM signature from the reporting domain. Over HTTPS, it’s a POST with the media type
application/tlsrpt+gzip. - You read the results. Each report lists the policies the sender applied, total successful and failed sessions, and a breakdown of every failure type.
Senders must deliver reports even when your own TLS is broken, so a report about a certificate failure can still reach you. That also means a report may arrive unencrypted, which is one reason it contains counts and host names rather than message content.
How to Read a TLS-RPT Report
Report attachments are named sender!your-domain!begin!end!id.json.gz, with the begin and end times as Unix timestamps. Decompress one and you get JSON like this example adapted from RFC 8460:
{
"organization-name": "Company-X",
"date-range": {
"start-datetime": "2016-04-01T00:00:00Z",
"end-datetime": "2016-04-01T23:59:59Z"
},
"contact-info": "sts-reporting@company-x.example",
"report-id": "5065427c-23d3-47ca-b6e0-946ea0e8c4be",
"policies": [{
"policy": {
"policy-type": "sts",
"policy-string": ["version: STSv1", "mode: testing",
"mx: *.mail.company-y.example", "max_age: 86400"],
"policy-domain": "company-y.example",
"mx-host": "*.mail.company-y.example"
},
"summary": {
"total-successful-session-count": 5326,
"total-failure-session-count": 303
},
"failure-details": [{
"result-type": "certificate-expired",
"sending-mta-ip": "2001:db8:abcd:0012::1",
"receiving-mx-hostname": "mx1.mail.company-y.example",
"failed-session-count": 100
}, {
"result-type": "starttls-not-supported",
"sending-mta-ip": "2001:db8:abcd:0013::1",
"receiving-mx-hostname": "mx2.mail.company-y.example",
"receiving-ip": "203.0.113.56",
"failed-session-count": 200
}, {
"result-type": "validation-failure",
"sending-mta-ip": "198.51.100.62",
"receiving-ip": "203.0.113.58",
"receiving-mx-hostname": "mx-backup.mail.company-y.example",
"failed-session-count": 3,
"failure-reason-code": "X509_V_ERR_PROXY_PATH_LENGTH_EXCEEDED"
}]
}]
} Read it from the top down:
organization-nameanddate-rangetell you who sent the report and which day it covers.policy-typeshows what the sender applied:stsfor MTA-STS,tlsafor DANE, orno-policy-foundwhen you have neither, in which case the report still shows plain STARTTLS results.policy-stringis the policy the sender actually used. If it doesn’t match your current file, the sender has an old copy cached, and you probably forgot to change the id.summarygives successful and failed session totals. In this example, 303 of 5,629 sessions failed.failure-detailsbreaks the failures down by type, receiving MX, IP address, and count. Here,mx1has an expired certificate,mx2doesn’t offer STARTTLS, and a backup MX has a certificate chain problem.
TLS-RPT Result Types
| Result Type | What It Means | What to Check |
|---|---|---|
starttls-not-supported | The MX didn’t offer STARTTLS | Gateway or server TLS settings, or interference on the network path |
certificate-host-mismatch | The certificate isn’t valid for the MX host name | Certificate names on that MX, and the host names in your policy |
certificate-expired | The MX certificate has expired | Renewal automation on that server |
certificate-not-trusted | Untrusted authority, broken chain, or similar | Missing intermediate certificates or a self-signed certificate |
validation-failure | Another TLS failure | The failure-reason-code field for details |
sts-policy-fetch-error | The sender couldn’t retrieve your MTA-STS policy | DNS for the mta-sts host, redirects, and uptime |
sts-policy-invalid | The policy file didn’t validate | Syntax, line endings, and stray content in the file |
sts-webpki-invalid | The policy host’s HTTPS certificate failed validation | The certificate for the mta-sts subdomain |
tlsa-invalid, dnssec-invalid, dane-required | DANE-specific failures | TLSA records and DNSSEC signing |
A few failures from a single sender IP are usually that sender’s problem. The same failure across Google and Microsoft on the same MX is yours. Transient network errors such as timeouts aren’t required to be reported, so anything that does appear is worth a look.
Where to Send Reports
- A dedicated mailbox. Create an address such as
tls-reports@yourdomainthat accepts gzip attachments from any sender. It’s free, but someone has to decompress and read the JSON, which gets old fast across several domains. - A reporting service. Services such as URIports parse TLS-RPT alongside DMARC reports and alert you to new failures. Point the
ruaat the address the service gives you. - Your own HTTPS endpoint. If you already run a log pipeline, an endpoint that accepts POSTs of
application/tlsrpt+gzipcan feed reports straight into it. It must return a 200 or 201. - More than one. List a mailbox and a service together during setup, then drop the one you don’t use.
Keep the mailbox off any filter that strips attachments or quarantines compressed files, or the reports disappear before anyone reads them.
How TLS-RPT and MTA-STS Work Together
The two standards were designed as a pair. MTA-STS tells senders to require TLS with a valid certificate for the MX hosts you list. TLS-RPT tells you how that went. Together they make a safe rollout possible:
- Publish TLS-RPT and read a week of reports to see your baseline with no policy.
- Publish MTA-STS in testing mode. Reports now show
policy-type: stsand flag anything that would fail under enforcement. - Fix every legitimate failure until reports come back clean.
- Switch MTA-STS to enforce and keep reading reports to catch expiring certificates and unlisted MX hosts before they cost you mail.
The MTA-STS Builder creates the policy file and TXT record, imports your MX hosts, and checks your live setup. If you use DANE instead of or alongside MTA-STS, TLS-RPT reports cover DANE failures too.
Common TLS-RPT Mistakes
- Publishing at the wrong host. The record lives at
_smtp._tls.yourdomain, not at the root and not at_tlsalone. Older drafts and some guides used a different name. - Forgetting the scheme. A bare email address isn’t valid. It needs
mailto:, which the builder adds for you. - Using http. Only
https://endpoints are allowed. - Splitting destinations into separate records. Use one record with comma-separated destinations.
- Sending reports to a mailbox nobody reads. A record without a reader is no better than no record.
- Filtering away the reports. Attachment filters and spam rules can quietly drop gzip files.
- Stopping at reports. TLS-RPT only observes. Pair it with MTA-STS or DANE so senders actually require encryption.
Key Takeaways
- TLS-RPT is a single TXT record at
_smtp._tlsthat tells senders where to report TLS successes and failures for your domain. - It can’t block or delay mail, so it’s the safest email security record to publish and the right one to publish first.
- Google and Microsoft send daily gzip-compressed JSON reports listing failure types, MX hosts, and session counts.
- Reports are what make MTA-STS testing mode useful and enforcement safe.
- Send reports to a mailbox someone reads or to a service that parses them, and act on certificate and policy errors quickly.
Frequently Asked Questions
Does TLS-RPT Affect Email Delivery?
No. TLS-RPT only asks senders to report what happened. It never changes whether or how a message is delivered, so publishing it carries no delivery risk.
Who Sends TLS-RPT Reports?
Google and Microsoft are the major providers that send them today. Other senders may add support over time, so expect reports from the largest mailbox providers first.
Do I Need MTA-STS to Use TLS-RPT?
No. Without MTA-STS or DANE, reports show policy-type no-policy-found and still summarize successful and failed STARTTLS sessions. The reports become far more useful once you publish MTA-STS in testing mode.
How Often Do Reports Arrive?
Each participating sender typically sends one report per day covering a full UTC day, delivered a few hours after the day ends.
Can I Send TLS Reports to the Same Address as DMARC Reports?
You can, but separate addresses make filtering and processing easier. TLS reports are JSON while DMARC aggregate reports are XML, and many reporting services give you a distinct address for each.
Are TLS Reports Private?
Reports contain counts, IP addresses, MX host names, and policy details, not message content or recipient addresses. They may be delivered unencrypted, so treat the destination like any operational mailbox.
Does Each Subdomain Need Its Own TLS-RPT Record?
Yes, if the subdomain receives mail. Senders look for the record at the exact domain they deliver to, so publish _smtp._tls for every domain and subdomain with MX records.
Related Email Authentication Guides
- TLS-RPT and MTA-STS are the acronym entries for the two standards.
- MTA-STS Builder: Require Encrypted Email Delivery and Stop STARTTLS Downgrade Attacks builds the policy that reports help you enforce.
- Import, Modify, or Build Your DMARC TXT Record sets up the authentication reports that sit alongside TLS reports.
- Import, Modify, or Build Your SPF Record authorizes every service that sends mail for your domain.
- BIMI Record Builder puts your logo in the inbox once DMARC is enforced.
- How to Validate Your Email Authentication Is Set Up Correctly for DKIM, DMARC, SPF & BIMI is the checklist after you publish.
Check your domain with the builder first. If there’s no record, publish one today. It takes a minute, it can’t hurt delivery, and tomorrow you’ll start seeing how the world’s largest senders actually reach your inbox.







