DKIM Record Checker
DKIM signs outgoing emails. Receivers verify the signature using a public key in DNS.
DKIM lives on <selector>._domainkey.<domain>. If selector is empty, we try common ones.
Result for ups.com
Found
Selector: selector1
(TXT on selector1._domainkey.ups.com)
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC6w3l+AiWVB8ySfvoLC0b2JM3sqB0OuUgVEkeqCaDHX8DZzHpBx3bJ9QnPL6q0WddgK+WEaHrkkMCy8itRbi6/A4xYn477Dea0JF+bsooUzZsG8FUk9+xiwY/VY9VS2Td5oJNUSuKx/tiP2PHSbDScl/TNbtEX7VCyXMjasgxF1wIDAQAB; n=1024,1467941662,1483839262
FAQ
Why does DKIM require a selector?
Selectors allow rotating keys and running multiple keys per domain.
Where is DKIM published?
TXT on <selector>._domainkey.<domain>.
DKIM record exists but emails still fail DKIM?
Signing may be disabled or the selector used in email differs from DNS.
Do I need DKIM if I have SPF?
Yes, many providers use both for best deliverability and DMARC alignment.
Can I have multiple DKIM selectors?
Yes, that is common for key rotation or multiple senders.
What is DKIM?
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing emails. DNS stores a public key that allows receivers to verify authenticity.
Example
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0B...
Common mistakes
- Wrong selector (the record exists but under a different selector).
- Key is split incorrectly across multiple TXT chunks (some DNS UIs break it).
- Publishing DKIM but not enabling signing on the mail provider.