TL;DR: Across more than 73 million domains, just 14.9% have a basic DMARC policy and 2.5% enforce p=reject, Red Sift found, so spoofing still has room to impersonate trusted senders. Email authentication only protects mail when sender inventory, alignment and enforcement move together.
Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “Most businesses still can't answer one simple question about their email”.
By the numbers:
- only 14.9% have implemented even a basic DMARC policy
- roughly 84% of domains have no visible DMARC record at all
Key questions
Q: Should organisations rely on DMARC to stop phishing?
A: No. DMARC helps reduce spoofing, but it does not stop attacks that use valid infrastructure, collaboration channels, or post-delivery manipulation. Organisations should keep DMARC in place, but measure phishing resilience across the whole delivery chain, including session abuse, channel trust, and user action after delivery.
A: The clearest signs are a persistent p=none policy, incomplete sender inventory, unresolved SPF or DKIM alignment problems, and reports showing unknown services sending as the domain.
A: Start by inventorying every authorised sender, including marketing, support, and transactional platforms, then validate SPF and DKIM for each one.
Practitioner guidance
- Map every authorised sender Inventory every platform, service and third party that sends email on behalf of the domain, then verify SPF and DKIM alignment for each one before changing policy.
- Escalate from monitor-only to enforcement Move DMARC from p=none to p=quarantine and then p=reject only after legitimate senders are confirmed and reporting is stable.
- Use aggregate reports to find shadow senders Review DMARC aggregate reports to identify unauthorised or forgotten services that are still sending as the domain, including legacy business tools and external platforms.
Bottom line: Most domains still fail to enforce DMARC, which leaves spoofing and phishing able to exploit trusted domain identity.
Glossary terms: DMARC None Policy, Sender Inventory, Email Authentication Alignment, DMARC Aggregate Reporting
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DMARC enforcement is now an identity governance issue, not just an email deliverability issue. Once a domain can claim sender identity, it becomes part of the broader trust fabric that customers, partners and internal systems rely on. A policy that stops at monitoring leaves that trust ungoverned, which is why security teams should treat email authentication as a control boundary, not a messaging preference.
A question worth separating out:
Q: Who should own DMARC enforcement in an organisation?
A: DMARC enforcement should be jointly owned by security and the teams operating domain-based mail services. Security should define the policy and monitoring expectations, while platform or messaging teams validate legitimate senders and fix alignment issues. That split keeps deliverability, fraud prevention, and change control tied to one operating model.
👉 Read our full editorial: DMARC enforcement remains incomplete across most domains