CONTINUOUS INTERNET TELEMETRY24H DRIFT35,267 material changesacross 32,953 domains · 24h to ~2h agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,387 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,370 sites429 rate-limit / 403 bot-block, a posture signal

yogafriends.de

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

This reading of yogafriends.de was taken 8d ago

yogafriends.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yogafriends.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 yogafriends.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 09:43 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 yogafriends.de actually stands on - every host below is a signed observation
yogafriends.de
A / AAAA
5.9.10.752a01:4f8:b13:1001::4
2a01serves the site
NS
ns12.realtime.atns11.realtime.at
realtime.atanswers its DNS

DNS Records

A 1

  • 5.9.10.75

AAAA 1

  • 2a01:4f8:b13:1001::4

MX 1

  • 10

TXT 9

  • v=spf1 mx -all
  • v=DMARC1; p=reject;
  • v=spf1 mx -all
  • v=DMARC1; p=reject;
  • v=spf1 mx -all
  • v=spf1 mx -all
  • v=DMARC1; p=reject;
  • v=DMARC1; p=reject;
  • v=spf1 mx -all

NS 2

  • ns12.realtime.at
  • ns11.realtime.at

SOA 1

  • ns11.realtime.at office.realtime.at

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_043229af93f44836
Output Hash
ce9c9ccbc3da93af68c728abf66a8f80bf06feb431a413a273c63cb8c6b33b46
Signature
ed25519:49fbdb7a6ff90d0ff6a3d7b2ea44ee4324e52c90277be53475a939d33bd8cb8218c4efcf921b592e644618096b7326995e28a8e9540e5e794fddc1ae4208ca08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser