CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · 24h to ~30m agoSHIFT21 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,263 sites429 rate-limit / 403 bot-block, a posture signal

zebnet.de

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

This reading of zebnet.de was taken 1d ago

zebnet.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zebnet.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 zebnet.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
Also usesGoogle Search Console
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 22:31 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 zebnet.de actually stands on - every host below is a signed observation
zebnet.de
A / AAAA
5.135.124.1042001:41d0:203:87e9::1
2001serves the site
NS
rob.ns.cloudflare.comdawn.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mail.zebnet.co.uk
zebnet.co.ukreceives its email
TLS
zebnet.co.uk
Let's Encryptissued its certificate

DNS Records

A 1

  • 5.135.124.104

AAAA 1

  • 2001:41d0:203:87e9::1

MX 1

  • 10mail.zebnet.co.uk

TXT 2

  • v=spf1 a mx -all
  • google-site-verification=fruiZM9Xb6etqS1OKSpx1tOcMSItNnDSWn3Vd3jt_5A

NS 2

  • rob.ns.cloudflare.com
  • dawn.ns.cloudflare.com

SOA 1

  • dawn.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 a mx -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:postmaster@zebnet.de; ruf=mailto:postmaster@zebnet.de; fo=1;

BIMI_RECORDS 1

  • v=spf1 a mx -all

MTA_STS_RECORDS 1

  • v=spf1 a mx -all

TLS Certificates (3)

Common NameIssuerExpires
zebnet.co.uk C=US, O=Let's Encrypt, CN=YR2 Mon, 21 Sep 2026 10:38:23 +0000
YR2 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_0b6347150ea78af5
Output Hash
d8ff85aa6340824402fb51d6d60a5201bd4ff2b30ab0b893b551d92c4dda318d
Signature
ed25519:2e92941d61f6945a21d831920f7df871ce0fb28b543388373d886da43473d26928037e227e42f5f569281bef10baa12a46b428ab17dbaad62e5ec6aefa989d07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser