Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
CIS Microsoft 365 Foundations v7.0.0 · 2.1.10

DMARC records should be published for all Exchange Online domains

  • E3 Level 1
  • Microsoft Defender
  • Automated check

This check looks at the DNS of every domain used for mail in Exchange Online and whether each one publishes a DMARC record. The safe setting is a DMARC TXT record on every sending domain, with a policy that tells receivers what to do with mail that fails authentication.

Why it matters

Without DMARC, anyone can send mail that claims to come from your domain and receivers have no instruction on how to treat it. DMARC builds on SPF and DKIM: it tells the receiving server to check that the visible From domain lines up with them, and what to do when it does not (nothing, quarantine or reject).

Microsoft documents DMARC as a core part of protecting your domain against spoofing, and publishes reports you can use to see who is sending as you.

Source: Microsoft Learn, Use DMARC to validate email, setup steps.

How to check it yourself

In the Microsoft 365 admin center open Settings > Domains to list your domains, including ones that never send mail. Then query DNS for each one. A read-only lookup from any workstation:

Resolve-DnsName -Type TXT -Name _dmarc.contoso.example

The answer should contain a string starting with v=DMARC1. To list the domains first, use Exchange Online PowerShell:

Connect-ExchangeOnline
Get-AcceptedDomain | Select-Object DomainName,DomainType

No result for _dmarc means the domain has no record. The domain names above are invented examples.

How to fix it

Start in monitoring mode so you do not block your own legitimate mail:

  • Make sure SPF and DKIM are in place for each domain that sends mail.
  • At your DNS host, add a TXT record named _dmarc with a value such as v=DMARC1; p=none; rua=mailto:dmarc-reports@contoso.example.
  • Read the aggregate reports, fix senders that fail, and then move the policy from none to quarantine and finally reject.
  • For domains that never send mail, publish a record with a reject policy straight away.

ConfigCobra never makes these changes for you: it reports the finding and suggests the steps.

What changes when you fix it

A record with p=none changes nothing about delivery; it only starts producing reports to the address you name. Moving to quarantine or reject affects every system that sends mail as your domain: marketing platforms, ticketing tools, printers and partners. Any of them that is not covered by SPF or DKIM will have its mail sent to junk or refused.

Work through the reports and fix each sender before you tighten the policy, and tell the owners of those systems when you do.

Included in

BenchmarkCIS IDProfile
CIS Microsoft 365 Foundations v7.0.02.1.10E3 Level 1

Check this on your Microsoft 365

ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial