CONTINUOUS INTERNET TELEMETRY24H DRIFT48,509 material changesacross 45,523 domains · 24h to ~3h ago · -13,567 vs yesterdayROTATION51 domains moved DNS from magpiedns.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hNOW531 curated domains not reachablelast probe, steadySITE ERRORS33,881 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,540 sites429 rate-limit / 403 bot-block, a posture signal

yilun-xu.com

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

This reading of yilun-xu.com was taken 4d ago

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

DNS Records

A 3

  • 172.237.146.39
  • 172.237.146.18
  • 172.237.146.46

MX 1

  • 970mx156.hostedmxserver.com

TXT 1

  • v=spf1 -all

NS 2

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

SOA 1

  • ns1.parklogic.com hostmaster.yilun-xu.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

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_0a2d45cfb6021a4c
Output Hash
5cbd7d3390307e81d4f63a9c773f57dacbb888dc85d4c31ff373c6b9acf18fbc
Signature
ed25519:7469c3158b94bfb7c528f9c69cd8dcd2616d8f197fe3909240d426234525b54a77cd76aee91fc80ce50f943a1b6e8689ce25707ad7f2d82d93d8a1cb0771c801
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser