Page contents
Ensure a correct DMARC setup in minutes and secure your email from day one. Domain-based Message Authentication, Reporting, and Conformance (DMARC) is an email authentication protocol that helps businesses prevent unauthorized use of their domains.
It builds on two existing standards:
With a proper DMARC setup, domain owners can instruct receiving email servers on how to handle messages that fail SPF or DKIM checks – whether to deliver, quarantine, or reject the message.
By learning how to implement DMARC correctly, you can protect recipients from phishing and spoofing attacks. DMARC enforcement also improves email deliverability by reducing Spam and Junk folder placement.
| Policy | Description | Use case |
|---|---|---|
none | Monitor only; no action is taken on failing emails | Use none during the initial DMARC setup to gather data without impacting deliverability |
quarantine | Place failing emails in the Spam folder or quarantine | Use quarantine to enable DMARC enforcement and reduce impersonation risks |
reject | Block and reject failing emails outright | Use reject for strict DMARC enforcement and maximum protection |
Start with p=none to monitor email traffic and identify legitimate senders. As your DMARC setup becomes more accurate and complete, gradually shift to quarantine to apply enforcement, and finally move to reject to reach full protection.
Before configuring DMARC, ensure that SPF and DKIM are correctly set up for your company. These are essential requirements, as DMARC relies on their authentication results to function effectively.
Wait at least 48 hours after setting up SPF and DKIM to allow for proper DNS propagation and validation before enabling DMARC.
A DMARC record is a DNS TXT record that defines your organization’s policy and reporting preferences. Below is an example of a DMARC record:
| Host | Type | Value |
|---|---|---|
| _dmarc.yourdomain.com | TXT | v=DMARC1; p=none; pct=100; rua=mailto:[email protected]; |
v=DMARC1: Specifies the DMARC versionp=none: Sets the policy to none (monitor and send reports)pct=100: Applies the policy to 100% of messagesrua: Defines the email address that receives aggregate DMARC reportsIn phase one, we migrate all existing SPF and DKIM records to the Sendmarc platform. This establishes a single source of truth for authentication and ensures DNS changes can be managed safely and consistently.
Key steps include:
Phase one typically takes one to five days, depending on DNS access, domain volume, and internal approval.
Phase two strengthens authentication by identifying every legitimate system sending email on behalf of the domain and ensuring each one is configured correctly.
Key steps include:
This phase usually takes 30 to 60 days, depending on the environment’s complexity.
By phase three, authentication and deliverability should be nearing full compliance. The DMARC setup is updated to p=quarantine, which routes non-compliant email to a Spam or quarantine folder rather than blocking it outright.
This stage acts as a safety net – teams can confirm that all legitimate systems have been correctly configured while still preventing high-risk email from reaching inboxes.
Key steps include:
Phase three is typically completed within 14 days.
Phase four applies the strongest form of protection: p=reject. This blocks all emails that fail SPF and/or DKIM alignment, preventing cybercriminals from impersonating your domain.
Before enabling enforcement, Sendmarc recommends completing these checks:
Phase four usually takes companies one day, but ongoing monitoring remains essential as new platforms or tools are introduced over time.
Sign up with Sendmarc today to simplify your DMARC setup, get expert support, and monitor email authentication easily.
DMARC provides reporting features that give your business visibility into authentication results and possible misuse of its domain. These reports allow you to:
Use Sendmarc’s enterprise DMARC solution to collect and analyze reports efficiently. Regular review of these reports is key to refining your company’s SPF, DKIM, and DMARC setups for better security and improved email deliverability.
Managing DMARC records can be complex, but Sendmarc makes it simple. Our platform offers expert tools that help your organization:
Sign up today or book a demo to see how Sendmarc makes DMARC setup and enforcement easy.
To set up Domain-based Message Authentication, Reporting, and Conformance (DMARC), your business must first configure Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) for its domain.
Once these are in place, your company can create a DMARC TXT record in its DNS with its chosen policy (none, quarantine, or reject) and specify email addresses to receive DMARC reports.
When learning how to implement DMARC, it’s best to set the policy to p=none to monitor email activity and gather data without affecting delivery. Once you’ve identified all legitimate sending sources and validated your DMARC setup, gradually move to quarantine and finally to reject for full DMARC enforcement.
If DMARC isn’t set up for a domain, its email is more vulnerable to spoofing, phishing, and impersonation attacks. Without a proper DMARC setup in place, emails that fail SPF or DKIM checks might still be delivered, putting organizations’ reputations and recipients at risk.