Skip to content
AdminKit

DKIM selector

What is DKIM selector?

A DKIM selector is a short label in a message's DKIM-Signature header that tells a receiving server exactly which DNS TXT record holds the public key needed to verify it, letting one domain publish several keys at once. AdminKit's guide to DKIM selector mistakes covers the failures its DKIM check tool most often surfaces.

By AdminKit team, Netbase JSC · Updated

A DKIM selector is a short label included in a message’s DKIM-Signature header, a field RFC 6376 defines (document record at the IETF Datatracker), that tells a receiving server exactly which DNS TXT record holds the public key needed to verify it, at the hostname selector._domainkey.example.com. Selectors let one domain publish multiple DKIM keys at once — a common setup when several outbound mail systems (a marketing platform, a helpdesk tool, an internal mail server) each sign with their own key and selector, such as mandrill._domainkey.example.com or the selector Google Workspace documents for its own outbound mail. Microsoft 365 takes the same approach: Microsoft’s DKIM setup guide has each custom domain publish two selector records, selector1 and selector2, with only one active at a time and the other used only after a future key rotation. A verification failure often traces back to a selector mismatch rather than a bad signature: the sending system changed selectors, rotated a key, or the DNS record for that specific selector was never published or was deleted during cleanup.

Why a DKIM verification failure happens:

  • The sending system rotated its key and switched selectors without telling anyone.
  • The DNS TXT record for that specific selector was deleted during cleanup.
  • The record was simply never published for the selector the signature actually names.

AdminKit’s guide to rotating a DKIM key without breaking mail covers how to make that kind of selector change deliberately — publishing the new key under a new selector and running both in parallel for an overlap period, rather than overwriting the old one and causing exactly this kind of verification failure.

AdminKit groups dKIM selector under its email authentication cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does a DKIM selector actually point to?

The label in a message's DKIM-Signature header -- selector._domainkey.example.com -- that tells a receiving server exactly which DNS TXT record holds the public key needed to verify the signature.

Why would one domain need more than one DKIM selector?

Because several outbound systems -- a marketing platform, a helpdesk tool, an internal mail server -- each sign with their own key, so separate selectors let each publish its own public key without overwriting another's record.

What's the most common cause of a DKIM verification failure?

A selector mismatch, not a bad signature: the sending system rotated its key and switched selectors, or the DNS TXT record for that specific selector was never published or was deleted during cleanup.

What's the safe way to rotate a DKIM key without breaking mail?

Publish the new key under a new selector and run both the old and new selectors in parallel for an overlap period, rather than overwriting the existing selector's record outright.