DMARCdrift
Skip to Content
DMARCdrift
Getting started

Set up TLS-RPT reports

How to point your TLS-RPT record at DMARCdrift, how TLS reports differ from DMARC reports, and what the TLS delivery reports card shows.

TLS-RPT (SMTP TLS Reporting, RFC 8460) tells you whether other mail servers could make an encrypted connection when they delivered mail to your domain, and why not when they could not. Typical causes are a mail server that does not offer encryption, an expired or mismatched certificate, or a broken MTA-STS policy file. DMARCdrift reads these reports and shows them on your domain page in the TLS delivery reports card.

How TLS reports differ from DMARC reports

DMARC reportsTLS reports
AboutMail sent from your domainMail sent to your domain
Tells youWhether senders pass SPF, DKIM and alignmentWhether delivery to your mail servers was encrypted
DNS record_dmarc.yourdomain.com_smtp._tls.yourdomain.com
Reporting tagrua= in the DMARC recordrua= in the TLS-RPT record

You use the same DMARCdrift address for both. Your address is shown in your domain settings and looks like d-abc123@in.dmarcdrift.com. See Add DMARCdrift to your DMARC record for where to find it.

Add your address to the TLS-RPT record

The TLS-RPT record is a TXT record at _smtp._tls.yourdomain.com.

No TLS-RPT record yet

Create a TXT record at _smtp._tls.yourdomain.com:

"v=TLSRPTv1; rua=mailto:d-abc123@in.dmarcdrift.com"

Replace d-abc123 with your assigned address. The free TLS-RPT generator builds the record for you, and the TLS-RPT checker confirms it is published correctly.

You already have a TLS-RPT record

Keep your existing destinations and append the DMARCdrift address to rua=, separated by a comma with no spaces:

"v=TLSRPTv1; rua=mailto:tls@yourdomain.com,mailto:d-abc123@in.dmarcdrift.com"

A domain publishes one TLS-RPT record. If you already have one, edit it rather than adding a second.

When the card has no reports to show, it says why. If you have no TLS-RPT record, or the record is invalid, it shows a ready-to-copy record. If the record is valid, it tells you it is waiting for the first report.

What the card shows

The TLS delivery reports card is on your domain page, below DNS posture. It covers mail arriving at your domain.

  • Success rate: successful sessions divided by all sessions reported by recognised providers.
  • Daily chart: sessions by report date. Days with no report are left blank, not drawn as zero.
  • Top failure reasons: the most common reasons connections failed, in plain English. These are the top reasons, not a share of the total, because providers are not required to include failure details.
  • Reporting providers: the providers whose reports are counted.
  • Other reporters: reports from senders DMARCdrift does not recognise are listed separately by sending domain. They are not counted in the totals or the success rate.

With only a few days of data the card shows the counts as text instead of a chart.

The card shows the last 7 days on Free, up to 180 days on Solo and up to 1 year on Pro. DMARCdrift keeps TLS report data for 365 days on every plan. See Report history and data retention.

How long until the first report

Most providers send TLS reports once a day, covering the previous day. Expect the first report 24 to 48 hours after your DNS change is live. Some providers only report once they have seen mail delivered to your domain.

TLS reports do not count as your first report. A domain that only receives TLS reports still shows as waiting for its first DMARC report. See When reports start arriving.

If nothing arrives

  1. Confirm the record is at _smtp._tls.yourdomain.com, not yourdomain.com.
  2. Check that your address in rua= matches your domain settings exactly, including mailto:.
  3. Check that your domain receives mail from large providers. Providers only report on domains they deliver to.
  4. Wait a full 48 hours after the change.

For other delivery problems, see Reports stopped arriving.

Ask AI about this page:ClaudeChatGPT