In plain English A digital signature added to every email you send, so the receiving side can check it really came from your domain and was not changed.
DKIM (DomainKeys Identified Mail) is a signature added to every email you send, proving the message came from your domain and was not changed on the way. Receiving mail servers check the signature against a public key published in your domain’s DNSDNS The internet’s phone book. It turns a name people can remember, like example.com, into the number address computers use to find the server. More about DNS →. A valid DKIM signature is one of the strongest signals that mail is genuine.
How it works
- Your mail provider holds a private key and signs each outgoing message with it, adding a
DKIM-Signatureheader. - The header says which domain signed (
d=example.com) and which key to use (the selector,s=selector1). - The receiving server looks up the public key at
selector1._domainkey.example.comand checks the signature.
The DNS record looks like this:
selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
Each sending service, such as your mailbox provider, newsletter tool or shop platform, has its own selector and key, so a domain can have several DKIM records side by side. Some providers ask for a CNAMECNAME record A domain setting that says “this name is just another name for that one”. For example, www pointing at the main domain. More about CNAME record → instead of a TXT record, so they can rotate keys for you.
Why it matters
DKIM survives forwarding, unlike SPF, which makes it the most reliable way to pass DMARC. Check a message’s result in its headers: look for dkim=pass in the Authentication-Results line. Setting it up is covered in how to set up SPF, DKIM and DMARC.
Check any domain’s record with the free SPF, DKIM and DMARC checker.