Glossary
DMARC
Definition
DMARC checks whether email authentication aligns with the visible From domain and lets domain owners request handling of messages that fail.
A message passes when SPF or DKIM passes with an identity aligned to its From domain. Published policies can request monitoring, quarantine or rejection.
A customer may include “DMARC” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Domain-based Message Authentication, Reporting, and Conformance (DMARC) connects email authentication to the domain in the visible From address. It lets a domain owner publish a policy for messages that fail and request reports about how its domain is used.
A message can pass DMARC through SPF or DKIM: at least one must pass using a domain aligned with the From domain. Alignment means a defined domain match, with stricter or more relaxed modes. Merely having an SPF or DKIM pass for an unrelated domain is insufficient.
Hypothetical example: a wholesaler's finance messages pass SPF for its email provider, but the provider uses a different delivery domain. Aligned DKIM signing may provide the path to a DMARC pass. The administrator checks all legitimate senders before tightening policy.
A monitoring policy does not request the same handling as a rejection policy, and receiving systems retain their own handling decisions. Review aggregate DMARC reports to identify legitimate senders and alignment failures, then tighten handling once mail sources are accounted for. DMARC cannot stop lookalike domains or a compromised genuine mailbox. DMARC cannot stop a scam sent from an attacker's lookalike domain or from a compromised genuine mailbox. Staff still need independent verification for sensitive changes.
Sources: IETF RFC 9989: DMARC; IETF RFC 9990: DMARC aggregate reporting.