Publish DMARC record(s) at Monitor

Publishing a DMARC record at a Monitor policy is one of the very first steps you’ll take in protecting your domain; it is also the method to start having data flow into DMARC Protection, and, indirectly, a way for you to for you to show to Agari that you are the owner of the domain. DMARC policies are published in the DNS as text (TXT) resource records (RR) and announce what an email receiver should do with non-aligned mail it receives for email from the given domain.

For each domain you plan to protect, you’ll publish a DMARC record with the “none” flag set for the policies; this requests that data reports be sent from receivers to Agari. You can then use DMARC Protection to analyze the data and modify your mail streams as appropriate.

NOTE: A DMARC record with “none” flag set for its policy does not impact mail flow or the deliverability of messages sent from that domain. A “none” flag is the simply first step in the process of authenticating email from your domains: it allows you to collect data for analysis. Over time, as you implement SPF and DKIM for a domain and authorize senders (in the following steps of this guide), you can modify your DMARC policy flags to a more stringent policy (like “quarantine” and ultimately, “reject.”)

To publish a DMARC record at monitor, you

• Create a DMARC Record With DMARC Builder
• Publish the DMARC Record in DNS
• Add Organization Domains for DMARC Policy Publication