d= and s= in the header
d= is the signing domain and s= is the selector. Here the key would be looked up at selector1._domainkey.example.com. Open a message the domain sent and read its DKIM-Signature header, or use the Email Header Analyzer.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Check your domain's DKIM public key using its selector. Review the published DNS key record, reported key details, and common configuration problems. Don't know your selector? Try a limited search of common names.
Example: DKIM record found
Use the signing domain (d=) and the selector (s=) your provider gave you, or copy both from a DKIM-Signature header.
DNS path, public key and key health.
Correct the selector or the key, then check again.
A DKIM key is published at selector._domainkey.domain, so you need both values. Illustrative header excerpt:
d= is the signing domain and s= is the selector. Here the key would be looked up at selector1._domainkey.example.com. Open a message the domain sent and read its DKIM-Signature header, or use the Email Header Analyzer.
With the selector blank, the checker tries a limited list of common names. It cannot find every custom selector, and no match does not mean a domain has no DKIM.
Some providers ask you to publish the key as a TXT record. Others ask for a CNAME at the selector name that points to a key they host. Use exactly the values your provider shows, and never guess a target.
Google Workspace generates the key in the Admin console, which shows the selector and TXT value to publish. Microsoft 365 asks for two CNAME records, selector1 and selector2, whose targets are shown in the Microsoft Defender portal. Confirm details in each provider's current documentation.
How selector._domainkey.domain is built and resolved.
Is there a non-empty p= value?
The DNS answer for the selector, as the check returns it.
Key type from the record. Key length shows Not reported unless the check supplies it.
The record exactly as published.
What each result means.
A DKIM record is a short list of tags. The p= tag holds the public key. For RSA, 1024 bits is the current minimum and 2048 bits is recommended where your provider supports it, so a 1024-bit key is not automatically invalid. Ed25519 is also a standardized DKIM algorithm, but this page does not fully validate Ed25519 keys.
| Tag | Meaning | What to look for |
|---|---|---|
| v=DKIM1 | Version of the record | Recommended but optional. DKIM1 is the default |
| k= | Key type, usually rsa | rsa is the default if omitted. ed25519 is also defined |
| p= | The public key | Required. An empty p= means the key is revoked |
| t= | Optional flags | t=y indicates testing mode |
The key lives at the selector your provider uses. A typo looks like a missing key.
The domain in the lookup must match the domain that signs the message.
An empty p= tag means the key was revoked.
A pasted key that is split or truncated will not validate.
DKIM can pass while DMARC fails if the signing domain does not align with From.
Messages already in flight may still be verified against the old key.
The checker reads what is published in DNS. It does not prove that messages are signed or that a signature verifies, because that happens per message at the receiving server. DMARC alignment is a separate test of whether the signing domain matches the From domain; use the DMARC Checker for policy and SPF Checker for the other half of authentication. To confirm signing, inspect the DKIM-Signature and Authentication-Results headers of a received message with the Email Header Analyzer.
Confirm the selector your provider asked you to publish.
Check old and new selectors side by side.
Rule out DNS before you investigate message signing.
A DKIM checker looks up the public key a domain publishes for a selector and reports whether the record is present and well formed. It reads DNS only and does not check the signature on any message.
A selector is a label that points to one DKIM key. It lets a domain publish several keys, for example one per provider.
Your email provider's setup page shows it, and the DKIM-Signature header of a sent message includes it as s=, next to the signing domain in d=. Auto-detect only tries a limited list of common selectors, so it cannot find every custom one.
Yes. Many providers publish the key themselves and ask you to add a CNAME at the selector name. This checker does not display CNAME targets or delegation chains, so use your provider instructions to confirm the CNAME value.
The key has been revoked, so receivers will not accept signatures made with it.
2048-bit RSA is recommended where your provider supports it. 1024 bits is the current minimum, so a 1024-bit key is not automatically invalid. Key size alone does not decide how mail is delivered.
Yes. Ed25519 is a standardized DKIM algorithm, but provider and receiver support varies, and this checker does not fully validate Ed25519 keys.
DMARC also requires alignment. If the DKIM signing domain does not match the From domain, DMARC can fail even though DKIM passes.
A verifying signature shows the signed parts of a message were not altered, which helps receivers trust it. It does not guarantee inbox placement, which also depends on reputation, content and list quality.
Rotate keys on a regular schedule and after any suspected exposure, and keep the old selector published until in-flight mail has cleared.
Open a message your domain sent and read the s= value in its DKIM-Signature header, or check your email provider setup page. You can also leave the selector blank and use auto-detect, which tries a limited list of common names and may find nothing.
No. A published key only shows the DNS side is in place. Whether messages are signed, and whether a signature verifies, is decided per message, so inspect the headers of a received email to confirm.
Only p= is required. v=DKIM1 is recommended but optional, and k= defaults to rsa when omitted. An empty p= means the key is revoked, and t=y marks the domain as testing DKIM.
A TXT record holds the key itself. A CNAME at the selector name points to a record your provider hosts, which lets them rotate keys. Use the exact record type and value your provider gives you.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.