VERA Vendor Risk Signals Library

DMARC and Vendor Risk

DMARC is an externally observable email security control that can provide useful insight into how a vendor protects its domain from spoofing and impersonation. This guide explains what DMARC can reveal, what it cannot prove, and how to interpret it as part of a broader third-party risk assessment.

What is DMARC?

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is an email authentication protocol that builds on SPF and DKIM. It allows a domain owner to publish a policy in DNS describing how receiving email systems should treat messages that fail authentication checks and, optionally, where authentication reports should be sent.

DMARC also introduces the concept of domain alignment. For a message to pass DMARC, the domain visible in the message’s From: address must align with a domain successfully authenticated through SPF or DKIM. This helps prevent an attacker from simply authenticating email using a different domain while making the message appear to come from the organization being impersonated.

A DMARC record is published as a DNS TXT record, typically at a location such as:

_dmarc.example.com

The policy can specify one of several handling preferences for messages that fail DMARC:

  • none — monitor authentication results without asking receivers to change message handling;
  • quarantine — request that failing messages receive suspicious treatment, such as placement in spam or quarantine; or
  • reject — request that failing messages not be accepted.

Under the current DMARC standard, a domain operating with p=none is considered to be in monitoring mode, while a policy other than p=none represents enforcement.

DMARC is currently standardized in RFC 9989, published in May 2026, which replaced the earlier RFC 7489 specification.

Why does DMARC matter in vendor risk?

Organizations routinely trust email from vendors.

Employees receive invoices, payment instructions, password-reset messages, project documents, support requests, contract communications, and account-change instructions from third parties every day. That trust makes a vendor’s domain useful to attackers attempting phishing, business email compromise, or other forms of impersonation.

DMARC helps a domain owner make unauthorized use of that domain more difficult. CISA specifically recommends DMARC as a way to reduce the likelihood of spoofed or modified messages appearing to originate from legitimate domains.

From a third-party risk perspective, this makes DMARC useful because the vendor does not have to tell you whether a policy exists. The relevant DNS records are publicly observable.

A vendor with no DMARC record or one operating only in monitoring mode may have less protection against direct domain spoofing than an organization enforcing a properly configured DMARC policy.

That does not make the vendor insecure. It does give the assessor a concrete piece of evidence worth considering.

What can VERA observe?

Because DMARC policy information is published in DNS, VERA can independently evaluate aspects of a vendor’s DMARC configuration without requiring access to the vendor’s internal systems.

Depending on the available evidence, VERA can observe:

  • whether a DMARC record is publicly available;
  • the published DMARC policy;
  • whether the domain is operating in monitoring or enforcement mode;
  • whether the requested policy is none, quarantine, or reject;
  • policy configuration affecting organizational domains and subdomains;
  • available reporting configuration;
  • alignment-related policy settings; and
  • malformed, incomplete, or potentially ineffective DMARC configurations.

VERA can also evaluate DMARC alongside related externally observable email-security signals such as SPF and DKIM.

That distinction is important. The objective is not simply to answer “Does this vendor have DMARC?”

The more useful question is:

“What does the vendor’s observable email-authentication configuration tell us, and how much weight should we give that evidence?”

What does this signal not prove?

A missing or weak DMARC policy does not prove that a vendor has been breached or that its email accounts are compromised.

It also does not prove that:

  • phishing messages are currently being sent using the vendor’s identity;
  • attackers have successfully impersonated the vendor;
  • the vendor lacks other email-security protections;
  • the vendor’s employees are susceptible to phishing;
  • its internal mail environment is insecure; or
  • the organization has a weak cybersecurity program overall.

Conversely, a p=reject DMARC policy does not prove that a vendor has strong security controls throughout the rest of its environment.

DMARC addresses a specific problem: authentication and policy handling associated with use of an email domain.

Even CISA notes an important limitation: DMARC helps protect the domain implementing it from being spoofed, but it does not by itself protect an organization from receiving spoofed messages from domains that have not implemented comparable protections.

There is another important distinction between absence and non-detection. External analysis may not always establish every mail-sending domain, service, or configuration used by an organization. A finding should therefore describe what was actually observed rather than making claims that exceed the available evidence.

How VERA uses this signal

VERA evaluates DMARC as part of a broader set of externally observable DNS and email-security indicators.

The signal is retained with its supporting evidence and evaluated in context rather than being treated as proof of an organization’s overall security posture.

Where possible, VERA considers DMARC alongside related controls, configuration details, and other risk indicators to distinguish a standalone configuration issue from a broader pattern that may warrant additional investigation.

This is central to VERA’s approach to vendor risk:

observe the evidence, understand its limitations, and use it to make a better-informed decision.

Related Vendor Risk Signals

No single external signal tells the whole story. These related signals can provide additional context when evaluating this finding as part of a broader third-party risk assessment.

DKIM and Vendor Risk

DKIM provides cryptographic authentication for email and works with DMARC to help establish whether messages are legitimately associated with a vendor’s domain.

SPF in Vendor Risk

SPF identifies systems authorized to send email for a domain and provides another externally observable layer of the vendor’s email-authentication posture.

Exposed Credentials as a Third-Party Risk Signal

Exposed credentials can increase the significance of weak email protections by creating additional opportunities for account takeover, impersonation, and social engineering.

Scroll to Top