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
- Start with p=none: Monitor first to identify all legitimate senders before enforcing.
- Set up RUA reports: Use a DMARC reporting service to analyze aggregate data.
- Graduate to p=reject: Once all legitimate sources pass, move to full rejection.
- 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.



