NERDTOOLS / DOMAIN DIAGNOSTICS

Free DMARC Record Checker

Look up and parse a domain’s DMARC TXT record to understand its policy, reporting configuration, alignment choices, and enforcement posture.

Common use cases

The DMARC checker reads the TXT policy at _dmarc, parses enforcement and reporting tags, and explains whether aligned SPF or DKIM can protect the visible From domain.

Policy is only one part of DMARC

DMARC passes when at least one authenticated SPF or DKIM identity aligns with the visible From domain. The p tag then tells participating receivers what to do when alignment fails.

  • Use aggregate reports to identify legitimate and unauthorized sending sources.
  • Authenticate each legitimate sender before moving from monitoring toward enforcement.
  • Review sp, adkim, aspf, pct, and reporting destinations instead of judging only the p tag.

Move toward enforcement deliberately

A monitoring policy can reveal the sending estate, but it does not request quarantine or rejection. Tighten policy after high-volume legitimate sources consistently authenticate and align.

  • Do not publish multiple DMARC records at the same owner name.
  • Protect report mailboxes and ensure external reporting destinations authorize receipt when required.
  • Use message headers and provider reports to investigate failures that public DNS alone cannot explain.

Standards and further reading

Diagnostic output is evidence, not a guarantee of security, deliverability, availability, or search ranking. Read the NerdTools methodology and limitations before making consequential changes.

Frequently asked questions

Where is a DMARC record published?

DMARC is published as a TXT record at _dmarc.example.com for the domain being checked.

What policy should I use?

Many domains start with p=none for monitoring, then move toward quarantine or reject after reviewing reports and authentication alignment.

Continue the diagnostic

DNS + email diagnostic tools