Glossary
DKIM
DKIM Explained: How DomainKeys Identified Mail Protects Your Brand
DKIM (DomainKeys Identified Mail) is an email authentication method that adds a cryptographic signature to every outgoing message. The receiving server checks the signature against a public key published in the sender's DNS, which proves that the message was authorised by the domain owner and that its signed content was not changed on the way.
For brands, DKIM makes forged emails easier to detect and helps legitimate emails reach the inbox.
What Is DKIM?
DKIM is defined in RFC 6376. It works with a pair of cryptographic keys. The sending mail system holds a private key and uses it to create a signature over selected message headers and the body. The matching public key is published in the domain's DNS (Domain Name System) as a TXT record.
Every DKIM signature names two things: the signing domain (the d= value) and a selector (the s= value). The receiver combines them to find the public key, at an address in the form selector._domainkey.example.com. Selectors let a domain run several keys at once, for example one per email provider, and rotate keys without downtime.
DKIM differs from SPF in what it proves. SPF checks which server sent the message. DKIM checks that the message carries a valid signature from a domain and has not been tampered with. Because the signature travels with the message, DKIM usually survives forwarding, which is where SPF often breaks.
How DKIM Works
- Signing. When a message is sent, the mail system calculates a hash of the body and selected headers and signs it with the private key. The result is added as a
DKIM-Signatureheader. - Lookup. The receiving server reads the domain and selector from the header and retrieves the public key from DNS.
- Verification. It recalculates the hash and checks it against the signature. A match means the message is authentic and unmodified in the signed parts.
- Result. The outcome (pass or fail) is recorded and fed into spam filtering and DMARC evaluation.
What DKIM Does Not Do
- It does not encrypt the message. DKIM is about authenticity, not secrecy.
- It does not, on its own, tell a receiver what to do with a failure.
- It does not check the visible "From" address. A criminal can sign a message with their own domain and still display your brand name. DMARC closes this gap by requiring that the signing domain aligns with the visible "From" domain.
Why It Matters for Brands
- Protection against spoofing. Messages that claim to come from your domain but lack a valid signature can be rejected once DMARC enforcement is in place. See Email Spoofing.
- Better deliverability. Mailbox providers use authentication as a trust signal for bulk and transactional email.
- Integrity. If a message such as an invoice or a password reset is changed in transit, the signature breaks.
- Foundation for BIMI. Showing a brand logo in the inbox requires an enforced DMARC policy, which in turn depends on working SPF or DKIM. See BIMI.
- Reduced phishing impact. Customers who receive fewer forged messages are less likely to fall for Phishing.
How to Set Up DKIM
- List every sender that uses your domain: corporate mail, newsletter tool, CRM, billing system, support desk.
- Enable DKIM in each system. Most providers generate a key pair and give you a DNS record to publish. Use your own domain as the signing domain so the signature aligns with your "From" address.
- Publish the public key as a TXT (or CNAME, if the provider asks for it) record under the selector name.
- Choose strong keys. 2048-bit RSA keys are widely recommended where your DNS provider supports the longer record.
- Test. Send a message to a test mailbox and check the headers for
dkim=pass. - Rotate keys periodically and remove selectors for providers you no longer use.
- Monitor with DMARC reports to see who is sending in your name and whether signatures pass.
Common DKIM Mistakes
- Relying on the email provider's default domain for signing instead of your own.
- Publishing the key at the wrong selector name or with line breaks that corrupt it.
- Leaving old keys in DNS after switching providers.
- Assuming that DKIM alone stops spoofing without a DMARC policy.
Related Terms
- SPF (Sender Policy Framework): lists which servers may send email for a domain.
- DMARC: uses SPF and DKIM results to decide how to handle suspicious messages.
- Email Spoofing: forging the sender of an email.
- Business Email Compromise (BEC): fraud that relies on impersonating trusted senders.
- Domain Monitoring: detecting new lookalike domains that DKIM cannot cover.
How Remove.tech Helps
DKIM protects messages that claim to come from your own domain. It does nothing about a criminal who registers a lookalike domain and authenticates it perfectly. Remove.tech finds lookalike domains, phishing pages and impersonating websites and submits takedown notices to registrars and hosts. To check what is targeting your brand today, get started.

