Identity
58
B
zoho.com
Posture Score: 81/100
Scanned May 9, 2026 at 1:03 AM UTC
Attack Surface
84
Reputation
100
Identity Findings
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.zoho.com
FCrDNS mismatch: 204.141.33.23 → smtpin3.zoho.com does not resolve back
PTR for 204.141.33.23 is smtpin3.zoho.com, but smtpin3.zoho.com does not resolve back to 204.141.33.23.
💡 Ensure the PTR hostname resolves back to the original IP address.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.zoho.com/.well-known/mta-sts.txt
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 204.141.33.23 used by multiple MX servers
The IP 204.141.33.23 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 136.143.191.23 used by multiple MX servers
The IP 136.143.191.23 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
No CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
Very low TTL on MX records: 271s
3 MX records have a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A record: 258s
The A record has a TTL of 258s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on NS records: 272s
8 NS records have a TTL of 272s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 39s
22 TXT records have a TTL of 39s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 39s
The SPF record has a TTL of 39s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 271s
The DMARC record has a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=0
Failure reports generated when all authentication mechanisms fail.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on smtpin.zoho.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2026050803, Refresh: 7200s, Retry: 1800s, Expire: 1209600s, Min TTL: 3600s
Authorized certificate authorities
CAA records restrict certificate issuance to: digicert.com, letsencrypt.org, sectigo.com
Attack Surface Findings
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.zoho.com/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
19 subdomain(s) discovered for zoho.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for zoho.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled with preload on zoho.com
Strict-Transport-Security: max-age=64072000; includeSubDomains; preload
security.txt present
Found security.txt at https://zoho.com/.well-known/security.txt.
TLS certificate valid for 166 days
Certificate for zoho.com expires on 2026-10-22.
Certificate issued by Sectigo Public Server Authentication CA DV R36
The certificate for zoho.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for zoho.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for zoho.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for zoho.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on zoho.com.
Domain valid for 1713 days
Domain zoho.com expires on 2031-01-16.
Domain transfer and delete locks enabled
Domain zoho.com has clientTransferProhibited and clientDeleteProhibited locks.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.zoho.com
HTTPS request to https://webmail.zoho.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2004-01-16 | Expires: 2031-01-16 | Updated: 2025-10-23
WHOIS privacy protection not detected
Domain zoho.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: reject
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: smtpin.zoho.com
PTR record proves mail server legitimacy
MX: smtpin.zoho.com
Mail server at 204.141.33.23
→
PTR Record
Reverse DNS: smtpin3.zoho.com
Mail Server Identity: smtpin2.zoho.com
PTR record proves mail server legitimacy
MX: smtpin2.zoho.com
Mail server at 204.141.33.23
→
PTR Record
Reverse DNS: smtpin.zoho.com
Mail Server Identity: smtpin3.zoho.com
PTR record proves mail server legitimacy
MX: smtpin3.zoho.com
Mail server at 136.143.191.23
→
PTR Record
Reverse DNS: smtpin3.zoho.com
Mail Server Reputation: smtpin.zoho.com
RBL check ensures server is not blacklisted
MX: smtpin.zoho.com
Mail server at 204.141.33.23
→
RBL Status
Not blacklisted
Mail Server Reputation: smtpin2.zoho.com
RBL check ensures server is not blacklisted
MX: smtpin2.zoho.com
Mail server at 204.141.33.23
→
RBL Status
Not blacklisted
Mail Server Reputation: smtpin3.zoho.com
RBL check ensures server is not blacklisted
MX: smtpin3.zoho.com
Mail server at 136.143.191.23
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✓
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/zoho.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan zoho.com Again