What Is a DMARC Record?
Last updated
Table of Contents
- What is a DMARC record?
- How DMARC works: building on SPF and DKIM
- Setting up, verifying, and monitoring DMARC
- Technical details
- Related articles
- Have more questions?
What is a DMARC record?
DMARC, which stands for Domain-based Message Authentication, Reporting and Conformance, is an email authentication, policy, and reporting protocol. It builds directly upon the foundational email authentication methods of SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) to provide an overarching framework for email security.
Its primary purpose is to help email receivers determine if an incoming message legitimately aligns with what is known about the sender’s domain. This capability is critical for combating email spoofing, phishing attacks, and spam, helping ensure only authorized messages reach inboxes.
How DMARC works: building on SPF and DKIM
DMARC adds a layer of enforcement and feedback on top of SPF and DKIM. A message passes DMARC if either SPF or DKIM passes and aligns, so you need at least one of them set up correctly. Setting up both is recommended.
Authentication and alignment
When a mail server receives an email, it first checks its SPF and/or DKIM status. DMARC then introduces the concept of alignment. It verifies that the “From” address (the one users see) in the email matches the domain that passed SPF authentication and/or the domain that signed the email with DKIM.
- SPF alignment: Checks if the visible “From” domain matches the domain used for the SPF check.
- DKIM alignment: Checks if the visible “From” domain matches the domain used for the DKIM signature.
If either SPF or DKIM passes and aligns with the visible “From” address, the message passes DMARC authentication.
Policy enforcement
Based on the DMARC record published in your DNS, you can instruct receiving mail servers what to do with messages that fail DMARC authentication and alignment.
These policies include:
-
p=none: Monitor only; take no action. -
p=quarantine: Treat as suspicious; usually means placing in spam/junk folder. -
p=reject: Do not accept the message; the receiving server refuses it during delivery.
Starting at p=none and moving to quarantine and then reject lets you ramp up enforcement gradually. See Implement a Gradual DMARC Policy.
Reporting and feedback
DMARC also provides a feedback mechanism. You can specify email addresses in your DMARC record to receive aggregate reports (rua) and failure reports (ruf) about email sent using your domain.
These reports provide invaluable insights into:
- Who is sending email claiming to be from your domain.
- Which emails are passing/failing SPF and DKIM.
- Where authentication failures are occurring.
This data helps you identify legitimate email streams that might need DMARC configuration adjustments and detect unauthorized use of your domain.
Key benefits of DMARC
Stronger anti-phishing and anti-spoofing: Provides a robust defense against impersonation.
Enhanced deliverability: Builds trust with receiving mail servers, improving inbox placement.
Brand protection: Prevents malicious use of your domain, safeguarding your brand reputation.
Visibility and control: The reporting feature gives you actionable data to understand your email ecosystem and enforce your sending policies effectively.
A DMARC record is published as a TXT record at the _dmarc subdomain, for example _dmarc.yourdomain.com. With DNS hosting at DNSimple, you add it in the record editor like any other TXT record. The content of this TXT record contains all the DMARC policy tags and reporting addresses.
Setting up, verifying, and monitoring DMARC
For step-by-step instructions on how to add a DMARC record to your DNSimple zone, including guidance on the required _dmarc subdomain and common policy tags, refer to Set Up DMARC.
To verify that your DMARC record is correctly published and configured, consult our how-to guide: Verify DMARC with dig and Online Tools. This covers using command-line tools like dig and online verification services.
Technical details
The DMARC specification is RFC 9989.
Related articles
- Set Up Email Authentication (SPF, DKIM & DMARC) - Set up SPF, DKIM, and DMARC together
- Email Authentication Best Practices - Ongoing maintenance for SPF, DKIM, and DMARC
- SPF, DKIM, and DMARC Alignment - How alignment requirements affect email authentication
- Implement a Gradual DMARC Policy - How to move from monitoring to enforcement
Have more questions?
If you have additional questions or need any assistance with your DMARC records, just contact support, and we’ll be happy to help. You can also read more about email forwarding at DNSimple.