Zoho Mail Email Verification

What Zoho's MX records look like

Domains hosted on Zoho Mail publish MX records pointing at mx.zoho.com, usually with mx2.zoho.com and mx3.zoho.com as backups at higher priority numbers. Regional Zoho data centres use equivalent hostnames under their own regional suffixes, so the same platform can appear under a slightly different hostname depending on where the tenant was provisioned. Mailthentic classifies a domain as Zoho hosted from the MX chain rather than the visible domain name, which is essential here: most Zoho mailboxes live on business domains that give no outward hint of who runs their mail.

How Zoho answers an SMTP probe

Zoho performs recipient validation during the SMTP conversation. A recipient that does not exist on the tenant draws a permanent rejection in the 550 family, typically with wording about an invalid recipient or relaying not being permitted, and a real mailbox draws a 250. That makes Zoho a provider where SMTP verification does real work: unlike Google and Microsoft, a 250 from Zoho on a non catch all tenant is a meaningful statement that the mailbox exists. Mailthentic opens the conversation, issues RCPT TO, and stops before DATA, so no message is ever sent.

Tenant configuration is the variable

Zoho is a business platform and its administrators have real control over recipient handling. Behaviour therefore varies by tenant configuration in ways it does not on a consumer service. An administrator can configure a catch all mailbox, in which case the domain accepts every recipient and no individual mailbox on it can be confirmed. Distribution lists, aliases and shared mailboxes all accept mail without corresponding to a single human. Some organisations put a third party security gateway in front of Zoho, in which case the MX points at the gateway and its recipient policy, not Zoho's, decides what you see at the SMTP layer.

This is exactly why Mailthentic probes each domain with a randomly generated local part before trusting any positive result. If the tenant rejects that random address, the domain is not catch all and a 250 on your target address is trustworthy. If the tenant accepts the random address, the domain is accept all and the honest verdict for every address on it is unconfirmed, regardless of how legitimate the address looks. Mailthentic will not report an accept-all domain as valid.

Rate limiting, deferrals and greylisting

Zoho throttles unfamiliar probing sources and returns temporary responses in the 421, 450 and 451 families when it wants a source to slow down. Greylisting, where a server temporarily refuses an unknown sender and expects a legitimate one to retry, produces the same kind of code. In neither case does the response say anything about the recipient. Mailthentic treats all three as deferrals, retries with a backoff, and only decides once it gets a stable permanent answer. Because every Zoho tenant shares the same MX cluster, it throttles by cluster rather than by domain, so a B2B batch containing many different Zoho hosted companies is paced against Zoho's endpoints as a whole rather than arriving as a burst.

So what does a Zoho result actually mean?

A 550 for an invalid recipient is a definitive answer and the address should be removed. A 250 on a tenant that rejected the random catch all probe is a real confirmation that the mailbox exists, and it is one of the more valuable verdicts you can get in a B2B list. A 250 on a tenant that accepted the random probe means only that the domain accepts everything, and Mailthentic reports that as accept-all and unconfirmed. An unknown verdict usually reflects a deferral rather than a problem with the address.

Read the catch all flag before you read the verdict

On a business platform like Zoho, the first question is not whether the address was accepted but whether the domain accepts everything. Mailthentic tells you this explicitly. On a tenant that rejected the random probe, a valid verdict is genuinely trustworthy and you can mail with confidence. On a catch all tenant, the same 250 means nothing about the individual mailbox, and you should treat the address the way you would treat any accept-all result: plausible, unproven, and best judged on other evidence.

What to do with each verdict

• Invalid. Zoho rejected the recipient outright. Suppress permanently.
• Valid on a non catch all tenant. A real confirmation. Mail it.
• Accept-all or unconfirmed. Do not delete automatically. Judge the address on how it was acquired, whether the local part follows the company's obvious naming pattern, whether it is a role address, and whether the contact has ever engaged. If you must send, send in a small, isolated batch and watch the bounce rate before committing the rest.
• Unknown or deferred. Almost always throttling. Re queue it later in a smaller batch.

B2B specifics worth remembering

Zoho lists are business lists, and business addresses decay faster than consumer ones because people change jobs. An address that verified cleanly six months ago may belong to somebody who has left, and Zoho will keep accepting mail for it if the tenant kept the mailbox or forwarded it. Re verify B2B lists on a regular cycle rather than treating a past verification as permanent. Be deliberate about role addresses too: info@, sales@ and support@ will usually verify as valid on a Zoho tenant, because they genuinely exist, but they land in shared inboxes and they are a common source of complaints. Keep them only if they are truly your audience.

Protecting deliverability into Zoho

• Authenticate. SPF, DKIM and DMARC on the sending domain are the baseline expectation.
• Warm up new IPs and domains gradually. Zoho will defer a cold source arriving with a large burst, and a deferral is a request to slow down rather than a rejection.
• Keep bounce rates low. Business tenants often run additional filtering on top of Zoho, and a high bounce rate is the fastest way to attract it.
• Honour unsubscribes immediately and keep your complaint rate down. On a small business tenant, a single annoyed administrator can block your domain outright.