The DNS records
The number in the host and the key are generated for your account. Copy both from Zoho Campaigns; the rows below use Zoho's example host.
DKIM key for the sender domain
Type: TXT · Host: 2232._domainkey
k=rsa; p=<public key shown in Zoho Campaigns>
Zoho's newer guide shows 23441._domainkey; your number will differ.
DKIM key when you send from a subdomain such as mail.example.com
Type: TXT · Host: 2232._domainkey.mail
k=rsa; p=<public key shown in Zoho Campaigns>
SPF on the sender domain
Type: TXT · Host: @
v=spf1 include:zcsend.net ~all
Add include:zcsend.net to an existing SPF record instead of creating a second one.
Set it up and turn on signing
- Add and verify a sender address on your own domain. Zoho says public mailbox domains can't be authenticated.
- As an organization admin, go to Settings > Email > Senders and Authentication and click Setup next to the domain (older accounts: Settings > Deliverability > Domain Authentication).
- Copy the DKIM host and value into a new TXT record. If your DNS host appends the domain, enter only the
._domainkeypart Zoho shows. - Click Authenticate. Zoho says DNS changes can take up to 24 hours to update globally; if the status still reads At risk, wait and validate again.
- With SPF and DKIM passing, the Custom Return Path section unlocks: publish its CNAME and click Validate CRP. Then publish your own DMARC record.
DMARC alignment
The numbered key lives under your sender domain, so Zoho Campaigns signs with d= your domain and DMARC can pass on DKIM even while bounces still use Zoho's default return path. Zoho says all addresses under an authenticated domain count as authenticated too. Adding the Custom Return Path moves bounces onto a subdomain of yours, which Zoho says aligns your domain across all its checks.
Key length and rotation
Zoho generates the key and you hold its public half as a TXT value, so a new key needs a DNS update on your side. Neither help article states a key length or rotation schedule. The numbered host makes a change easy to spot: a different number in the setup window means a new record to publish.
Common mistakes
- Putting the key on the root domain. The value goes on the numbered
._domainkeyhost, not on@. - Leaving off the subdomain. Sending from
mail.example.comneeds the host2232._domainkey.mail, with your own number. - Expecting Zoho to publish DMARC. Zoho Campaigns only shows a reminder; the
_dmarcrecord is yours to create. - A CRP host that already has MX or A records. Zoho says return path validation then fails.
Check your Zoho Campaigns DKIM key
Enter your domain and the selector from your Zoho Campaigns account. Free, reads public DNS only.
Frequently asked questions
What host name does the Zoho Campaigns DKIM record use?
A number Zoho assigns, followed by ._domainkey, such as 2232._domainkey in its example. For a subdomain sender like mail.example.com, Zoho adds the subdomain: 2232._domainkey.mail.
Does Zoho Campaigns create a DMARC record for me?
No. Zoho Campaigns shows a heads-up in the DMARC section when none is published, and asks you to create the record yourself. Our DMARC Record Generator builds one.
What do Zoho Campaigns' At risk and Protected statuses mean?
Zoho checks four parts: SPF, DKIM, DMARC and the custom return path. At risk means none are verified, Needs attention means some are, and Protected means all four are configured and verified.
Sources
- Zoho Campaigns Help: Senders & Authentication Settings
- Zoho Campaigns Help: Authenticate email domain
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Zoho Campaigns's documentation on November 3, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Zoho Campaigns
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated