Opens in a new tab

selector1 and selector2: Microsoft 365’s DKIM keys

selector1 and selector2 are Microsoft 365’s DKIM selectors — the same names for every organisation. Both are CNAMEs into your tenant; one signs at a time, so the other can take over when the key is rotated. Custom domains added since May 2025 point at dkim.mail.microsoft instead of onmicrosoft.com.

WhoseMicrosoft 365 — mailbox provider
Selectorselector1, selector2
Published asTwo CNAMEs, to selector1-<domain-with-dashes>._domainkey.<tenant>.<x>-v1.dkim.mail.microsoft — or, for domains added before May 2025, …<tenant>.onmicrosoft.com
KeyRSA 1024 or 2048 — New-DkimSigningConfig defaults to 1024; rotating with -KeySize 2048 upgrades one selector at a time
RotationIn the Defender portal (Rotate DKIM keys) or with Rotate-DkimSigningConfig; the new key starts signing after four days
Before you set it upMail is signed for <tenant>.onmicrosoft.com, which does not align with your domain for DMARC
Where to find itDefender portal → Email & collaboration → Policies & rules → Threat policies → Email authentication settings → DKIM
Can it go?Turn DKIM signing off for the domain first. Microsoft says not to publish DKIM records for domains that send no mail.

Is Microsoft 365’s key on your domain?

Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Microsoft 365’s key under selector1 and selector2, check it, and name every other key the domain publishes.

The records

Microsoft’s current shape — use the exact values it shows, from the Defender portal or Get-DkimSigningConfig:

selector1._domainkey.example.com  CNAME  selector1-example-com._domainkey.example.n-v1.dkim.mail.microsoft
selector2._domainkey.example.com  CNAME  selector2-example-com._domainkey.example.n-v1.dkim.mail.microsoft

How it works

The old and new target forms cannot both be used for one selector. Each subdomain that sends mail needs its own DKIM configuration.

Of the two selectors only the active one’s target answers with a key; the other may answer nothing until the next rotation.

Common mistakes

  • A TXT record instead of the CNAMEs — Microsoft does not support it.
  • Only selector1: without selector2 the key cannot rotate.
  • Dots instead of dashes in the target, or a missing partition letter (the n in n-v1).
  • A TTL under an hour, which Microsoft says causes intermittent temporary errors.

What changed

  • May 2025 — New custom domains get CNAMEs into dkim.mail.microsoft instead of onmicrosoft.com.

Setting up Microsoft 365 from scratch? Its SPF, DKIM and DMARC records, and a check of all three.

Questions

Why does selector1’s target not resolve?

Only one of the two selectors is active at a time; the inactive one may answer nothing until the next rotation. As long as the active one resolves, signing works.

Sources

Checked on 27 September 2026 against these official sources:

Know when a DKIM key disappears

Point your DMARC reports at us and we monitor the keys your mail is signed with — and email you when one stops answering, before receivers start failing your mail. Free for your first domain.

Create a free account