DKIM signature not found
"DKIM signature not found" usually means the message wasn't signed at all. Receivers record that as dkim=none. If there is a signature but the receiver can't find the public key at the selector it names, that's a different problem: the DKIM record isn't in DNS where the signature says it is, and verification fails. And if a checker tells you "a DKIM record does not exist for this domain," it may simply have looked under the wrong selector. Work out which of the three you have before you touch DNS, because the fixes don't overlap.
Three problems that look alike
| What you see | What it means | Where to fix it |
|---|---|---|
dkim=none in Authentication-Results, or "no DKIM signature" in a report |
The message carried no DKIM signature | The sending platform: signing isn't turned on |
dkim=permerror or dkim=fail with a reason like "no key" |
A signature exists, but there's no key at <selector>._domainkey.<domain> |
DNS: the record is missing, misnamed, or not visible yet |
| A checker says "a DKIM record does not exist for this domain" | The checker didn't find a key at the selector it tried | Possibly nothing: find your real selector and check again |
dkim=none: the message isn't signed
The DKIM result none means the message was not signed. There's no key lookup involved, so publishing or republishing a DNS record won't change it. Something on the sending side has to start signing.
Microsoft's troubleshooting page lists dkim=none (no signature found) with the cause "DKIM signing isn't configured for the sending domain, or the message wasn't signed". Typical cases:
- Microsoft 365 custom domains. Microsoft's DKIM page currently says: "Currently, no DKIM signing occurs for outbound mail from custom domains" (as fetched 12 Nov 2026). You configure DKIM for each custom domain, and "each subdomain you use to send email from Microsoft 365 requires its own DKIM configuration". Setup is in DMARC for Microsoft 365.
- Google Workspace with the key published but signing never started. Publishing the key is only half the job. You go back to the Admin console and click Start authentication (DMARC for Google Workspace).
- Apps, devices, and relays that send directly. A scanner, CRM plugin, or on-premises relay that hands mail to the internet itself won't sign unless you set it up to. Your aggregate reports show these as sources with no DKIM result (How to inventory sending sources).
A related case isn't "not found" at all: a vendor that signs with its own domain, say d=vendor.example, produces a valid signature that simply doesn't align with your From domain. That's covered in Third-party mail fails alignment.
What dkim=none does to DMARC
On its own, nothing final. DMARC passes on an aligned SPF pass or an aligned DKIM pass, so unsigned mail can still pass on SPF. But that leaves you depending on SPF alone, which breaks when mail is forwarded. And domains that publish p=reject must apply valid DKIM signatures. Fix unsigned streams before you tighten policy.
DKIM record not found: the key isn't where the signature says
When a message is signed, the DKIM-Signature header names a selector (s=) and a signing domain (d=). The receiver looks up exactly one name:
<s=>._domainkey.<d=>
For s=mail2026 and d=example.com, that's mail2026._domainkey.example.com. If nothing is published there, verification fails immediately with no key for the signature. It's usually reported as dkim=permerror or dkim=fail, depending on the receiver. If the DNS query times out instead, that's a temporary failure (key unavailable), not a missing key.
Common reasons the record isn't found:
- The host name was doubled. Many DNS hosts append the zone automatically. Microsoft's example: enter
selector1._domainkey.contoso.comin acontoso.comzone and "the actual record becomesselector1._domainkey.contoso.com.contoso.com." Enter onlyselector1._domainkey. - Wrong zone or wrong DNS host. The record went into a DNS provider or zone that isn't the one the world actually queries for that domain.
- A selector typo. The name in DNS has to match
s=character for character (DKIM selectors and DNS records). - The key was removed too early during a rotation, while mail signed with that selector was still in transit (How to rotate a DKIM key).
- DNS isn't visible yet. "after adding a DKIM key, it can take up to 48 hours for DKIM authentication to start working."
A record with an empty p= is a different signal. That's a revoked key, and there's no meaningful difference between a key that has been revoked and a key record that has been removed. Either way, mail signed with that selector won't verify.
If the record is found but the key is damaged, you'll see a syntax error rather than "no key." The usual cause is a 2048-bit key cut off by the 255-character TXT string limit, or split strings stored out of order. Google's fix is to split the key into multiple quoted strings in one TXT record and compare the result with the value in the Admin console (1024-bit vs 2048-bit DKIM keys). Other verification failures, such as "body hash did not verify," are in Why DKIM signatures fail.
Microsoft 365: CnameMissing
In Microsoft 365, the missing-record symptom usually shows up before any mail is sent. The DKIM toggle won't turn on and the status stays CnameMissing. Before keys exist, the status reads No DKIM keys saved for this domain. Microsoft's troubleshooting section lists the causes:
- The host name doubled, or missing the
_domainkeypart. - A TXT record holding a key instead of a CNAME. Managing keys yourself in TXT "isn't supported for Microsoft 365."
- A CNAME target that doesn't match what Microsoft generated, for example dots left in the domain, the wrong initial-domain prefix, or the dynamic partition character missing. Copy the exact values from the Defender portal or
Get-DkimSigningConfig.
Microsoft also requires both selector1 and selector2 CNAMEs. A missing selector2 doesn't always block the toggle, but key rotation fails later. More Microsoft 365 and Google Workspace symptoms are in Microsoft 365 or Google Workspace setup issues.
"A DKIM record does not exist for this domain"
That's checker wording, and it's misleading. DKIM has no single record per domain. Keys live under selectors, so example.com can have google._domainkey, selector1._domainkey, and a vendor's selector all at once. A checker that guesses a selector and finds nothing reports "not found," even when DKIM is working fine.
To check properly:
- Open a message you sent, as received, and find the
DKIM-Signatureheader. The selector is thes=value, and Microsoft points to the same place: "The selector… is stored in the s= value." - Look up
<that selector>._domainkey.<d= domain>in DNS, or give the checker the selector explicitly. - If the key is there and the received message shows
dkim=pass, DKIM is fine. The checker guessed wrong.
Some defaults help. Google's default prefix selector is google, and Microsoft 365 uses selector1 and selector2. Third-party senders use their own names, which you'll find in their setup screens or in your reports.
Parked domains are supposed to have no DKIM record
For domains you don't send from, "no DKIM record" is the right answer. Don't publish DKIM records for those domains. Lock them down with DMARC p=reject and SPF v=spf1 -all instead (Common SPF mistakes).
How to check, in order
- Get a received copy of a real message and read
Authentication-Results. dkim=none? Look at the sending platform. Is signing turned on for this domain and subdomain? Is this a source you didn't know sent mail?- No key, or permerror? Take
s=andd=from the signature and query<s>._domainkey.<d>from outside your network. Compare the host name and value with what your provider gave you. - Syntax error? Check for a truncated or out-of-order key.
- Only a checker complains? Re-run it with the selector from step 3.
- Just published? Give DNS time. Google allows up to 48 hours.
Mistakes worth avoiding
- Republishing DNS to fix
dkim=none. Unsigned mail doesn't look up a key. - Trusting a checker's "not found" without giving it your selector.
- Pasting the full host name into a DNS form that appends the zone.
- Creating only
selector1in Microsoft 365. - Publishing the Microsoft 365 key as TXT. Microsoft 365 needs CNAMEs.
- Deleting an old selector the day you rotate.
- Regenerating the Google key when the first one hasn't had time to propagate. Google also says DKIM may already be set up by default, or if you bought the domain from a Google partner, so check what's there first.
Free DMARC account
Not sure which sender is failing?
Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.
- Every sending source in one dashboard
- SPF, DKIM and alignment results per sender
- No XML files to read
FAQ
What does dkim=none mean?
The message wasn't signed with DKIM. It's a sending-side setting, not a DNS problem.
The checker says no DKIM record exists, but my mail passes DKIM. Why?
The checker probably tried the wrong selector. Use the s= value from a real message.
Microsoft 365 says CnameMissing. What's wrong?
Usually a doubled host name, a TXT record instead of a CNAME, a CNAME target that doesn't match Microsoft's value, or DNS that hasn't propagated yet.
Should parked domains have DKIM records?
No. Not to publish them. Use DMARC and SPF to say the domain sends no mail.