What a DKIM record is
DKIM adds a signature to every email you send. Receiving servers check that
signature against a public key you publish in DNS, which proves the message really came from your domain
and wasn't changed on the way. The key lives in a TXT record at
<selector>._domainkey.<your domain>, where the selector is a name your
mail provider chooses, such as google or selector1, so you can have several keys at once.
This validator reads one DKIM record and tells you exactly what it says: the key type and size, whether the key has been revoked, whether it is in testing mode, which hash algorithms it allows and which services it covers.
Two ways to check
Look up selector. Enter your domain and the selector. We ask DNS for that one record, follow any alias on the way, as Microsoft 365 uses, and check the key we find. If nothing is there, the result says so, which usually means a typo in the selector or a key your provider never asked you to publish.
Paste record. Paste the record text, for example from your provider's setup page before you publish it. Nothing is looked up. A pasted record is never refused as invalid input: whatever is wrong with it is listed as a finding with the fix.
What we check
- Key size. RSA keys under 1024 bits are too short to trust, and receivers ignore signatures made with them. 1024-bit keys still work but are the minimum; 2048 bits is today's normal size. Ed25519 keys are short by design and strong.
- Readability. A key cut short when pasted, quotes or spaces inside it, or an unknown key type make the record unreadable, so every signature fails.
- Revoked keys. An empty
p=tag means the key was withdrawn on purpose. That is fine for an old selector, but not for one your mail is still signed with. - Testing mode.
t=yasks receivers to treat failures leniently while you set things up. Remove it once signing works. - Hash algorithms.
h=sha1limits the key to SHA-1, which receivers no longer trust. - More than one record at the same selector, which makes results unpredictable.
When signing still fails
A valid key is only half the story. If DKIM fails although the record looks right, check that your
provider actually signs with this selector: the s= tag in the DKIM-Signature header of a sent message
shows which one it uses. Mailing lists and forwarding services that change the message body or subject
also break signatures; that is expected, and DMARC reports show where it happens.
Common mistakes when publishing a key
Most broken DKIM records come from copying. A DNS host's form may add your domain to the name you type, so
google._domainkey becomes google._domainkey.example.com.example.com. Long keys get cut off when a form
has a length limit, or pick up quotes and line breaks from an email or a PDF. Some hosts want the key split
into several quoted strings and others do the splitting themselves. Pasting the record here before you
publish catches all of these.
Rotating keys safely
Publish the new key under a new selector, switch your provider to it, wait a few days for mail in transit
to be delivered, then remove the old selector or revoke it with an empty p=. Checking each step here
takes seconds.
Reading the result
The result starts with a one-line verdict, then lists the facts we read from the record. Problems come below as findings, worst first, each with a short fix and a link to a step-by-step guide for the common mail providers. Nothing here is guessed: if the record can't be read, we say which part failed instead of showing partial facts.
The rest of your email setup
DKIM works together with SPF and DMARC. The full email check looks for DKIM keys at your provider's selectors and about 40 common ones, and grades the whole setup. To write the other records, use the SPF builder and the DMARC builder.