Enable DKIM signing
Publish your provider's signing key so your mail carries a verifiable signature.
20 min
why this matters
DKIM survives forwarding, which SPF does not. Unsigned mail is far more likely to be filtered, and DMARC needs DKIM to pass reliably.
Step by step
- 1
Generate the key in your email provider
In Google Workspace this is Apps → Google Workspace → Gmail → Authenticate email. In Microsoft 365 it is the Defender portal's DKIM page. Marketing platforms have a domain authentication screen. Ask for a 2048-bit key.
- 2
Publish the record they give you
It is a TXT or CNAME record on a selector subdomain. Copy the value exactly — a single missing character breaks the signature.
Type: TXT Name: google._domainkey Value: v=DKIM1; k=rsa; p=MIIBIjANBgkq... - 3
Turn on signing
Publishing the key does nothing until you click 'Start authenticating' or the equivalent in the provider. DNS needs up to an hour to propagate first.
- 4
Repeat for every sending service
Each platform gets its own selector. Do your marketing tool, helpdesk and invoicing system too, not just your mailbox provider.
how to check it worked
- Show original in Gmail reports dkim=pass
- The signing domain in the header matches your domain
related guides
Publish an SPF record
Tell mailbox providers which servers are allowed to send email as your domain.
Merge multiple SPF records into one
Two SPF records is a permanent failure — combine them.
Set your SPF enforcement correctly
Replace +all or a missing all mechanism with -all.
Get SPF back under the 10-lookup limit
Flatten or consolidate includes so SPF stops returning permerror.