Free mail diagnostics

Inspect your TLS reporting signal.

Discover the DNS record that requests mail-transport failure reports. TLS-RPT complements MTA-STS, while DMARC aggregate reports describe a different layer: sender authentication.

Public DNS, live answersNo account neededNo email sent
Email toolboxTLS-RPT — DNS discoverySwitch tool
Required only for DKIM.

Use a domain, not an email address or URL. For PTR, enter a public IP.

Query names are sent to Google Public DNS. Please use public, non-sensitive domains. Privacy details

From record to next step

Evidence, not guesswork.

No. TLS-RPT describes transport-security successes and failures; DMARC reports describe authentication and aligned sender domains. The XML analyzer accepts DMARC aggregate XML, not TLS-RPT JSON. This DNS check does not verify report-destination acceptance or analyze transport reports.

01

Choose the exact domain

For MX and SPF, use the domain you want to inspect. DMARC checks _dmarc at that exact domain; inherited organizational policies are not inferred.

02

Read the finding, not just the badge

“Inspected” means evidence was parsed, not that delivery is guaranteed. “Needs review” explains a policy trade-off; “Issue found” identifies a configuration problem. Resolver errors stay distinct.

03

Verify in your mail workflow

Confirm findings with your receiving provider and real message headers. After DNS changes, allow caches to expire. Review legitimate senders before enforcing stricter policies.

Good questions

Before you change DNS.

Need address-level intelligence?
Are TLS-RPT reports the same as DMARC reports?

No. TLS-RPT describes transport-security successes and failures; DMARC reports describe authentication and aligned sender domains. The XML analyzer accepts DMARC aggregate XML, not TLS-RPT JSON. This DNS check does not verify report-destination acceptance or analyze transport reports.

Is this free, and will you send email?

The public tools are free and do not require an account. No email is sent, no SMTP session is opened and no recipient mailbox is probed. DNS tools query public records; header analysis and policy generation make no external requests. Up to 12 checks per minute are allowed per network address.

What happens to the domain I enter?

Maail does not save submitted domains or DNS results in an application history. Query names, including referenced SPF domains, are sent to Google Public DNS over HTTPS and are subject to Google’s resolver privacy policy. Request history stays in this page’s memory and disappears on reload. Rate protection stores a hash of your network address with short-lived counters; infrastructure logs may also contain request metadata. Do not enter private or sensitive hostnames.

Does a good DNS result guarantee delivery?

No. DNS is one part of mail delivery. Server availability, sender reputation, authentication of actual messages, spam filtering and recipient policies also matter. Findings describe the inspected records, not a delivery guarantee.

Build it into your workflow

Go beyond a manual lookup.

Explore Maail’s email intelligence API for address-level signals, or use these free tools whenever you need to inspect public DNS.