Quick Answer
DMARC connects email authentication with the domain people see in the From address. A message passes when SPF or DKIM passes and that passing identity aligns with the visible From domain. The domain owner publishes a DNS TXT policy under _dmarc to express a preference for handling failures and request reports. Inventory legitimate senders, verify alignment, and review real traffic before changing enforcement. DMARC helps address domain impersonation, but it does not prevent every phishing message or guarantee inbox placement.
A domain can have an SPF record and several DKIM keys while legitimate messages still fail DMARC. The missing piece is often alignment: the domain that authenticated may belong to a sending platform instead of the business shown in the From address.
Start with our comparison of SPF, DKIM, and DMARC if you need the broader setup sequence. This guide explains the DMARC protocol, its DNS record, and how to make policy decisions using message evidence.
What DMARC does
DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It uses existing SPF and DKIM results, compares their authenticated domains with the visible From domain, and supplies a way for the domain owner to express a policy and request feedback.
SPF checks an envelope-sender identity; DKIM verifies a signature from a signing domain. DMARC needs at least one of those paths to pass and align. It does not require both paths to pass for the protocol’s DMARC result. Receiving providers can impose additional sender requirements, so meeting that result is not the entire delivery checklist.
For example, Amazon SES explains its provider-specific paths in its DMARC authentication guidance. Correct configuration depends on the identity a service actually uses, not whether a generic DNS checker displays three green labels.
What a DMARC record contains
A DMARC record is a TXT policy published at the appropriate _dmarc name. For example.com, the direct policy name is _dmarc.example.com. This synthetic teaching example requests monitoring and aggregate reports:
Type: TXT
Name: _dmarc.example.com
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Do not paste that example into a live zone. The reporting address must exist, have an owner, and be appropriate for the data and message volume. Use your DNS provider’s naming rules; some interfaces append the domain to a short host label.
| Field | Purpose |
|---|---|
v=DMARC1 |
Identifies the DMARC policy format. |
p= |
Expresses a handling preference for messages that fail DMARC. |
rua= |
Requests aggregate feedback at the specified destination. |
adkim= |
Sets relaxed or strict alignment for DKIM. |
aspf= |
Sets relaxed or strict alignment for SPF. |
sp= |
Expresses a subdomain policy where the applicable discovery rules use it. |
Keep one valid DMARC policy at a given policy name. Multiple competing records can prevent evaluation as intended. A parent-domain policy may also affect subdomains without their own applicable policy. Microsoft’s DMARC configuration guidance discusses subdomains, separate sending uses, and DNS publication. Review all affected domains before changing a parent policy.
Understand alignment
Alignment compares domains, not the whole email address. Under strict alignment, the relevant authenticated domain must match the visible From domain exactly. Relaxed alignment can accept domains sharing the same organizational domain. Organizational-domain discovery has defined rules; it is not always the last two labels of a hostname.
The following examples assume a visible From address of billing@example.com. They illustrate identity relationships, not measured delivery results.
Scroll horizontally to see all columns.
| Passing identity | Relaxed alignment | Strict alignment |
|---|---|---|
SPF envelope domain example.com |
Aligned | Aligned |
SPF envelope domain bounce.example.com |
Aligned | Not aligned |
DKIM signing domain example.com |
Aligned | Aligned |
DKIM signing domain mail.example.com |
Aligned | Not aligned |
SPF or DKIM domain example.net |
Not aligned | Not aligned |
If a service uses example.net for both a passing envelope identity and a passing signature, neither aligns with example.com. DMARC fails. If an additional valid signature uses d=example.com, that aligned DKIM path can make DMARC pass. The SPF guide and DKIM guide explain how to inspect those identities.
Choose a handling policy
The three familiar p= values communicate different preferences for failures:
noneexpresses no requested special treatment through this policy. It is useful while studying traffic.quarantineexpresses that failing mail should be treated as suspicious.rejectexpresses that the failing use of the domain should not be accepted.
Receivers retain their own filtering and handling decisions. A monitoring policy does not switch off spam filtering, and a DMARC pass does not require a provider to accept a message. Google’s sender guidelines include authentication alongside other sending requirements.
A general-purpose employee mail domain needs different analysis from a domain confirmed never to send mail. Mailing lists and forwarding can create legitimate indirect delivery paths that fail authentication or alignment. The current DMARC standard, RFC 9989, cautions against rejection policies for general-purpose user email because of interoperability problems. Choose a policy around the domain’s actual use and the effect on legitimate messages.
Read reports with a purpose
Aggregate reports summarize mail streams observed by participating receivers, including source IPs, counts, policy information, and authentication outcomes. They are commonly delivered as XML attachments, sometimes compressed. RFC 9990 now specifies aggregate reporting separately from the main protocol.
Use a repeatable review rather than treating a report as a pass/fail score for the business:
- Check the reporting period, reporting organization, and policy domain.
- Group sources by known provider or system owner, then confirm uncertain sources before classifying them.
- Compare authentication results with the domains that authenticated and the alignment result.
- Separate known legitimate failures, expected indirect delivery, unknown traffic, and suspected unauthorized use.
- Assign a specific sender configuration check or support investigation and compare later evidence.
An unknown IP is a lead, not proof that the business is compromised. A report row also cannot establish where a particular recipient’s message appeared. Keep the original data and the interpretation separate.
Not every receiver sends reports, and no single period proves every legitimate route is configured. Reports sent to an outside service may require additional destination authorization. Choose an appropriate recipient, access controls, retention, and review owner. Google’s DMARC reporting guidance covers operational handling and external reporting destinations.
Individual failure reports are a different feature. They can expose message details, and availability depends on receiver policy. RFC 9991 describes their privacy implications. Do not enable detailed failure reporting as an unexamined default or post genuine reports publicly.
Plan a measured rollout
- Inventory senders and domain uses. Include employees, forms, stores, booking tools, newsletters, invoices, and infrequent jobs. Record visible From, envelope, signing domain, and owner for each route.
- Preserve current DNS and settings. Include parent and sending-subdomain policies. Identify who can restore the previous state if a change affects legitimate mail.
- Configure authentication for each route. Verify provider-specific SPF and DKIM setup using actual received messages.
- Establish monitoring and report ownership. Use a suitable monitoring configuration and confirm reports reach an approved destination.
- Investigate representative traffic. Include the business’s occasional sending cycles and indirect paths, not only one successful test from a staff mailbox.
- Agree on the policy and exceptions. Record the domain-use assumptions and legitimate-mail consequences. Avoid assuming that every domain should end at rejection.
- Change deliberately and monitor. Verify new messages, reports, errors, and affected business workflows. Revisit the setup when a new sender or domain is introduced.
A monitoring period is useful only if someone reviews the results. Give the task an owner and a clear next decision. Keep technical verification separate from claims about improved delivery; the latter needs suitable observation.
Account for the 2026 standard
RFC 9989, published in May 2026, replaces the older core DMARC specification. Aggregate and failure reporting now have separate RFCs. The revision removes the older pct tag and introduces a testing flag, t; it also changes other policy and discovery details.
Older help pages, control panels, and receivers may reflect different stages of that transition. Do not rely on a pct value as a dependable guarantee that a stated percentage of failures will receive enforcement. Do not assume every receiver implements newer testing behavior either. Review the current instructions of the actual provider and validate observed handling before using advanced tags.
The monitoring example in this article keeps the policy straightforward. A more advanced configuration should have a documented purpose, compatibility review, and verification plan instead of a longer list of copied tags.
Verify and troubleshoot DMARC
A read-only teaching query is Resolve-DnsName -Name _dmarc.example.com -Type TXT in Windows PowerShell, or dig TXT _dmarc.example.com with dig installed. Substitute the domain under investigation. These commands illustrate a lookup and have not been run against your domain.
Confirm the authoritative policy, then examine a new message at the destination. Record the visible From domain, SPF result and evaluated identity, each relevant DKIM result and signing domain, DMARC result, and any receiver explanation. Google’s DMARC troubleshooting guide connects policy checks with message-level investigation.
When DMARC fails, first ask which authentication path failed or did not align. Publishing another DMARC record will not fix a missing DKIM signature or a service-owned envelope domain. When DMARC passes but the message goes to junk, use the spam-placement investigation to examine the other delivery evidence.
Key Takeaways
- DMARC needs a passing SPF or DKIM path that aligns with the visible From domain.
- A DNS policy, sender configuration, received-message result, and inbox placement are separate evidence.
- Use reports to investigate real sending routes before changing enforcement.
- Account for domain use, indirect mail, and current standard/provider differences when choosing a policy.
Frequently Asked Questions
What is the difference between DMARC and a DMARC record?
DMARC is the protocol for alignment, policy, and feedback. The DMARC record is the DNS TXT policy through which a domain owner publishes the relevant preferences and reporting destinations.
Do SPF and DKIM both have to pass DMARC?
The protocol needs at least one passing, aligned path. Receiving-provider requirements can also call for both SPF and DKIM to be configured, so check those requirements separately.
Why can SPF and DKIM pass while DMARC fails?
Both passing identities may belong to domains that do not align with the visible From domain. Compare the actual identities instead of relying on the pass labels alone.
Does p=none mean my email cannot be filtered?
No. It expresses no requested special handling through that policy. A receiver can still reject or filter a message using other rules.
Should every business use p=reject?
No universal policy fits every domain. Examine employee use, automated senders, forwarding, mailing lists, the current standard, and receiving-provider behavior before deciding.
Will DMARC stop all impersonation?
It helps receivers evaluate use of the protected domain. Lookalike domains, misleading display names, compromised accounts, and other deceptive content require additional controls.
For email connected to your website or hosting, request a focused review with the sending services, affected route, approximate time, and non-sensitive errors. Our cPanel and Cloudflare authentication guide explains where records belong when mail and DNS use separate providers.

