CONTINUOUS INTERNET TELEMETRY24H DRIFT37,653 material changesacross 34,127 domains · 24h to ~20m agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,351 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,386 sites429 rate-limit / 403 bot-block, a posture signal

zassets.com

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

This reading of zassets.com was taken 2d ago

zassets.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zassets.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 zassets.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 06:41 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 zassets.com actually stands on - every host below is a signed observation
zassets.com
NS
faye.ns.cloudflare.commoura.ns.cloudflare.com
cloudflare.comanswers its DNS

DNS Records

TXT 1

  • _lqykvkhqgonx7qzu8hcfbi5lfjplbil

NS 2

  • faye.ns.cloudflare.com
  • moura.ns.cloudflare.com

SOA 1

  • faye.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:rua@zappos.com; ruf=mailto:ruf@zappos.com

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_43247383552bed16
Output Hash
e9d412538fdb8d24ae44ea75aadb98c8f3ddbe363af88b168766ce5458b74129
Signature
ed25519:2b0c27a7bd056e8aa4aeec7159ef2283f7facb5e769f00afad22a759f3b2b38bc92d16726c5b0f50ac3d32ad19062753d6a09017436372eb14174aa1b403f40b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser