Call (703) Book ↗
On this page
DMARC · RFC 7489 Enforcement

DMARC Monitoring Mode (p=none)

A DMARC policy of p=none monitors mail but blocks zero spoofing attacks. Follow our 3-phase roadmap to move safely from p=none to p=reject.

Stuck in Monitoring Mode?

Check whether your domain is enforced or sitting at p=none with our Free Email Deliverability Scanner.

Why p=none blocks zero spoofing attacks

A p=none DMARC record tells receiving mail servers around the world: "If an attacker spoofs our exact domain to send fake wire instructions, don't block it—just deliver it normally and email us an XML log later."

p=none was designed solely as a temporary discovery phase. Unfortunately, many IT providers publish p=none to earn a superficial green checkmark and never come back—leaving the business with 0% mechanical spoof protection under RFC 7489.

MONITORING ONLY (0% PROTECTION) VS. ENFORCED REJECTION
; Monitoring Only (allows spoofed mail into inboxes)
_dmarc  300  IN  TXT  "v=DMARC1; p=none; rua=mailto:[email protected];"

; Graduated Containment (quarantine 25% -> 100% of failing mail)
_dmarc  300  IN  TXT  "v=DMARC1; p=quarantine; pct=25; sp=quarantine; rua=mailto:[email protected];"

; Enforced Protection (rejects unauthorized root AND subdomain spoofing)
_dmarc  300  IN  TXT  "v=DMARC1; p=reject; sp=reject; adkim=r; aspf=r; rua=mailto:[email protected];"

Why 70%+ of small businesses stay stuck at p=none

Most organizations stay frozen at monitoring mode out of a legitimate fear: breaking real business email. If you flip straight to p=reject without mapping every sender (QuickBooks, Mailchimp, CRM, website forms, payroll), real customer invoices can bounce. Worse, raw DMARC rua= XML reports generate thousands of unreadable XML files every month without an ingestion tool.

Key DMARC policy tags every admin should understand

TagPurposeRecommended Rollout Value
p= Root domain enforcement action (none, quarantine, reject) Step none → quarantine → reject once legitimate senders reach 99–100% pass.
sp= Subdomain policy (protects unused subdomains from spoofing) Set sp=reject alongside p=reject so attackers cannot forge billing.yourdomain.com.
pct= Percentage of failing mail subject to the active policy (1–100) Use pct=25 → pct=50 → pct=100 during quarantine testing, then omit (defaults to 100) at full reject.
adkim= / aspf= Identifier alignment mode: r (relaxed organizational domain) vs. s (exact strict match) Keep relaxed (r) unless you have strict compliance requirements—never weaken an existing strict s policy accidentally.
rua= Aggregate XML telemetry destination (mailto: URI) Route to a dedicated Hosted DMARC parser address, never a human employee's daily inbox.

The safe 3-phase path from p=none to p=reject

  1. Phase 1 — Discovery & Telemetry Ingestion (p=none)Ingest 14–30 days of aggregate DMARC XML reports into a visual dashboard to uncover every shadow cloud tool sending on your domain—from Stripe and ADP to website contact plugins and CRM platforms.
  2. Phase 2 — Sender Alignment & Quarantine (p=quarantine)Enable 2048-bit custom DKIM signing and aligned SPF on every authorized sender, then step safely through p=quarantine; pct=25 → pct=100 while monitoring compliance reports daily.
  3. Phase 3 — Full Enforcement (p=reject)Once 100% of legitimate mail passes alignment cleanly, enforce p=reject; sp=reject;—blocking exact-domain spoofing, satisfying cyber insurance underwriters, and qualifying for BIMI readiness.

Provider-specific DKIM & DNS notes before escalating policy

  • Microsoft 365: Out of the box, Exchange Online signs outbound mail with your *.onmicrosoft.com domain—which fails DMARC DKIM alignment! Before moving past p=none, open Microsoft Defender → Email authentication → DKIM, publish both custom selector1._domainkey and selector2._domainkey CNAMEs, and toggle DKIM signing ON for every custom domain.
  • Google Workspace: Generate a 2048-bit key under Admin Console → Apps → Gmail → Authenticate email, publish the google._domainkey TXT record, wait for propagation, and click Start authentication before tightening DMARC.
  • Cloudflare & GoDaddy: Always enter host/name strictly as _dmarc (both dashboards auto-append your root domain—typing _dmarc.yourdomain.com in GoDaddy creates an invalid _dmarc.yourdomain.com.yourdomain.com record). Keep TTL at 300 seconds during policy transitions so you can roll back within 5 minutes if a forgotten billing vendor surfaces.

Verify your active DMARC policy via CLI

INSPECT LIVE _DMARC TXT RECORD
# macOS / Linux
dig +short TXT _dmarc.yourdomain.com

# Windows PowerShell / CMD
nslookup -type=txt _dmarc.yourdomain.com 1.1.1.1

Common DMARC enforcement pitfalls

  • Relying on SPF alone without aligned DKIM: When a client forwards your email or uses a mailing list, SPF breaks because the forwarding server's IP isn't in your SPF record. Aligned 2048-bit DKIM survives forwarding intact and keeps legitimate mail passing at p=reject.
  • Hosted DMARC delegation vs. manual TXT edits: With Enuclea Hosted DMARC, your _dmarc record can be managed cleanly with visual XML telemetry so you see every shadow sender before tightening policy—eliminating guesswork and unreadable raw XML attachments.
  • Forgetting external rua= authorization: If your rua=mailto: points to a different domain (e.g., a reporting service), that external domain must publish a yourdomain.com._report._dmarc.reportdomain.com TXT record containing v=DMARC1, or providers will drop the reports.
Want Our Engineers to Fix Your DNS Cleanly?

One stray character in SPF or DMARC can bounce every invoice your company sends. Let Enuclea audit your senders, flatten SPF safely, align 2048-bit DKIM, and configure DMARC cleanly starting at $250 flat. Test your domain free, book a 15-minute call (24-hr notice) ↗, or call (703) 239-4620.