Record current DNS or website settings before editing production systems. Confirm changes with your actual provider and test after deployment. These guides explain common scenarios; individual configurations vary.
In this guide
- Find and read your DMARC record
- How DMARC decides whether a message passes
- Common DMARC warnings
- Safe rollout checklist
- Frequently asked questions
Find and read your DMARC record
Look up the correct DNS name
DMARC is published as a TXT record at _dmarc.yourdomain.com. The record begins with v=DMARC1 and contains semicolon-separated tags.
Understand the policy tag
p=none requests monitoring without a DMARC enforcement action; p=quarantine requests suspicious handling; p=reject requests rejection for failing messages. Receivers retain discretion in handling.
Check reporting destinations
rua=mailto:address@example.com requests aggregate reports. Confirm that the mailbox or reporting service can accept XML reports and that any external reporting destination is properly authorized.
How DMARC decides whether a message passes
SPF alignment
SPF must pass and its authenticated envelope-from domain must align with the visible From domain. Relaxed alignment permits an organizational-domain match; strict alignment requires an exact match.
DKIM alignment
DKIM must verify and its signing d= domain must align with the visible From domain. A message can pass DMARC with aligned DKIM even if SPF fails.
One aligned pass is sufficient
DMARC passes when at least one of SPF or DKIM both passes authentication and aligns. It does not require both methods to pass.
Common DMARC warnings
No record found
Publish a valid TXT record at _dmarc. Do not put the DMARC policy at the root of the domain.
Malformed record or multiple records
Incorrect tag syntax or multiple DMARC records at the same name can cause evaluation errors. Maintain a single syntactically valid policy.
Policy stuck at none
Monitoring is useful during rollout, but p=none does not request quarantine or rejection of failing mail. Move toward enforcement only after confirming all legitimate sending streams.
Unknown report addresses
Reports may contain sending IP addresses and aggregate authentication results. Use an address you control or a trusted reporting provider and check privacy implications.
Safe rollout checklist
Inventory legitimate mail services
Include marketing tools, transactional systems, CRM, support platforms and forwarding paths.
Enable DKIM where possible
Configure each sender’s DKIM domain and verify actual signed messages.
Monitor aggregate reports
Review which sources pass and fail alignment, and distinguish authorized senders from spoofing.
Increase enforcement deliberately
After verifying senders, consider progressing from none to quarantine and then reject with suitable monitoring and operational review.
Frequently asked questions
Does p=none protect my domain from spoofing?
It provides monitoring but does not request enforcement against failing mail.
Do I need both SPF and DKIM for DMARC?
DMARC can pass with either aligned SPF or aligned DKIM, though configuring both improves resilience.
Will DMARC reports show every individual email?
Aggregate rua reports summarize authentication activity; they are not a complete log of individual messages.
Use our Free DMARC analyzer to review public signals. Results are informational and may not capture account-level settings.
Open free toolWhen to request expert support
If you have multiple sending platforms, a live website migration, authentication failures affecting customers, or conflicting DNS settings, document the symptoms and seek help before making risky production changes. See DMARC implementation support or contact our IT support team.