Updated · Volt Ghost team
zoho.com and zohomail.com MX records
We read these records from Cloudflare's public DNS-over-HTTPS resolver on 30 October 2026. Both domains returned exactly the same three hosts.
| Priority | Mail server (MX host) | Role |
|---|---|---|
| 10 | smtpin.zoho.com | Primary |
| 20 | smtpin2.zoho.com | First backup |
| 50 | smtpin3.zoho.com | Second backup |
The gap between 20 and 50 doesn't change anything for a sender: only the order counts, so smtpin3 is simply the last resort. Each host returned one IPv4 address when we checked.
Business domains on Zoho use different hosts
The smtpin hosts belong to Zoho's own domains. A company that hosts its mail on Zoho Mail points its MX at mx.zoho.com, mx2.zoho.com and mx3.zoho.com, or at the .eu, .in or other regional versions if its account lives in that data centre. On 30 October 2026 those three names resolved too (mx.zoho.com to two IPv4 addresses, mx2 and mx3 to one each). Our email host lookup recognises all of these patterns and names Zoho Mail as the provider, whichever region the domain uses.
Zoho's sender authentication records
| Record | Where it lives | Value on 30 Oct 2026 |
|---|---|---|
| SPF | zoho.com TXT | v=spf1 include:spf.zoho.com include:zcsend.net include:spf.zohomail.com include:popspf.zohomail.com -all |
| SPF | zohomail.com TXT | v=spf1 include:spf.zohomail.com -all |
| DMARC | _dmarc.zoho.com TXT | v=DMARC1; p=reject; sp=reject; fo=0; rua=…; ruf=… (reports to a zoho.com address) |
| MTA-STS | _mta-sts.zoho.com TXT | No record found |
| TLS reporting | _smtp._tls.zoho.com TXT | v=TLSRPTv1;rua=mailto:[email protected] |
- Hard-fail SPF: both domains end their SPF with
-all, telling receivers to fail any server not listed. Proton and Fastmail end their own records with the softer~all. - DMARC p=reject: the strictest policy. Mail claiming to be from @zoho.com or @zohomail.com that fails SPF and DKIM alignment should be refused outright.
- TLS reporting without MTA-STS: Zoho asks for reports on TLS failures but did not publish an MTA-STS policy when we checked, so senders aren't told to require TLS.
Why look these up
Most people check Zoho's records while setting up their own domain, and the common mistake is copying the smtpin hosts from zoho.com instead of the mx hosts Zoho's console gives you. Developers sometimes check them when a sign-up form rejects or accepts a zohomail.com address unexpectedly. If you want to see what a received message's SPF and DMARC results were, paste its headers into our email header analyzer; for any other domain's raw records use the MX lookup.
Questions
What is the MX record for zoho.com?
zoho.com has three MX records: smtpin.zoho.com at priority 10, smtpin2.zoho.com at 20 and smtpin3.zoho.com at 50.
Are these the MX records I should use for my own domain on Zoho Mail?
Usually not. Business domains on Zoho Mail are pointed at mx.zoho.com, mx2.zoho.com and mx3.zoho.com (or the .eu or .in versions for those data centres). Use the values shown in your Zoho Mail admin console.
Does Zoho reject forged mail?
Its DMARC policy asks receivers to: zoho.com and zohomail.com both publish p=reject and sp=reject, the strictest DMARC setting.
Is zohomail.com a disposable email domain?
No. It is Zoho's permanent free mailbox domain and is not on the public disposable-domain list our checker uses.