24 Oct 2026

Email Authentication Explained: SPF, DKIM, and DMARC for Business Email Security

An analysis of 1.8M domains found just over half had a DMARC record in 2026 — far fewer set to block forged mail. What SPF, DKIM and DMARC each do.

EasyDMARC’s 2026 global DMARC adoption analysis, covering the top 1.8 million domains worldwide, found that 52.1% had published a DMARC record — up from 47.7% the year before, but still meaning nearly half had none at all. More tellingly, the same analysis found only around 9% of domains combined a meaningful enforcement policy with active reporting — the configuration that actually stops forged mail rather than just monitoring it. Most organizations with any DMARC presence are watching spoofing happen, not blocking it.

SPF, DKIM, and DMARC are the three standards that, together, let a receiving mail server verify that an email claiming to be from your domain actually came from a source you authorized. None of them is new technology, and none requires specialist infrastructure to deploy — but the gap between “published” and “actually enforcing” is where most of the real-world protection is lost.

What each standard actually does

SPF (Sender Policy Framework) is a DNS record listing which mail servers are authorized to send email on behalf of your domain. A receiving server checks the sending server’s IP address against your SPF record; if it doesn’t match an authorized source, that’s a signal the mail might be forged. SPF’s main limitation: it breaks when mail is forwarded through an intermediate server, since the forwarding server’s IP won’t match your original SPF record.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing mail, generated using a private key your mail server holds, verifiable against a public key published in your DNS. A receiving server checks that signature against the message content — if anything in the signed portion was altered in transit, or the signature doesn’t match, verification fails. Unlike SPF, DKIM survives most forwarding, since the signature travels with the message content rather than depending on the sending server’s IP.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties the two together and adds the piece that actually matters for taking action: it tells receiving servers what to do when a message fails both SPF and DKIM alignment (do nothing, quarantine it, or reject it outright), and it gives you visibility — aggregate reports showing every source sending mail claiming to be from your domain, authorized or not. DMARC is what turns SPF and DKIM from passive checks into an enforceable policy.

Why “published” isn’t the same as “protected”

A DMARC record can exist at three meaningfully different enforcement levels:

  • p=none — monitoring only. Receiving servers report on alignment failures but take no action on the mail itself. This is the correct starting configuration, not a finished one.
  • p=quarantine — mail failing alignment gets routed to spam/junk rather than the inbox.
  • p=reject — mail failing alignment gets rejected outright, never reaching the recipient at all.

The adoption gap described above — roughly half of domains with any DMARC record, but a much smaller fraction actually enforcing — mostly reflects organizations publishing a record at p=none and never progressing further, whether from uncertainty about what might break or simply never circling back. A p=none record provides visibility but doesn’t stop a single forged email from reaching its target. It’s genuinely a case where most of the real protective value sits at the end of the rollout, not the beginning.

Rolling out DMARC safely: don’t skip the monitoring phase

The reason organizations hesitate to move to enforcement is legitimate: a business typically has more authorized senders than it initially assumes — the CRM platform sending transactional email, the invoicing tool, the marketing newsletter service, a help-desk system sending notifications — and if even one of those isn’t accounted for when you flip to p=reject, that legitimate mail starts bouncing.

A safe rollout follows this order:

  1. Publish SPF and DKIM first, correctly configured for every legitimate sending source you can currently identify.
  2. Publish a DMARC record at p=none with an aggregate-reporting address configured. This starts collecting data without affecting delivery at all.
  3. Review the aggregate reports for several weeks (most guidance suggests at least two to four weeks, longer for businesses with infrequent but legitimate bulk senders like quarterly newsletters). Reports will surface every source claiming to send as your domain — including legitimate tools you may not have initially listed.
  4. Authorize every legitimate source in your SPF record and/or DKIM configuration as you identify it from the reports.
  5. Move to p=quarantine once reports show only expected, authorized sources passing alignment, and unauthorized sources are the ones failing.
  6. Move to p=reject once you’re confident in the quarantine phase’s results — this is the enforcement level that actually stops domain spoofing rather than just flagging it.

Skipping straight to p=reject without the monitoring phase is the single most common cause of DMARC rollouts breaking legitimate mail and getting reversed in frustration — which then leaves the domain at no protection at all, often for longer than a cautious rollout would have taken.

Why this matters even for a small business

Domain spoofing attacks don’t require a recognizable brand to be effective — they require a recipient who already trusts mail from a specific sender. An invoice-fraud attempt impersonating a small business’s own domain, sent to that business’s actual customers or suppliers, works just as well regardless of company size, and arguably faces less scrutiny from recipients who aren’t primed to expect a large company’s domain to be spoofed. A fully enforced DMARC policy (p=reject) is one of the few controls that directly and structurally prevents exact-domain email spoofing — not just detects it after the fact.

It’s worth noting what DMARC does not cover: it stops exact-domain spoofing (mail claiming to be you@yourdomain.com), but not lookalike-domain tricks (you@yourdomaiin.com) or display-name spoofing that doesn’t use your actual domain at all. DMARC is necessary, not sufficient, as part of a broader email-security and user-awareness approach.

Email authentication rollout checklist

  • SPF record published, listing every current legitimate sending source
  • DKIM configured and signing outgoing mail for all legitimate senders
  • DMARC record published at p=none with aggregate reporting enabled
  • Aggregate reports reviewed for several weeks before any policy change
  • Every legitimate sending source identified and authorized
  • Policy progressed to p=quarantine, then p=reject, only after reports confirm no legitimate mail is failing alignment
  • Reports continue being monitored after reaching p=reject — new legitimate tools added later need authorizing too

Key takeaways

SPF and DKIM let a receiving server verify an email’s claimed origin; DMARC is what turns that verification into an actual, enforceable policy and gives you visibility into who’s sending mail as your domain. Global adoption data shows roughly half of domains have published some DMARC record, but only a small fraction have progressed to real enforcement — meaning most organizations with “DMARC” technically in place are still watching spoofing attempts happen rather than blocking them. A careful, monitored rollout from p=none to p=reject is what actually closes that gap.

Shahid Security’s Secure Website Development and Monitoring & Training services include email-authentication configuration as part of a broader domain and email security review.

Not sure whether your domain’s DMARC policy is actually enforcing anything? Book a free consultation.


Sources: EasyDMARC 2026 Global DMARC Adoption Report, Red Sift US DMARC Adoption Report.

FAQ

If we already have spam filtering, do we still need SPF, DKIM, and DMARC?

Yes — they solve a different problem. Spam filtering looks at incoming mail you receive and tries to judge whether it's unwanted. SPF, DKIM, and DMARC protect outgoing authenticity — they let receiving mail servers verify that mail claiming to come from your domain actually did, which is what stops someone else from sending convincing fake email that appears to be from you.

Will setting up DMARC break our legitimate email, like newsletters or invoicing tools?

It can, if you jump straight to full enforcement without checking first. That's exactly why the rollout starts at p=none — a monitoring-only mode that reports on every sending source claiming to be your domain, including legitimate third-party tools, without blocking anything. You review those reports, authorize every legitimate sender, and only then move to enforcement.

Do we need DMARC if we're a small business with no brand recognition to spoof?

Domain spoofing doesn't require brand recognition to be effective — it requires a target trusting an email that appears to come from a specific person or company they already do business with. A small business's domain is just as spoofable for a convincing invoice-fraud or business-email-compromise attempt as a larger company's, and in some cases a smaller company's email security gets less scrutiny from recipients, not more.

Shahid Iqbal

Written by Shahid Iqbal

Founder & Cybersecurity Consultant, Shahid Security