How to Set Up SPF, DKIM and DMARC for Zoho Mail

If your business email runs on Zoho Mail, three DNS records decide whether your email reaches the inbox or the spam folder: SPF, DKIM and DMARC. This guide walks you through all three, in order, with the exact values to copy.

Time needed: about 15 minutes of work, plus waiting time for DNS changes (usually under an hour, occasionally up to 48 hours).

Before you start, you’ll need two logins:

  • A Zoho Mail admin account, so you can open the Admin Console.
  • The company that manages your domain’s DNS. This is often where you bought the domain (GoDaddy, Squarespace, Namecheap) or a service like Cloudflare. Not sure? Our free check shows your current records.

Why this matters now

Gmail, Yahoo and Microsoft’s Outlook.com now require senders to prove their email is genuine. Businesses that send in volume must have all three records; everyone else is judged more harshly without them. A missing or broken record is one of the most common reasons invoices, quotes and replies quietly land in spam.

Zoho makes this easier than most: the Admin Console shows the exact record for each step and has a Verify button, so you know right away if something’s wrong.

RecordWhat it doesYou set it up in
SPFLists the servers allowed to send email for your domainYour DNS host
DKIMAdds a digital signature proving your email wasn’t forged or changedZoho Admin Console, then your DNS host
DMARCTells receivers what to do with email that fails SPF and DKIM, which stops others from spoofing youYour DNS host

First: which Zoho region are you on?

Zoho runs separate data centers around the world, and the SPF value depends on which one holds your account. The easiest tell is the web address you use to sign in, or your MX records:

You sign in atYour MX records end inSPF include
mail.zoho.comzoho.cominclude:zohomail.com
mail.zoho.euzoho.euinclude:zohomail.eu
mail.zoho.inzoho.ininclude:zohomail.in
mail.zoho.com.auzoho.com.auinclude:zohomail.com.au
mail.zoho.jpzoho.jpinclude:zohomail.jp

Most US businesses are on zoho.com. The free check shows your MX records if you’re not sure. When in doubt, copy the value Zoho shows you in the Admin Console (Step 1 explains where).

Step 1: Add your SPF record

First, look at your existing DNS records for a TXT record that starts with v=spf1. A domain can only have one SPF record. If one already exists, edit it instead of adding a second, because two SPF records cancel each other out.

If you only send email through Zoho Mail (US data center), add this TXT record:

TypeTXT
Host / Name@ (some hosts want your domain name, like yourcompany.com)
Valuev=spf1 include:zohomail.com -all

Swap in your region’s include from the table above if you’re not on zoho.com. Zoho recommends ending with -all (a hard fail). If other services also send email as you and you haven’t added them all yet, ~all is the gentler choice while you work.

Do other services send email as your domain? Newsletters, CRMs, invoicing and help desk tools often do. Add each one’s include: to the same record, before -all. For example, Zoho Mail plus Google Workspace:

v=spf1 include:zohomail.com include:_spf.google.com -all

Keep the total under 10 DNS lookups; past that, SPF fails for every email. The free check counts them for you.

Confirm it in Zoho: in the Admin Console, go to Domains, select your domain, open Email Configuration, choose SPF, and click Verify.

Step 2: Turn on DKIM signing

DKIM is a two-part job: Zoho creates a key, you publish it in DNS, then you tell Zoho to start signing.

Create the key in Zoho

  1. Sign in to Zoho Mail as an administrator and open the Admin Console.
  2. Go to Domains, select your domain, and open the Email Configuration tab. Choose DKIM.
  3. Click Add. For the selector name, enter zoho (any short word works, but this one is easy to recognize).
  4. Choose 2048 bits for key length and click Add.
  5. Zoho shows a long TXT record value starting with v=DKIM1. Copy it, and keep this page open.

Publish it in DNS

At your DNS host, add a new TXT record:

TypeTXT
Host / Namezoho._domainkey (use your selector name if you chose a different one)
ValueThe full value Zoho gave you, starting with v=DKIM1; k=rsa; p=

Two common mistakes: Zoho displays the host as zoho._domainkey.yourcompany.com, but most DNS hosts (GoDaddy, Cloudflare, Squarespace) add your domain automatically, so enter only zoho._domainkey. And copy the whole value; it’s long. If your DNS host rejects it as too long, create a 1024-bit key in Zoho instead.

Start signing

Back in the Admin Console on the same DKIM page, click Verify next to your selector. Once it verifies, click Enable DKIM. If Zoho can’t find the record yet, wait an hour and try again; new DNS records can take up to 48 hours to appear everywhere.

Step 3: Add DMARC, then tighten it

Once SPF and DKIM both verify, add DMARC in monitor-only mode, so nothing gets blocked while you confirm everything passes:

TypeTXT
Host / Name_dmarc
Valuev=DMARC1; p=none; rua=mailto:[email protected]

Replace [email protected] with a mailbox you’ll check. Mail providers send daily reports there showing every server that sent email using your name. A Zoho group address or an email alias keeps them out of your main inbox. Zoho can also build this record for you: in the Admin Console, go to Domains, select your domain, then Email Configuration → DMARC.

Monitor mode alone doesn’t stop spoofing. Zoho recommends raising enforcement gradually. Once your real email passes for at least a week, tighten the policy in steps:

StageDMARC valueWhat happens
1. Monitor (1+ week)v=DMARC1; p=none; rua=mailto:[email protected]Nothing is blocked; you collect reports
2. Quarantine a sharev=DMARC1; p=quarantine; pct=10; rua=mailto:[email protected]10% of failing email goes to spam; raise pct to 25, 50, then 100 over a few weeks
3. Rejectv=DMARC1; p=reject; rua=mailto:[email protected]Forged email using your domain is refused

Step 4: Check that it worked

  1. Run your domain through the free MailWatchman check. SPF, DKIM and DMARC should all show as passed (DMARC shows “needs attention” while it’s at p=none, which is expected at first).
  2. Send an email from your Zoho account to a personal Gmail address. Open it, click the three dots, and choose Show original. You should see PASS next to SPF, DKIM and DMARC.

Common problems and fixes

ProblemFix
SPF won’t verify in ZohoCheck you used the include for your region, and that there’s only one SPF record.
DKIM won’t verifyCheck the host is zoho._domainkey without your domain repeated, the value was copied in full, and wait up to 48 hours.
DKIM verified but email isn’t signedYou still need to click Enable DKIM after verifying.
Two SPF recordsMerge every include: into one record and delete the other.
Newsletter or invoices still go to spamThat tool sends on its own servers. Add its SPF include, and turn on DKIM in that tool too.
DMARC stuck at p=noneIt protects nothing at this setting. Move through the stages above once reports are clean.

These records can break without warning

A website change, a new email tool or a DNS update can quietly undo this work. MailWatchman checks your domain every day and emails you the moment something changes, with the fix. Plans start at $6 a month.

Based on Zoho’s own instructions for SPF, DKIM and DMARC. Zoho occasionally renames menus; if a step looks different, the record values above stay the same. Using a different provider? See all our email setup guides. Curious how common this is? See our Santa Clara County email spoofing study.