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

zalafilms.com

Observed Jul 26, 2026, 09:55 UTC (9d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zalafilms.com was taken 9d ago

zalafilms.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zalafilms.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 zalafilms.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
Email byMailchimp
Secured byLet's Encrypt
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 04:39 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 zalafilms.com actually stands on - every host below is a signed observation
zalafilms.com
A / AAAA
20.119.76.151
unattributedserves the site
NS
ns1.turbify.comns2.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.netmx-biz.mail.am0.yahoodns.net
Mailchimpreceives its email
TLS
zalafilms.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 20.119.76.151

MX 2

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

TXT 5

  • v=spf1 ptr:yahoo.com ptr:yahoo.net include:servers.mcsv.net ~all
  • v=spf1 a mx ip4:20.119.76.151 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.119.76.151 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.119.76.151 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.119.76.151 include:relay.mailchannels.net -all

NS 2

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

SOA 1

  • ns1.turbify.com webmaster.turbify.com

TLS Certificates (3)

Common NameIssuerExpires
zalafilms.com C=US, O=Let's Encrypt, CN=YR2 Tue, 08 Sep 2026 02:46:05 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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_3e9eb51326336004
Output Hash
5cf1dc08241d3afd7365af4a17d179b434afc6f6afc470fdbcea5b43c8ed5b4e
Signature
ed25519:a8389a0050bc7873cdfdf9b860f23f177d109f01e43c25028506c51f6715a9c2f0258c3cfe176b117a53852615bea783f49741579ac6a16357635e266e82f707
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser