TL;DR: DMARC enforcement still sits at 40% across five Southwest states, with Red Sift pointing to many domains remaining in monitoring or quarantine rather than blocking unauthenticated mail. Email identity governance has to close that gap before spoofed messages can keep reaching payment, access and trust decisions.
Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “Only 40% of the Southwest's top organizations block spoofed email”.
By the numbers:
- 138 domains across the region run p=none policies that monitor but take no action against spoofed emails.
- 114 domains sit at p=quarantine, close to full protection but not finishing the move to reject.
- 47 domains have no DMARC record published at all.
Key questions
Q: Why do p=none and p=quarantine leave organisations exposed?
A: p=none and p=quarantine are useful transitional states, but they still allow many spoofed messages to reach users.
Q: How should security teams implement DMARC enforcement across multiple email senders?
A: Start by inventorying every system that sends mail for the domain, then validate SPF and DKIM for each one before moving from monitoring to quarantine or reject.
Q: What breaks when organisations delay DMARC enforcement?
A: Delayed enforcement leaves hidden sender dependencies undiscovered until a mailbox provider begins rejecting mail.
Practitioner guidance
- Tighten DMARC policy from monitoring to rejection Set a dated transition plan for domains still at p=none or p=quarantine, with explicit owner sign-off for each sending source before moving to reject.
- Inventory every legitimate sender Build a current list of all systems, vendors and business units sending mail on the domain so SPF and DKIM alignment can be validated before enforcement changes.
- Treat email impersonation as fraud exposure Bring business email compromise scenarios into fraud and identity governance reviews where payments, vendor onboarding and account recovery depend on email trust.
Bottom line: The core risk is not just spoofed email, but the ability to impersonate an organisation’s identity in workflows that trigger payment, access or trust decisions.
Glossary terms: DMARC, Email Authentication Alignment, Business email compromise, Sender Inventory
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DMARC enforcement is now an identity governance control, not a mail-server preference. When domains are used to authorise payments, procurement messages and account recovery flows, spoofing becomes an access problem as much as a messaging problem. That means security teams should assess enforcement as part of the organisation’s trust boundary, especially where external parties act on email instructions. The practical conclusion is simple: if a domain can still be impersonated, the identity boundary is still soft.
A question worth separating out:
Q: What should security teams verify before moving a domain to reject?
A: Before moving to reject, teams should verify every legitimate sender, confirm SPF and DKIM alignment, and remove or reconfigure stale sources that still send on behalf of the domain. If the sender inventory is incomplete, enforcement will break legitimate mail and create pressure to roll the policy back. Good enforcement depends on governance of authorised senders, not just record changes.
👉 Read our full editorial: DMARC enforcement lags across the Southwest despite high-value targets