_dmarc DNS lookup
Queries the exact host receivers use — _dmarc.yourdomain.com.
Free tools
Enter your organizational sending domain to check the DMARC TXT record at _dmarc, policy mode (none/quarantine/reject), aggregate reporting addresses, and alignment settings.
Query _dmarc.domain, validate policy, reporting, and alignment tags.
Capabilities
Catch missing records, bad reporting addresses, and premature p=reject before they affect deliverability.
Queries the exact host receivers use — _dmarc.yourdomain.com.
Validates p=none, quarantine, or reject and optional subdomain sp= policy.
Parses rua aggregate and ruf forensic mailto destinations.
Shows adkim and aspf relaxed (r) vs strict (s) alignment settings.
Flags partial pct rollout and warns before p=reject without SPF/DKIM readiness.
Image captcha, session verification, and per-IP rate limits for public use.
How to use
Use the domain in your From address — the organizational domain that publishes DMARC.
Complete the image challenge before querying DNS.
Check p= mode and whether sp= differs for subdomains.
Confirm rua= points to a monitored mailbox or DMARC vendor.
Move from none → quarantine → reject after SPF/DKIM pass consistently.
Domain-based Message Authentication, Reporting and Conformance (DMARC) builds on SPF and DKIM. It tells receivers what to do when authentication fails and where to send aggregate reports about your mail.
DMARC is published as a TXT record at _dmarc.yourdomain. Policy tag p= controls enforcement: none (monitor), quarantine, or reject.
Most teams start with p=none and rua= reporting to collect data. After SPF and DKIM align consistently, move to quarantine, then reject.
Publishing p=reject before authentication is fixed can block legitimate mail from new providers or subdomains.
This checker validates DNS publication and DMARC syntax. It does not process DMARC XML reports or prove inbox placement.
SPF hint is a quick presence check only — validate full SPF and DKIM with the dedicated tools.
For regulatory context on commercial email in the United States, see the FTC CAN-SPAM compliance guide.
Delivery note: MailFleet helps users manage campaigns through their own sending providers. Delivery outcomes depend on sender reputation, DNS authentication, content quality, recipient engagement, list quality, provider rules, and mailbox filtering systems.
Yes. p=none lets you collect rua reports without enforcing failures. Fix SPF/DKIM issues, then tighten policy.
Get started
Campaign logs, provider profiles, and pre-send checks help you move DMARC policy safely.
Available on
Same desktop experience across every platform — one workflow for your entire team.