How DKIM works and how to read your DKIM check
DKIM adds a cryptographic signature to every message you send. Your mail server signs it with a private key, and receivers fetch the matching public key from DNS to confirm the message came from your domain and wasn't changed on the way. The DKIM checker above finds that public key and tells you whether receivers can use it.
What's inside a DKIM record
The record lives at selector._domainkey.yourdomain.com. The selector is a label you or your provider chose, so one domain can hold several keys, one per sending service. Inside the TXT value, v=DKIM1 sets the version, k=rsa names the key type and p= carries the public key itself. An empty p= means the key was revoked on purpose. You may also see t=y, which marks the key as in testing. Use 2048-bit keys: 1024 bits is the minimum receivers accept, and anything shorter fails.
How to find your DKIM selector
If the checker finds nothing, the record often exists under a selector it didn't try. Google Workspace uses google by default, and Microsoft 365 publishes two CNAME records, selector1 and selector2. Most email platforms set their own. The quickest way to find yours is to open a message you sent, view the original headers and read the s= value in the DKIM-Signature line. Our guide to finding DKIM selectors shows where to look for each major provider.
Why a DKIM check fails
The usual causes are simple. The key was never published, or it was published under a different selector. The DNS host cut a long key at 255 characters instead of splitting it into strings. Signing was never switched on in the provider's admin panel, which is common in Google Workspace, where DKIM is off until you start it (setup steps here). A forwarding service or a footer tool changed the message body after signing. And for DMARC, the d= domain in the signature has to match the domain in your From address, or DKIM passes while DMARC still fails.
When to use the DKIM generator
Most providers create and host the key for you, so you only copy their record into DNS. The DKIM generator is for senders who run their own mail server, such as Postfix with OpenDKIM, or who need to rotate a key. The key pair is created in your browser and the private key never leaves your device. Rotate keys every 6 to 12 months, and publish the new selector before you retire the old one.
Next step after DKIM passes
DKIM is one of three records Gmail and Yahoo expect. Check your policy with the DMARC Checker and your SPF with the SPF Checker. With all three in place, authentication stops holding you back and reputation decides where you land. Warmy builds that reputation with warm-up from real mailboxes and watches your DNS records daily, so a broken key doesn't go unnoticed.
SPF, DKIM and DMARC done? Build the reputation on top. Start a 7-day trial or book a demo.

























