CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW535 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 129,659 sites429 rate-limit / 403 bot-block, a posture signal

uwe-henze.de

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

This reading of uwe-henze.de was taken 2d ago

uwe-henze.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting uwe-henze.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 uwe-henze.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Email byMicrosoft 365
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 21:34 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 uwe-henze.de actually stands on - every host below is a signed observation
uwe-henze.de
A / AAAA
217.91.54.44
unattributedserves the site
NS
ns81.domaincontrol.comns82.domaincontrol.com
domaincontrol.comanswers its DNS
MX
uwehenze-de0i.mail.protection.outlook.com
Microsoft 365receives its email

DNS Records

A 1

  • 217.91.54.44

MX 1

  • 0uwehenze-de0i.mail.protection.outlook.com

TXT 3

  • v=spf1 include:spf.protection.outlook.com a ip4:34.216.216.69 ip4:34.216.216.70 ~all
  • MS=ms67892865
  • lmg665rl5v9u7os1h20hnq0or9

NS 2

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

SOA 1

  • ns81.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 mx a include:ispgateway.de ~all

DMARC_RECORDS 1

  • v=DMARC1;p=quarantine;pct=100;ruf=mailto:mh@aitt.eu;rua=mailto:mh@aitt.eu

BIMI_RECORDS 1

  • v=spf1 mx a include:ispgateway.de ~all

MTA_STS_RECORDS 1

  • v=spf1 mx a include:ispgateway.de ~all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

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_967cd8d8b92d9b9f
Output Hash
ae58d69c5242abfd54ca540c99463f1391e843693680145c72993e2b278df964
Signature
ed25519:39eecd8dca7d2c28191aa9b3c37ad335759b001dd09c24a7845ba7b8909be7495ed5a4cc455c1cc4ca09648a18282e0f318cef32cbe3da8ed6c31ca403e66202
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser