CONTINUOUS INTERNET TELEMETRY24H DRIFT48,244 material changesacross 46,548 domains · 24h to ~5h ago · +13,627 vs yesterdaySHIFT101 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,821 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 135,269 sites429 rate-limit / 403 bot-block, a posture signal

zh-ch-9game.com

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

This reading of zh-ch-9game.com was taken 3d ago

zh-ch-9game.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zh-ch-9game.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 zh-ch-9game.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.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 23:07 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 zh-ch-9game.com actually stands on - every host below is a signed observation
zh-ch-9game.com
A / AAAA
157.90.33.74157.90.33.73
unattributedserves the site
NS
ns1.park-my-domain.netns2.park-my-domain.net
park-my-domain.netanswers its DNS
TLS
zh-ch-9game.com
Let's Encryptissued its certificate

DNS Records

A 2

  • 157.90.33.74
  • 157.90.33.73

NS 2

  • ns1.park-my-domain.net
  • ns2.park-my-domain.net

SOA 1

  • ns1.park-my-domain.net hostmaster.zh-ch-9game.com

TLS Certificates (5)

Common NameIssuerExpires
zh-ch-9game.com C=US, O=Let's Encrypt, CN=YR1 Tue, 27 Oct 2026 05:16:27 +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
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 (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_c51143dedb92b85a
Output Hash
0475a0b3f958c8dd1554470c5da36672798d104711c2d2416b2035b85c44d624
Signature
ed25519:b7ea83ae12c28e0f2ca8e9f18d6786d4c89f0186dc67abc057436a8a29cdb93c9d0415f0ed4979fb6dfacd85082e1b7360114be38628f123b5ae81ade8de780c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser