CONTINUOUS INTERNET TELEMETRY24H DRIFT30,639 material changesacross 29,370 domains · 24h to ~2h agoSHIFT26 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW559 curated domains not reachablelast probe, steadySITE ERRORS34,112 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,305 sites429 rate-limit / 403 bot-block, a posture signal

yunciot.com

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

This reading of yunciot.com was taken 2d ago

yunciot.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yunciot.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 yunciot.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
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-02 12:32 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 yunciot.com actually stands on - every host below is a signed observation
yunciot.com
A / AAAA
208.91.197.46
unattributedserves the site
NS
sk.s5.ans2.ns148.ztomy.comsk.s5.ans1.ns148.ztomy.com
ztomy.comanswers its DNS
MX
\~
unattributedreceives its email

DNS Records

A 1

  • 208.91.197.46

MX 1

  • 300\~

TXT 1

  • v=spf1 a -all

NS 2

  • sk.s5.ans2.ns148.ztomy.com
  • sk.s5.ans1.ns148.ztomy.com

SOA 1

  • sk.s5.ans1.ns148.ztomy.com abuse.confluence-networks.com

MCP_RECORDS 1

  • v=spf1 a -all

DMARC_RECORDS 1

  • v=spf1 a -all

BIMI_RECORDS 1

  • v=spf1 a -all

MTA_STS_RECORDS 1

  • v=spf1 a -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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_72e538e049034986
Output Hash
5bfd921ca338ae77561b4f1f85aa626258932c9ed72480394eb29a4234cbed1c
Signature
ed25519:36dd9d112e3ef86dd1ab724c1d09932ea9d4f4c67fe2e41210be1710d87db19db4ba7d5e7247aafa2c6738988a038e22c1e9b03fcc33469bafbb4dc565e04e03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser