Introduction
To authenticate a domain on Zoho Mail, publish one SPF record that includes Zoho's sending domain for your data centre, create a DKIM selector in the Zoho Mail Admin Console and publish its TXT record, then add a DMARC record at _dmarc. All three are managed under Domains, Email Configuration in the Admin Console.
The order matters, and so do two Zoho specifics that trip up MSPs: Zoho runs regional data centres with different DNS values, and its built-in DMARC generator still offers a policy percentage that the current standard no longer has. This guide walks through each record for a client onboarding, then covers alignment checks, combining Zoho with other senders and the most common errors. For background on the protocols, see the DMARC guide.
Key takeaways
- Copy the SPF value from the client's own Admin Console. Zoho's help pages use
include:zohomail.comas the generic value, but the domain varies by data centre. - A domain can have only one SPF record. Merge Zoho into the existing record instead of adding a second one.
- DKIM is created per domain in the Admin Console: add a selector, publish the TXT record at
selector._domainkey, verify, then make it default and enable it. - Use Zoho's DMARC generator for convenience, but leave the policy percentage empty and remove any
pcttag: RFC 9989 removed it. - Zoho does not support DKIM for domains configured with Email Routing and Outbound Gateways, so check how the client's mail flows before you start.
Where are the SPF, DKIM and DMARC settings in Zoho Mail?
All three live in the same place. Sign in to the Zoho Mail Admin Console as an Administrator or Super Administrator, choose Domains in the left menu, select the domain, and open Email Configuration. From there you can view and manage the MX, SPF, DKIM, DMARC and BIMI records, according to Zoho's domain management help.
Zoho shows the exact values for that organisation in the console, and its help pages repeatedly note that some values depend on the data centre. Treat the console as the source of truth for every record you publish. You add the records at the client's DNS host, not in Zoho.
What is the correct SPF record for Zoho Mail?
For a domain that sends only through Zoho Mail, Zoho's SPF help page gives v=spf1 include:zohomail.com -all as the record, published as a TXT record at the root of the domain (@). If the organisation uses several Zoho services, the same page gives include:one.zoho.com instead.
example.com. TXT "v=spf1 include:zohomail.com -all"
-all tells receivers that nothing other than the listed senders is authorised. Zoho's own combined examples use ~all (soft fail). Under DMARC, either works, because DMARC acts on the SPF pass or fail result and the policy decides what happens. Many MSPs keep ~all while sender discovery is still running and tighten it later.
Does the Zoho SPF include change by data centre?
Yes, it can. Zoho's help pages state that the top-level domain in MX records varies with the data centre where the organisation's data is hosted, and they direct admins to the values shown in the Admin Console. Zoho also publishes separate regional SPF domains, so the generic zohomail.com value is not always the right one for a client.
When we checked Zoho's DNS on 10 November 2026, these domains each published their own SPF record:
| Region (MX hosts) | SPF domain published by Zoho |
|---|---|
United States (mx.zoho.com) |
zohomail.com |
Europe (mx.zoho.eu) |
zohomail.eu |
India (mx.zoho.in) |
zohomail.in |
Australia (mx.zoho.com.au) |
zohomail.com.au |
Japan (mx.zoho.jp) |
zohomail.jp |
Saudi Arabia (mx.zoho.sa) |
zohomail.sa |
Use the table as a sanity check, not as a substitute for the console. The client's existing MX records are a quick clue to its data centre: if they point to mx.zoho.eu, an SPF record with include:zohomail.com deserves a second look. Check the console value before you publish, and for regions not listed here, rely on the console alone.
How do you verify SPF in the Admin Console?
Go to Domains, select the domain, open Email Configuration, choose SPF and click Verify SPF Record. Zoho reads the live DNS, so verification fails until the record has propagated. Zoho notes that DNS changes can take 12 to 24 hours depending on TTL, and that a record added at a DNS host the domain's nameservers do not point to will never validate.
How do you set up DKIM in Zoho Mail?
DKIM in Zoho Mail is created per domain: you add a selector in the Admin Console, Zoho generates a public key, you publish it as a TXT record, then you verify the selector and make it the default. Until DKIM is enabled, Zoho does not sign mail for that domain with the client's own key. The steps below follow Zoho's DKIM configuration help.
- In the Admin Console, go to Domains and choose the domain.
- In the Email Configuration tab, select DKIM.
- Click Add to create a new selector, and enter a selector name, for example
zoho. - Choose a key length of 1024 bits or 2048 bits, then click Add. Zoho generates the TXT record value.
- At the client's DNS host, create a TXT record with the host
zoho._domainkeyand paste the full key as the value. - Once the record resolves, click Verify next to the selector in the Admin Console.
- Make the verified selector the default and enable DKIM for the domain.
The published record looks like this, with the key shortened:
zoho._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA..."
Choose 2048 bits unless the DNS host cannot store a TXT value that long. Some DNS hosts, such as GoDaddy and Namecheap, append the domain automatically, so you enter only zoho._domainkey as the host. If you type the full name there, you end up with zoho._domainkey.example.com.example.com.
Can a domain have more than one Zoho DKIM selector?
Yes. Zoho lets one domain have several selectors, for example per office or team, and you can assign extra selectors to specific users from the user list. Users without an assignment sign with the default selector. Separate selectors are also how you rotate keys without a gap: publish and verify the new one before switching the default. How to rotate DKIM keys safely covers the timing, and DKIM selectors explained explains how receivers find the key.
How do you publish a DMARC record for a Zoho Mail domain?
Publish one TXT record at _dmarc.example.com that starts with v=DMARC1 and a policy. For a new client, start at p=none with an aggregate report address so you can see every source sending as the domain before enforcing. Zoho's Admin Console can generate the record for you under Email Configuration, DMARC.
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
Zoho's DMARC policy help describes the generator: you choose the action for failed messages, enter aggregate and forensic report addresses, set a subdomain policy, set SPF and DKIM alignment, then click Generate, publish the TXT record and click Verify. Three of its fields need care:
- Policy percentage. Leave it empty. The
pcttag was removed in RFC 9989, which replaced RFC 7489. If the generated value contains apcttag, delete it before you publish. Rollout isp=none, thenp=quarantine, thenp=reject, and RFC 9989 offerst=yas a test flag instead. Why pct is going away explains the change. - Alignment. Zoho's example record uses
aspf=s. Relaxed alignment (r) is the default in RFC 9989 and the safer starting point, because it lets subdomains of the client's domain align. Leave both alignment settings relaxed unless there is a reason not to. - Forensic address. Failure reports (
ruf, defined in RFC 9991) are optional and can contain message content. Aggregate reports are what you need for onboarding.
Zoho also allows only one DMARC record per domain. A second record makes DMARC fail with a permanent error, so check for an existing record before adding Zoho's.
How do you check alignment for Zoho Mail?
DMARC passes only when SPF or DKIM passes for a domain that aligns with the visible From address. Send a test message from a Zoho mailbox to an external mailbox, open the full headers and look at three things: the DKIM d= domain, the Return-Path domain and the dmarc= result in Authentication-Results.
Authentication-Results: mx.example.net;
dkim=pass header.d=example.com header.s=zoho;
spf=pass smtp.mailfrom=user@example.com;
dmarc=pass header.from=example.com
If header.d shows the client's domain and the selector you created, DKIM is aligned and DMARC will pass even when mail is forwarded and SPF breaks. If there is no passing signature for the client's domain, DKIM is not enabled or the selector is not the default yet. Our email header analyzer reads these fields for you, and DMARC alignment explained covers the strict and relaxed rules.
Do not rely on the test message alone. The aggregate reports that arrive over the following days show every IP sending as the domain, including the ones nobody mentioned during onboarding.
How do you combine Zoho Mail with other senders?
Add every sender to a single SPF record and give each one its own DKIM selector. A domain must have exactly one SPF record: Zoho warns that multiple SPF TXT records make validation fail. Merge the mechanisms instead:
example.com. TXT "v=spf1 include:zohomail.com include:_spf.example-esp.net ip4:203.0.113.25 ~all"
Keep within the 10 DNS lookup limit from RFC 7208; each include costs at least one lookup, and nested includes count too. Remove includes for services the client no longer uses. Multiple SPF records: how to merge them and SPF too many DNS lookups cover both problems in detail.
Other Zoho products are separate senders. Zoho Campaigns, for example, uses its own return-path domain by default, and Zoho's Campaigns help explains that a custom return-path on the client's domain is needed for SPF alignment. Authenticate each Zoho service in its own settings rather than assuming the Zoho Mail setup covers it. How to handle third-party senders gives the general approach.
What are the most common Zoho Mail authentication errors?
Most failures come from DNS entry mistakes rather than from Zoho itself. The table lists the problems we see most during onboarding and the fix for each.
| Symptom | Likely cause | Fix |
|---|---|---|
| SPF verification fails in the Admin Console | Two SPF records, or the record was added at a DNS host the nameservers do not use | Merge into one v=spf1 record at the authoritative DNS host |
| SPF verification fails although a Zoho include is present | Include for the wrong data centre | Replace it with the value shown in the client's Admin Console |
SPF permerror |
More than 10 DNS lookups | Remove unused includes or replace them with ip4/ip6 |
| DKIM selector will not verify | Truncated key, or host entered as zoho._domainkey.example.com at a DNS host that appends the domain |
Paste the full key; enter only zoho._domainkey |
| DKIM verified but no signature for the client's domain | Selector not set as default or DKIM not enabled | Make the selector default and enable DKIM |
| No DKIM option works | Domain uses Email Routing and Outbound Gateways | Zoho does not support DKIM there; sign at the outbound gateway instead |
| DMARC permanent error | Two _dmarc TXT records, or a missing v/p tag |
Keep one record that starts with v=DMARC1; p= |
Use the SPF analyzer, DKIM validator and DMARC checker to confirm what receivers actually see, rather than what the DNS panel shows. Common DMARC errors covers more general cases.
When can a Zoho Mail domain move to p=reject?
Move up when the aggregate reports show that every legitimate source passes DMARC with aligned SPF or DKIM. Go from p=none to p=quarantine, watch the reports, then move to p=reject. There is no fixed waiting period; the reports decide. The UK's National Cyber Security Centre recommends the same staged approach in its email security and anti-spoofing guidance, ending with a policy that rejects spoofed mail.
For an MSP managing several Zoho clients, keep the per-domain status in one place: data centre, SPF value, DKIM selector and key length, DMARC policy and the date of the last change. A multi-tenant platform such as DMARC AI for MSPs parses the aggregate reports for every client domain, so you can see which Zoho tenants are ready for enforcement. How to move from monitoring to enforcement safely and the DMARC onboarding checklist for MSP clients set out the full process.
FAQ
What SPF include does Zoho Mail use?
Zoho's help pages give include:zohomail.com as the generic value, or include:one.zoho.com when several Zoho services send for the domain. The domain can differ by data centre, and Zoho publishes regional SPF domains such as zohomail.eu, so always copy the value shown in the client's Admin Console.
What is the Zoho Mail DKIM selector name?
You choose it. When you add a selector under Domains, Email Configuration, DKIM, Zoho asks for a name and uses zoho as its example. The TXT record is then published at that name followed by ._domainkey, for example zoho._domainkey.example.com. Different clients can use the same selector name safely.
Should I use 1024-bit or 2048-bit DKIM keys in Zoho Mail?
Use 2048 bits where the client's DNS host accepts the longer TXT value, because a longer key is harder to break. Zoho offers both lengths when you add a selector. If the DNS panel rejects the 2048-bit key, check whether it requires the value split into strings before falling back to 1024 bits.
Does Zoho Mail create a DMARC record automatically?
No. The Admin Console can generate a DMARC record from the options you choose, but you still publish it as a TXT record at _dmarc at the client's DNS host and click Verify. Leave the policy percentage empty, because RFC 9989 removed the pct tag, and start at p=none.
Why does DMARC fail for a Zoho Mail domain when SPF passes?
Usually because SPF passed for a domain that does not align with the From address, or DKIM is not enabled yet. Check that the DKIM signature uses the client's domain and your selector, and that the Return-Path domain matches the From domain under relaxed alignment. Why DMARC fails when SPF passes explains the mechanism.
Final thoughts
Zoho Mail makes authentication straightforward once you respect its two quirks: take the SPF value for the client's data centre from the console, and ignore the policy percentage in the DMARC generator. Publish one merged SPF record, enable a 2048-bit DKIM selector, start DMARC at p=none and let the aggregate reports tell you when each client domain is ready for p=reject. For the SPF fundamentals, see the SPF guide, and for signing, the DKIM guide.