CONTINUOUS INTERNET TELEMETRY24H DRIFT38,088 material changesacross 34,280 domains · last 24hDNS DRIFT53 domains changed DNS providertop destination koaladns.com · +31 vs yesterdayNOW543 curated domains not reachablelast probe, steadySITE ERRORS33,703 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,225 sites429 rate-limit / 403 bot-block, a posture signal

vegan.cz

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

This reading of vegan.cz was taken 2d ago

vegan.cz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vegan.cz 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 vegan.cz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
Registered withREG-MOJEID
Also usesGoogle Search Console
IPv6 · 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 11:53 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 vegan.cz actually stands on - every host below is a signed observation
vegan.cz
A / AAAA
37.9.175.2112a00:4b40:aaaa:2011::7
2a00serves the site
NS
ns4.gransy.comns2.gransy.comns.gransy.comns5.gransy.com+1 more
gransy.comanswers its DNS
MX
mail.vegan.cz
vegan.czreceives its email
TLS
vegan.cz
Let's Encryptissued its certificate

DNS Records

A 1

  • 37.9.175.211

AAAA 1

  • 2a00:4b40:aaaa:2011::7

MX 1

  • 10mail.vegan.cz

TXT 2

  • v=spf1 include:spf.active24.com ip4:31.15.10.171 ip6:2a02:4a8:ac24:110::10:171 ~all
  • google-site-verification=xOwbRlfd02SULNy-v_0wG83-406IGZmyeDupuhS-vzs

NS 5

  • ns4.gransy.com
  • ns2.gransy.com
  • ns.gransy.com
  • ns5.gransy.com
  • ns3.gransy.com

SOA 1

  • ns.gransy.com root.gransy.com

MCP_RECORDS 2

  • v=spf1 include:spf.active24.com ip4:31.15.10.171 ip6:2a02:4a8:ac24:110::10:171 ~all
  • google-site-verification=xOwbRlfd02SULNy-v_0wG83-406IGZmyeDupuhS-vzs

DMARC_RECORDS 2

  • v=spf1 include:spf.active24.com ip4:31.15.10.171 ip6:2a02:4a8:ac24:110::10:171 ~all
  • google-site-verification=xOwbRlfd02SULNy-v_0wG83-406IGZmyeDupuhS-vzs

BIMI_RECORDS 2

  • v=spf1 include:spf.active24.com ip4:31.15.10.171 ip6:2a02:4a8:ac24:110::10:171 ~all
  • google-site-verification=xOwbRlfd02SULNy-v_0wG83-406IGZmyeDupuhS-vzs

MTA_STS_RECORDS 2

  • google-site-verification=xOwbRlfd02SULNy-v_0wG83-406IGZmyeDupuhS-vzs
  • v=spf1 include:spf.active24.com ip4:31.15.10.171 ip6:2a02:4a8:ac24:110::10:171 ~all

TLS Certificates (3)

Common NameIssuerExpires
vegan.cz C=US, O=Let's Encrypt, CN=YR1 Fri, 16 Oct 2026 04:17:35 +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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_cbbf1e2cbe5e9b61
Output Hash
fa2d17c87b23264d8b3cb6500d040db3f3a57c3f25a07018dd819f24b69a8cbf
Signature
ed25519:1d70ac361562c6082ef8ce20694db0d2a6ca2ef17623cb3532c076a770ead5342b38c32e386a763c1c0990f74f8db96d77d05cbaf4f2e5aa96ff5d099d213307
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser