CONTINUOUS INTERNET TELEMETRY24H DRIFT64,140 material changesacross 60,105 domains · last 24h · +29,523 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 133,434 sites429 rate-limit / 403 bot-block, a posture signal

vavada-aa.top

Observed Jul 25, 2026, 22:17 UTC (11d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of vavada-aa.top was taken 11d ago

vavada-aa.top is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vavada-aa.top 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-aa.top 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 09:50 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-aa.top actually stands on - every host below is a signed observation
vavada-aa.top
A / AAAA
172.237.129.108172.237.129.236172.237.129.242
unattributedserves the site
NS
ns2.ns306.parklogic.comns1.ns306.parklogic.com
parklogic.comanswers its DNS
MX
mail.eye-mail.net
eye-mail.netreceives its email

DNS Records

A 3

  • 172.237.129.108
  • 172.237.129.236
  • 172.237.129.242

MX 1

  • 1mail.eye-mail.net

TXT 5

  • v=spf1 ip6:fdec:ae16:fda7::/48 -all
  • v=spf1 ip6:fdec:ae16:fda7::/48 -all
  • v=spf1 ip6:fdec:ae16:fda7::/48 -all
  • v=spf1 ip6:fdec:ae16:fda7::/48 -all
  • v=spf1 ip6:fdec:ae16:fda7::/48 -all

NS 2

  • ns2.ns306.parklogic.com
  • ns1.ns306.parklogic.com

SOA 1

  • ns1.parklogic.com hostmaster.vavada-aa.top

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_9889be1dcbb3240b
Output Hash
f5810fab5502190c710595a7c50ad8700ea55863cfca8d7cbe956e02217fc29e
Signature
ed25519:a3201099d146e86b87c2b6f44e61f06ef60d3d72d22fb8853361f8776a6978c868a1d870c6a12405537a553a59952d738d97a6f437aaf9944ed32b5654aec103
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser