CONTINUOUS INTERNET TELEMETRY24H DRIFT36,140 material changesacross 33,159 domains · 24h to ~2h agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW559 curated domains not reachablelast probe, steadySITE ERRORS33,449 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,636 sites429 rate-limit / 403 bot-block, a posture signal

zzuit.edu.cn

Observed Aug 2, 2026, 09:17 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zzuit.edu.cn was taken 2d ago

zzuit.edu.cn is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zzuit.edu.cn under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch zzuit.edu.cn Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 01:21 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 zzuit.edu.cn actually stands on - every host below is a signed observation
zzuit.edu.cn
NS
dns2.zzuit.edu.cndns1.zzuit.edu.cndns3.zzuit.edu.cn
edu.cnanswers its DNS
MX
hzmx01.mxmail.netease.comhzmx02.mxmail.netease.com
netease.comreceives its email

DNS Records

MX 2

  • 5hzmx01.mxmail.netease.com
  • 10hzmx02.mxmail.netease.com

TXT 3

  • fw8s52q3c7tp04jynw71kvyhfc8f88gq
  • svhnqch39bw86yldqrh6njkfvlmzb87r
  • v=spf1 include:spf.163.com -all

NS 3

  • dns2.zzuit.edu.cn
  • dns1.zzuit.edu.cn
  • dns3.zzuit.edu.cn

SOA 1

  • dns.zzuit.edu.cn support.wodcloud.cn

MCP_RECORDS 1

  • svhnqch39bw86yldqrh6njkfvlmzb87r

DMARC_RECORDS 1

  • v=dmarc1

BIMI_RECORDS 1

  • svhnqch39bw86yldqrh6njkfvlmzb87r

MTA_STS_RECORDS 1

  • svhnqch39bw86yldqrh6njkfvlmzb87r

TLS Certificates (0)

None.

Subdomains (0)

None observed.

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_8af772ae8b9ead97
Output Hash
0c5803caedc07aedc6996f3cb8c2cf329656708228679095d96a9ce0d3c1d263
Signature
ed25519:ca7245f47fac88e780460f0306d0a3a820e0974570d50016b5f35dc1cb06219f6fdc08465c4944814faa8dadf99f91071a012bede6cd1e1cf3a3a264eaa85a0c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser