Skip to main content
All CollectionsEmail Authentication Protocols
How to Run a DMARC Lookup and Interpret the Results
How to Run a DMARC Lookup and Interpret the Results

Learn how to run a DMARC lookup and interpret the results to improve email security and deliverability.

Updated over a week ago

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is essential for email security, helping domain owners prevent spoofing and phishing attacks. Running a DMARC lookup allows you to check your domain’s DMARC record and ensure it’s correctly configured. But what do the results mean, and how can you fix errors?

In this guide, we’ll walk you through running a DMARC lookup, interpreting the results, and troubleshooting common issues.


What is a DMARC Lookup?

A DMARC lookup is a diagnostic tool that retrieves and analyzes your domain’s DMARC record from the DNS. It helps ensure your email authentication policies are correctly set up and enforced.

Why Should You Run a DMARC Lookup?

✅ Verify that your DMARC record is published correctly
✅ Detect errors in syntax or policy configuration
✅ Ensure email authentication (SPF, DKIM) is working
✅ Improve email deliverability and security


Step-by-Step Guide to Running a DMARC Lookup

1. Use an Online DMARC Lookup Tool

There are several online tools available:

  • YourDMARC Lookup Tool (Recommended)

  • MXToolbox

  • DMARC Analyzer

  • EasyDMARC

Simply enter your domain name, and the tool will fetch and display your DMARC record.

2. Manually Check Your DMARC Record in the DNS

If you prefer a manual check, use the following command in your terminal:

nslookup -type=TXT _dmarc.yourdomain.com

Or on Linux/macOS:

dig TXT _dmarc.yourdomain.com

Understanding DMARC Lookup Results

Here’s a breakdown of common DMARC record components and what they mean:

Component

Description

Example Value

v

DMARC version

v=DMARC1

p

Policy (How to handle failing emails)

p=reject (or quarantine, none)

rua

Aggregate report email

ruf

Forensic report email

fo

Failure reporting options

fo=1 (Send reports on all failures)

pct

Percentage of emails to apply policy to

pct=100


Common DMARC Issues and Fixes

Here are some typical problems and their solutions:

Issue

Possible Cause

Solution

DMARC record not found

No DMARC record published

Create and add a DMARC record in your DNS settings

Syntax errors

Incorrect format or missing semicolons

Validate your record using an online DMARC checker

Policy not enforced

Policy set to p=none

Change policy to p=quarantine or p=reject

Reports not received

Incorrect rua or ruf email

Ensure emails are correctly formatted and accessible


Frequently Asked Questions (FAQs)

1. How often should I check my DMARC record?

It’s recommended to check your DMARC record regularly, especially after making changes to SPF or DKIM settings.

2. What should my DMARC policy be?

  • Start with p=none to monitor traffic.

  • Move to p=quarantine once you analyze reports.

  • Finally, enforce p=reject to block unauthorized emails.

3. Why am I not receiving DMARC reports?

Ensure that your rua and ruf email addresses are correctly set up and that your mailbox can receive large report files.

4. Does DMARC affect email deliverability?

Yes. A correctly configured DMARC policy improves deliverability by proving your emails are legitimate.


Final Thoughts

Running a DMARC lookup is a crucial step in securing your email domain and preventing unauthorized use. By understanding the results and fixing any issues, you can enhance your email security and maintain brand trust.

Need help setting up DMARC? Try YourDMARC’s automated DMARC management tool today!

Did this answer your question?