CONTINUOUS INTERNET TELEMETRY24H DRIFT46,719 material changesacross 45,086 domains · 24h to ~6h ago · +12,102 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,814 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 134,598 sites429 rate-limit / 403 bot-block, a posture signal

vetogene.it

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

This reading of vetogene.it was taken 3d ago

vetogene.it is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vetogene.it 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 vetogene.it Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 21:20 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 vetogene.it actually stands on - every host below is a signed observation
vetogene.it
A / AAAA
80.88.84.4
unattributedserves the site
NS
ns.abdns.infons.abdns.euns.abdns.biz
abdns.info + abdns.eu + moreanswers its DNS
MX
in.arubabusiness.it
arubabusiness.itreceives its email
TLS
vetogene.it
Let's Encryptissued its certificate

DNS Records

A 1

  • 80.88.84.4

MX 1

  • 10in.arubabusiness.it

TXT 1

  • v=spf1 a mx include:_spf.arubabusiness.it ip4:80.88.95.95 -all

NS 3

  • ns.abdns.info
  • ns.abdns.eu
  • ns.abdns.biz

SOA 1

  • ns.abdns.biz postmaster.arubabusiness.it

MCP_RECORDS 1

  • v=spf1 a mx include:_spf.arubabusiness.it ip4:80.88.95.95 -all

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none; adkim=r; aspf=r

BIMI_RECORDS 1

  • v=spf1 a mx include:_spf.arubabusiness.it ip4:80.88.95.95 -all

MTA_STS_RECORDS 1

  • v=spf1 a mx include:_spf.arubabusiness.it ip4:80.88.95.95 -all

TLS Certificates (3)

Common NameIssuerExpires
vetogene.it C=US, O=Let's Encrypt, CN=YR1 Tue, 13 Oct 2026 08:17:01 +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_d810d6379280f3bb
Output Hash
5e5aedcf9c584b6163639cd9d56e983e792d27542a0d811b53fa4cb872d7edaf
Signature
ed25519:e33652947ec848b29f78d5d176249e44fd00b6bb5f28a44bf23d057bfb3bbbfccc9b3af5cddffc993c9e2ece4d5b95317ad1d03a3005256bb8ef0f18bfce700e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser