Check DMARC DNS records or paste a TXT value. Find duplicate records, syntax issues, reporting gaps and monitoring versus enforcement settings.
Live TXT lookup with plain-English interpretation of p=none, quarantine, reject, rua, and pct.
Look up public TXT records or lint a record before publishing. A parsed record is not proof that your mail passes DMARC, reaches the inbox, or meets a provider’s sender requirements.
Try a fictional example (not a live lookup)
DMARC passes when at least one authenticated SPF or DKIM identity aligns with the visible From domain. Use the SPF record checker to review sending authorization and the DKIM selector checker to inspect the published signing key. DNS alone cannot verify a message’s alignment or signature.
For a broader diagnosis, follow the email deliverability stack’s sender-health workflow. A policy cannot fix list quality, complaints or inbox placement.
Standards reviewed August 31, 2026: RFC 9989: DMARC, RFC 9990: aggregate reports and RFC 9991: failure reports. RFC 9989 treats the legacy pct, ri and rf tags as obsolete. Receiver adoption varies.
DMARC ties the visible From domain to an authenticated SPF or DKIM identity. Either mechanism can provide an aligned pass. The published policy informs receiver handling when neither provides an aligned pass; a record lookup does not evaluate a real message.
Review p, sp and np for domain and subdomain policies; adkim and aspf independently default to relaxed alignment. rua requests aggregate reports. Under RFC 9989, t=y reduces reject to quarantine and quarantine to none; pct is obsolete. Older receivers may interpret these differently.
Start with a fictional monitoring example: v=DMARC1; p=none; rua=mailto:dmarc@example.com. Replace the example mailbox with your monitored destination before publishing. Keep one DMARC TXT record, confirm external reporting authorization if needed, and review legitimate senders before enforcing. A missing record at a subdomain may inherit a parent policy; this tool does not perform that discovery.
A DMARC record is a DNS TXT record at _dmarc.yourdomain.com that defines how receivers handle mail that fails authentication alignment.
p=none means DMARC is monitoring only. It can collect reports, but it does not ask receivers to quarantine or reject failing mail.
Move to quarantine or reject after confirming legitimate mail passes SPF or DKIM alignment. Jumping too fast can block real email.
No. This checker lints a record at one DNS name. It does not verify real message authentication, organizational-domain discovery, external report authorization, provider compliance, reputation or inbox placement. DNS failures leave the result unknown.
Email deliverability test
Inspect public DNS and message text with clear next steps. Inbox placement and reputation are not measured.
Email spam checker
Review plain-text email with highlighted copy notes, unresolved tokens and practical next steps.
DKIM checker
Selector-specific DNS lookup with public-key syntax checks and clear next steps.
SPF record checker
SPF syntax checks, duplicate-record detection and bounded recursive include/redirect inspection.
