emailsecuritygrade.com

DKIM Record Checker: How to Verify Your DKIM Setup Is Actually Working

November 5, 2026

Running your domain through a DKIM record checker and seeing a green "valid" result tells you one thing: a TXT record exists at that selector and its syntax parses. It does not tell you whether your mail server is actually signing outgoing messages with the matching private key, or whether that signature survives to the inbox. Those are two different checks, and mixing them up is why DKIM looks "fixed" in a lookup tool while mail still fails authentication in production.

Key facts

  • A DKIM TXT record lives at <selector>._domainkey.yourdomain.com and must contain a v=DKIM1 tag plus a p= public key value; a checker validates this syntax, not live signing.
  • The selector (the string before ._domainkey) is chosen by your sending platform — common examples are google._domainkey (Google Workspace), selector1/selector2 (Microsoft 365), and custom values for ESPs like SendGrid or Mailchimp.
  • You can confirm real signing only by reading the DKIM-Signature header on a message you actually sent — the d= tag shows the signing domain and the s= tag shows the selector used.
  • RFC 6376 defines DKIM; a record can be 100% RFC-valid and still fail in practice if the selector in your DNS doesn't match the selector your sending platform signs with.
  • Multiple DKIM selectors can coexist on one domain — normal when you send from more than one platform — as long as each selector name is unique and each has its own correctly published key.
  • A DKIM pass alone doesn't guarantee DMARC alignment; DMARC also checks that the domain in the d= tag matches your visible From-header domain.

What a DKIM record checker actually verifies

Paste your domain and selector into any DKIM lookup tool and it runs a DNS query against <selector>._domainkey.yourdomain.com, then checks the TXT value it gets back for three things:

  1. The record exists — something is published at that exact selector.
  2. The v=DKIM1 tag is present — marks it as a DKIM record, not just any TXT entry.
  3. The p= value is a well-formed public key — not truncated, not malformed base64.

That's the full scope. The checker never sends an email, never sees your mail server's signing configuration, and never confirms the private key on your sending platform actually matches the public key you published. It's a syntax and existence check — necessary, but not sufficient.

Where DKIM actually breaks in practice

Three failure patterns account for most "my checker says pass but mail fails" reports:

Selector mismatch. You publish a record at selector1._domainkey because that's what one setup guide told you, but your sending platform is actually signing with selector2 (or a custom selector tied to your account). The checker finds nothing wrong with the record you published — it just isn't the one being used.

Right record, wrong platform. You migrated from one email provider to another and never removed the old provider's DKIM record or added the new one. Mail now goes out through the new platform, but DNS still only has a key for the old one.

Key rotation gap. Some platforms rotate DKIM keys periodically. If DNS isn't updated to match the new key, signatures start failing verification even though a valid-looking (but now outdated) record is still published.

How to actually confirm DKIM is signing your mail

A record checker is step one, not the whole process. To confirm DKIM is live on real mail:

  1. Send a test email to an address you control (Gmail works well for this).
  2. Open the raw message headers (in Gmail: "Show original").
  3. Find the DKIM-Signature header and read the d= tag (signing domain) and s= tag (selector used).
  4. Compare the s= value to the selector you published in DNS — they must match exactly.
  5. Check the authentication results — Gmail and most providers add an Authentication-Results header showing dkim=pass or dkim=fail for that specific message.

If the selector in step 4 doesn't match what's in your DNS, you've found the problem — the TXT record you checked isn't the one your mail is signed with.

A broader SPF, DKIM & DMARC checker is the faster way to catch this: it checks all three records together and flags a selector or alignment mismatch in the same pass, instead of you manually diffing header values against DNS.

Check your grade free

Don't guess what's broken — see it. Scan your domain free at emailsecuritygrade.com and get an instant A-F grade on your SPF, DKIM, DMARC, and MX records, with a plain-language fix for anything failing. No signup, no install — it runs in your browser.

If your emails are still landing in spam after fixing the records, a deliverability tool like InboxAlly can train mailbox providers to trust your sending — worth a look once your grade is solid.

Fixed your records? Now fix deliverability.

Correcting SPF, DKIM, and DMARC is step one — but inbox providers don't trust a domain overnight. InboxAlly trains Gmail, Outlook, and Yahoo to trust your sending domain by generating real engagement signals, so your emails stop landing in spam within weeks instead of months. Most users see open rates double in 2–4 weeks.

Start free with InboxAlly →