CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~2h ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW539 curated domains not reachablelast probe, steadySITE ERRORS33,856 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 149,215 sites429 rate-limit / 403 bot-block, a posture signal

yoopayment.com

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

This reading of yoopayment.com was taken 2d ago

yoopayment.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yoopayment.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 yoopayment.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-05 04:37 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 yoopayment.com actually stands on - every host below is a signed observation
yoopayment.com
A / AAAA
40.83.78.3035.201.241.55
unattributedserves the site
NS
damian.ns.cloudflare.comsneh.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mx.yandex.net
yandex.netreceives its email

DNS Records

A 2

  • 40.83.78.30
  • 35.201.241.55

MX 1

  • 10mx.yandex.net

TXT 1

  • t3wfbmg2y15hfkz0zpck78gt49n3ck3h

NS 2

  • damian.ns.cloudflare.com
  • sneh.ns.cloudflare.com

SOA 1

  • damian.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • 1j1z3v7lr3tsgb96g5dzth0mdjrnkngc

DMARC_RECORDS 1

  • 1j1z3v7lr3tsgb96g5dzth0mdjrnkngc

BIMI_RECORDS 1

  • 1j1z3v7lr3tsgb96g5dzth0mdjrnkngc

MTA_STS_RECORDS 1

  • 1j1z3v7lr3tsgb96g5dzth0mdjrnkngc

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_73e9c1ff689e20fa
Output Hash
a776f51f619e452be99ddee6e054e846d363244c1d09ce93130df71ef7218611
Signature
ed25519:077b70399b4a7d1e7ed64e1df41e72bb97c6e0ad4b479bf1fa0ab29b9c265870a7ba59cde39c0ac762e0a2692aded1fb9b0a6f95caf8908adc2dbdf2d2344700
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser