Microsoft 365, AD and Windows · #16
Online Microsoft 365 DNS Checker
Reads the MX, SPF, Autodiscover, DMARC and DKIM records Microsoft 365 needs from live DNS and compares them with the expected values.
- Live DNS query (Cloudflare DNS over HTTPS)
Tool
What does this tool do?
Most mail problems during and after a Microsoft 365 migration come from DNS: the MX still points to the old server, SPF lacks the Microsoft include, DKIM CNAMEs are missing. The tool reads the records from a public resolver and separates three states: the observed value, Microsoft's expected pattern, and what cannot be verified in the tenant.
The tool does not connect to your tenant. If you enter the exact values shown on the Domains page of the Microsoft 365 admin center, it compares them one to one.
How to use it
- Enter the domain (e.g.
contoso.com). - Optionally enter the MX target from the admin center (
contoso-com.mail.protection.outlook.com) and part of the DKIM CNAME target. - Change the selector list if you use other DKIM selectors, then press Run.
Fields
- Domain
- Domain only; no http:// or path.
- Expected MX target (optional)
- MX value from Microsoft 365 admin center › Domains › DNS records.
- DKIM selectors
- Exchange Online defaults are selector1 and selector2.
- Expected DKIM target (optional)
- Part of the CNAME target from the Defender portal, e.g. contoso.onmicrosoft.com.
Worked example
| Input | Value |
|---|---|
| Domain | contoso.com |
| Expected MX target (optional) | contoso-com.mail.protection.outlook.com |
| DKIM selectors | selector1,selector2 |
Expected result: In the sample data MX, SPF, Autodiscover, DMARC and selector1 match; the selector2 CNAME does not exist (NXDOMAIN) and is marked 'missing'.
If selector2 is missing, signing breaks when Microsoft rotates to the second selector. Do not enable DKIM in the Defender portal until both CNAMEs are published.
Method and assumptions
Queries go from your browser to Cloudflare DNS over HTTPS (1.1.1.1): MX and TXT of the domain, the autodiscover CNAME, the _dmarc TXT and selectorN._domainkey CNAMEs.
Expected patterns follow Microsoft's external DNS records documentation: MX target *.mail.protection.outlook.com (newer tenants may use *.mx.microsoft), include:spf.protection.outlook.com in SPF, Autodiscover CNAME autodiscover.outlook.com, DKIM CNAME target selectorN-…._domainkey.….onmicrosoft.com.
An MX pointing elsewhere is not automatically an error: with an email security gateway it is expected and shown as 'external target observed'.
Using the result and troubleshooting
Fix 'missing' rows first, especially SPF and MX. Compare 'external target' with your architecture: with a filtering service, Exchange Online needs an inbound connector and enhanced filtering.
DKIM CNAMEs in DNS do not prove that signing is enabled in the tenant. Check that the status is 'Signing' under Email authentication › DKIM in the Defender portal.
Limits and common mistakes
- Tenant settings (accepted domains, connectors, DKIM status) cannot be read.
- SRV and lyncdiscover records for Teams/Skype and Intune CNAMEs are not checked in this version.
- Because of DNS caching, a recent change may not be visible until the TTL expires.
Frequently asked questions
My MX points to a filtering service — is that an error?
No. The tool marks it as 'external target observed'. What matters is that Exchange Online is configured to accept mail only from that service.
The DKIM records exist but mail is unsigned — why?
The CNAMEs are only a prerequisite. Signing must be enabled in the Defender portal; on first activation Microsoft may need a few minutes to publish the keys.
Related tools and service
- DNS LookupFetches the DNS records of one name and type from a public resolver, with TTLs.
- SPF Record CheckerExpands an SPF record with its include and redirect chain, counts the DNS lookup budget and shows structural errors.
- DKIM Selector LookupReads a DKIM selector's DNS record and shows key type, length and revocation state.
- DMARC Record CheckerReads the _dmarc record and interprets its policy, reporting and alignment settings.
Related service: Microsoft 365, Azure, AWS and Google Cloud Services