Warning

No DKIM key found at the usual selectors

The short version

Turn on DKIM signing with your mail provider and publish its key; enter your selector if you know it.

What it means

We looked for DKIM keys at your mail provider's selectors and at the selectors most services use, and found none. A selector is the name a key is published under, such as google._domainkey.example.com. Your mail may still be signed with a selector we didn't try.

Why it matters

DKIM signs every message so receivers can tell it really came from you and wasn't changed on the way. Without it, DMARC depends on SPF alone, which breaks whenever mail is forwarded. Gmail and Yahoo expect DKIM from bulk senders.

How to fix it

  1. If you know your selector, enter it under "More options" and check again. It appears in the s= tag of the DKIM-Signature header of any message you send.
  2. If DKIM isn't set up yet, turn it on in your mail provider's admin panel and publish the record it gives you.

Google Workspace

In the Admin console go to Apps, Google Workspace, Gmail, Authenticate email. Generate a 2048-bit key, publish the TXT record it shows at your DNS host, wait for it to appear, then press Start authentication.

Microsoft 365

In the Defender portal open Email authentication settings, then DKIM. Publish the two CNAME records it lists for selector1 and selector2, then turn signing on for the domain.

Check it worked

Run the DKIM record validator with your domain and selector, or the full email check. New keys show up once DNS has updated, usually within an hour. Send yourself a message and look for dkim=pass in its headers to confirm signing works end to end.