To configure your DMARC setup, you need to start by creating a DMARC record. As complicated as it may sound, the process for how to setup DMARC is comparatively straightforward! DMARC is a TXT (text) record that can be published on your DNS following a few simple steps to configure the protocol for your domain.
What is DMARC Configuration?
Setting up the DMARC protocol is your first step toward gaining compliance with your emails. You start off by creating a DNS record that defines your policy and establishes the implementation.
To create a free record use our DMARC generator tool:
- Choose your DMARC policy
- Click on “Generate”
- Copy the TXT record to the clipboard and paste it on your DNS to activate the protocol
What is needed for DMARC?
Should you set up a DMARC record, and have decided to go for it, there are certain prerequisites that you need to have in place before you move on to implementation.
- You need access to your DNS management console
- Make sure you recognize all your authorized email senders
- Publish an SPF and/or DKIM record in your DNS
Can you setup DMARC without DKIM or SPF?
No. You need to configure either of the two to make sure your emails are authenticated. You may choose to set up both, which is the recommended approach for maximum security, however that is completely optional.
We have covered both approaches in depth in our knowledgebase.
What is DMARC used for?
A DMARC setup can be useful in the following situations:
- To ensure only authorized senders are allowed to send emails on your domain’s behalf
- To prevent email phishing and direct-domain spoofing attacks
- To view who is sending emails on your behalf
- To prevent spammy messages from reaching your recipients
- To improve deliverability of legitimate emails
Should I Configure DMARC?
When you ask industry experts “Should I turn on DMARC?” , most say “Yes! You should”. The reason becomes clear when we consider the surge in phishing and spoofing attacks in the cyberspace, and the amount of data and information that is comprised because of these attacks. The statistics strike up fear in us, making us wonder which organization would be the next target of scammers.
90% of phishing attacks use email as a vector, making email authentication indispensable. This instantly brings DMARC to the forefront. Patience and consistency in your DMARC configuration journey can minimize spoofing attacks, drastically.
Manual DMARC Setup
Here is an example of how to manually configure your DMARC setup:
DMARC record example:
Note: While beginning your email authentication journey, you can keep your DMARC policy (p) at none instead of reject, to monitor your email flow and resolve issues before shifting to a strict policy.
Learn how to publish DMARC record on your DNS.
What’s the best DMARC setting?
While a suitable DMARC setting depends on the amount of enforcement you desire (how stringently you want receivers to handle emails that fail DMARC), the best setting if you want maximum protection against attacks is p=reject (where p is the mechanism used to specify your record policy).
Should I set DMARC to reject?
You must ensure that your DNS record is set up correctly, and your third party vendors are aligned, before you leverage a reject policy. Else the delivery of legitimate emails may get blocked.
How to Setup DMARC Easily with PowerDMARC
When you create an account on PowerDMARC, we handle protocol implementation and setup for you. We also manage and monitor the health of your domain and emails, parse your aggregate reports and organize your authentication results on a dedicated dashboard.
If you don’t want to go through the hassle of a manual setup, you can automate the process by taking a free 15-day trial with us.
Why is DMARC Needed in the Current Situation?
The FBI’s Internet Crime Complaint Center of 2020 (FBI IC3 Report 2020) reported that 28,500 complaints were received in the US pertaining to email-based attacks. The FBI investigated e-mail scam attacks describing the Coronavirus Aid, Relief, and Economic Security Act (CARES Act), which strived to provide assistance to small businesses during the pandemic. These attacks specifically targeted unemployment insurance, Paycheck Protection Program (PPP) loans, and Small Business Economic Injury Disaster Loans.
Did You Know?
- 75% of organizational domains from all around the world were spoofed in 2020 to send phishing emails to victims
- 74% of those phishing campaigns were successful
- The frequency of BEC has increased by 15% since last year
- IBM reported that one in every 5 companies in the last year has experienced data breaches caused by malicious emails
Every 14 seconds, an organizational domain is spoofed by an attacker to send out phishing emails to receivers who trust them. This is why email authentication is a mandatory addition to your security.
Check your domain right now to see how protected you are against email fraud!
Leveraging DMARC to Prevent Domain Spoofing
Note that if you are configuring DMARC to stop your domain from being Spoofed and keep phishing and BEC attacks at bay, we recommend you select the following criterion while generating your DMARC record with our DMARC record generator tool:
Set your DMARC policy to p=reject
What does this mean?
When you are opting for DMARC enforcement at your organization by choosing a reject policy, this means that whenever an email sent from your domain fails DMARC authentication checks and fails DMARC, the malicious email would be instantly rejected by the receiving MTA, instead of being delivered to your receiver’s inbox.
Another factor that you would want to consider is gaining visibility on your email flow and monitoring emails passing and failing authentication. DMARC reporting ensures that you never miss malicious activity on your domain and you stay informed at all times. To enjoy the benefits of email authentication, and setup DMARC in a way that would effectively protect your domain, sign up with DMARC analyzer today!