CONTINUOUS INTERNET TELEMETRY24H DRIFT35,821 material changesacross 32,384 domains · 24h to ~40m agoSHIFT26 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW559 curated domains not reachablelast probe, steadySITE ERRORS34,062 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,368 sites429 rate-limit / 403 bot-block, a posture signal

zonalatina.com

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

This reading of zonalatina.com was taken 1d ago

zonalatina.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zonalatina.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 zonalatina.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.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 21:12 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 zonalatina.com actually stands on - every host below is a signed observation
zonalatina.com
A / AAAA
20.51.208.248
unattributedserves the site
NS
ns2.turbify.comns1.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.net
yahoodns.netreceives its email

DNS Records

A 1

  • 20.51.208.248

MX 1

  • 20mx-biz.mail.am0.yahoodns.net

NS 2

  • ns2.turbify.com
  • ns1.turbify.com

SOA 1

  • ns1.turbify.com webmaster.turbify.com

MCP_RECORDS 1

  • v=spf1 a mx ip4:20.51.208.248 include:relay.mailchannels.net -all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:20.51.208.248 include:relay.mailchannels.net -all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:20.51.208.248 include:relay.mailchannels.net -all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:20.51.208.248 include:relay.mailchannels.net -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_ceaf671aa40666a9
Output Hash
6d1f0237849ffa023cdba0b016a8e9199e79fe3e4b80bc77c68f5c46cfa8bfbe
Signature
ed25519:9b66853428d5e6c85044f3e2b1ff9ea98e760a1b2bcae1f0a6d422f7061addec133dce7ed4708f20af28fca853bb96c8e2f7b1913db71e92f4d5ff069394990b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser