NOTE: Google and Yahoo announced requirements that bulk senders must have DMARC in place beginning February 2024.

Understanding Gmail and Yahoo DMARC Requirements - dmarcian

Set up DMARC#

DMARC is an email security standard that allows domain owners to monitor who’s sending email using their domain and instructs email receivers (like Gmail) to approve, quarantine, or reject emails that aren’t sent from an authenticated source.

Gmail and Yahoo will start requiring DMARC for all bulk senders who send more than 5,000 messages a day, but even if you aren’t sending at that volume, we encourage you to set up DMARC anyway. Here’s a step-by-step walkthrough of how you can set up DMARC for your domain. Gmail and Yahoo don't require strict DMARC policies, so you can get started with a “p=none” policy. With that policy in place, you can start monitoring who’s sending email using your domain without receivers taking any action just yet.


More information on the DMARC record can be found online ( to understand its use and impact, but here is an overview:

Report(s) are emailed to the rua= and ruf= mailto addresses entered. The ruf parameter can be skipped.

RUA is reporting that provides an aggregate view of all of a domain’s traffic. The other option is RUF reports that are redacted forensic copies of the individual emails that are not 100% compliant with DMARC. While RUA reports show the traffic of the email, RUF reports contain snippets from the actual emails themselves. While RUA reporting is all that is needed for DMARC deployment, more advanced users may also add the RUF tag, which will send more sensitive information.

Create a TXT record.


Host/Name: _dmarc

Record Type: TXT (if needed)

NOTE: for Value, replace the text in red.

Value:v=DMARC1;p=none; or quarantine; or reject;(1)



(1) For example, p=none;, p=quarantine;, or p=reject;.
 If unfamiliar with the DMARC record, the p=none option can be used when setting up the record.

One example is,