About this tool
Inspect a domain's DMARC TXT record before email setup, deliverability reviews, or policy enforcement so spoofing protection and reporting settings are visible in one report.
DMARC Record Checker inspects the _dmarc TXT record that tells mail receivers how to handle unauthenticated email for a domain. It parses policy, reporting, alignment, percentage rollout, and subdomain behavior so domain owners can spot risky or incomplete email authentication settings quickly.
- Looks up the expected _dmarc hostname and extracts DMARC TXT records.
- Parses p, sp, rua, ruf, pct, adkim, aspf, fo, and ri tags into a readable summary.
- Flags missing records, multiple records, weak monitoring-only policies, invalid rollout values, and missing aggregate reporting.
How to use DMARC Checker
Enter a domain or _dmarc hostname, run the check, and review the detected TXT record plus parsed tags. Start with the p policy, pct rollout, rua reporting address, and adkim or aspf alignment before copying the report into an email setup, deliverability, or security ticket.
When this tool is useful
- Check a new domain before connecting marketing, support, or transactional email platforms.
- Review p, pct, rua, and alignment settings before moving from monitoring to quarantine or reject.
- Debug deliverability or spoofing reports when SPF, DKIM, and DMARC settings need to be compared.
Practical tips
- Keep exactly one DMARC TXT record at the _dmarc hostname because multiple records can invalidate the policy.
- Use p=none with rua reporting while collecting data, then tighten to quarantine or reject after legitimate senders are aligned.
- Check SPF and DKIM alignment before enforcing DMARC so valid mail is not rejected unexpectedly.
Examples you can test
These examples show the kind of real input and reviewed output this tool is designed to support. Use them as a starting point before pasting your own production content, then compare the output with the destination system that will use the result. The goal is not only to produce a value, but to make the input assumptions, output format, and review step clear enough that the result can be trusted in a real workflow.
Check monitoring policy
Example input
example.com
Expected output
DMARC record with p=none and a rua reporting destination
Useful while collecting aggregate reports before moving a domain to enforcement.
Review enforcement rollout
Example input
_dmarc.example.com
Expected output
Policy, pct rollout, reporting, and alignment tags
Check pct and alignment before switching from monitoring to quarantine or reject.
Validation checklist
Run through these checks before copying the result into a CMS, codebase, spreadsheet, campaign, support ticket, or production document. Small formatting differences, unit assumptions, hidden whitespace, and platform-specific rules are common sources of mistakes in quick browser tools, so the final review should happen in the same context where the output will be used.
- Keep exactly one DMARC TXT record at _dmarc.example.com.
- Start with reporting before moving to quarantine or reject.
- Use a valid rua mailbox or report processor you can monitor.
- Review pct when rolling out enforcement gradually.
- Check SPF and DKIM alignment before tightening policy.
Why people use this tool
DMARC affects brand trust, phishing resistance, and deliverability. A missing or weak record can leave domains easier to spoof, while a strict record deployed too quickly can block legitimate mail, so a focused checker helps teams stage changes carefully.
Related search intents
dmarc record checker, dmarc checker, dmarc lookup, check dmarc record, dmarc txt checker.