CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,804 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 130,707 sites429 rate-limit / 403 bot-block, a posture signal

zhongxing3.com

Observed Jul 26, 2026, 10:01 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zhongxing3.com was taken 10d ago

zhongxing3.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zhongxing3.com 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 zhongxing3.com 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.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 04:42 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 zhongxing3.com actually stands on - every host below is a signed observation
zhongxing3.com
A / AAAA
172.239.193.33172.238.170.106172.236.114.219
unattributedserves the site
NS
ns1.parklogic.comns2.parklogic.com
parklogic.comanswers its DNS
MX
mx156.hostedmxserver.com
hostedmxserver.comreceives its email

DNS Records

A 3

  • 172.239.193.33
  • 172.238.170.106
  • 172.236.114.219

MX 1

  • 50mx156.hostedmxserver.com

TXT 5

  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • ns1.parklogic.com
  • ns2.parklogic.com

SOA 1

  • ns1.parklogic.com hostmaster.zhongxing3.com

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_b5b87eb9600b7380
Output Hash
43e5b3f7d88db75caef0800a89612c60e91bcb33fd4cfb362b0d074a95a66668
Signature
ed25519:581f057418108576eff55a595d1228bcc34ecf5c48492c406ab2de199aefb5107bd9dd08803f11b3c5b2fe1da019802635f3386e711858aef2f7150a890faf07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser