DKIM breaks quietly. A wrong selector, a trimmed key or a leftover test flag all look the same from the outside. This page shows how to check a DKIM record and read what comes back.
Key facts:
- A DKIM public key lives in a TXT record at
selector._domainkey.domain(RFC 6376). - The selector is the
s=tag and the signing domain is thed=tag in a message’s DKIM-Signature header (RFC 6376). - An empty
p=tag means the key was revoked, andt=ymeans the domain is testing DKIM (RFC 6376). - RFC 8301 sets 1024 bits as the minimum for RSA signing keys.
- Per the BillionVerify DKIM Checker, you must supply both domain and selector, and the tool does not search for selectors.
How to check a DKIM record
You need two values, and the tool cannot guess them.
- Send a message to a mailbox you control and open its full headers.
- Find the
DKIM-Signatureheader. Copy thed=value as the domain and thes=value as the selector. - Enter both in the checker and run it.
Use the d= domain, not the visible From domain. They differ whenever a service signs for you.
What the DKIM result tells you
The record and a key line
The tool prints the full TXT value and a line such as the key type with its bit length. RSA is the default type when the record has no k= tag. If the length is short, ask your provider to rotate to a longer key. Many senders choose 2048 bits.
Key type with no bit length
The tool could not parse the public key, so it shows only the type. A key cut off during a copy and paste is the usual cause. Compare the p= value with what your provider issued, then publish it again.
The testing flag
A line saying the testing flag is on means the record carries t=y. The domain is announcing that DKIM is still in test. Remove the tag once signing works, so receivers treat the signatures as live.
Revoked key
An empty p= tag reads as a revoked key. This is correct only if you retired that selector on purpose. If mail still signs with it, publish the key again or point your sender at a current selector.
No record found
The selector is wrong, the record sits on a different name, or it was never published. Check the s= tag against the header again. Providers that use CNAME records for DKIM still need those CNAMEs in place.
What this check does not cover
It confirms a key is published. It does not prove that a particular message was signed or that its signature verified. For that, read the authentication results in the message headers.
A valid key does not fix bad recipients. If signed mail still bounces, test the addresses themselves. You can try single addresses at billionverify.com, with 20 free full checks per IP every 24 hours and no sign-up.
What to check next
Move on to DMARC. It needs DKIM or SPF to pass and align with your From domain. When you want to be sure a recipient exists, verify a mailbox over SMTP before you resend.