CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,804 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 130,707 sites429 rate-limit / 403 bot-block, a posture signal

vavada-rug.buzz

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

This reading of vavada-rug.buzz was taken 3d ago

vavada-rug.buzz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vavada-rug.buzz 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 vavada-rug.buzz 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 03:35 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 vavada-rug.buzz actually stands on - every host below is a signed observation
vavada-rug.buzz
A / AAAA
37.1.198.233148.222.187.209
unattributedserves the site
NS
ns1.example.comns2.example.com
example.comanswers its DNS
MX
mail.vavada-rug.buzzmail.vavada-rug.buzz
vavada-rug.buzzreceives its email
TLS
vavada-rug.buzz
Let's Encryptissued its certificate

DNS Records

A 2

  • 37.1.198.233
  • 148.222.187.209

MX 2

  • 20mail.vavada-rug.buzz
  • 10mail.vavada-rug.buzz

TXT 1

  • v=spf1 ip4:148.222.187.209 a mx ~all

NS 2

  • ns1.example.com
  • ns2.example.com

SOA 1

  • v532440978.local root.example.com

TLS Certificates (3)

Common NameIssuerExpires
vavada-rug.buzz C=US, O=Let's Encrypt, CN=YR1 Thu, 03 Sep 2026 02:17:46 +0000
YR1 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_f8b2db6d58d4b8f2
Output Hash
7ea63d86609f5a69a8823ee7ffedd3e777b34bda18a41072cb7fd383bfc8b277
Signature
ed25519:0f80ecfe0cf3918a6a2f1ff6994718d15d30c2884bca2e3fb7be163334d94d6658676755d2a3f82ab96dd1e30ed6e8f58743c8e4f0fe187639b82f581392d002
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser