🔑 DKIM Lookup

Instantly retrieve and parse the DKIM (DomainKeys Identified Mail) record for any domain and selector. View version, key type, hash algorithm, public key, and validity — free, unlimited, browser-only.

Try: google.com / google   yahoo.com / s2048   protonmail.com / protonmail3
🕒 Recent Lookups
No recent lookups yet.

📚 What Is a DKIM Record?

DKIM (DomainKeys Identified Mail), defined in RFC 6376, is an email authentication method that adds a cryptographic signature to an outgoing message's headers. The signature is generated with a private key on the sending mail server and can be verified by any receiving server using the matching public key, which the domain publishes in DNS as a TXT record at selector._domainkey.domain.

Unlike SPF, which only checks the sending IP, DKIM proves two things at once: the message content and key headers were not altered in transit, and whoever signed it had access to the domain's private key — a strong signal of legitimacy that also survives forwarding, which breaks SPF.

⚙️ How DKIM Verification Works

1️⃣
Sign
The sending server hashes selected headers and the message body, then encrypts the hash with its private key, adding the result as a DKIM-Signature header.
2️⃣
Publish
The domain owner publishes the corresponding public key as a DNS TXT record at selector._domainkey.domain — this is exactly what this tool queries.
3️⃣
Receive
The receiving server reads the s= and d= tags from the DKIM-Signature header to know which selector and domain to look up.
4️⃣
Verify
It fetches the public key from DNS, decrypts the signature, and compares it against a fresh hash of the received message. A match means DKIM pass.

📋 DKIM Tag Reference

TagMeaningRequired?Example
v=Version — always DKIM1Recommendedv=DKIM1
k=Key type (algorithm)Optional (default rsa)k=rsa
p=Base64 public key dataRequiredp=MIGfMA0GCS...
h=Acceptable hash algorithmsOptionalh=sha256
s=Service type this key applies toOptional (default *)s=email
t=Flags — y (testing), s (strict subdomain match)Optionalt=y
n=Human-readable notesOptionaln=admin contact

🔑 Common Selectors by Provider

If a lookup returns no record, the selector is usually wrong rather than DKIM being unset. Try these common defaults:

ProviderTypical Selector(s)
Google Workspace / Gmailgoogle
Microsoft 365 / Outlookselector1, selector2
Mailchimpk1, k2, k3
SendGrids1, s2
Mailgunmailo, k1, smtp
Zoho Mailzoho, zmail
Amazon SESRandom per key — check SES console
Klaviyodkim, google

🛡️ Use Cases for DKIM Lookup

📧
Email Deliverability Troubleshooting
A missing or misconfigured DKIM record is a common reason legitimate email lands in spam. Verify the record matches what your sending platform expects before opening a support ticket.
🔄
Key Rotation Verification
After rotating DKIM keys, confirm the new selector resolves correctly and the old one is either still valid during transition or properly revoked (empty p=).
🔐
Security Audits
Security teams check whether a domain publishes weak (1024-bit) keys, still-active old selectors that should have been retired, or unusual key types worth investigating.
📈
DMARC Alignment Checks
Confirm the d= domain in your DKIM signature aligns with your From: domain — required for DMARC's DKIM alignment check to pass under strict mode.

🔗 More Ways to Investigate Email Authentication

Check the sending policy with SPF Lookup, confirm mail routing with MX Lookup, or run a full validation with Email Checker. New to DKIM? Start with What Is DKIM?, then read the complete picture in SPF vs DKIM vs DMARC. Also see our Website Security Checklist for the full audit picture beyond just email.

ToolsNovaHub tools are built and independently maintained with a focus on accurate, no-signup network and security utilities. Spotted an error? Let us know.

🎓
Expert Tip
DNS and mail records can take up to 48 hours to fully propagate — if DKIM Lookup shows an unexpected result right after a change, wait and re-check before assuming misconfiguration.
ToolsNovaHub Pro Tip
Run DKIM Lookup from more than one network (office Wi-Fi + mobile data) to rule out local resolver caching before reporting a bug.
⚠️
Common Beginner Mistake
Editing a live DNS or mail record without noting the previous value first. Always save the old record from DKIM Lookup's output so you can roll back instantly if something breaks.

📋 Related Tools & Guides Comparison

ResourceTypeLink
DNS LookupNetworkOpen Tool →
DNS Propagation CheckerNetworkOpen Tool →
Reverse DNS LookupNetworkOpen Tool →
How to Debug Website Caching Issues Using HTTP HeadersGuideRead Guide →
DNS Propagation Guide: TTL, Global DNS & Migration Best PracticesGuideRead Guide →

FAQ

DKIM (DomainKeys Identified Mail) is an email authentication method defined in RFC 6376. It adds a cryptographic signature to outgoing mail headers, and receiving servers verify it against a public key published in DNS.
A selector is a label letting a domain publish multiple DKIM keys at different DNS locations (selector._domainkey.domain). The selector used is included in the DKIM-Signature header's s= tag.
Open a sent email's raw headers and find the DKIM-Signature header — the s= tag is the selector. Without a sample email, try common provider selectors like google, selector1, or k1.
v=DKIM1 is the version tag identifying the record as a DKIM public key. It's optional per RFC 6376 but recommended and expected as the first tag by most receivers.
p= holds the base64-encoded public key used to verify signatures. An empty p= means the key has been revoked — mail signed with it will now fail DKIM.
An empty p= is the standard way to revoke a key while keeping the record in place, typically done during key rotation or when decommissioning a sending source.
k= specifies the algorithm. rsa is default and most widely supported. ed25519 (RFC 8463) is newer, smaller, and faster but not yet universally validated by receivers.
1024-bit RSA is weak and deprecated — some receivers reject it. 2048-bit is the current recommended minimum; some providers use 4096-bit for extra margin.
h= restricts acceptable hash algorithms, typically sha256. If absent, all hash algorithms the receiver supports are accepted — sha256 is now the de facto standard.
SPF authorizes sending IPs. DKIM cryptographically signs the message to prove integrity and origin. DMARC ties both together and tells receivers what action to take when either fails.
Multiple selectors let you run several sending sources at once, each with its own key, and rotate keys without downtime by publishing a new selector before retiring the old one.
Usually the selector is wrong. Check a sent email's DKIM-Signature header for the exact s= value, or try common selectors for your provider from the reference table above.
Yes — TXT records are limited to 255 characters per string, and 2048-bit RSA keys often exceed that. DNS lets one record contain several quoted strings concatenated in order; this tool reconstructs them automatically.
No. DKIM proves a message wasn't altered and was signed by a key the domain published, but it doesn't stop unsigned spoofed mail. Full protection requires DMARC with an enforcement policy.
Generate a key pair with your provider or OpenSSL, publish the public key as a TXT record at selector._domainkey.yourdomain.com with value v=DKIM1; k=rsa; p=<key>, and keep the private key on your mail server.
Yes — completely free, unlimited lookups, no sign-up needed. Queries go through Google's public DNS-over-HTTPS resolver and results appear instantly.