zoho.com is a free email provider

zoho.com is a major consumer mailbox provider. Anyone can open an address, and at this scale a forged message is usually caught by the provider even where the domain's own records would let it through.

89 /100

Strong

Email authentication report card

What zoho.com publishes in DNS to stop other people sending mail in its name, read record by record.

2 pass 2 weak 1 fail

Can mail be forged as this domain?

No, a forgery is rejected

DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.

  • Fail

    SPF No record

    No SPF record is published, so receivers have no list of hosts allowed to send as this domain.

  • Pass

    DMARC p=reject

    Receivers are asked to reject any message that fails DMARC. This is the strongest published setting.

  • Weak

    MTA-STS Not published

    No MTA-STS policy, so a sending server has nothing that tells it to insist on verified TLS for this domain.

  • Weak

    DNSSEC Not signed

    The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.

  • Pass

    TLS-RPT Published

    Sending servers have an address to report failed TLS deliveries to.

Why it scores 89?

  1. Registered more than five years ago.
  2. DMARC is published and enforced, so forged mail is rejected or quarantined.
  3. Accepts mail through 3 MX hosts.

What to publish to close the gaps

The records zoho.com is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.

  1. Publish an SPF record

    Namezoho.com
    TypeTXT
    Valuev=spf1 include:<your mail platform> -all

    List every platform that sends on your behalf, then end the record in -all so everything else fails.

  2. Publish an MTA-STS policy

    Name_mta-sts.zoho.com
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

    Serve the policy body at https://mta-sts.zoho.com/.well-known/mta-sts.txt, start it in testing mode, then switch it to enforce so senders refuse to deliver over an unverified connection.

  3. Sign the zone with DNSSEC

    Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.

Questions about zoho.com

Every answer below is generated from the stored record for this domain.

Is zoho.com a disposable email domain?
No. zoho.com is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is zoho.com spoofable?
No, a forgery is rejected. DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.
Does zoho.com publish SPF and DMARC?
zoho.com publishes no SPF record, so no receiver is told which hosts may send in its name. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for zoho.com?
Mail for zoho.com is handled by Zoho Mail, which carries 18 other domains we track.
How old is the zoho.com domain?
The zoho.com domain was registered 22 years ago. The registrar of record is MarkMonitor Inc.
How do I block zoho.com on my signup form?
We do not classify zoho.com as disposable, so blocking it outright would turn away real people. If you want to act on it, decide on the signals listed above rather than the name.
Can I trust email from zoho.com?
zoho.com scores 89 out of 100, which is a strong band. The score is a summary of the classification, infrastructure, authentication, reputation and lifecycle signals we hold, not a judgment about any individual sender at that domain.

Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.