DMARC Configuration and Alignment
What you'll learn: How to properly configure DMARC DNS records, understand identifier alignment requirements, and implement a gradual enforcement strategy to protect your domain.
Understanding DMARC Records
Now that you understand DMARC policy basics, it's time to configure it correctly. DMARC records are published as TXT records in DNS at _dmarc.yourdomain.com. A basic record looks like:
v=DMARC1; p=none; rua=mailto:reports@yourdomain.com; pct=100; aspf=r; adkim=r
Each tag matters: p= sets your policy (none/quarantine/reject), rua= specifies where aggregate reports go, pct= controls what percentage of mail the policy applies to, while aspf= and adkim= define alignment modes.
Identifier Alignment Modes
Think of alignment as verifying that the "From" address you see matches what SPF and DKIM validated behind the scenes. DMARC requires at least one to align:
- SPF alignment: The domain in the envelope "Mail From" must match the visible "From" header
- DKIM alignment: The domain in the DKIM signature (
d=) must match the "From" header
Alignment comes in two flavors:
- Relaxed (
r): Allows subdomain matches (mail.example.com aligns with example.com) - Strict (
s): Requires exact domain match
Use aspf=r for SPF and adkim=r for DKIM alignment in your DMARC record.
Gradual Enforcement Strategy
Never jump straight to p=reject! Start with p=none to monitor reports without blocking mail. Use pct=10 to apply policies to only 10% of traffic initially. Over weeks, gradually increase to pct=100, then move to p=quarantine, and finally p=reject once you're confident legitimate mail passes authentication.
Key Takeaway: DMARC configuration requires careful DNS record setup with proper alignment modes (relaxed or strict) and a phased enforcement approach—start monitoring with p=none, then gradually tighten to quarantine and reject while analyzing authentication reports.