Speak to an Email Deliverability Consultant FOR FREE
Trusted by 1000+ companies
Publishing a DKIM record means creating a TXT record with a selector-specific hostname in your domain's DNS zone. Most domain registrars and DNS hosting providers (GoDaddy, Cloudflare, Route 53, Namecheap) have a DNS management console where you add records manually.
Access your domain registrar or DNS hosting control panel. Look for "DNS Management," "Zone Editor," or "Advanced DNS."
Find the domain you're configuring DKIM for. Select it to open the record editor.
Choose "Add Record" or "Create Record." Set the record type to TXT.
Enter your DKIM hostname in this format: selector._domainkey.yourdomain.com — replace "selector" with your chosen selector name (like s1, default, or mail) and "yourdomain.com" with your actual domain.
Copy the public key value from EmailWarmup.com's DKIM generator and paste it into the "Value" or "TXT Content" field. Enclose the entire value in double quotes.
Use the default TTL (usually 3600 seconds / 1 hour) or set a custom value. Lower TTL values propagate changes faster, but increase DNS query load.
Store the private key securely on your mail server or ESP. Configure your email system to sign outgoing messages using this key and your selector. (Third-party ESPs like Google Workspace or Microsoft 365 often provide their own DKIM keys — check their documentation.)
Wait 10-30 minutes for DNS propagation. Use EmailWarmup.com's free DKIM checker to confirm the record is published correctly, and the signature validates properly.
A DKIM record contains cryptographic and policy tags published as a DNS TXT record. The receiving mail server retrieves these tags to verify your email's digital signature.
| Tag | What It Does | Example Value | Required |
|---|---|---|---|
| v | Protocol version (always DKIM1) | v=DKIM1 | Yes |
| p | Public key string (RSA or Ed25519) | p=MIGfMA0GCSqGSI... | Yes |
| k | Key type algorithm | k=rsa or k=ed25519 | No (defaults to rsa) |
| a | Signing algorithm used | a=rsa-sha256 | No |
| t | Testing mode flag | t=y (testing) or t=s (strict) | No |
| s | Service types allowed | s=email or s=* | No |
| h | Acceptable hash algorithms | h=sha256 | No |
| n | Notes for administrators | n=Production key 2025 | No |
| g | Granularity (local-part matching) | g=support or g=* | No |
DKIM key length determines encryption strength. Longer keys provide stronger security but may hit DNS record size limits on some providers.
| Key Length | Security Level | DNS Compatibility | Recommendation |
|---|---|---|---|
| 1024-bit | Basic protection | Universal support | Deprecated — vulnerable to modern attacks |
| 2048-bit | Strong protection | Supported by 99% of providers | Recommended — best balance of security and compatibility |
| 4096-bit | Maximum protection | May exceed DNS limits on some hosts | Use only if your DNS provider supports large TXT records |
Your DKIM signature proves you sent the email — but it doesn't prevent attackers from sending emails that look like they're from you using a different domain (like yourcompany-secure.com instead of yourcompany.com).
You need a complete email authentication setup to protect your brand and maximize inbox placement. At EmailWarmup.com, you can talk to an email deliverability consultant for free and let our team:
Book your time today and make sure your email security is 100% locked down — so spoofed emails get rejected instead of reaching your customers' inboxes.
Here’s everything you need to know about our SPF Generator: