TL;DR: DMARC monitoring alone does not stop spoofing or brand impersonation, according to Valimail. Email domains need quarantine or reject policies, plus SPF and DKIM alignment, to turn trust into enforcement.
Editorial analysis by NHI Mgmt Group, based on content published by Valimail: “How to create and publish your own DMARC record”.
Key questions
Q: Why does weak DMARC adoption increase the risk of email fraud and brand impersonation?
A: Weak DMARC adoption leaves attackers with an easier path to forge messages that appear to come from a trusted domain.
Q: What breaks when a domain stays on p=none?
A: You still get reports, but you do not stop spoofed mail from arriving in inboxes.
A: Start by inventorying every authorised sender, including marketing, support, and transactional platforms, then validate SPF and DKIM for each one.
Practitioner guidance
- Publish DMARC with a staged enforcement plan Start with monitoring only if you need discovery, but set a clear path to quarantine or reject once SPF and DKIM alignment are stable across legitimate senders.
- Inventory every authorised mail source Map all platforms, applications, and third-party services that send on your domain so unexpected sources do not remain hidden in aggregate reports.
- Validate alignment before tightening policy Check that SPF and DKIM are published, aligned, and working for each sending stream before moving from p=none to stronger enforcement.
Bottom line: DMARC turns email-domain trust into an enforceable policy decision, which is why monitoring alone leaves organisations exposed to spoofing and impersonation.
Glossary terms: DMARC, SPF, DKIM, Email Spoofing
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DMARC enforcement is a trust boundary, not an email housekeeping task. The article makes the right distinction between monitoring and enforcement, but the deeper governance point is that unauthorised domain use is an access problem at the message layer. Once a receiver trusts the From domain, the attacker can borrow brand authority without compromising the underlying mailbox. Practitioners should therefore treat DMARC policy as part of identity assurance for communications, not just deliverability tuning.
A question worth separating out:
Q: How do security teams know whether DMARC enforcement is actually working?
A: Look for fewer authentication failures from legitimate senders, stable alignment for critical mail flows, and reporting that clearly shows why a message passed or failed. If failures cannot be explained quickly, the programme is not ready for stricter enforcement. Working DMARC is visible, reproducible, and backed by clean sender inventory.
👉 Read our full editorial: DMARC enforcement is now the baseline for brand and inbox protection