DMARC Explained: Protecting Your Domain From Email Impersonation
Most teams know phishing is a problem. Fewer start with a simpler question: can somebody send email that appears to come from our domain?
An impersonation attempt is often aimed beyond your own inbox. Customers, suppliers, investors and partners may all trust your brand name. If an attacker can use it convincingly, the recipient is left to decide whether an email is real at exactly the moment the attacker wants to create pressure.
In Scaling Cyber S1E8, Sacha Matulovich of Sendmarc describes the practical objective as stopping bad actors from impersonating a company’s email addresses outside the organisation. DMARC is one of the mechanisms that helps make that objective enforceable.
What DMARC does
DMARC stands for Domain-based Message Authentication, Reporting and Conformance. The acronym is technical, but the operating question is straightforward: which systems are allowed to send mail for this domain, and what should a receiving mail system do when a message fails those checks?
DMARC works alongside SPF and DKIM. SPF tests whether a client host is authorised to send with a stated identity. DKIM provides a signature a receiver can verify. DMARC applies identifier-alignment checks to those results, lets a domain owner publish a policy, and supports aggregate reporting.
For a practitioner, the point is not to become fluent in three acronyms. It is to establish and maintain a defensible sending posture: legitimate mail keeps flowing, unauthorised use is visible, and the domain is progressively protected from being used as a believable sender identity.
Why the control is about people outside your perimeter
Secure email gateways and endpoint controls are important, but they mainly protect people inside your environment. Domain impersonation can be aimed at anyone who trusts your name. A supplier may receive a payment-change request. A customer may receive a fake service notice. An investor may receive a message that looks like a familiar contact.
That is why a domain-authentication programme should not be treated only as mail-administration hygiene. It is part of brand and business protection. The aim is to reduce the chance that recipients must recognise a forgery on their own.
Matulovich’s framing is useful here: the work should happen before the message reaches a human decision-maker. That does not make people irrelevant, and it does not remove the need for awareness or payment-verification processes. It reduces one avoidable way an attacker can borrow your identity.
Start with visibility, not an abrupt enforcement change
A common mistake is to think of DMARC as a record to publish and forget. In practice, the difficult part is understanding every legitimate source that sends mail for the domain: business applications, marketing platforms, ticketing systems, outsourced providers and regional teams can all be part of the picture.
Start by establishing reporting and inventorying those senders. Investigate failures rather than assuming every failure is hostile. Fix alignment and authentication issues in legitimate services first. Then move deliberately toward an enforcement posture that matches the organisation’s risk tolerance and operational confidence.
The Guardian360 DACH MSP Email Security Benchmark 2026 illustrates why visibility and enforcement are separate milestones. Its public-DNS scan of 1,311 MSPs counted only p=reject as protected: 25.5% met that threshold, while 42.0% had no aggregate reporting configured. Those figures apply to the report’s DACH sample. They show that publishing a record differs from reaching a controlled, monitored enforcement state.
Make DMARC an owned operating process
The programme needs a clear owner. Email administrators understand the systems; security teams understand the abuse case; business owners know which platforms must continue sending. A workable process brings those perspectives together.
Use a short, repeatable cycle:
-
Maintain an approved inventory of sending services and domain owners.
-
Review authentication reports and investigate unfamiliar sources or failure patterns.
-
Test changes with the business system owner before tightening policy.
-
Record exceptions with an expiry and a responsible owner.
-
Treat new SaaS purchases and domain registrations as changes to the email-authentication estate.
DMARC is a continuing identity-control practice. The value comes from knowing what is permitted to use your name and responding when that picture changes.
The practical outcome
The operational outcome is clear: legitimate mail is understood, reporting is reviewed, and the organisation can confidently reduce impersonation opportunities without breaking critical communication.
That makes DMARC a useful example of preemptive security: strengthen the identity signal before an attacker turns trust in your domain into a delivery mechanism. For a wider view of the identity problem, see DMARC: The Identity Reckoning.
Frequently asked questions
Does DMARC stop every phishing attack?
No. DMARC addresses unauthorised use of domains that an organisation controls. It does not remove the need for other email, identity, payment-verification and awareness controls, and it does not automatically prevent look-alike domains.
Why begin with reporting?
Aggregate reports give domain owners visibility into authentication results and policy effects. The current DMARC reporting specification is designed to help owners validate ongoing policy decisions against the mail streams receivers see.
What do SPF and DKIM contribute?
SPF publishes sending-host authorisation. DKIM lets a receiver verify a domain-associated signature. DMARC evaluates their results in relation to the visible author domain.
Who should own the programme?
Email operations, security and business-system owners each have a role. A named owner should coordinate the sending-service inventory, reporting review, exception handling and change decisions.
Watch the Scaling Cyber S1E8 conversation with Sacha Matulovich: https://youtu.be/XxGjIpp4BmI.