PowerDMARC

How to Publish a DMARC Record in 3 Steps?

Maitham Al Lawati
publish dmarc record blog

publish dmarc record blog

The DMARC adoption rates in the industry are slowly (but surely) increasing with the introduction of new industry mandates. DMARC record and policy adoption increased by a whopping 84% through 2021 and has been on a steady rise since then. This highlights that businesses are finally recognizing its importance in the information security landscape. 

To configure DMARC, you need to create a DMARC record. The created DMARC record is a TXT record that is then published on your DNS. This kicks start your email authentication process. By setting up a DMARC record you empower domain owners to instruct receivers how they should respond to emails sent from unauthorized or illegitimate sources.

DMARC Record Explained

The DMARC record contains information such as the domain’s policy for handling failed authentication (reject, quarantine, or none), a reporting email address to receive feedback on email authentication results, and optional additional instructions.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) helps prevent email spoofing and phishing by providing a way for email receivers to differentiate legitimate emails from fraudulent ones, reducing the risk of email-based scams and attacks.

Why Do You Need to Add DMARC Record?

Businesses need to add DMARC records in order to protect their domain names and emails against various forms of email-based attacks, impersonation, and fraud. 

Here are some key reasons why you might want to add a DMARC record:

  1. Email authentication: DMARC helps verify the authenticity of emails sent from your domain.
  2. Protect against phishing: Phishing attacks often involve the impersonation of well-known brands or organizations. By setting up DMARC, you can prevent cybercriminals from using your domain name to send fraudulent emails to unsuspecting recipients.
  3. Email deliverability: A DMARC record helps improve the deliverability of legitimate emails from your domain, as receivers can confidently identify legitimate emails and avoid marking them as spam.
  4. Reporting and visibility: DMARC also includes reporting mechanisms that provide valuable insights into the email ecosystem and potential abuse of your domain. 
  5. Complying with Google and Yahoo’s requirements: Google and Yahoo now require bulk email senders to implement DMARC. Non-compliance will result in deliverability issues. 
  6. Complying with PCI-DSS v4 requirements: Version 4 of PCI-DSS will require credit card companies handling sensitive financial data to implement DMARC from March 2025.  

Top 6 Reasons to Add DMARC Record for Enhanced Security

DMARC records play a pivotal role in an organization’s security posture. As discussed above, DMARC prevents a wide range of email-based attacks, which is more important now than ever before since: 

  1. The Federal Trade Commission reported emails as a prominent vector for cyber attacks 
  2. In 2021, more than 40 million US dollars was lost to phishing attacks
  3. Google blocks 100 million phishing emails every day
  4. FBI’s IC3 report outlined that Business Email Compromise made businesses lose 10.3 billion in 2022

How to create a DMARC record? 

To create a DMARC DNS record for your domain, make sure you have – a) a reliable tool to generate the record and b) access to your DNS management console to publish the record. Follow the steps given below:

1. Use a DMARC Record Generation Tool 

Sign up to access our portal using an email address or sign up using Gmail/Office 365. Go to Analysis Tools > PowerToolbox > DMARC Record Generator to start creating your DMARC record.

3. Define a DMARC policy for your DMARC record

Decide on a DMARC policy depending on your desired enforcement level (none, quarantine, or reject). Here’s how you choose your DMARC record  policy: 

While not all fields are mandatory, we recommend you configure a few useful optional fields in your DMARC record. Let’s find out what they are: 

  1. Aggregate (rua) reporting field: If you configure the rua field, you will receive DMARC authentication data directly on your email address. 
  2. Florence (ruf) reporting field: Gain insights into forensic incidents like cyber attacks by configuring the ruf field in your DMARC record. 
  3. DKIM/SPF alignment modes” Choose whether you wish to opt for a relaxed or a strict alignment for SPF and/or DKIM. 

How to Publish DMARC Record?

To publish DMARC record there are a few prerequisites: 

Step 1: Access your DNS Management Console 

Given below is an example of a cPanel DNS management console, however, steps will vary depending on your DNS hosting provider (e.g. Cloudflare, Godaddy, Bluehost, Amazon SES, etc.)

Step 2: Click on DNS Zone Editor 

Under the Domains section, click on DNS Zone editor or Advanced Zone Editor 

Step 3: Add a TXT type record 

Add DMARC record of type TXT (tex), filling in details as shown below. In the “TXT data” or “value” field you need to paste your previously created DMARC record.

Note: Steps may vary depending on your DNS hosting provider. 

How to Verify Your DMARC Record?

To verify your DMARC record you can use our free verification tool. 

1. Sign up for free and navigate to Analysis Tools > PowerToolbox > DMARC Record Checker

2. Review your DMARC record status, syntax and tags to uncover any errors you may have 

Types of DMARC Record Statuses 

StatusWhat it meansWhat can you do
ValidYour DMARC record is correct and free of errorsDo nothing
InvalidYour DMARC record has errors. This can be due to an incomplete or erroneous syntax.Review your syntax, refer to our complete guide on DMARC tags, or contact us for expert assistance.
No Record FoundNo DMARC record was present in your DNS.Create a DMARC record for your domain and publish it on your DNS.

Once you detect errors in your record, you must implement the necessary changes to your DNS and save changes. You may recheck your record once the changes are processed. 

DMARC Record Examples 

Example 1: A typical error-free DMARC record with only mandatory fields:

v=DMARC1; p=none; 

The generated record is now to be published in your domain’s DNS on the subdomain: _dmarc.YOURDOMAIN.com

Example 2: A typical error-free DMARC record with a none policy looks something like this:

v=DMARC1; p=none; rua=mailto:example@domain.com; ruf=mailto:example@domain.com; fo=1;

Example 3: A typical error-free DMARC record with a quarantine policy looks something like this:

v=DMARC1; p=quarantine; rua=mailto:example@domain.com; ruf=mailto:example@domain.com; fo=1;

Example 4: A typical error-free DMARC record with a reject policy looks something like this:

v=DMARC1; p=reject; rua=mailto:example@domain.com; ruf=mailto:example@domain.com; fo=1;

DMARC Record is Published: What’s Next?

After you are done publishing your DMARC record your next step should be to focus on protecting your domain from scammers and impersonators. That is your main agenda when you are implementing security protocols and email authentication services. 

Simply publishing a DMARC record with a p=none policy doesn’t offer any protection against domain spoofing attacks and email fraud. For that, you need to shift to DMARC enforcement.

DMARC Enforcement with PowerDMARC

To gain immunity from impersonation attacks while making sure that your email deliverability doesn’t get impacted at enforcement, what you need to do is:

With DMARC aggregate and forensic reports, moving from monitoring to enforcement becomes a cakewalk for domain owners, as you can visually monitor your email flow and track and respond to deliverability issues instantaneously from the PowerDMARC platform. Sign up today for your free DMARC analyzer trial!

Latest posts by Maitham Al Lawati (see all)
Exit mobile version