Fail

A DKIM record can't be read

The short version

Publish the record exactly as your mail provider gives it.

What it means

A DKIM record was found but can't be read as a key. The usual causes are a key cut short when it was pasted, quotes or spaces inside the base64 key, a record split in the wrong place, or a k= tag naming a key type receivers don't support. The finding's detail names the problem.

Why it matters

Receivers can't check signatures against a key they can't read, so mail signed with this selector fails DKIM, and DMARC has to fall back on SPF.

How to fix it

  1. Copy the record again from your mail provider's DKIM settings, in full.
  2. Paste it as the TXT value without adding quotes yourself. If your DNS host needs long values split, let it do the splitting.
  3. Check the record with the DKIM record validator by pasting it before you publish.
  4. Replace the broken record at your DNS host.

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.