Analyze the TLS-RPT reporting record used for email delivery

For web teams checking a launch or tracing a fault, this test provides an immediate point of reference. Analyze the TLS-RPT reporting record used for email delivery.

Analyze the TLS-RPT reporting record used for email delivery. The result organizes the useful evidence so you can focus the diagnosis.

How to use

Enter the domain used by your email service, the one whose TLS-RPT record you want to inspect.
Run the check so the YOORfree server queries the public DNS records associated with that domain.
Look in the result for a TLS-RPT record and identify the destinations where reports are meant to be sent.
Confirm that the reporting address or service matches the one your team actually wants to use.

Example

An email team keeps seeing TLS delivery warnings and wants to know where the reports are sent. They enter the domain used for outbound mail, run the check, then read the reporting destination to confirm that the data reaches the mailbox or service chosen by the team.

Limits and formats

The check reads the public DNS record at the moment it runs; a recent change may not have propagated yet, so a second check later can be useful.
It does not prove that reports are actually received or that the destination address accepts messages from the reporting system.
A domain without a TLS-RPT record may be normal if this reporting mechanism has not been set up for that email flow.
The record syntax and scope should be confirmed by your DNS or email team before you rely on it operationally.

Where processing happens

The domain you enter is sent to the YOORfree server. That server queries the public DNS itself to find the TLS-RPT record and then displays the response. No file is uploaded during the check.

Frequently asked questions

What is a TLS-RPT record used for?

It tells mail systems where to send reports about TLS encryption failures in email delivery. This helps teams monitor transport problems and fix configurations that may affect delivery.

Why does my domain show no record?

The mechanism may not be configured, or the DNS publication may not have propagated yet. Check the DNS zone and wait before deciding that something is wrong.

Does the result prove that reports are arriving?

No. It only shows the published DNS configuration. Actual delivery depends on the collection service, its address and whether it is working correctly.