CONTINUOUS INTERNET TELEMETRY24H DRIFT69,910 material changesacross 66,081 domains · 24h to ~2h ago · +35,293 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,856 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 125,257 sites429 rate-limit / 403 bot-block, a posture signal

ebusy.de

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

This reading of ebusy.de was taken 9d ago

ebusy.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ebusy.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 ebusy.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
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-04 15:51 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 ebusy.de actually stands on - every host below is a signed observation
ebusy.de
A / AAAA
167.235.120.91
unattributedserves the site
NS
hydrogen.ns.hetzner.comoxygen.ns.hetzner.comhelium.ns.hetzner.de
hetzner.com + hetzner.deanswers its DNS
MX
dedi8928.your-server.de
your-server.dereceives its email
TLS
ebusy.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 167.235.120.91

MX 1

  • 10dedi8928.your-server.de

TXT 8

  • v=spf1 mx a include:ispgateway.de ip4:88.99.192.89 ip4:88.99.31.110 ip4:49.12.92.76 ip4:92.205.49.7 ip4:5.9.235.231 ip4:167.235.120.91 ip4:78.46.5.205 ~all
  • google-site-verification=QPAERWW8Y-nVho63wXLU75uovesgVArK6eOzaum11Ts
  • google-site-verification=lFosb-b_SQ8IB1BfgmvxffHxYXmbujTztXvRXutWqv4
  • jd686aeurc94ng3gtev2iggk3m
  • v=DMARC1;p=quarantine;sp=none;pct=100;rua=mailto:status@ebusy.de;adkim=r;aspf=r;
  • v=spf1 mx a include:ispgateway.de ip4:88.99.192.89 ip4:88.99.31.110 ip4:49.12.92.76 ip4:92.205.49.7 ip4:5.9.235.231 ip4:167.235.120.91 ip4:78.46.5.205 ~all
  • v=spf1 mx a include:ispgateway.de ip4:88.99.192.89 ip4:88.99.31.110 ip4:49.12.92.76 ip4:92.205.49.7 ip4:5.9.235.231 ip4:167.235.120.91 ip4:78.46.5.205 ~all
  • v=spf1 mx a include:ispgateway.de ip4:88.99.192.89 ip4:88.99.31.110 ip4:49.12.92.76 ip4:92.205.49.7 ip4:5.9.235.231 ip4:167.235.120.91 ip4:78.46.5.205 ~all

NS 3

  • hydrogen.ns.hetzner.com
  • oxygen.ns.hetzner.com
  • helium.ns.hetzner.de

SOA 1

  • hydrogen.ns.hetzner.com dns.hetzner.com

TLS Certificates (3)

Common NameIssuerExpires
ebusy.de C=US, O=Let's Encrypt, CN=YR1 Thu, 03 Sep 2026 19:04:59 +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_3d0a5d0d002b65d9
Output Hash
2e0a20ee426d7508b5d1170b8f980314ea9d5b04bdd07a8246c27778315c8d63
Signature
ed25519:2662d278282fc1ef168223fdb58f8b3855788bcae903b9e2e03d70346f7b93e7bd8c2099ec2fbf25f24d2d4378aecdc065aecfeaec98a6b911ce605262c1160b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser