Fail

Your DKIM key is too short to trust

The short version

Create a 2048-bit key with your mail provider and publish it.

What it means

The DKIM key published at this selector is an RSA key shorter than 1024 bits. Keys this short can be broken with ordinary computing power, and the current standard tells receivers not to trust them.

Why it matters

Receivers ignore signatures made with keys under 1024 bits, so your mail is treated as unsigned and DMARC has only SPF to go on. Worse, someone who breaks the key could sign forged mail that passes as yours.

How to fix it

  1. In your mail provider's DKIM settings, generate a new 2048-bit key. Use a new selector name if the provider allows it, so the old and new keys can live side by side.
  2. Publish the new key and switch signing to it.
  3. After a few days, remove the old short key, or replace its value with v=DKIM1; p= to mark it revoked.

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. The key should show as 2048-bit RSA.