Zoho Mail
How to set up SPF, DKIM and DMARC for Zoho Mail
Authenticate mail sent through Zoho Mail from your own domain: one SPF include, a DKIM key from the Zoho Admin Console and a DMARC record.
Check your current setup:
Before you start
You need an administrator or super administrator login for the Zoho Mail Admin Console. You also need access to the DNS panel where your domain's nameservers point. That panel can belong to a different company from the one where you registered the domain.
Zoho shows the values for your domain in the Admin Console, on its domain setup and DNS mapping pages. When the console and this guide differ, follow the console.
Work in this order: SPF, DKIM, then DMARC. Zoho's DMARC page asks you to publish valid SPF and DKIM records first.
Step 1: SPF
SPF is a DNS record that lists the servers allowed to send mail for your domain. Zoho Mail authorizes its servers with one include. Start with this record:
v=spf1 include:zohomail.com ~all
Zoho's own examples end in -all when Zoho is the only sender, and Zoho says ~all suits domains that also send through other servers. With ~all, mail from an unlisted server is a soft failure. That is the safer start while you confirm your senders in DMARC reports.
- Look for a TXT record at the root of your domain (
@) that starts withv=spf1. - If there is none, create one with the value above.
- If one exists, add
include:zohomail.comto it, before the final~allor-all. A domain can have only one SPF record. - In the Admin Console, open Domains, select your domain, go to Email Configuration, choose SPF and verify the record.
Some of Zoho's translated help pages show include:zoho.com instead. That name also publishes a valid SPF record, and it lists more Zoho networks than zohomail.com does. Use the value your console shows.
If several Zoho services send from the same domain, Zoho suggests include:one.zoho.com to avoid SPF lookup failures. Zoho Mail's help does not publish a table of SPF values by data center. Zoho CRM's help lists one.zoho.eu and one.zoho.in for CRM accounts in those regions. If your account is hosted in the EU or India, copy the value your console shows.
Step 2: DKIM
DKIM adds a signature to each message, and receivers check it against a public key you publish in DNS. Learn more about DKIM selectors.
- In the Admin Console, open Domains, select your domain, go to Email Configuration and choose DKIM.
- Click Add. Choose a selector accepted by Zoho and a 1024-bit or 2048-bit key;
zohois an example. Use that same selector in DNS. Prefer 2048 bits if your provider supports it. - Zoho generates a TXT record. Copy the entire value.
- In DNS, publish the TXT at
<chosen-selector>._domainkeyunder the sending domain.zoho._domainkeyis only an example for selectorzoho. Strip only the DNS zone suffix if the panel appends it; copy Zoho’s complete name and public key. - Back in Zoho, click Verify next to the selector. Make the selector the default and enable DKIM for the domain.
The key lives under your domain, so the signature uses your domain and can align with the address people see in From. Alignment means the authenticated domain matches the From domain. See how DMARC alignment works.
Step 3: DMARC
DMARC tells receivers how to treat mail that fails alignment, and it asks them to send you reports about who uses your domain. If _dmarc already has a TXT record that starts with v=DMARC1, edit that record instead of creating a second one. Receivers discard all the records when they find more than one (RFC 9989 Section 4.10).
Create a TXT record named _dmarc:
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace the rua address with your DMARC Pulse reporting address. You can also build the record in Zoho: open Domains, select your domain, go to Email Configuration, choose DMARC, fill in the form and click Generate. Publish the result, then click Verify.
Zoho’s form still exposes a policy-percentage field. pct was defined by the earlier RFC 7489 and removed by RFC 9989. Omit it from new policy records and do not rely on partial enforcement; existing receivers may implement the older behavior.
Zoho Mail's help does not say which domain it uses as the envelope sender, the bounce address that SPF checks. Your reports will show whether SPF aligns. Treat DKIM as the result to watch for mail sent through Zoho.
Step 4: Check, then enforce
Run the SPF checker, the DKIM checker with your selector and the DMARC checker on your domain.
Preserve any existing policy and report destinations. For a first deployment, monitor at p=none. After every legitimate sender passes with alignment, assess p=quarantine. Consider p=reject separately, including mailing-list and forwarding risks; it is optional. Receivers decide how to handle individual messages.
Zoho Mail hosts everyday mailboxes, so take the same section's warning seriously. It says domains whose users might post to mailing lists should not publish p=reject. A domain that does publish it must sign its mail with DKIM and cannot rely on SPF alone.
Common problems
- Two SPF records. Zoho warns that multiple SPF records interrupt the check and that mail can land in spam. RFC 7208 Section 3.2 forbids them too. Merge every sender into one record.
- SPF will not verify in Zoho. Check where the domain's nameservers point. Zoho says the TXT record must exist at that provider, even when you registered the domain elsewhere.
- Too many lookups. SPF allows 10 DNS lookups (RFC 7208 Section 4.6.4). If Zoho Mail shares the record with several other senders, the record can pass that limit and return a permanent error. Use the SPF checker to count them.
- The selector stays unverified. Zoho says DNS changes can take 12 to 24 hours with a high TTL, the time resolvers keep a record. Its Cloudflare page allows 4 to 48 hours for SPF and DKIM. Copy the full key before you try again.
- Doubled host name. A record at
zoho._domainkey.example.com.example.commeans your panel added the domain a second time. Enter only the prefix. - DKIM verified but mail goes out unsigned. Verifying does not start signing. Zoho asks you to make the selector the default and enable it. The status switch stays locked until the selector is verified.
- DKIM fails with an outbound gateway. Zoho says DKIM works only for mail generated in Zoho and delivered directly to external servers. Domains that use routing or outbound gateways, and mail generated on other servers, are outside that support. That mail needs its own authentication at the system that sends it.
- Other tools fail DMARC. Zoho's DMARC page warns that third-party senders need SPF or DKIM authorization of their own. Your reports list each source, so set them up before you tighten the policy.