CONTINUOUS INTERNET TELEMETRY24H DRIFT7,874 material changesacross 7,306 domains · 24h to ~2h ago · -889 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

zohodesk.in

Observed Aug 2, 2026, 08:33 UTC (23h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Up right now
Email byZoho Mail
Secured byLet's Encrypt
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 08:33 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat zohodesk.in actually stands on - every host below is a signed observation
zohodesk.in
A / AAAA
103.103.196.99
unattributedserves the site
NS
NS1.ZOHOCORP.COMPDNS90.ULTRADNS.NETPDNS90.ULTRADNS.COMPDNS90.ULTRADNS.BIZ+4 more
zohocorp.com + ultradns.net + moreanswers its DNS
MX
mx.zoho.inmx2.zoho.inmx3.zoho.in
Zoho Mailreceives its email
TLS
mailer1.zohocrm.in
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.103.196.99

MX 3

  • 10mx.zoho.in
  • 20mx2.zoho.in
  • 50mx3.zoho.in

TXT 1

  • v=spf1 include:zoho.in include:zeptomail.net.in ~all

NS 8

  • NS1.ZOHOCORP.COM
  • PDNS90.ULTRADNS.NET
  • PDNS90.ULTRADNS.COM
  • PDNS90.ULTRADNS.BIZ
  • NS41.ZNS-53.NET
  • NS31.ZNS-53.COM
  • NS21.ZNS-53.NET
  • NS11.ZNS-53.COM

SOA 1

  • NS1.ZOHOCORP.COM dnsadmin.vtitan.COM

MCP_RECORDS 1

  • v=spf1 include:zoho.in include:zeptomail.net.in ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none; fo=0; rua=mailto:dmarc.reports.in@zohodesk.com; ruf=mailto:dmarc.reports.in@zohodesk.com

BIMI_RECORDS 1

  • v=spf1 include:zoho.in include:zeptomail.net.in ~all

MTA_STS_RECORDS 1

  • v=spf1 include:zoho.in include:zeptomail.net.in ~all

TLS Certificates (3)

Common NameIssuerExpires
mailer1.zohocrm.in C=US, O=Let's Encrypt, CN=YR1 Wed, 21 Oct 2026 07:33:52 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_a408ad3d132def58
Output Hash
ed53ba413f196e457b496a56aa711d2f2c3e091ebb3d0bec881f0fd0377a58ff
Signature
ed25519:2eed7903842fb9c5e81b70bf38d198e18577931ff6e397207b20ebed8ace023253aad50648dfafd99ebc290b4913a4a43407652edf332cdf0298e05776c09f05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser