What the DKIM checker tests
DKIM lets a receiving server confirm that a message was signed by the domain it claims to come from and was not changed on the way. The signature is checked against a public key in your DNS. If that key is missing or damaged, every signature fails, however correct the sending side is. This tool looks up the TXT record at selector._domainkey.yourdomain.com and checks it the way a receiver would:
- Record exists. No record at that name means receivers cannot verify mail signed with this selector.
- Exactly one record. Two TXT records under the same selector leave the result undefined, so receivers may fail the signature.
- Tags. The checker parses every tag defined in RFC 6376:
v(version),k(key type),p(public key),t(flags),h(hash algorithms),s(service type) andn(notes). - Key validity and size. The
p=value must be valid base64. For RSA keys the checker decodes the key and reads the real modulus length instead of guessing from the length of the text. - Revoked keys and testing mode. An empty
p=means the key was withdrawn, andt=ytells receivers the domain is only testing DKIM.
How to find your DKIM selector
Unlike SPF and DMARC, a DKIM record has no fixed address. Each sending service chooses its own selector name, and DNS offers no way to list the selectors a domain uses. The reliable way to find yours is to read it from a message:
- Send an email from the domain to a mailbox you control.
- Open the raw message headers (in Gmail, "Show original"). Our guide on how to read email headers shows where to find them in other mail clients.
- Find the
DKIM-Signatureheader. Thes=tag is the selector and thed=tag is the signing domain.
DKIM-Signature: v=1; a=rsa-sha256; d=example.com; s=selector1; ...For this header you would enter example.com and selector1. You can also paste the headers into the email header analyzer, which shows the DKIM result for you.
The buttons under the form fill in selector names that are in wide use, such as google, selector1 and k1. They are guesses. If a guess returns no record, it only means that name is not in use, not that the domain has no DKIM. A message with several DKIM-Signature headers has several selectors, so check each one.
How to read the result
A typical DKIM record looks like this, with the key shortened:
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...v=DKIM1is the version. It is optional, but if present it must be the first tag.k=rsais the key type. RSA is the default when the tag is missing. The other type ised25519(RFC 8463), which not every receiver verifies yet.p=is the public key in base64. Long keys are stored in DNS as several quoted strings; the checker joins them the way receivers do.
Key size
RFC 8301 says signers should use RSA keys of at least 2048 bits and that receivers must not accept keys shorter than 1024 bits. The checker therefore passes 2048 bits and above, warns on 1024 bits and fails anything smaller.
Revoked key
An empty p= is a deliberate signal that the key has been revoked. It is normal for an old selector after a key rotation. If your current mail still uses that selector, publish the new public key from your email provider.
Invalid base64 or not a public key
The key was damaged when it was pasted into DNS: a missing piece, a stray quote or a line break. Copy the full value from your provider again. If your DNS host limits a TXT string to 255 characters, split the key into several strings inside the same record, not into separate records.
No record found
Check the selector spelling and the domain first. Some providers ask you to publish a CNAME instead of a TXT record; the checker follows it, so a miss here means the target has no key either.
DKIM is one of three checks
A valid key is only part of the picture. DMARC also needs the signing domain to align with your From address, and SPF covers the sending servers. The guide What is DKIM? explains signing and alignment, and the SPF checker and DMARC checker test the other two records. Authentication proves the mail is yours. Whether it reaches the inbox also depends on your bounce rate, so verify your list before you send.