What is DKIM?
DKIM (DomainKeys Identified Mail) is an email authentication protocol that prevents email spoofing and
phishing attacks. When you send an email, your mail server signs it with a private cryptographic key.
Recipients verify this signature using a public key published in your domain's DNS records—specifically
in selector._domainkey.yourdomain.com TXT records.
Without DKIM, anyone can claim to send emails from your domain. With DKIM properly configured, email providers like Gmail and Outlook can verify that messages genuinely came from your servers, drastically improving deliverability and protecting your brand reputation.
Why Use a DKIM Extractor?
Extracting DKIM records serves multiple critical purposes in email security and deliverability management:
Verify Email Authentication
Confirm that your domains have DKIM properly configured. Missing or incorrect DKIM records can cause legitimate emails to land in spam or be rejected entirely by strict mail servers.
Audit Competitor Configurations
Analyze how competitors or partners configure email authentication. Learn which email service providers they use (Google Workspace, Office 365, SendGrid) based on DKIM selector patterns.
Bulk Client Audits
Agencies managing multiple client domains can quickly verify DKIM status across entire portfolios. Identify which clients need email authentication improvements before deliverability issues arise.
Migration Validation
When migrating email providers (e.g., from G Suite to Microsoft 365), verify new DKIM records propagated correctly across DNS. Prevent email disruption due to authentication failures.
How DKIM Works (Technical Overview)
- Key Pair Generation: Your mail server generates a public/private key pair. The private key stays secret on your server; the public key is published in DNS.
- Email Signing: When sending mail, the server hashes email headers and body, then encrypts this hash with the private key, creating a DKIM signature added to the email headers.
- DNS Lookup: The recipient's mail server extracts the selector and domain from the
DKIM signature, queries
selector._domainkey.domain.com, and retrieves the public key. - Signature Verification: The recipient decrypts the signature using the public key and compares it to a fresh hash of the received email. If they match, the email is authenticated.
Understanding DKIM Selectors
A DKIM selector is simply a label that identifies which public key to use. Domains can have multiple selectors for different mail streams:
- google – Used by Google Workspace (Gmail for business)
- selector1/selector2 – Common in Microsoft 365
- k1, k2, k3 – Often used by Mailchimp, SendGrid, Amazon SES
- default – Generic selector for simple configurations
If you don't know your selector, this tool automatically scans the 20+ most common ones used by major email service providers.
DKIM Best Practices
- Use 2048-bit Keys: While 1024-bit keys work, modern best practice recommends 2048-bit RSA keys for stronger security against brute-force attacks.
- Rotate Keys Annually: Change DKIM keys at least once per year. If a private key is compromised, old signed emails could be spoofed.
- Combine with SPF and DMARC: DKIM alone isn't enough. Implement SPF (authorized sender IPs) and DMARC (policy enforcement) for complete email authentication.
- Use Unique Selectors Per Service: If you send via multiple providers (transactional emails via SendGrid, marketing via Mailchimp), use different selectors to isolate keys.
- Monitor DNS Propagation: After adding/updating DKIM records, verify they've
propagated globally. Use tools like this extractor or command-line
digto check. - Test Before Going Live: Send test emails to services like mail-tester.com to verify DKIM signatures are valid before launching campaigns.
Common DKIM Mistakes
- Wrong Selector: Publishing the key under
default._domainkeybut configuring your mail server to usegoogleselector. They must match. - Truncated Public Keys: Some DNS providers split long TXT records incorrectly. The public key must be a single continuous string (often 300+ characters).
- Missing Quotes: TXT records with special characters need proper quoting. Example:
"v=DKIM1; k=rsa; p=MIGfMA0..." - Ignoring TTL: Set reasonable TTL (3600-86400 seconds). Too high delays updates; too low wastes DNS queries.
- Forgetting to Sign: Adding the DNS record isn't enough—your mail server must actually sign outgoing messages with the DKIM private key.
Impact on Email Deliverability
DKIM directly affects whether your emails reach the inbox:
- Gmail: Strongly favors DKIM-signed emails. Missing DKIM can reduce inbox placement by 15-30%.
- Outlook/Office 365: Requires either DKIM or SPF for bulk senders. Without both, emails often land in Junk.
- Yahoo/AOL: Enforces strict DMARC policies. DKIM failures can lead to complete rejection.
- B2B Servers: Corporate mail servers increasingly require DKIM. Missing authentication may block your domain entirely.



