DKIM record
checker
Look up your domain's DKIM public key by selector. Verify the key is active, understand the configuration, and get advice if something looks wrong.
How DKIM signing works.
DKIM proves your email was sent by your domain and wasn't altered in transit.
Cryptographic signature
Your sending server signs each email using a private key. The corresponding public key is published in DNS. Receiving servers verify the signature to confirm authenticity.
Selector system
Each DKIM key is identified by a selector. You can have multiple selectors (and keys) per domain, allowing key rotation and multiple sending providers at the same time.
Tamper detection
The DKIM signature covers specific email headers and the body. If the email is modified in transit, the signature breaks and DKIM fails — protecting against content manipulation.
Key rotation
Best practice is to rotate DKIM keys annually. Publish the new key under a different selector, update your sending infrastructure, then revoke the old key by setting p= to empty.
DKIM alone is not enough
Like SPF, DKIM authentication alone doesn't protect the visible From header. You need DMARC to enforce authentication policies and protect against spoofing.
2048-bit RSA minimum
1024-bit RSA keys are considered insecure. Use at least 2048-bit RSA or switch to Ed25519, which provides equivalent security with much smaller keys.
Sign every email. Reach the inbox.
Plunk configures DKIM signing automatically and guides you through setting up SPF and DMARC for your domain.