DKIM checker

This DKIM checker looks up the DKIM record of a domain, confirms a public key is published and reports whether it is 1024 or 2048 bits. Enter a domain, add your selector if you know it, and check it now.

Leave the selector empty to try 35 common ones. Reads public DNS only. Nothing is stored.

Example result

This is a sample. Enter a domain above to see its own record.

1024-bit key on selector k1

  • Warning

    DKIM: 1024-bit key on selector k1

    The key works, but 2048-bit is the current standard. Rotate to a 2048-bit key.

    k1._domainkey  v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC...

One record is one of six checks. The full test also reads MX, the other two authentication records, MTA-STS and BIMI.

Run the full test

What does a DKIM checker test?

A DKIM checker looks up the TXT record at selector._domainkey.yourdomain.com and tests the public key it finds against RFC 6376, the DKIM standard. DKIM (DomainKeys Identified Mail) adds a digital signature to every message, and the DNS record holds the public key that receivers use to verify it.

What the DKIM checker tests
TestPasses whenWhy it matters
Record existsA TXT record is published at the selectorWith no key, receivers cannot verify your signature and DKIM fails
Key is presentThe p= tag holds a keyAn empty p= means the key was revoked
Key lengthThe key is 2048 bits1024-bit keys still verify but are below the current standard

A DNS lookup proves the key is published. It cannot prove your mail is signed with it. To confirm signing, send yourself a message and read its headers, as described below.

What is a DKIM selector and how do you find yours?

A DKIM selector is a short name that tells the receiving server which key to fetch. One domain can publish many keys, one per sending service, and the selector picks between them. There is no way to list a domain's selectors from DNS, which is why this tool asks for one.

To find your selector:

  1. Send an email from the service you want to check to an address you can open.
  2. Open the message and view its full headers. In Gmail this is "Show original".
  3. Find the DKIM-Signature header.
  4. The value after s= is the selector. The value after d= is the signing domain.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=example.com; s=google; h=from:to:subject:date;
  bh=2jUSOH9NhtVGCQWNr9BrIAPreKQjO6Sn7XIkfJVOzv8=; b=AuUoFEfDxTDkHlLXSZEpZj79LICEps6eda7W3deTVFOk...

In this header the selector is google, so the key lives at google._domainkey.example.com.

Common DKIM selectors by platform, as of November 15, 2026
PlatformUsual selectors
Google Workspacegoogle
Microsoft 365selector1, selector2
Mailchimpk1, k2, k3
SendGrids1, s2
Klaviyokl, kl2
HubSpoths1, hs2
Postmarkpm

Platforms change their defaults and many let you choose your own, so the header of a real message is the reliable source.

How do you read a DKIM record?

A DKIM record is a short list of tags followed by a long public key. A typical record looks like this, with the key shortened:

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
DKIM record tags
TagMeaning
v=DKIM1Version. Recommended, and must come first when present
k=rsaKey type. RSA is the default
p=The public key, base64 encoded. Required
t=yTest mode. Receivers should not treat failures as final

Should a DKIM key be 1024 or 2048 bits?

A DKIM key should be 2048 bits. RFC 8301 requires signers to use at least 1024 bits and says they should use at least 2048. A 1024-bit key still verifies today, but it is the weaker choice and some receivers score it lower.

Rotating to a 2048-bit key takes three steps: generate the new key in your sending platform, publish it under a new selector, then switch signing to that selector and remove the old record after a week. A 2048-bit key is longer than 255 characters, so DNS stores it as two quoted strings. That is normal and receivers join them.

Why does DKIM fail when the record is correct?

DKIM fails with a correct record when the message was changed after signing, or when the signing domain does not match your From domain. The three causes we see most:

  • Content changed in transit. A mailing list or security gateway that rewrites the subject or adds a footer breaks the signature.
  • The platform signs with its own domain. The message passes DKIM for the platform's domain, which does not align with yours, so DMARC still fails. Set up custom domain signing in the platform.
  • The key was pasted wrong. A missing character or a line break inside the key at the DNS host makes every signature fail.

DKIM is one of the two checks DMARC relies on. Test the others with the SPF record checker and the DMARC checker, or run the full email deliverability test. If signatures keep failing and mail is landing in spam, see what our email deliverability audit covers.