Back to Tools

Bulk DMARC Extractor

Extract and analyze DMARC policy records.

Email Security Tool

Manual Input

Enter one domain per line. Don't include protocols (http://) or subdomains unless needed.

CSV Upload

Upload a CSV file with domains. Select the column containing domains below.

Processing Settings

DMARC Query: Queries _dmarc.domain.com for DMARC policy records (v=DMARC1).
Processing Domains
00:00
0
Total
0
Processed
0
Successful
0
DMARC Found
0
Batch
Ready to start...

DMARC Records Found

0 records

Complete Guide to DMARC

What is DMARC?

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that builds on SPF and DKIM. It tells receiving mail servers what to do when messages fail authentication—reject them, quarantine them, or just monitor.

Published as a DNS TXT record at _dmarc.yourdomain.com, DMARC also provides reporting mechanisms so domain owners can see who's sending email on their behalf, including attackers attempting spoofing.

Why Extract DMARC Records?

Security Assessment

Audit DMARC policies across your organization's domains. Identify domains with p=none (monitoring only) that aren't fully protected against spoofing.

Email Deliverability

Verify DMARC is properly configured before sending marketing campaigns. Missing or misconfigured DMARC hurts inbox placement.

Competitive Intelligence

Analyze competitors' DMARC policies to understand their email security maturity and identify report addresses.

DMARC Record Syntax

v=DMARC1; p=reject; rua=mailto:dmarc@example.com; ruf=mailto:forensics@example.com; pct=100
  • v=DMARC1: Version identifier (required)
  • p= (policy): none (monitor), quarantine (spam folder), reject (block)
  • rua=: Aggregate report destination (daily summaries)
  • ruf=: Forensic report destination (real-time failure alerts)
  • pct=: Percentage of messages to apply policy (for gradual rollout)

Best Practices

  1. Start with p=none: Monitor first to identify all legitimate senders before enforcing.
  2. Set up RUA reports: Use a DMARC reporting service to analyze aggregate data.
  3. Graduate to p=reject: Once all legitimate sources pass, move to full rejection.
  4. Implement for subdomains: Add sp= for subdomain policy to prevent subdomain spoofing.

Common Mistakes

  • p=none forever: Monitoring without enforcement provides no protection.
  • Missing alignment: DMARC requires SPF or DKIM to pass AND align with From header.
  • Ignoring reports: RUA reports reveal unauthorized senders—review them regularly.

Frequently Asked Questions

What's the difference between DMARC policies?

p=none only monitors. p=quarantine sends failures to spam. p=reject blocks delivery entirely. Start with none, graduate to reject.

Do I need SPF and DKIM before DMARC?

Yes. DMARC requires at least one to pass and align. Implement both SPF and DKIM before DMARC for best protection.

Why do some domains have p=none?

They're in monitoring phase or haven't completed DMARC rollout. It's a safe starting point but provides no enforcement.

About the Author: Nicola Selenu

Nicola is a Lead Developer and Digital Marketing Technologist with years of hands-on experience in technical SEO, web analytics, and deliverability. He builds tools to bridge the gap between complex marketing technicalities and easy-to-use solutions.