DMARC (Domain-based Message Authentication, Reporting, & Conformance) is a proposed standard for email authentication and handling of fraudulent emails. It’s gathering speed as more and more ISPs and companies begin implementing it for security. The impact is growing and we want to keep you on top of the latest developments.
DMARC uses the SPF and DKIM records in your domain’s DNS to check the validity of an email sent using your domain. It is the next step of security to protect your brand and sending reputation and to prevent illegitimate email (i.e. spam) from harming your reputation. All companies risk spoofers impersonating them in email. With a DMARC record in place for your domain, you can identify these would-be spoofers and now instruct email servers on how to handle their email messages: quarantine, reject, or take no action.
The benefits to implementing DMARC with your domain are twofold:
1. Use it to actively monitor any email that fails authentication to gain insight into those using your domain to send email.
2. Instruct email servers to quarantine (or junk) email that fails authentication or instruct them to reject it outright.
When you add a DMARC record to your domain, the greatest benefit is the added security for your messages, your brand, and your sending reputation.
Major ISPs have already implemented or are in the process of implementing reject policies in their DMARC records, including Yahoo, AOL, Gmail, and Microsoft. One of the results of these ISPs implementing DMARC is that if you send using a third party ESP like JangoMail, with a From Address at Gmail or Yahoo or AOL, then your email will be rejected when it fails this check.
If you have SPF and DKIM in place and are ready to implement a DMARC record, follow the instructions in this Help Article. If you can’t implement DMARC because you don’t have SPF or DKIM set up using your own domain, or if you’re still using an address @gmail.com or another free provider, contact Support so we can help you get rolling!