Knowledge base
Government and industry DMARC mandates
Where DMARC is required by government policy or industry standards.
DMARC has moved from good practice to an expectation. Several governments require it for their own domains, and industry standards and insurers increasingly ask for it. Requirements change, so treat this as an overview and check the current text that applies to you.
Governments
- United States. Binding Operational Directive 18-01 (2017) requires federal civilian agencies to publish DMARC at
p=reject, along with SPF and STARTTLS. - United Kingdom. Government guidance requires public sector email domains to use SPF, DKIM and DMARC, working towards
p=reject, and to use MTA-STS and TLS-RPT. - Australia. The Information Security Manual recommends DMARC with a reject policy for all government domains, including those that do not send mail.
- New Zealand. The Secure Government Email framework requires agencies to use SPF, DKIM and DMARC with a reject policy, and MTA-STS.
- Many other countries, including Canada, the Netherlands and Denmark, have similar requirements for public bodies.
Industry
- Mailbox providers. Google, Yahoo and Microsoft require DMARC from bulk senders. See sender requirements.
- PCI DSS 4.0 requires mechanisms to protect against phishing; DMARC is a common way to meet that for your own domains.
- Cyber insurance questionnaires commonly ask whether DMARC is enforced.
Whatever the driver, the path is the same: start monitoring, fix your senders, then enforce.
See it on your own domain.
Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.
Start free