What it means
The DKIM record limits signatures to SHA-1 with the tag h=sha1. SHA-1 is an old hash algorithm that the current DKIM standard tells signers not to use and receivers not to trust.
Why it matters
Receivers increasingly treat SHA-1 signatures as invalid, so your mail may be counted as unsigned. Limiting the key to SHA-1 also stops your provider from moving to SHA-256 with the same key.
How to fix it
- Check your mail provider's current DKIM setup; modern providers sign with SHA-256.
- Remove the
h=tag from the record, or change it toh=sha256. Without the tag any algorithm is allowed. - If the provider still signs with SHA-1, generate a new key in its settings; current keys default to SHA-256.
- Update the 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.