NOTE: If you have a DMARC record on your main root domain, you do not necessarily need to put one on your sending subdomain (if used). If you are testing with DMARCIAN, and you see the red error box, pay close attention to the text under the red box. You may be protected by your root domains DMARC policy. However it is considered best practice giving you more security and control with your DMARC policies.
HOW TO FIX: The first thing we recommend you do is test your sending domain to see if you already have a DMARC record.
Testing for Your DMARC Record can be done here: https://dmarcian.com/dmarc-inspector/
We recommend testing your root domain as well, you will want a DMARC record on your root domain as well.
If you 'fail' the test, that simply means we need to add a DMARC record to your domain. Follow the steps in the video above to accomplish that. The key is to make sure you are using the correct domain setting for your DMARC record, as well as the correct value, which we have listed below:
TYPE: TXT
NAME: _dmarc.[your sending subdomain]
CONTENT/VALUE: v=DMARC1; p=none;
If you need to create a DMARC record for your ROOT domain as well, it's the same exact process with the exception of the 'name' value being just _dmarc, like so:
TYPE: TXT
NAME: _dmarc
CONTENT/VALUE: v=DMARC1; p=none;
HOW TO FIX: The best way to achieve this goal is to make sure you're sending to subscribers who actually asked for your email, and to make sure your messaging is what they're expecting to receive from you. You can usually track your spam rate from within your service provider (this goes for the DM Hub) however Google does not share this information with your service provider, so we highly recommend signing up for Google Postmaster which will provide you critical and ongoing information about your email sending practices. More on this below.
IMPORTANT NOTE: If you are planning on testing your email with Arsen as shown above, please allow some time to pass until you test if you just now added a DMARC value to allow time for everything to propagate. Recognizing DMARC records takes time. It usually requires a few hours to spread across DNS servers. Your DNS can take up to 72 hours to update your DMARC record, but in most cases, it gets updated within far less than 24 hours.