What is DMARC?
DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS policy that tells receiving servers what to do with mail that claims to be from your domain but fails authentication. It also asks them to send you reports on who is sending as your domain.
DMARC (RFC 7489) builds on SPF and DKIM. A message passes DMARC when SPF or DKIM passes and the domain it passed for matches the domain in the visible From address. That match is called alignment, and it closes the spoofing gap SPF and DKIM leave on their own.
The record is a TXT record at _dmarc on your domain. Its p= tag sets the policy, and its rua= tag says where receivers should send aggregate reports, which most send daily.
A DMARC record
Check the record on any domain with /tools/dmarc-checker.
_dmarc.northwind.example. 3600 IN TXT "v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc@northwind.example; adkim=r; aspf=r"
v=DMARC1 version, must come first
p=quarantine failing mail goes to spam
pct=50 apply the policy to 50% of failing mail
rua=mailto:dmarc@northwind.example where aggregate reports go
adkim=r; aspf=r relaxed alignment for DKIM and SPFDMARC policy values
| Policy | What receivers do with failing mail | When to use it |
|---|---|---|
p=none | Nothing changes; you just receive reports | The first weeks: find every service sending as you |
p=quarantine | Treat it as suspicious, usually delivering to spam | Once reports show your legitimate mail passes |
p=reject | Refuse the message during the SMTP conversation | The end state for a domain you fully control |
Receivers treat the policy as a request, not an order, and may apply their own judgment.
The other tags
| Tag | Meaning | Default |
|---|---|---|
rua= | Where to send aggregate (summary) reports, delivered as XML | None |
ruf= | Where to send failure (forensic) reports. Many receivers don't send these | None |
pct= | Percentage of failing mail the policy applies to, for a gradual rollout | 100 (all of it) |
adkim= | DKIM alignment: r relaxed (same organizational domain) or s strict (exact match) | r |
aspf= | SPF alignment, relaxed or strict | r |
sp= | Policy for subdomains, if different from p= | Same as p |
fo= | Which failures trigger a failure report | 0 (only when SPF and DKIM both fail) |
A safe path to p=reject
- 01
Publish p=none with rua
Start collecting aggregate reports without changing how any mail is handled.
- 02
Fix every legitimate sender
Use the reports to find each service sending as your domain, and give it aligned SPF or DKIM.
- 03
Move to quarantine
Switch to
p=quarantineand raisepctin steps while you watch the reports for legitimate mail that fails. - 04
Finish at reject
When the only failures left are spoofing, switch to
p=rejectand keep reading the reports.
What Gmail and Yahoo require
Since February 2024, Gmail and Yahoo require bulk senders to publish a DMARC record (p=none is the minimum) with the From domain aligned to SPF or DKIM. Gmail counts you as a bulk sender once you send close to 5,000 or more messages to personal Gmail accounts in a day. Bulk senders also need both SPF and DKIM, one-click unsubscribe on marketing mail, and a spam complaint rate below 0.3%. Microsoft introduced similar requirements for high-volume senders to Outlook.com addresses in 2025.
DMARC questions
What does p=none do?
Nothing to delivery. It asks receivers to send you reports while applying no policy, so you can see who sends as your domain before you start enforcing. It meets the minimum DMARC requirement for Gmail and Yahoo bulk senders, but it doesn't stop spoofing.
What is DMARC alignment?
The requirement that the domain which passed SPF or DKIM matches the domain in the From header. Relaxed alignment accepts the same organizational domain, so mail.northwind.example aligns with northwind.example. Strict alignment needs an exact match.
Do I need both SPF and DKIM for DMARC?
DMARC passes if either one passes with alignment. Set up both anyway: SPF often breaks on forwarding, DKIM can break when content is modified, and Gmail and Yahoo require both from bulk senders.
Can DMARC reports go to another domain?
Yes, but the receiving domain has to authorize it with a TXT record such as northwind.example._report._dmarc.reports.example containing v=DMARC1. DMARC reporting services usually set this up for you.
DMARC protects your name. Verification protects your bounce rate.
Mailbox providers judge authenticated senders on what they send. Make sure every address on the list is real.