DKIM Checker
Enter a domain and a DKIM selector to check the public key that receivers use to verify your email signatures.
What this tool checks
DKIM (DomainKeys Identified Mail, RFC 6376) lets a sending server add a cryptographic signature to each message. The receiving server looks up the sender’s public key in DNS and verifies the signature. A valid signature proves that the message was authorised by the signing domain and that the signed headers and body were not changed in transit.
Public keys are published as TXT records at:
<selector>._domainkey.<domain>
The selector is a label chosen by the sender, so a domain can have several keys at once: one per service, or an old and a new one during rotation.
Given a domain and a selector, the checker looks up that record and reports:
- whether a key exists at that name;
- the key type (
rsaored25519) and, for RSA, its length in bits; - whether the key has been revoked (an empty
p=tag); - syntax problems, such as a missing
v=DKIM1or a truncated key.
Without a selector, the email checker shows an information notice instead of a DKIM result.
Finding the selector
The selector is in the DKIM-Signature header of every signed message. A shortened example:
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com; s=s1;
h=from:to:subject:date; bh=...; b=...
Here d=example.com is the signing domain and s=s1 is the selector, so the key is at s1._domainkey.example.com. A message can carry several DKIM-Signature headers, for example one from your domain and one from your email provider’s own domain; check the one whose d= matches your From domain, because that is the one DMARC uses.
Some email providers use fixed selector names that appear in their setup instructions, and some publish the key for you through a CNAME pointing to their own DNS. The checker follows such CNAMEs automatically.
How to read the result
| Tag | Example | Meaning |
|---|---|---|
v |
DKIM1 |
Version. Recommended; must be first if present. |
k |
rsa |
Key type: rsa (default) or ed25519. |
p |
MIIBIjANBg... |
The public key in base64. Empty means revoked. |
t |
y |
Flags: y means the domain is testing DKIM; s restricts the key to the exact domain, not subdomains. |
h |
sha256 |
Acceptable hash algorithms (optional). |
As a guide to key length:
- Under 1024 bits: error. Many receivers ignore such keys.
- 1024 bits: warning. Still accepted, but upgrading to 2048 bits is advisable.
- 2048 bits or more: OK.
Common problems and fixes
- No record at the selector. The selector is misspelt, DKIM is not yet enabled at your provider, or the record was created on the wrong name (for example
s1._domainkey.example.com.example.com). Enable DKIM in your provider’s admin panel and copy the record exactly. - Truncated key. RSA keys of 2048 bits are longer than the 255-byte limit of a single TXT string. If your DNS panel cut the value instead of splitting it into several strings, the key is broken. Re-enter it, or ask your provider for a CNAME-based setup.
- Spaces or line breaks inside
p=. Copying from a web page sometimes inserts them. Remove them. - DKIM passes but DMARC fails. The signature’s
d=domain belongs to your provider, not to you. Configure the provider to sign with your own domain, so that it aligns with the From address. See the DMARC checker. - Test flag left on.
t=yasks receivers to treat failures leniently. Remove it once DKIM works.
Related
- Email checker: DKIM together with MX, SPF, DMARC, MTA-STS, TLS-RPT and BIMI.
- SPF checker: the other authentication method DMARC relies on.
- TXT record guide: how long values are split into strings.
Frequently asked questions
How do I find my DKIM selector?
Open an email sent from your domain and view its full headers (often called 'Show original' or 'View source'). Find the DKIM-Signature header: s= is the selector and d= is the signing domain. For example, s=s1; d=example.com means the key is at s1._domainkey.example.com.
Can you find my selector automatically?
No. DNS offers no way to list all the names in a zone, so a selector can only be found if you already know it. Guessing common names is unreliable, so we ask you to enter it.
What key length should I use?
RSA keys of 2048 bits are the common recommendation. RFC 8301 requires at least 1024 bits, and many receivers treat shorter keys as invalid. Ed25519 keys (RFC 8463) are shorter and strong, but not every receiver supports them yet, so they are usually published alongside an RSA key.
Can a domain have more than one DKIM key?
Yes. Each selector is a separate key, so each sending service can have its own, and you can rotate keys by publishing a new selector before retiring the old one.