Security measures for emails go beyond the creation of an official email address for business use. You can still be attacked where people spoof your domain and send fraudulent emails on behalf of your organization to your clients, staff or business partners. As a result, you require an effective method of monitoring how receiving mail servers authenticate emails sent from your domain.
DMARC (Domain-Based Message Authentication, Reporting and Conformance) assists in solving this issue through the provision of the ability for domain owners to configure what actions should be taken when a message fails to authenticate.
Additionally, it offers reporting capabilities that show the sender servers that use your domain to send their messages, as well as authentication results.
Nevertheless, the receipt of DMARC reports does not guarantee that one knows what the contents of the reports are all about. Reports contain technical details regarding the sending IPs, SPF, DKIM, alignment and email policy. This article is going to help you interpret the reports, detect any authentication issues and utilize the information for your email security.
Table of Contents
What Is a DMARC Report? And Why Is It Important?
What Is a DMARC Report?
A DMARC report is an email from a receiving server that tells the domain owner details about email authentication actions regarding the domain. The purpose of a DMARC report is to inform the administrator about the results of DMARC checking actions and how the receiving server handles emails that fail the check.
For instance, if your company uses [email protected], then DMARC reports will reveal which senders use yourbusiness.com domain and if their emails have passed the SPF or DKIM check.
Why Companies Require DMARC Report Monitoring
The absence of continuous monitoring means that you might not be aware that the email system used by one of your employees has incorrect authentication settings or that an unauthorized server is pretending to be from your domain.
Additionally, DMARC report helps you determine legitimate senders and also prevents you from blocking real business emails while hardening your email security system.
How do DMARC Reports Prevent Email Spoofing?
DMARC acts in conjunction with SPF and DKIM to authenticate whether the emails meet the authentication guidelines specified by your domain. By configuring the DMARC policy, you can specify no action to be taken, quarantine or reject emails based on the result of the DMARC test.
You will learn from the reports how your policy works in relation to incoming emails that try to make use of your domain.
Understand the Two Major Types of DMARC Reports
There are two main ways by which DMARC generates reports: aggregate report and failure reports. Both offer different data related to the domain’s email authentication practices.
1. Aggregate Reports (RUA)
The aggregate report is a statistical summary of email activity that relates to the email authentication of your domain. This kind of report is typically sent by receiving mail servers periodically.
These contain information like sender IP addresses, number of emails sent, results of SPF and DKIM checks, alignment and DMARC disposition.
Therefore, aggregate reports are helpful in determining legitimate email senders as well as irregularity in sending activities.
2. Failure Reports (RUF)
Failure reports include information about messages that fail the DMARC assessment individually, depending on the practices of the receiving service provider and your settings.
However, unlike aggregated reports, they can include information about messages that can be used by the administrators to look into particular failures in authentication. Nevertheless, most leading email providers do not offer such reports due to privacy reasons
Learn About the Information Included in a DMARC Report
It is necessary to be familiar with the various technical fields included in any report before starting with its analysis. The technical information describes the sender of the emails, the number of emails received, and whether or not authentication was successful.
Reporting Organisation and Metadata for the Report
The metadata specifies the organisation producing the report, the subject matter of evaluation, the report number, and the reporting period.
For instance, the reporting period enables you to determine the time at which the recipient server saw the email activity.
Sending IP Addresses and Email Volume
The source_ip denotes the IP address from which the e-mails have been sent and the count shows the number of e-mails reported under the particular result.
Thus, compare those with the IP addresses and the sending service providers allowed by your organization.
SPF and DKIM Authentication Results
SPF determines if the sending server is authorized to send the message for the specified envelope domain. DKIM validates the authenticity of the digital signature attached to the message.
Nonetheless, being validated through one of the two authentication checks does not mean that the message will be considered compliant with DMARC. It also requires alignment between the authenticated domain and the visible From domain.
Read more here to see how SPF, DKIM, and DMARC cooperate in authenticating emails from websites and diagnosing issues with email authentication
DMARC Alignment Pass
DMARC alignment involves checking whether the domain that has passed SPF or DKIM verification is the same as the domain in the “From” address of the email. There is assurance that DMARC will pass as long as at least one method passes the authentication and satisfies the alignment requirements.
Applied DMARC Policies
The disposition variable indicates how the messages were actually handled by the receiver when evaluated according to the DMARC standards. Possible values are:
- none: No DMARC-based policy was applied by the receiver.
- quarantine: The message was treated as being suspicious and was likely placed in the spam folder.
- reject: The message was rejected.
These results will assist you to see how the published DMARC policy influences failed message authentication.
How to Read and Understand a DMARC Aggregate Report in Steps
DMARC aggregate reports usually come as zipped XML files. Despite seeming intimidating at first sight, one can make sense of the data from the fields in the right order.
Aggregate reports are usually delivered in the form of compressed XML attachments. While the format may seem complex, all the vital information is actually contained in the fields in the right order.
1. Open and Extract the DMARC XML Report
Start by downloading the attachment sent to your business email account. The report is usually attached in either .xml, .zip, or .gz format.
Unzip the file, and then open the XML file using any text editor or any tool used for analysing DMARC reports. An analysis tool will automatically present the data contained in the XML in tabular and graphical form.
2. Understanding Report Metadata and Reporting Period
First find the section that says report_metadata. In this section, there are details about the reporting organisation, report ID, and reporting period.
The next step is to check policy_published. In this section, there are DMARC policy details found by the receiving server for your domain, which include p, sp, adkim, and aspf.
3. Sending IP Addresses and Email Sources
Under each entry, check the source_ip tag. It indicates the IP address corresponding to the email action.
Compare the addresses with your legitimate email hosting company, website server, marketing system and others for sending emails. When you are uncertain about an address, look into it to determine whether it is really an attack or not.
4. Analyzing SPF and DKIM Authentication Results
Take a look at the SPF and DKIM results in the auth_results part. Next, you should contrast the information found in the policy_evaluated field, where you will see whether SPF/DKIM passed DMARC alignment check.
The reason why the difference is important is that an email may pass SPF/DKIM authentication but fail DMARC because of non-alignment of the two domains.
5. DMARC Alignment and Disposition Explained
Lastly, take a look at the disposition, spf and dkim under policy_evaluated.
For instance:
| XML <policy_evaluated> |
In this case, DKIM has been aligned by DMARC, but SPF failed alignment. There is also no DMARC enforcement applied by the recipient. Because DKIM alignment has passed, the email can still pass DMARC.
6. Assessment of the Emails that Passed or Failed the DMARC Protocol
Use the authentication and alignment findings together in order to come up with an end result, whether the email failed or passed DMARC.
Keep in mind that the failure of one test does not necessarily mean failure on the part of the whole message in DMARC compliance. The structure of the XML report determines these fields and their relationship.
Understanding the Meaning of the Most Common DMARC Report Results
Once you learn how to read the report, you need to comprehend its results regarding your business field.
Emails That Have Passed DMARC Authentication
As long as SPF and DKIM authentication both succeed with the proper alignment, then the email will succeed DMARC verification, which is usually a good sign, provided that the sending IP address belongs to the approved service.
Email Failing SPF Alignment
This is a case where SPF failed to provide an aligned pass. Determine whether the sending service is included in the SPF record as well as using the correct envelope domain.
Emails that Fails Both SPF and DKIM
If both techniques fail the alignment test, then the email will fail DMARC. Analyse the sending source especially when you are not sure about its IP address.
Unknown Sending IP Addresses
The IP address that is unknown to you could be from a trusted third-party email service provider, an old system, or an unauthorised sender. It is advisable to ensure that you know about it first before making any changes in your DNS settings.
Steps to Discover and Fix Issue Detected from DMARC Reports
After discovering any problems related to email authentication, make sure that you find out the cause of such a problem before you alter the domain settings.
1. Check Your SPF DNS Record
Check your SPF TXT record and ensure that you have authorised all the sending systems that send email on your behalf. Also, check for more than one SPF record because a domain can only have one SPF record policy.
Also note that there is a restriction in SPF where it allows up to 10 DNS lookups in its evaluation process. Too many DNS-based systems will lead to a permerror.
2. DKIM Settings Verification
Confirm whether your email provider signs all emails using DKIM and that the public key for this is stored in the DNS records for your domain.
If you have switched to another email provider recently, ensure that the right DKIM selector and signing domain are used.
3. Unauthorised Email Sender Investigation
In case the report shows an unknown IP address, find out who owns it. Verify this information by checking your hosting account, email service providers and web applications to find out if the IP address is from a genuine service.
Moreover, in the event that you discover that an unauthorized individual has been spoofing your domain, check your security policies and maintain proper DMARC policies.
4. Third-Party Email Service Checkup
Marketing tools, web-forms, billing software and CRM systems could use your company’s domain when sending out emails.
Hence, ensure that the settings for SPF and DKIM are correct for each of the services. Otherwise, legitimate emails will not pass DMARC alignment.
5. DMARC Policy: Review It Before Making Any Changes
Before switching your policy to p=reject on the basis of any authentication failures, find out the legitimate sources and fix their authentication.
If you are certain that your legitimate messages are passing through DMARC successfully, then start from p=none and proceed to p=quarantine and finally p=reject.
Common Errors to Watch Out For While Analyzing DMARC Reports
Even with frequent reports, mistakes in their misinterpretations may cause DNS errors and mail deliverability issues.
- Misconception Regarding Alignment for SPF/DKIM and DMARC: The passing of the SPF/DKIM does not guarantee that of the DMARC policy. It is important to ensure that at least one authentication mechanism is aligned with the visible From domain.
- Unauthorized Blocking of Emails: A new IP address does not always signify any sort of malicious attack. Before blocking any such sender, it is essential to authenticate it as an authorized sender.
- Neglecting Unrecognised Sending IP Addresses: While there may be some unknown addresses that are from legitimate email senders, one must review them anyway. Negligence of any questionable sending will leave your domain open for spoofing.
- Implementing New DMARC Policies without Checking Reports: Jumping straight into implementation of new policies without checking your reports can influence legitimate emails which were not authenticated.
- Assuming all authentication failures are a sign of an attack: An authentication failure could be caused by wrong DNS records, configurations on third party services, or forwarding and unauthorized actions. Determine the cause prior to reacting to the issue.
How to Use DMARC Reports for Improved Business Email Security
The reports generated by DMARC analysis gain importance because they are used to ensure that email authentication remains consistent and your domain is protected.
- Authorize All Legal Email Senders: Keep a current list of those applications that use the domain name to send emails. Whenever a new email application is introduced, set up its SPF and DKIM record to pass DMARC alignment.
- Consistently Monitor DMARC Reports: Monitor your aggregate reports on a regular basis to check whether there have been any changes in your email sending volumes, authentication results, and unknown IPs.
- Slowly Work Up to a Strong DMARC Policy: Begin with p=none if you want to know about your email traffic. Once you have resolved your authentication issues, you can then add quarantine and rejection policies. Alternatively, you can use the pct tag in order to enforce an enforcement policy on a given percentage of messages within a transition period, where applicable to your implementation.
- Keep SPF, DKIM, and DMARC Records Up to Date:Â Always check your DNS records if there is any switch of email hosts, email platform, or email sender applications. Make sure your authentication records are current and correctly configured for your existing email setup.
Conclusion
The DMARC reports provide businesses with information on how receiving mail servers verify emails sent through the domains owned by them. You can detect authentication issues as well as suspicious email activities by looking at the sender IP addresses, the SPF and DKIM tests, alignment and policy enforcement.
Nevertheless, relying on reports of received emails will not safeguard your domain. You will have to check the data periodically and ensure your configuration is right.
Need reliable business email hosting services?
At HarmonWeb, we offer reliable hosting services that can enable businesses to set up email addresses based on their domains. Along with using reliable email hosting, make sure that you have SPF, DKIM, and DMARC settings right in place.


