DKIM · DKIM_NOT_FOUND
DKIM record not found (DKIM_NOT_FOUND)
No DKIM public key was found for your domain’s selector. Learn how DKIM selectors work and how to turn on signing in Google Workspace or Microsoft 365.
What it means
No DKIM public key was found at <selector>._domainkey.<domain> for the selector that was checked, so receivers cannot verify a DKIM signature from this domain.
Why it matters for sending
DKIM lets receivers verify that a message was signed by your domain and not changed in transit. Google and Yahoo require SPF or DKIM for all senders and both for bulk senders, and DMARC alignment usually depends on DKIM.
How to fix it
- Turn on DKIM signing in your mail provider’s admin console (Google Admin → Gmail → Authenticate email, or the Microsoft Defender portal for Microsoft 365).
- Publish the record the provider gives you: a TXT record for Google (default selector google) or two CNAME records for Microsoft 365 (selector1 and selector2).
- Start signing in the provider after the record is live.
- Re-run the DKIM checker with the correct selector.
Example record
google._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBg..."Replace the values with your own domain and provider.
Frequently asked questions
What is a DKIM selector?
A selector is the label before ._domainkey that tells receivers which public key to use. Providers choose it, for example google for Google Workspace or selector1/selector2 for Microsoft 365.
Sources
This page is based on public standards and provider documentation, reviewed on 2026-09-25.
MailQV checks the domains of your connected mailboxes automatically.
When you connect a mailbox, MailQV checks SPF, DKIM, DMARC, MX and blocklist status and warns you before a campaign if something is wrong.
Start free