// how to fix
No DKIM signature on your emails
DKIM adds a digital signature that proves an email really comes from your domain. Turn it on in your email provider and publish its key in DNS.
What it means
DKIM (DomainKeys Identified Mail) adds an invisible digital signature to every email you send. Receivers check it with a public key published in your DNS. If it matches, they know the email really comes from your domain and was not changed on the way.
Your test email arrived with no DKIM signature at all.
Why it matters
- Gmail and Yahoo require DKIM for bulk senders, and strongly prefer it for everyone.
- DKIM survives forwarding, unlike SPF. It is often what makes DMARC pass.
- Without it, your emails look less trustworthy and are more likely to go to spam.
How to check
Delivmail checks this for you in two ways:
- Send a test email: on the home page, copy your unique test address, send it a normal email from the mailbox you want to check, then open the report. The DKIM line says "not signed" when no signature is found.
- Use the Domain scanner: type your domain at
/domain-scannerto read your DNS records without sending anything.
The Domain scanner looks for DKIM keys on the usual names (called "selectors"), like google, selector1 or default. A key can be published while signing is still switched off, so the test email is the real proof.
How to fix it
DKIM is always a two-part job: turn on signing in the service that sends your emails, and publish the public key in your DNS.
Google Workspace
- In the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email.
- Generate a new record (choose 2048-bit if your DNS provider accepts long values).
- Add the TXT record it shows, with the name
google._domainkey. - Wait until it is visible, then click Start authentication.
google._domainkey.yourdomain.com TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh...(long key)..."
Microsoft 365
- In the Microsoft Defender portal, open Email authentication settings, then DKIM.
- Select your domain. Microsoft shows two CNAME records,
selector1._domainkeyandselector2._domainkey. - Add both CNAME records at your DNS provider, exactly as shown.
- Come back and switch on "Sign messages for this domain with DKIM signatures".
selector1._domainkey.yourdomain.com CNAME (value shown by Microsoft) selector2._domainkey.yourdomain.com CNAME (value shown by Microsoft)
Web hosts, newsletter tools and other services
Look for a setting called "DKIM", "domain authentication" or "authenticate your domain". The service gives you one or more records (TXT or CNAME) to copy into your DNS. Every service that sends email in your name needs its own DKIM setup.
Common mistakes
- Some DNS providers add your domain automatically. If you type
google._domainkey.yourdomain.comas the name, it can becomegoogle._domainkey.yourdomain.com.yourdomain.com. Type onlygoogle._domainkey. - Long keys can get cut or broken by extra spaces when copied. Paste the value in one go.
- Publishing the key is not enough: signing must also be switched on.
Check that it is fixed
DNS changes are not instant. Most are visible within a few minutes, but some providers take up to 24 to 48 hours.
Run the Domain scanner to see the key, then send a new test email from the home page. The report should show a valid DKIM signature from your own domain.
Provider help: Google Workspace DKIM and Microsoft 365 DKIM.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- No SPF record on your domainYour domain does not say which servers may send email for it. Add one TXT record and receivers can tell your real emails from fakes.
- SPF error: too many DNS lookups (permerror)SPF allows at most 10 DNS lookups. Above that, the whole record breaks and receivers treat it as invalid. Here is how to slim it down.
- Several SPF records on one domainA domain must have only one SPF record. With two or more, SPF breaks for every email. Merge them into a single line.
- SPF fails: the sending server is not authorizedYour domain has an SPF record, but the server that sent your email is not in it. Find which service sent the email and add it.
- DKIM signature fails (invalid signature or body hash)Your email is signed, but the signature does not check out. Usually the DNS key is wrong, or something changed the email after it was signed.