Skip to content
SpoofKiller
Free tool · no signup

Check that your DKIM key is published, intact, and long enough to matter.

Enter a domain and, if you know them, your selectors. The checker fetches each key, measures it, and flags the truncated, revoked, and undersized ones. With no selector it tries the names popular providers use.

What the checker examines

A signature is only as good as the key anyone can look up.

DKIM signs each message with a private key. Receivers verify it against the public half in your DNS. This tool inspects that public half.

Whether a key exists at the selector
The TXT record at selector._domainkey.yourdomain. If the name is a CNAME to your provider, the checker follows it and tells you where it leads, or that it leads nowhere.
Key type and length
RSA or Ed25519, and for RSA the actual modulus length read from the key data. Under 1024 bits is rejected by major receivers (RFC 8301). 2048 is the current recommendation.
Keys that cannot be parsed
A key cut short by a DNS host’s 255-character field, or with a stray space from a paste, is the most common DKIM fault there is. Common DKIM errors shows the repair.
Revoked and testing keys
An empty p= means the key was deliberately revoked. t=y means the selector is in testing mode, and verifiers may treat its signatures as if they were absent.
Common selectors, tried for you
Leave the selector blank and the checker tries a list of names typical for well-known mailbox and sending providers. It also detects wildcard records, which would otherwise answer for every name.
What it cannot know
DNS has no way to list a domain’s selectors. A blank result means “not at the names we tried.” The selector your mail really uses is in the s= tag of its signature; the header analyzer will read it out.
How to read the result

Valid, and aligned, are different words.

DKIM is the sturdier of the two authentication methods. SPF checks which server delivered a message, and so breaks the moment the message is forwarded. A DKIM signature travels with the message, and survives forwarding as long as nobody rewrites the signed parts. For a plain introduction, see what DKIM is.

A green result here means a usable key is published. It does not mean your mail is signed with it. That depends on the sending service being configured to sign, and to sign as your domain. Plenty of services sign every message with their own domain by default. Such a signature verifies perfectly and counts for nothing under DMARC, because DMARC wants the signing domain to match the From address. The remedy is always in the provider’s settings, under a name like “domain authentication” or “custom DKIM.”

So treat this tool as one of three. Confirm the key here; confirm the policy with the DMARC checker; then look at real traffic. Aggregate reports list the selector and signing domain for the mail receivers actually saw, which is how DKIM monitoring learns your selectors without guessing. Setup steps by provider are in the guides for Google Workspace and Microsoft 365.

Rows of keys hanging on a locksmith's board, with one bright yellow key among them.
The public key hangs on a board where anyone can see it. The check is whether it is the right one, and whole.
Common problems and fixes

The DKIM faults this checker finds.

  • No key at the selector you entered

    Check the spelling against the provider's setup page, and confirm the record was added under selector._domainkey, not at the root. Some DNS hosts append the domain automatically, producing a doubled name.

  • The key is truncated

    A 2048-bit key is longer than one 255-character DNS string. Your DNS host must split it into several quoted strings inside one TXT record. Re-copy the full value from the provider and paste it without line breaks.

  • A CNAME that points at nothing

    The selector is delegated to a provider, but the provider has not published the key. Finish (or restart) domain authentication in that provider's console, or remove the stale CNAME.

  • A 1024-bit key

    It still verifies. Rotate to 2048 bits when convenient: generate a new key at the provider, publish it under a new selector, switch signing over, then retire the old record.

  • t=y left on in production

    Testing mode tells verifiers they may ignore the signature. Remove the flag once you have seen signed mail pass.

  • The key is fine and DMARC still fails

    The service is signing with its own domain, or not signing at all. Enable custom-domain signing there. Alignment explained covers why a passing signature can still not count.

How to

How to check a DKIM record

Find your selector and verify the key behind it.

  1. 1

    Find the selector

    Open a message your domain sent, view its headers, and read the s= value in the DKIM-Signature header.

  2. 2

    Enter domain and selector

    Type the domain from the d= value and the selector. Several selectors can be separated by commas.

  3. 3

    Read the key details

    Confirm the key type, that the length is 1024 bits or more (preferably 2048), and that no testing or revoked flags are set.

  4. 4

    Fix and recheck

    Correct the DNS record or finish setup at the provider, wait for the TTL, and run the check again.

See all twelve free tools

FAQ

Questions about this tool

Straight answers. If yours is not here, ask us and a person will reply.

Ask a question

Free, no obligation

Cannot find your selector?

Tell us the domain and which services send your mail. We will tell you where each one keeps its DKIM settings and what to look for.

  • A person reads every message
  • No sales sequence, no list rental
  • Reply within one business day

We use your details to reply. Nothing else.

Your reports already know which selectors you use.

Create a free account, point your DMARC reports at it, and see the signing domains and selectors receivers observed, instead of guessing at names.