Skip to content
LookupOwl

TLS-RPT checker

Find out whether you will hear about it when mail sent to your domain fails to use encryption.

The domain people send mail to, such as example.com. An email address works too; we only use the part after the @, and it is not stored.

Results for ducky.github.com

Checked live lookup18 ms

JSONCheck again

TLS-RPT: Not set up

ducky.github.com has no TLS reporting record.

Nobody will tell you about TLS problems on mail sent to you.

  • MTA-STSNone
  • DANENot checked yet
  • ReportsNone
Add_smtp._tls.ducky.github.com. 300 IN TXT "v=TLSRPTv1; rua=mailto:[email protected]"
Structured result (JSON) · 583 B
{
  "domain": "ducky.github.com",
  "verdict": "none",
  "record": null,
  "rua": [],
  "related": {
    "mtaSts": {
      "present": false,
      "mode": null
    },
    "dane": {
      "checked": false
    }
  },
  "issues": [
    {
      "code": "NO_RECORD",
      "severity": "info",
      "message": "ducky.github.com has no TLS reporting record. Nobody will tell you about TLS problems on mail sent to you.",
      "fix": "Publish a TLS-RPT record.",
      "snippet": "_smtp._tls.ducky.github.com. 300 IN TXT \"v=TLSRPTv1; rua=mailto:[email protected]\""
    }
  ]
}

Next step

What TLS-RPT is

When one mail server delivers a message to another, the two try to agree on encryption (TLS). Sometimes that fails: a certificate has expired, the name does not match, or the server does not offer TLS at all. TLS-RPT (RFC 8460) is how a domain asks other mail providers to tell it about these failures.

It is one TXT record at _smtp._tls.example.com. It lists one or more addresses, and mail providers that deliver to you send a daily summary there: how many sessions worked, how many failed and why. On its own the record changes nothing. It is the feedback channel for MTA-STS and for DANE.

What this checker does

We read the record and judge it by the rules of RFC 8460, then look at each reporting address.

  • The record must be the only one at the name, must start with v=TLSRPTv1 and must have a rua= list. A trailing semicolon is fine: the standard allows it.
  • Each address must be a mailto: or an https: address. Plain http: is not allowed, and neither is a space inside an address.
  • For a mailto: address we check that its domain has mail servers, or at least an address mail can fall back to. If it has neither, reports sent there would bounce.
  • For an https: address we check that the host name resolves. We never open the endpoint and we never post a test report.
  • We say whether the address is on your own domain, on a related one, on a known report processing company, or on another domain.

The "Works with" strip shows whether the domain has an MTA-STS policy and in which mode. DANE shows as "Not checked yet", because that check is not built yet.

When reports go to another domain

Plenty of domains send their TLS reports to a service that reads them for them: a report processor that turns a pile of daily summaries into one dashboard. That is normal, and we show it as a neutral label, never as a warning. When we recognise the company we name it.

Still, these reports describe your mail traffic: which servers connect, from where, and what failed. Send them only to people and services you trust. If you are not sure that an address belongs to a company you chose, find out before you leave it in place.

Problems we find most often

  • The version tag is not first. A record that starts with rua= is ignored by senders.
  • There are two TLS-RPT records, often one left over from a former provider. Senders ignore all of them.
  • The mailto: address is on a domain that no longer receives mail, so every report bounces.
  • The address uses http:// instead of https://.
  • The record is fine, but the domain has neither an MTA-STS policy nor DANE records. Providers only produce reports for domains that publish one of the two, so nothing arrives.

How to set it up

  1. Choose where reports goAn address you read, such as [email protected], or the address a report processing service gives you.
  2. Publish one TXT recordAt _smtp._tls.example.com, with the value v=TLSRPTv1; rua=mailto:[email protected]. Separate several addresses with commas.
  3. Publish an MTA-STS policyReports only come for domains that publish one. Check yours with the MTA-STS checker.
  4. Read the first reportsThey arrive as small compressed JSON files, about a day after the first mail. Fix what they show before you move MTA-STS to enforce.

Questions people ask

Is TLS-RPT useful without MTA-STS?

Not on its own. Mail providers send TLS reports for domains that publish an MTA-STS policy or DANE records. With neither, the record is valid but nothing produces reports.

How long does it take for the first report to arrive?

Providers send one summary a day, so expect the first one within a day or two of mail flowing to you. Small domains may see a report only on days when a provider delivered mail.

Can I list more than one address?

Yes. Put them in one rua list, separated by commas, for example a mailto address and an https endpoint. Do not add a second rua field and do not publish a second record.

Does the trailing semicolon matter?

No. RFC 8460 allows a final semicolon, so both v=TLSRPTv1; rua=mailto:[email protected] and the same text without the last semicolon are valid.

Do you send a test report to my address?

No. We only read DNS: whether a mailto address has mail servers and whether an https host resolves. We never send mail and never post to your endpoint.

Does this page store the email address I type?

No. If you type an address, only the part after the @ is used. It is cut before anything is looked up and it is not stored.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is tls_rpt_check. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/tls-rpt-check?q=gmail.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp