CONTINUOUS INTERNET TELEMETRY24H DRIFT46,719 material changesacross 45,086 domains · 24h to ~6h ago · +12,102 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,814 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 134,598 sites429 rate-limit / 403 bot-block, a posture signal

ydsp.cc

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

This reading of ydsp.cc was taken 3d ago

ydsp.cc is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ydsp.cc 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 ydsp.cc 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
Registered withNameSilo, LLC
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 02:02 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 ydsp.cc actually stands on - every host below is a signed observation
ydsp.cc
A / AAAA
172.237.129.242172.237.129.236172.237.129.108
unattributedserves the site
NS
ns1.ns306.parklogic.comns2.ns306.parklogic.com
parklogic.comanswers its DNS
MX
mail.eye-mail.net
eye-mail.netreceives its email

DNS Records

A 3

  • 172.237.129.242
  • 172.237.129.236
  • 172.237.129.108

MX 1

  • 1mail.eye-mail.net

TXT 1

  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

NS 2

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

SOA 1

  • ns1.parklogic.com hostmaster.ydsp.cc

MCP_RECORDS 1

  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdec:ae16:fda7::/48 -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_598125f48a0bb2a9
Output Hash
0c567a9a8988e2a4a28e7018b9887479855756790ce4efadf7bfea78fa5fb1c9
Signature
ed25519:c3ef4a283cda016dc59a5956f3a6c706635421bda4ca0a7588d76ba9e01e31c5bae606289a9390aa797b2ada3074c2d998a8554265af16aa2f0eea2ab82a5c05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser