zohosites.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns11.zns-53.com, ns21.zns-53.net, ns31.zns-53.com, ns41.zns-53.net; only in the zone: dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, pdns90.ultradns.org. dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net, ns1.zohocorp.com, ns11.zns-53.com, ns21.zns-53.net, ns31.zns-53.com, ns41.zns-53.net, pdns90.ultradns.biz, pdns90.ultradns.com, pdns90.ultradns.net, pdns90.ultradns.org report NS dns1.p09.nsone.net dns2.p09.nsone.net dns3.p09.nsone.net dns4.p09.nsone.net ns1.zohocorp.com pdns90.ultradns.biz pdns90.ultradns.com pdns90.ultradns.net pdns90.ultradns.org.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: zc-mx.zohocorp.com, zc-mx2.zohocorp.com, zc-mx3.zohocorp.com

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.103.197.150 (zc-mx.zohocorp.com), 103.103.197.150 (zc-mx3.zohocorp.com). Ask your hosting provider to set one.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.