Fail

Your DKIM selector has no key

The short version

Publish the DKIM key from your mail provider at that selector.

What it means

There is no DKIM key at the selector you named. The lookup for <selector>._domainkey.<your domain> found no record, or found a record that isn't a DKIM key.

Why it matters

If your mail is signed with this selector, every signature fails, because receivers can't find the key to check it against. DMARC then relies on SPF alone, and forwarded mail fails DMARC. If the selector was a guess, it is simply the wrong name.

How to fix it

  1. Check the selector's spelling: look at the s= tag in the DKIM-Signature header of a message you sent.
  2. Look in your mail provider's DKIM settings for the record to publish, and make sure the name matches exactly. Some DNS hosts add your domain to the name automatically, which can double it.
  3. If the provider gives a CNAME instead of a TXT record, publish the CNAME exactly as shown.

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.