How to find your DKIM selector and turn on DKIM
Find the DKIM selector each sender really uses from a received message, and if none signs as your domain, turn DKIM signing on at the mail provider.
Last reviewed
Why it matters
DKIM signs outgoing mail with a key published in DNS. It is the authentication that usually survives forwarding, and what lets services sending on your behalf pass DMARC. DNS cannot be listed, so Owl Keeper tries the common selector names; your key may exist under another one.
How to fix it
Replace the highlighted values: example.com with your domain, google with your DKIM selector.
Any DNS host
Start by finding the real selector: the key may already be there.
-
Send a message from each system that sends as the domain (the main mailbox, website forms, CRM, invoicing, newsletters) to a Gmail or Outlook mailbox you can read.
-
Open the full headers. In Gmail: open the message, More next to Reply, Show original. In Outlook on the web and the new Outlook: More actions > View > View message details. In classic Outlook: File > Properties > Internet headers.
-
Find the
DKIM-Signature:header:d=is the signing domain ands=the selector.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=google; ...
Authentication-Results: ... dkim=pass header.i=@example.com header.s=google
- Look the key up. The answer should be a
v=DKIM1; k=rsa; p=…record, directly or through a CNAME; an emptyp=means the key was revoked.
dig TXT google._domainkey.example.com +short
dig CNAME google._domainkey.example.com +short
- If
d=is your domain and the key resolves, DKIM is set up under a custom selector and nothing needs fixing: accept the finding in Owl Keeper. If there is no signature, ord=is the provider's domain, turn on DKIM with your domain in that service and publish the record it gives you, exactly as given.
Sources: RFC 6376, Gmail: show original, Outlook: view headers.
Google Workspace
Owl Keeper already tries Google's default selector, google, so on a Workspace domain this usually means DKIM was never turned on.
- As a super administrator go to Menu > Apps > Google Workspace > Gmail > Authenticate email.
- Choose the domain in Selected domain and click Generate New Record.
- Pick 2048 bits if your DNS host supports it (otherwise 1024), keep the prefix selector google, and click Generate.
- Add the record Google shows at the DNS host. Copy the key from the console; it is too long to type:
Name: google._domainkey
Type: TXT
Value: v=DKIM1; k=rsa; p=<the key from the Admin console>
- Wait for DNS (Google says up to 48 hours; on a new Workspace account the key appears 24 to 72 hours after Gmail is turned on).
- Back in Authenticate email, select the domain and click Start authentication, only once the record is published.
Source: Set up DKIM.
Microsoft 365
Owl Keeper already tries selector1 and selector2, so on a Microsoft 365 domain this usually means DKIM is not enabled for the custom domain.
- In the Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM.
- In the custom domain's row, set the toggle to Enabled. A dialog lists the CNAMEs needed; select OK.
- Open the domain's details and copy the two values under Publish CNAMEs.
- Create the two CNAME records at the DNS host with exactly those values (they differ by tenant and by when the domain was added, so always copy them):
selector1._domainkey CNAME <Selector1CNAME value from the portal>
selector2._domainkey CNAME <Selector2CNAME value from the portal>
- After a few minutes, turn on Sign messages for this domain with DKIM signatures in the same panel. The status should read Signing DKIM signatures for this domain. Keep both CNAMEs: the second is used after key rotation.
Source: Microsoft: configure DKIM.
Cloudflare
Add DKIM records as at any DNS host, but set a CNAME-based DKIM record (Microsoft 365 and many sending services use them) to DNS only. A proxied CNAME is flattened to Cloudflare's addresses and the key no longer resolves.
Source: Proxy status.
Check that it worked
dig TXT google._domainkey.example.com +short
dig CNAME selector1._domainkey.example.com +short
dig TXT google._domainkey.example.com +short
After the TTL (or up to 48 hours for Google), send a test to an outside Gmail or Outlook mailbox and confirm dkim=pass with header.d=example.com, then run the Owl Keeper Email authentication check again. A custom selector will still not be found by the check: accept the finding once you have confirmed the key yourself.
What can go wrong
- Signing before the key is published makes mail fail DKIM, which is why Google says not to click Start authentication early.
- Long keys break when pasted. Some DNS interfaces truncate or split a 2048-bit key; compare the published value with the
digoutput. - Removing a selector you have not traced to a sender breaks that sender's signing.
- A proxied DKIM CNAME on Cloudflare does not resolve to the key.