<\/span><\/h2>\nDKIM stands for DomainKeys Identified Mail. While SPF verifies who is sending an email, DKIM ensures what is being sent hasn\u2019t been tampered with during transmission. It’s like sealing a letter in an envelope with a wax stamp \u2014 the recipient can confirm it hasn\u2019t been opened or altered.<\/p>\n
DKIM works by attaching a digital signature to your emails. This signature is generated using a private cryptographic key, and the corresponding public key is published as a TXT record in your DNS. Email servers receiving your message then verify the signature using that public key.<\/p>\n
If the verification passes, your email is considered trustworthy. If not, it may end up in the spam folder \u2014 or get rejected altogether.<\/p>\n
Adding a DKIM record requires accessing your DNS panel and publishing the appropriate TXT record. It\u2019s a technical task, but not impossible with the right steps.<\/p>\n
<\/span>How DKIM Authenticates Emails<\/strong><\/span><\/h3>\nHere\u2019s how the DKIM process works step-by-step:<\/p>\n
\n- Signing the Email<\/strong>: When you send an email, your mail server (e.g., Google Workspace, Microsoft 365, Mailchimp) generates a unique DKIM signature using a private key.<\/li>\n
- Adding a Header<\/strong>: This signature is added to your email\u2019s header.<\/li>\n
- Publishing the Key<\/strong>: Your public key is stored in your domain’s DNS as a TXT record.<\/li>\n
- Verification<\/strong>: The receiving server fetches the public key via DNS and checks the email’s DKIM signature. If they match, the email is verified.<\/li>\n<\/ol>\n
A sample DKIM record might look like: Name\/Host: default._domainkey.yourdomain.com\u00a0 Type: TXT\u00a0 Value: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GN… (public key continues)<\/p>\n
![\"How](\"https:\/\/telahosting.ng\/blog\/wp-content\/uploads\/2025\/05\/How-to-Use-TXT-Records-for-Email-Authentication-SPF-DKIM-DMARC-711x400.avif\" "\\"\\"")
<\/p>