What is DMARC? A complete guide for IT professionals
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a DNS-based email authentication standard that tells receiving mail servers what to do when an email fails SPF or DKIM checks. It also gives domain owners visibility into who is sending email using their domain.
Why DMARC matters
Without DMARC, anyone can send an email with your domain in the From address. This is how business email compromise (BEC) and phishing attacks work. DMARC closes that gap by letting you tell receivers: "If a message claims to be from us and fails authentication, reject it."
DMARC also enables reporting. Receiving servers send aggregate reports back to you showing how much mail is passing and failing, and from which IP addresses. This is how you discover shadow IT senders, misconfigured third-party tools, and active spoofing attempts.
How DMARC works
DMARC builds on SPF and DKIM. For a message to pass DMARC:
- The message must pass SPF and the SPF-authenticated domain must align with the From domain, or
- The message must pass DKIM and the DKIM signing domain must align with the From domain.
If neither condition is met, DMARC fails and the policy you have configured applies.
DMARC record syntax
A DMARC record is a DNS TXT record published at _dmarc.yourdomain.com. Example:
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@senduras.io; aspf=r; adkim=r;
| Tag | Meaning |
|-----|---------|
| v=DMARC1 | Required. Identifies this as a DMARC record. |
| p= | Policy: none, quarantine, or reject |
| pct= | Percentage of failing mail to apply the policy to (1–100) |
| rua= | Aggregate report destination (one or more mailto: URIs) |
| ruf= | Forensic report destination (optional) |
| aspf= | SPF alignment mode: r (relaxed) or s (strict) |
| adkim= | DKIM alignment mode: r (relaxed) or s (strict) |
DMARC policy options
p=none: Monitor only. Failing messages are delivered normally, and reports are still sent if rua is configured. Use this when you are first setting up DMARC and need to understand your mail flow before enforcing anything.
p=quarantine: Failing messages are sent to the spam or junk folder. This is the intermediate step between none and reject, and a good way to test enforcement before committing.
p=reject: Failing messages are rejected outright. This is the strongest protection. Only move here once you are confident all legitimate sending sources are aligned.
How to reach enforcement
Getting from p=none to p=reject without breaking legitimate mail requires a structured approach:
- Publish p=none with rua to start collecting aggregate reports.
- Identify all sending sources. Use report data to find every service sending as your domain (Google Workspace, Mailchimp, Salesforce, and so on).
- Fix alignment gaps. Make sure every source has SPF or DKIM alignment, and add DKIM signing where it is missing.
- Move to p=quarantine with pct=10. Start with a small percentage and increase gradually.
- Move to p=reject at 100% once all sources are aligned and no legitimate mail is failing.
Reading DMARC aggregate reports
Aggregate reports are XML files sent daily by receiving mail servers. They contain:
- Total message volume from your domain
- SPF and DKIM pass/fail counts per sending IP
- Alignment results for each source
- Policy applied to failing messages
Raw XML is hard to read. A DMARC management tool like Senduras ingests these reports and shows them in plain language: which sources are aligned, which are failing, and what needs fixing.
Common mistakes
Not configuring rua. Without a reporting address, you get no visibility. Always include rua=, even on p=none.
Staying on p=none. This is the most common mistake. p=none provides no protection on its own; it only makes sense as a first step on the way to quarantine and reject.
Setting pct=100 and jumping straight to reject. If you have unconfigured sending sources, this will break legitimate mail. Increase pct gradually.
Switching to strict alignment too early. aspf=s and adkim=s require exact domain matches. Start with relaxed (r) unless you have a specific reason for strict.