DMARC Record Lookup — Evaluate Policy and Reporting

What this DMARC check tests

The tool reads the TXT record at _dmarc.yourdomain.com and evaluates it against RFC 7489:

• Record validity — v=DMARC1 must be the first tag, a valid p= must be present, duplicate tags are detected.
• Policy strength — none only observes, quarantine files into spam, reject refuses. Only the latter two actually stop spoofing.
• Subdomain policy — without sp= every subdomain inherits the main policy. If sp= is weaker than p=, that is exactly where the gap sits.
• Enforcement — pct= below 100 applies the policy to only a share of messages; pct=0 makes it effectively inert.
• Alignment — adkim and aspf decide whether domains must match exactly (s) or at organizational level (r).
• Reporting — rua and ruf for format and count. Many receivers only deliver to the first one or two destinations.

The check other tools skip

If your rua points at a different domain — a DMARC vendor, say — the entry alone is not enough. That destination domain must itself publish a record at yourdomain.com._report._dmarc.vendor.com, confirming it is willing to accept reports for you. Without it, conforming receivers send no reports — and you wait for analytics that never arrive.

This tool actually resolves that authorization record for every external destination, rather than merely validating the address syntax.

Observe first, enforce later

The usual path is p=none with rua set: you receive aggregate reports without any mail being refused. Only once the reports show that every legitimate source passes SPF or DKIM do you move to quarantine and later reject. Jumping straight to reject tends to cost you invoices and order confirmations.

What this check cannot see

DMARC passes when SPF or DKIM passes and the respective domain aligns with the From domain. Whether that holds for your real messages depends on the sending IP and the DKIM signature — both of which only exist in the message. DNS lets you assess the policy, not its outcome.

For the actual evaluation, send an email to hello@analyzemy.email: the report shows the SPF and DKIM results, both alignments, and the resulting DMARC verdict for that specific message.