On this page
- What happens when your domain has no DMARC record
- Safe starting DMARC TXT record (zero risk of blocking real mail)
- Anatomy of a valid DMARC record
- Provider-specific DNS publishing notes
- Verify your DMARC record via dig & nslookup
- Four common mistakes that silently invalidate DMARC
- Moving safely to active enforcement
Missing DMARC Record
Missing DMARC lets attackers spoof your exact domain and hurts Gmail & Yahoo deliverability. Exact safe starting TXT record syntax and rollout guide.
Run your domain through our Free Email Deliverability Scanner to verify whether a _dmarc record exists, then publish the safe zero-risk starting record below.
What happens when your domain has no DMARC record
SPF and DKIM are ID badges, but DMARC is the security guard at the door. When an attacker sends a forged invoice claiming to come from [email protected], the recipient's server checks your _dmarc DNS record to ask what to do when authentication fails.
Without a DMARC record, there is no instruction—so receiving servers default to letting the spoofed email through. Starting in 2024, Google and Yahoo also began enforcing DMARC requirements for senders, meaning missing DMARC actively hurts inbox placement for your legitimate business mail as well.
Safe starting DMARC TXT record (zero risk of blocking real mail)
Never jump straight to p=reject on day one before inventorying your third-party senders (QuickBooks, CRM, website forms, newsletters). Start cleanly by publishing a discovery record at host _dmarc:
_dmarc 300 IN TXT "v=DMARC1; p=none; rua=mailto:[email protected]; fo=1;"
Exception — Parked or Defensive Domains: If you own extra domains that never send email (e.g., typo-squatting defenses or retired brand names), lock them immediately on day one alongside v=spf1 -all:
_dmarc 300 IN TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected];"
Anatomy of a valid DMARC record
| Component | Required? | What It Controls |
|---|---|---|
Host: _dmarc |
Yes | Subdomain label where receiving mail gateways look for your policy (_dmarc.yourdomain.com). |
v=DMARC1; |
Yes (first tag) | Protocol version—must be exact uppercase DMARC1 and must appear first. |
p=none; |
Yes | Initial monitoring action (delivers failing mail while logging telemetry so you don't disrupt unmapped apps). |
rua=mailto:... |
Strongly recommended | Destination for daily aggregate XML reports showing every IP and cloud tool sending as your domain. |
fo=1; |
Optional | Requests diagnostic failure samples whenever either SPF or DKIM fails independently. |
Provider-specific DNS publishing notes
- Cloudflare: Open DNS → Records → Add record → Type
TXT, Name_dmarc, TTLAutoor5 min, Contentv=DMARC1; p=none; rua=mailto:[email protected]; fo=1;. - GoDaddy: Go to Manage DNS → Add New Record → Type
TXT, Name_dmarc(do not include your domain name—GoDaddy appends it automatically), Valuev=DMARC1; p=none; ..., TTL600 seconds. - Microsoft 365 & Google Workspace: Neither Microsoft 365 nor Google Workspace publishes a
_dmarcTXT record automatically during setup. Before escalating fromp=noneto enforcement, verify that custom DKIM signing is enabled in Microsoft Defender (selector1/selector2) or Google Admin Console (google._domainkey).
Verify your DMARC record via dig & nslookup
# macOS / Linux — confirm exactly one "v=DMARC1; ..." record returns dig +short TXT _dmarc.yourdomain.com # Windows PowerShell / CMD nslookup -q=txt _dmarc.yourdomain.com 8.8.8.8
Send a test email to a Gmail address, inspect Show original, and confirm you see DMARC: PASS alongside SPF: PASS and DKIM: PASS.
Four common mistakes that silently invalidate DMARC
- Publishing two
_dmarcTXT records: Under RFC 7489 Section 6.6.3, multiplev=DMARC1records cause receiving servers to discard DMARC entirely—leaving you unprotected. - Lowercase
v=dmarc1or missing semicolons: The version string is case-sensitive (v=DMARC1) and every tag-value pair must be separated by semicolons. - Doubling the domain name in the host field: Typing
_dmarc.yourdomain.cominto GoDaddy or Namecheap creates_dmarc.yourdomain.com.yourdomain.com, which mail servers never query. - Omitting
mailto:inrua=: Writing[email protected]instead ofrua=mailto:[email protected]silently disables aggregate reporting.
Moving safely to active enforcement
Once your starting record is live and aggregate reports confirm that Microsoft 365 / Google Workspace plus every legitimate SaaS sender passes DKIM and SPF alignment, follow our DMARC Monitoring to p=reject Guide to ratchet safely to p=quarantine and p=reject.
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.