Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 24 Apr 2026, 14:25 UTC
Duration 18.9s
Version v26.47.06
Integrity 99cac91d2d25053d0e99c1c3474928ed98baa9a81e8581fe4c46212c3318e828c65497961cad80a5abb9e85b243777164331f9544393e47050b5ac6c3209a4b9
Subject Domain
zoho.com

Engineer's DNS Intelligence Report

zoho.com
24 Apr 2026, 14:25 UTC · 18.9s ·v26.47.06 · SHA-3-512: 99ca✱✱✱✱ Verify ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint Zoho Mail 2 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
5 protocols configured, 3 not configured, 1 unavailable on provider Why we go beyond letter grades
1 monitoring
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 64% Currency 66/100 Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Stale
ICuAE Details
DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type Observed TTL Typical TTL Severity Context
NS 92s 1 day (86400s) high NS TTL is below typical — observed 92s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX 10s 1 hour (3600s) high MX TTL is below typical — observed 10s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
A 4 minutes (240s) 1 hour (3600s) high A TTL is below typical — observed 4 minutes (240s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT 215s 1 hour (3600s) high TXT TTL is below typical — observed 215s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
SOA 5 minutes (300s) 1 hour (3600s) high SOA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
CAA 5 minutes (300s) 1 hour (3600s) high CAA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for zoho.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.
Primary NS ns1.zohocorp.com
Serial 2026042402
Admin dnsadmin.vtitan.com
Provider Unknown
Timer Value RFC 1912 Range
Refresh7200s1,200–43,200s (20 min – 12 hrs)
Retry1800sFraction of Refresh
Expire1209600s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)3600s300–86,400s (5 min – 1 day)
All SOA timer values are within RFC 1912 recommended ranges.
Suggested Scanner Configuration High Confidence
Based on 19 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 30.5s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Configured
Monitoring
DKIM signing inferred from provider — could not directly verify selector
Configured
SPF (hard fail), DMARC (reject), DKIM (inferred via Zoho Mail), TLS-RPT, CAA
Not Configured
MTA-STS, BIMI, DNSSEC
Unavailable on Provider
DANE
Priority Actions Achievable posture: Secure
Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035
Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.
TypeTXT
Hostdefault._bimi.zoho.com (BIMI default record)
Valuev=BIMI1; l=https://zoho.com/brand/logo.svg
RFC 9495
Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.zoho.com (MTA-STS policy record)
Valuev=STSv1; id=zoho.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Where domain was purchased
Email Service Provider INFERRED
Zoho Mail
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting OBSERVED
UltraDNS (Neustar/Vercara)
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Consistent

Does this domain declare who may send email on its behalf? Yes
Success -all 3/10 lookups

SPF valid with strict enforcement (-all), 3/10 lookups

v=spf1 include:spf.zoho.com include:zcsend.net include:spf.zohomail.com -all
RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Consistent

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; sp=reject; fo=0; rua=mailto:dmarcaggregation@zoho.com; ruf=mailto:dmarcaggregation@zoho.com
Alignment: SPF relaxed DKIM relaxed sp=reject
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Consistent

Are outbound emails cryptographically signed? Provider-managed
Provider Verified

DKIM not discoverable via common selectors (large providers use rotating selectors)

Zoho Mail detected as primary mail platform — DKIM signing is managed by the provider. The primary provider may use custom selectors not discoverable through standard checks.
Know your DKIM selector? Re-scan with a custom selector to verify.
RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Consistent

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Consistent

Will failures in TLS delivery be reported? Yes — reports configured
Success

TLS-RPT configured - receiving TLS delivery reports

v=TLSRPTv1;rua=mailto:tlsaggregation@zoho.com
DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Zoho Mail does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Zoho Mail

Zoho Mail does not publish DANE/TLSA records for its MX hosts.

Recommended alternative: MTA-STS

Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain has neither DANE nor MTA-STS. Since Zoho Mail does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Consistent Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Consistent Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only Sectigo, Let's Encrypt, DigiCert can issue certificates

Authorized CAs: Sectigo Let's Encrypt DigiCert
0 issue "sectigo.com"
0 issue "letsencrypt.org"
0 issue "digicert.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

security.txt properly configured

Contact

https://bugbounty.zohocorp.com/bb/#/submitbug
mailto:security@zohocorp.com

Expires

2026-06-30 Valid

Encryption

https://www.zohocorp.com/security/zoho-security-pub.txt

Policy

https://bugbounty.zohocorp.com/bb/info
en Canonical URL
Source: https://zoho.com/.well-known/security.txt
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt View robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
TypeDetailSeverityConfidence
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
Sources scanned (1)
  • https://zoho.com/
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

DNS Server Security Hardened

No DNS server misconfigurations found on pdns90.ultradns.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Test inconclusive
Open Recursion Disabled Test inconclusive
Nameserver Identity Hidden Test inconclusive
Cache Snooping Protected Test inconclusive

Tested nameservers: pdns90.ultradns.com, ns31.zns-53.com, ns21.zns-53.net, pdns90.ultradns.biz, ns11.zns-53.com, ns1.zohocorp.com, ns41.zns-53.net, pdns90.ultradns.net

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns1.zohocorp.com No N/A N/A OK
ns11.zns-53.com No N/A N/A OK
ns21.zns-53.net No N/A N/A OK
ns31.zns-53.com No N/A N/A OK
ns41.zns-53.net No N/A N/A OK
pdns90.ultradns.biz No N/A N/A OK
pdns90.ultradns.com No N/A N/A OK
pdns90.ultradns.net No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 300s Drift: 0s

SOA Serial Consistency Consistent

ns1.zohocorp.com: 2.026042402e+09
ns11.zns-53.com: 2.026042402e+09
ns21.zns-53.net: 2.026042402e+09
ns31.zns-53.com: 2.026042402e+09
ns41.zns-53.net: 2.026042402e+09
pdns90.ultradns.biz: 2.026042402e+09
pdns90.ultradns.com: 2.026042402e+09
pdns90.ultradns.net: 2.026042402e+09
Nameserver Fleet Matrix Healthy

Analyzed 8 nameserver(s) for zoho.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns21.zns-53.net 136.143.173.99 2602:801:c00b::99 AS397849 2026042402
ns11.zns-53.com 136.143.172.88 2602:801:c00a::88 AS397849 2026042402
pdns90.ultradns.biz 156.154.66.90 2610:a1:1015::7e AS12008 2026042402
ns41.zns-53.net 169.148.152.99 2602:801:c00c::99 AS397849 2026042402
ns31.zns-53.com 169.148.151.88 2602:801:c00c::88 AS397849 2026042402
pdns90.ultradns.net 156.154.65.90 2610:a1:1014::7e AS12008 2026042402
pdns90.ultradns.com 156.154.64.90 2001:502:f3ff::7e AS12008 2026042402
ns1.zohocorp.com 156.154.67.90 2001:502:4612::7e AS12008 2026042402
Unique ASNs
2
Unique Operators
0
Unique /24 Prefixes
8
Diversity Score
Good

2 ASNs, 8 /24 prefixes across 8 nameservers

Mail Transport Security Beta Is mail transport encrypted and verified? Partially TLS reporting is configured but no transport enforcement policy is active

All 3 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • TLS-RPT configured — domain monitors TLS delivery failures (RFC 8460)
Telemetry
TLS-RPT configured — domain receives reports about TLS delivery failures from sending mail servers (RFC 8460)
Reporting to: mailto:tlsaggregation@zoho.com
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
smtpin2.zoho.com TLSv1.3 TLS_AES_256_GCM_SHA384 Valid
Expires: 2027-01-29 (280 days)
Issuer: DigiCert Inc
smtpin.zoho.com TLSv1.3 TLS_AES_256_GCM_SHA384 Valid
Expires: 2027-01-29 (280 days)
Issuer: DigiCert Inc
smtpin3.zoho.com TLSv1.3 TLS_AES_256_GCM_SHA384 Valid
Expires: 2027-01-29 (280 days)
Issuer: DigiCert Inc
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 1 responded
US-East (Boston) observed
All servers support TLS
France - EU skipped
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 1 IP address(es)

ASNNameCountry
AS2639 US
IPv4 Mappings:
204.141.42.155 → AS2639 (204.141.42.0/23)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 2 services

2 SaaS services detected via DNS TXT verification records

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

ServiceVerification Record
Google Workspace google-site-verification=HJDhZb7eVwcBS1ZHYfa3zJKD7Ta5OlTtjGODvld90vs
HubSpot hubspot-developer-verification=ODRmYWExODEtMjBjMS00NTczLThhODgtZGFhZmFjZThkMjcz
Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Consistent Unsigned

DNSSEC not configured - DNS responses are unsigned

Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.
Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.

NS Delegation Verified

8 nameserver(s) configured

Nameservers: 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
Managed DNS
All 8 nameservers hosted by UltraDNS (Neustar/Vercara). Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): UltraDNS (Neustar/Vercara)
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (2 differences found)
Resolver Differences:
TXT: OpenDNS returned different results: [ 2nb6vfc9zm9t9f941qhzh8c66z5x6lxp 5d7tzsjx9vpr6dwqfd9910mkffcr1893 OSSRH-65508 _7w86ubhx27sgdoo84npral89s33t2u3 _9xdko5m9wh9tx7q8vz3vs0eo2y6l239 _cxpexq0rrrkb0kkkz3mc1v37kl4dsrp _op091a6o68i6m2yma8y9axhq463xldm openai-domain-verification=dv-cZm3nfyBwGQo4BZTvFnA8KfA qm36k1hcyk8f6rcncfpj7ngl5708cvhl vgsr5l5dhfv2qr8g5ntl0w9jn9tnqr94]
NS: Quad9 returned different results: [NS11.ZNS-53.com. NS21.ZNS-53.NET. NS31.ZNS-53.com. NS41.ZNS-53.NET. PDNS90.ULTRADNS.BIZ. PDNS90.ULTRADNS.NET. PDNS90.ULTRADNS.com. ns1.zohocorp.com.]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

204.141.42.155
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

10 smtpin.zoho.com.
20 smtpin2.zoho.com.
50 smtpin3.zoho.com.
Priority + mail server for email delivery
Zoho Mail

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (1 IPv4, 0 IPv6) Mail: 3 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 207 subdomains discovered
How did we find these?
CT logs unavailable 207 current 0 expired 54 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
account.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
accounts-ro.zoho.com CT Log Current — 1 2026-04-09T00:00:00Z
accounts.zoho.com CT Log Current — 1 2026-04-09T00:00:00Z
admin.zoho.com DNS Current accounts.zoho.com 7 2025-03-27 —
analytics.zoho.com DNS Current — 7 2025-03-27 —
api.catalyst.zoho.com CT Log Current — 2 2026-03-08T03:52:09Z
api.marketplace-ro.zoho.com CT Log Current — 1 2025-11-21T00:00:00Z
api.marketplace.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
api.wiki.zoho.com CT Log Current — 2 2026-03-16T20:06:45Z
api.zoho.com DNS Current zs-lc3-19.zoho.com 7 2025-03-27 —
apihelp.zoho.com CT Log Current — 2 2026-03-16T20:06:45Z
apps.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
assets.zoho.com DNS Current zs-us4-lc2.zoho.com 7 2025-03-27 —
auth.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
autodiscover.zoho.com DNS Current mailadmin.zoho.com 7 2025-03-27 —
b.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
bi.zoho.com DNS Current reports.zoho.com 7 2025-03-27 —
billing.zoho.com DNS Current zs-us4-lcbooks-h2.zoho.com 7 2025-03-27 —
blog.zoho.com CT Log Current — 1 2025-11-09T00:00:00Z
blogs.zoho.com CT Log Current — 1 2025-11-09T00:00:00Z
blogsint.zoho.com CT Log Current — 2 2025-10-10T00:00:00Z
booking.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
calendar.zoho.com DNS Current zs-lc1-19-h2.zoho.com 7 2025-03-27 —
campaign.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
campaigns.zoho.com DNS Current — 7 2025-03-27 —
catalyst-ro.zoho.com CT Log Current — 2 2026-03-24T17:52:42Z
catalyst.zoho.com CT Log Current — 2 2026-03-24T17:52:42Z
cdn.zoho.com CT Log Current — 2 2025-09-26T00:00:00Z
chat.zoho.com DNS Current cliq.zoho.com 7 2025-03-27 —
checkout.zoho.com DNS Current — 7 2025-03-27 —
cloud-edgetesting.zoho.com CT Log Current — 4 2026-01-24T19:23:24Z
cloud.zoho.com DNS Current — 7 2025-03-27 —
code.zoho.com DNS Current zs-us4-lc3.zoho.com 7 2025-03-27 —
commerceplus.zoho.com CT Log Current — 7 2026-02-15T21:02:33Z
community.zoho.com DNS Current — 7 2025-03-27 —
connect.zoho.com DNS Current zs-lc2-19.zoho.com 7 2025-03-27 —
console.catalyst.zoho.com CT Log Current — 2 2026-03-08T03:52:09Z
contacts.zoho.com CT Log Current — 8 2026-02-11T03:34:50Z
crm-dataiq.zoho.com CT Log Current — 4 2026-03-06T03:57:00Z
crm-download.zoho.com CT Log Current — 2 2026-03-11T18:30:25Z
crm-g11-sandbox.zoho.com CT Log Current — 4 2026-01-28T00:06:05Z
crm-us4-download-accl.zoho.com CT Log Current — 2 2026-03-13T15:06:35Z
crm-us4-download.zoho.com CT Log Current — 2 2026-03-13T15:06:35Z
crm.zoho.com CT Log Current — 2 2025-08-01T00:00:00Z
crmrelease-internal.crm.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
crmreleasesandbox-internal.crm.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
csuiteinfo.zoho.com CT Log Current — 2 2026-03-18T14:15:14Z
customer-books.zoho.com CT Log Current — 2 2026-03-22T23:45:19Z
customer-campaign.zoho.com CT Log Current — 2 2026-03-06T03:56:14Z
customer-creator.zoho.com CT Log Current — 4 2026-02-05T06:02:55Z
customer-expense.zoho.com CT Log Current — 2 2026-03-08T00:32:50Z
customer-invoice.zoho.com CT Log Current — 5 2026-02-11T21:57:06Z
customer-mail.zoho.com CT Log Current — 2 2026-03-10T14:58:29Z
customer-reports.zoho.com CT Log Current — 8 2026-01-28T13:04:25Z
customer-survey.zoho.com CT Log Current — 4 2026-02-09T18:02:31Z
customer-wiki.zoho.com CT Log Current — 3 2026-03-19T03:30:09Z
customer-wms.zoho.com CT Log Current — 2 2026-03-04T12:12:08Z
customer1-creator.zoho.com CT Log Current — 4 2026-01-26T12:59:09Z
customer1-recruit.zoho.com CT Log Current — 5 2026-01-25T12:14:45Z
d.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
db.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
developer.zoho.com DNS Current platform.zoho.com 7 2025-03-27 —
developers.zoho.com DNS Current platform.zoho.com 7 2025-03-27 —
dino-hunt.deluge.zoho.com CT Log Current — 12 2026-03-13T09:57:06Z
directory.zoho.com CT Log Current — 2 2025-09-03T00:00:00Z
discuss.zoho.com DNS Current discussions.zoho.com 7 2025-03-27 —
discussions.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
docs.fortify-ro.zoho.com CT Log Current — 2 2026-03-06T03:57:28Z
docs.fortify.zoho.com CT Log Current — 2 2026-03-06T03:57:28Z
docs.zoho.com DNS Current — 7 2025-03-27 —
docssandbox.zoho.com CT Log Current — 4 2026-03-24T17:59:59Z
domain.zoho.com CT Log Current — 2 2026-03-13T20:11:50Z
domains.zoho.com CT Log Current — 1 2025-09-09T00:00:00Z
download.zoho.com DNS Current — 7 2025-03-27 —
ecommerce.zoho.com DNS Current zs-lc1-25-h2.zoho.com 7 2025-03-27 —
erp.zoho.com DNS Current zs-us4-lcinternal.zoho.com 7 2025-03-27 —
events.zoho.com DNS Current — 7 2025-03-27 —
forms.zoho.com DNS Current zs-us4-lcpci-dss-h2.zoho.com 7 2025-03-27 —
forum.zoho.com DNS Current discussions.zoho.com 7 2025-03-27 —
forums.catalyst.zoho.com CT Log Current — 34 2026-02-05T20:17:17Z
forums.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
go.zoho.com DNS Current tu.zoho.com 7 2025-03-27 —
help.api.zoho.com CT Log Current — 2 2026-03-16T20:06:45Z
help.zoho.com CT Log Current — 2 2026-03-11T10:32:40Z
host.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
imap.zoho.com DNS Current — 7 2025-03-27 —
integrations.zoho.com CT Log Current — 10 2026-01-28T08:55:06Z
internal.accounts.zoho.com CT Log Current — 1 2026-04-09T00:00:00Z
internal.crm.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
internal.marketplace.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
internal.signals.zoho.com CT Log Current — 8 2026-02-15T19:15:17Z
internal2.crm.zoho.com CT Log Current — 2 2025-07-22T00:00:00Z
inventory.zoho.com DNS Current zs-us4-lcbooks-h2.zoho.com 7 2025-03-27 —
invoice.zoho.com DNS Current — 7 2025-03-27 —
ir.zoho.com DNS Current — 7 2025-03-27 —
issuing.zoho.com CT Log Current — 1 2025-12-15T00:00:00Z
kbase.creator.zoho.com CT Log Current — 2 2026-03-16T20:06:45Z
kites-ro.zoho.com CT Log Current — 4 2026-03-21T14:47:08Z
kites.zoho.com CT Log Current — 4 2026-03-21T14:47:08Z
ldap.directory.zoho.com CT Log Current — 1 2025-09-12T00:00:00Z
learn.zoho.com DNS Current zs-lc1-19-h2.zoho.com 7 2025-03-27 —
linkthread.zoho.com CT Log Current — 8 2026-02-04T22:11:31Z
live.zoho.com DNS Current zs-lc3-19.zoho.com 7 2025-03-27 —
livecontent.zoho.com CT Log Current — 4 2026-02-13T15:04:02Z
logs.zoho.com DNS Current — 7 2025-03-27 —
lprezoho.zoho.com CT Log Current — 2 2026-04-08T21:36:00Z
m.zoho.com DNS Current mobile.zoho.com 7 2025-03-27 —
mail.zoho.com DNS Current — 7 2025-03-27 —
mailer-lp.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
mailer-tu.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
maps.zoho.com DNS Current — 7 2025-03-27 —
marketing.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
marketplace.zoho.com CT Log Current — 4 2026-03-08T10:38:21Z
mdm.zoho.com DNS Current zs-us4-lcgiant.manageengine.com 7 2025-03-27 —
media.livecontent.zoho.com CT Log Current — 1 2026-03-12T05:35:39Z
media.zoho.com DNS Current zohostatic.com 7 2025-03-27 —
meet.zoho.com DNS Current tu.zoho.com 7 2025-03-27 —
meeting.zoho.com DNS Current — 7 2025-03-27 —
memktg.wiki.zoho.com CT Log Current — 4 2026-02-15T21:02:33Z
mobile-transmail.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
mobile.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
mproxy-transmail.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
mx.zoho.com DNS Current — 7 2025-03-27 —
mx2.zoho.com DNS Current — 7 2025-03-27 —
mx3.zoho.com DNS Current — 7 2025-03-27 —
nimbus-certtest.zoho.com CT Log Current — 6 2026-01-26T15:21:27Z
notification-kms.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
notification.bugbounty.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
notifications-sd.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
notifications.antivirus.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
notifymw.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
office.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
partner.zoho.com DNS Current store.zoho.com 7 2025-03-27 —
partners.zoho.com DNS Current store.zoho.com 7 2025-03-27 —
pay.zoho.com DNS Current zs-us4-lcpay.zoho.com 7 2025-03-27 —
payment.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
payments.zoho.com DNS Current zs-us4-lcpay.zoho.com 7 2025-03-27 —
payroll.zoho.com DNS Current zs-us4-lcbooks-h2.zoho.com 7 2025-03-27 —
platformai-ro.zoho.com CT Log Current — 4 2026-03-20T07:08:38Z
platformai.zoho.com CT Log Current — 6 2026-03-20T07:08:38Z
pop.zoho.com DNS Current — 7 2025-03-27 —
predesk.zoho.com CT Log Current — 4 2026-02-18T09:50:32Z
predocsutil.zoho.com CT Log Current — 4 2026-02-18T09:50:32Z
preexpense.zoho.com CT Log Current — 4 2026-02-10T03:38:38Z
premics.zoho.com CT Log Current — 2 2026-04-16T10:13:36Z
presandbox.zoho.com CT Log Current — 4 2026-01-24T16:28:38Z
presolutions-ro.zoho.com CT Log Current — 4 2026-01-31T12:40:01Z
presolutions.zoho.com CT Log Current — 8 2026-01-31T12:40:01Z
prestore.agents-ro.zoho.com CT Log Current — 4 2026-02-07T19:25:51Z
prestore.agents.zoho.com CT Log Current — 4 2026-02-07T19:25:51Z
presupport.zoho.com CT Log Current — 4 2026-02-18T09:50:32Z
preus3-zvpmsrs.zoho.com CT Log Current — 1 2026-01-27T00:00:00Z
preus4-zvpmsrs.zoho.com CT Log Current — 1 2026-01-27T00:00:00Z
prewiki-ro.zoho.com CT Log Current — 4 2026-03-08T10:36:43Z
prewiki.zoho.com CT Log Current — 4 2026-03-08T10:36:43Z
prewww.zoho.com CT Log Current — 3 2026-04-16T00:00:00Z
prezoho.zoho.com CT Log Current — 1 2025-08-12T00:00:00Z
prezohoweb.zoho.com CT Log Current — 2 2026-03-09T17:00:04Z
profile.zoho.com DNS Current contacts.zoho.com 7 2025-03-27 —
qaasw.zoho.com CT Log Current — 2 2026-03-28T04:09:59Z
qengine-tunnel.zoho.com CT Log Current — 4 2025-07-08T00:00:00Z
queue.zoho.com DNS Current — 7 2025-03-27 —
recruit.zoho.com DNS Current zs-lc1-25-h2.zoho.com 7 2025-03-27 —
repo-archive.zoho.com CT Log Current — 4 2026-02-13T13:15:43Z
report.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
reporting.zoho.com DNS Current zurs.zoho.com 7 2025-03-27 —
reports.zoho.com DNS Current — 7 2025-03-27 —
sandbox.zoho.com CT Log Current — 4 2026-01-24T16:28:38Z
sandboxlab-ro.zoho.com CT Log Current — 8 2026-02-10T04:40:11Z
sandboxlab.zoho.com CT Log Current — 8 2026-02-10T04:40:11Z
scanner.zoho.com DNS Current zs-lc3-19.zoho.com 7 2025-03-27 —
search.zoho.com DNS Current zs-lc1-19.zoho.com 7 2025-03-27 —
search360alerts.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
signwebhook.zoho.com CT Log Current — 1 2026-01-21T00:00:00Z
smtp.zoho.com DNS Current — 7 2025-03-27 —
solutions.zoho.com CT Log Current — 6 2026-01-29T00:00:00Z
status-internal.zoho.com CT Log Current — 2 2026-03-03T13:23:08Z
status.zoho.com CT Log Current — 11 2026-01-25T03:02:51Z
store.agents-ro.zoho.com CT Log Current — 4 2026-02-10T12:36:38Z
store.agents.zoho.com CT Log Current — 4 2026-02-10T12:36:38Z
store.zoho.com DNS Current — 7 2025-03-27 —
support.zoho.com DNS Current — 7 2025-03-27 —
survey.zoho.com DNS Current zs-lc2-19-h2.zoho.com 7 2025-03-27 —
tu-test.zoho.com CT Log Current — 9 2026-02-20T21:03:32Z
tv.zoho.com CT Log Current — 2 2026-03-09T08:20:37Z
upload.zoho.com DNS Current — 7 2025-03-27 —
us3-zvpmsrs.zoho.com CT Log Current — 1 2026-01-27T00:00:00Z
us4-zvpmsrs.zoho.com CT Log Current — 1 2026-01-27T00:00:00Z
usa-help.zoho.com CT Log Current — 5 2026-02-13T07:32:48Z
vault.zoho.com DNS Current — 7 2025-03-27 —
video.zoho.com DNS Current zs-us4-lcinternal.zoho.com 7 2025-03-27 —
webinar.zoho.com DNS Current — 7 2025-03-27 —
wiki-ro.zoho.com CT Log Current — 2 2025-05-06T00:00:00Z
wiki.zoho.com CT Log Current — 6 2025-05-06T00:00:00Z
workspace.zoho.com DNS Current zs-us4-lc4.zoho.com 7 2025-03-27 —
wpstatus.zoho.com CT Log Current — 5 2026-02-17T16:25:41Z
www.domains.zoho.com CT Log Current — 1 2025-09-09T00:00:00Z
www.issuing.zoho.com CT Log Current — 1 2025-12-15T00:00:00Z
www.ldap.directory.zoho.com CT Log Current — 1 2025-09-12T00:00:00Z
www.prewww.zoho.com CT Log Current — 3 2026-04-16T00:00:00Z
www.prezoho.zoho.com CT Log Current — 1 2025-08-12T00:00:00Z
www.signwebhook.zoho.com CT Log Current — 1 2026-01-21T00:00:00Z
www.zoho.com CT Log Current — 6 2025-09-26T00:00:00Z
zohosites.wiki.zoho.com CT Log Current — 2 2026-03-16T20:06:45Z
zohotv.zoho.com CT Log Current — 2 2026-03-09T08:20:37Z
zurs-1.zoho.com CT Log Current — 4 2026-02-15T21:02:33Z
zurs.zoho.com CT Log Current — 2 2026-04-02T18:02:31Z
Export Recon (CSV)
Δ Changes Detected: TXT Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 1 / 1 records
204.141.42.155
204.141.42.155
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 Synchronized 3 / 3 records
0 issue "sectigo.com"
0 issue "digicert.com"
0 issue "letsencrypt.org"
0 issue "letsencrypt.org"
0 issue "digicert.com"
0 issue "sectigo.com"
DMARC _dmarc.zoho.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; sp=reject; fo=0; rua=mailto:dmarcaggregation@zoho.com; ruf=mailto:dmarcaggregation@zoho.com
v=DMARC1; p=reject; sp=reject; fo=0; rua=mailto:dmarcaggregation@zoho.com; ruf=mailto:dmarcaggregation@zoho.com
MX RFC 5321 Synchronized 3 / 3 records
10 smtpin.zoho.com.
10 smtpin.zoho.com.
20 smtpin2.zoho.com.
20 smtpin2.zoho.com.
50 smtpin3.zoho.com.
50 smtpin3.zoho.com.
NS RFC 1035 Synchronized 8 / 8 records
ns1.zohocorp.com.
ns1.zohocorp.com.
ns11.zns-53.com.
ns11.zns-53.com.
ns21.zns-53.net.
ns21.zns-53.net.
ns31.zns-53.com.
ns31.zns-53.com.
ns41.zns-53.net.
ns41.zns-53.net.
pdns90.ultradns.biz.
pdns90.ultradns.biz.
pdns90.ultradns.com.
pdns90.ultradns.com.
pdns90.ultradns.net.
pdns90.ultradns.net.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.zohocorp.com. dnsadmin.vtitan.com. 2026042402 7200 1800 1209600 3600
ns1.zohocorp.com. dnsadmin.vtitan.com. 2026042402 7200 1800 1209600 3600
TLS-RPT _smtp._tls.zoho.com RFC 8460 §3 Synchronized 1 / 1 records
v=TLSRPTv1;rua=mailto:tlsaggregation@zoho.com
v=TLSRPTv1;rua=mailto:tlsaggregation@zoho.com
TXT RFC 7208 §4 Propagating 23 / 1 records
2nb6vfc9zm9t9f941qhzh8c66z5x6lxp
OSSRH-65508
5d7tzsjx9vpr6dwqfd9910mkffcr1893
—
OSSRH-65508
—
_7w86ubhx27sgdoo84npral89s33t2u3
—
_9xdko5m9wh9tx7q8vz3vs0eo2y6l239
—
_cxpexq0rrrkb0kkkz3mc1v37kl4dsrp
—
_op091a6o68i6m2yma8y9axhq463xldm
—
google-site-verification=HJDhZb7eVwcBS1ZHYfa3zJKD7Ta5OlTtjGODvld90vs
—
google-site-verification=SEMszgPBLwGVsVcKzkWqXFsgw8B2IbSPm3X5lVMnoLY
—
google-site-verification=mQpZgdgWartH2aVfQgUPDRJ5AR2qqfCdGHtQqqNWBWw
—
google-site-verification=npo_5EGYt0elo-8NI3LdXc77FK2_lnKC5z4y_dHcxL0
—
hubspot-developer-verification=ODRmYWExODEtMjBjMS00NTczLThhODgtZGFhZmFjZThkMjcz
—
openai-domain-verification=dv-cZm3nfyBwGQo4BZTvFnA8KfA
—
postman-domain-verification=034222fcdc924fe91765763089a17ed482c4ae518ded4bb86a19ec03e744d91fce586e8c4da2b9a464a632414abde6331277fb126c22d70426869b6207a8bd1c
—
postman-domain-verification=9783fef3f967a95d9ae1b2e487850866e686c1b446fb385b037d7f8031b09aee0524196e7274f8ed956df0139866ff36f9d04db18d9d3baf897dcffd1ed34711
—
qm36k1hcyk8f6rcncfpj7ngl5708cvhl
—
site24x7-signals-domain-verification=ccec90b648534446606c200af00e9295
—
site24x7-signals-domain-verification=df57290b9f0e5eb1fbcaca5849cc43b5
—
tiktok-developers-site-verification=8r8evNiFT1R72lVTisYkXtd7MUXuDoy1
—
v=spf1 include:spf.zoho.com include:zcsend.net include:spf.zohomail.com -all
—
vgsr5l5dhfv2qr8g5ntl0w9jn9tnqr94
—
zoho-nimbus-mrePMidEyuuAwUlwP+s2IbAqvJIO0MkIbdfSbpojeiU=
—
zoom-domain-verification=e4699571-2e14-4588-bfe0-471a645d4059
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

99cac91d2d25053d0e99c1c3474928ed98baa9a81e8581fe4c46212c3318e828c65497961cad80a5abb9e85b243777164331f9544393e47050b5ac6c3209a4b9
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 24 Apr 2026, 14:25 UTC.
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-zoho.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-zoho.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-zoho.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-zoho.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/15884/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for zoho.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer zoho.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer zoho.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer zoho.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer zoho.com NS
Query TXT records RFC 1035 
dig +noall +answer zoho.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short zoho.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.zoho.com TXT
Check DKIM key for selector 'default' RFC 6376 
dig +short default._domainkey.zoho.com TXT
Check DKIM key for selector 'google' RFC 6376 
dig +short google._domainkey.zoho.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.zoho.com TXT
Check DKIM key for selector 'selector2' RFC 6376 
dig +short selector2._domainkey.zoho.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer zoho.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer zoho.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd zoho.com A @1.1.1.1

Transport Security

Check TLSA record for smtpin.zoho.com RFC 7672 
dig +noall +answer _25._tcp.smtpin.zoho.com TLSA
Check TLSA record for smtpin2.zoho.com RFC 7672 
dig +noall +answer _25._tcp.smtpin2.zoho.com TLSA
Check TLSA record for smtpin3.zoho.com RFC 7672 
dig +noall +answer _25._tcp.smtpin3.zoho.com TLSA
Verify TLS certificate on primary MX (smtpin.zoho.com) RFC 6698 
openssl s_client -starttls smtp -connect smtpin.zoho.com:25 -servername smtpin.zoho.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.zoho.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.zoho.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.zoho.com TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.zoho.com TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer zoho.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer zoho.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer zoho.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/zoho.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (smtpin.zoho.com) RFC 3207 
openssl s_client -starttls smtp -connect smtpin.zoho.com:25 -servername smtpin.zoho.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.zoho.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116 
curl -sL https://zoho.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://zoho.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://zoho.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 204.141.42.155 (Team Cymru) 
dig +short 155.42.141.204.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent 15107 runs
DKIM
Consistent 14884 runs
DMARC
Consistent 15088 runs
DANE/TLSA
Consistent 14866 runs
DNSSEC
Consistent 15065 runs
BIMI
Consistent 14881 runs
MTA-STS
Consistent 14902 runs
TLS-RPT
Consistent 14917 runs
CAA
Consistent 14914 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer zoho.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer zoho.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer zoho.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer zoho.com NS
Query TXT records (RFC 1035) 
dig +noall +answer zoho.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short zoho.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.zoho.com TXT
Check DKIM key for selector 'default' (RFC 6376) 
dig +short default._domainkey.zoho.com TXT
Check DKIM key for selector 'google' (RFC 6376) 
dig +short google._domainkey.zoho.com TXT
Check DKIM key for selector 'selector1' (RFC 6376) 
dig +short selector1._domainkey.zoho.com TXT
Check DKIM key for selector 'selector2' (RFC 6376) 
dig +short selector2._domainkey.zoho.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer zoho.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer zoho.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd zoho.com A @1.1.1.1

Transport Security

Check TLSA record for smtpin.zoho.com (RFC 7672) 
dig +noall +answer _25._tcp.smtpin.zoho.com TLSA
Check TLSA record for smtpin2.zoho.com (RFC 7672) 
dig +noall +answer _25._tcp.smtpin2.zoho.com TLSA
Check TLSA record for smtpin3.zoho.com (RFC 7672) 
dig +noall +answer _25._tcp.smtpin3.zoho.com TLSA
Verify TLS certificate on primary MX (smtpin.zoho.com) (RFC 6698) 
openssl s_client -starttls smtp -connect smtpin.zoho.com:25 -servername smtpin.zoho.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.zoho.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.zoho.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.zoho.com TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.zoho.com TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer zoho.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer zoho.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer zoho.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/zoho.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (smtpin.zoho.com) (RFC 3207) 
openssl s_client -starttls smtp -connect smtpin.zoho.com:25 -servername smtpin.zoho.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.zoho.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt (RFC 9116) 
curl -sL https://zoho.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://zoho.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://zoho.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 204.141.42.155 (Team Cymru) 
dig +short 155.42.141.204.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls