CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 15,250 material changesacross 14,659+ domains · 24h to ~6h ago · a floor, 18h of 24 walkedNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

vebu.de

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

This reading of vebu.de was taken 1d ago

vebu.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vebu.de 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 vebu.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byGoogle Workspace
Secured byStarfield Technologies
IPv6 · 1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 09:32 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 vebu.de actually stands on - every host below is a signed observation
vebu.de
A / AAAA
134.119.86.2222a00:116a:10b:8760::
Cloudflareserves the site
NS
ns82.domaincontrol.comns81.domaincontrol.com
domaincontrol.comanswers its DNS
MX
alt3.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.comaspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
vebu.de
Starfield Technologiesissued its certificate

DNS Records

A 1

  • 134.119.86.222

AAAA 1

  • 2a00:116a:10b:8760::

MX 5

  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 1aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 2

  • v=spf1 a mx include:cmail1.com ~all
  • v=spf1 mx a include:_spf.google.com ip4:178.77.97.127 ip4:80.67.18.65 ip4:80.67.18.66 ip4:80.67.18.67 ip4:80.67.18.68 ip4:80.67.18.69 ip4:80.67.18.70 ~all

NS 2

  • ns82.domaincontrol.com
  • ns81.domaincontrol.com

SOA 1

  • ns81.domaincontrol.com dns.jomax.net

MCP_RECORDS 2

  • v=spf1 a mx include:cmail1.com ~all
  • v=spf1 mx a include:_spf.google.com ip4:178.77.97.127 ip4:80.67.18.65 ip4:80.67.18.66 ip4:80.67.18.67 ip4:80.67.18.68 ip4:80.67.18.69 ip4:80.67.18.70 ip4:85.214.60.147 ~all

DMARC_RECORDS 2

  • v=spf1 a mx include:cmail1.com ~all
  • v=spf1 mx a include:_spf.google.com ip4:178.77.97.127 ip4:80.67.18.65 ip4:80.67.18.66 ip4:80.67.18.67 ip4:80.67.18.68 ip4:80.67.18.69 ip4:80.67.18.70 ip4:85.214.60.147 ~all

BIMI_RECORDS 2

  • v=spf1 a mx include:cmail1.com ~all
  • v=spf1 mx a include:_spf.google.com ip4:178.77.97.127 ip4:80.67.18.65 ip4:80.67.18.66 ip4:80.67.18.67 ip4:80.67.18.68 ip4:80.67.18.69 ip4:80.67.18.70 ip4:85.214.60.147 ~all

MTA_STS_RECORDS 2

  • v=spf1 a mx include:cmail1.com ~all
  • v=spf1 mx a include:_spf.google.com ip4:178.77.97.127 ip4:80.67.18.65 ip4:80.67.18.66 ip4:80.67.18.67 ip4:80.67.18.68 ip4:80.67.18.69 ip4:80.67.18.70 ip4:85.214.60.147 ~all

TLS Certificates (4)

Common NameIssuerExpires
vebu.de C=US, O=Starfield Technologies, CN=Starfield TLS Intermediate CA DV - R1v1 Wed, 27 Jan 2027 14:04:40 +0000
Starfield TLS Intermediate CA DV - R1v1 C=US, O=Starfield Technologies, CN=Starfield TLS Root CA - R1 Thu, 23 Aug 2040 11:59:59 +0000
Starfield TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Starfield Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2 Thu, 31 Dec 2037 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_c40db878cf8dc507
Output Hash
3fc947e6b2d55d59c4e21d6ac40d1624dad7656f072c63c05dcfb175b3c804c4
Signature
ed25519:facd611056816f023439ff26b91b46ff8c2dc13651eeeb43574a63930652e62e431904d9c80f817209d176f5086a8b3994de11782447889428e011bc9a90420c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser