DMARC Check: Is Your Domain Spoofable?
2026-11-06 · 6 min read · By the DomainGuard team
The short version
Your domain is spoofable if it has no DMARC record, or a DMARC record set to p=none — in both cases, anyone on the internet can send email that claims to be from your exact domain, and receiving servers have no instruction to stop it. The check takes one DNS lookup: query the TXT record at _dmarc.yourdomain.com. No record = fully spoofable. p=none = monitored but unprotected. p=quarantine = suspicious mail goes to spam. p=reject = spoofed mail is refused outright — the only setting that actually closes the hole. DomainGuard's free report reads your live DMARC, SPF, and DKIM posture and shows you which of these you are. Check mechanics as shipped in DomainGuard's scanner, November 2026.
What does a DMARC check actually read?
Three records, all public DNS, all readable by anyone — including attackers choosing targets:
| Record | Where it lives | What the check reads |
|---|---|---|
| SPF | TXT at your root domain | Which servers may send for your domain; whether the list ends in a hard fail (-all) or a soft shrug (~all) |
| DKIM | TXT at <selector>._domainkey | Whether your mail is cryptographically signed, and whether the signing domain aligns with your From domain |
| DMARC | TXT at _dmarc.yourdomain.com | The policy (p=) you instruct receivers to enforce, the alignment mode, and where your reports go (rua=) |
The word that matters is alignment. SPF and DKIM each authenticate a domain — but DMARC only passes when the domain they authenticate matches the domain in the visible From header. Attackers exploit the gap constantly: mail that passes SPF for a domain they control, displayed as your brand. That is a different failure from a lookalike domain, and this check is about your exact domain. (For the cousin-domain problem DMARC cannot touch, see our lookalike check guide.)
How do you run the check yourself in one minute?
Step 1: look up the TXT record at _dmarc.yourdomain.com (any DNS lookup tool, or dig TXT _dmarc.yourdomain.com). Nothing there? Your domain is spoofable today.
Step 2: read the p= value. none means you are collecting reports but telling receivers to deliver spoofed mail anyway. quarantine sends failures to spam. reject refuses them.
Step 3: check the percentage tag (pct=) if present — a p=reject; pct=10 record enforces on only 10% of failing mail, a half-finished rollout frozen in place.
Step 4: confirm SPF ends in -all and that your real senders (your mail host, your invoicing tool, your newsletter platform) are inside it — the two failure shapes are "no SPF" and "SPF so permissive it authenticates half the internet."
Why does this matter more in 2026 than it used to?
Because the big mailbox providers made it a deliverability requirement, not just a security nicety. Gmail, Yahoo, and Microsoft now require bulk senders to publish SPF, DKIM, and DMARC — mail from high-volume senders without them is rejected or spam-foldered as a matter of policy. So the same missing record now costs you twice: your domain stays open to spoofers impersonating you, and your legitimate campaigns quietly stop landing in inboxes. Our DMARC, SPF, DKIM rollout guide covers the safe order of operations for fixing it without breaking your own mail — start at p=none with reporting on, read the reports until every legitimate sender is aligned, then tighten to quarantine and finally reject.
What can't DMARC do?
Three things, stated plainly so the check does not oversell itself. It cannot stop lookalike domains — a cousin domain passes its own checks. It cannot stop display-name spoofing on its own ("Your CEO <[email protected]>") — that is a training and mail-client problem. And it cannot help if your own account is compromised — mail from your real mailbox is authenticated by definition. DMARC closes one specific, enormous hole: strangers sending as your exact domain. Our impersonation defense cheat sheet shows where that hole sits in the full playbook, next to CAA records and certificate monitoring.
FAQ
How do I check if my domain is spoofable?
Look up the TXT record at _dmarc.yourdomain.com. No record, or a record with p=none, means anyone can send email as your exact domain and receivers have no instruction to stop it. DomainGuard's free report runs this check plus SPF and DKIM and shows your live posture.
What is the difference between p=none, p=quarantine, and p=reject?
p=none monitors only — failing mail is still delivered. p=quarantine sends failing mail to spam. p=reject tells receivers to refuse failing mail outright. Only quarantine and reject protect you, and reject is the complete setting.
Will turning on DMARC break my email?
Not if you roll it out in the safe order: publish at p=none with report delivery (rua) on, read the reports until every legitimate sender — mail host, invoicing, newsletters — is SPF/DKIM aligned, then step up to quarantine, then reject. Broken mail comes from jumping straight to reject with a forgotten sender still unaligned.
Does DMARC stop phishing emails that look like mine?
It stops phishing sent as your exact domain. It does not stop lookalike domains (a cousin domain passes its own SPF and DKIM), display-name tricks, or mail from a genuinely compromised account. Those need lookalike monitoring and takedown, which is the rest of the DomainGuard playbook.
Do I need DMARC if I only send a little email?
Yes. Spoofers do not care how little you send — they care that your domain is trusted by your customers and suppliers. And the Gmail/Yahoo/Microsoft sender rules mean even small senders feel the deliverability side. The record takes minutes to publish.