CONTINUOUS INTERNET TELEMETRY24H DRIFT55,932 material changesacross 50,731 domains · 24h to ~40m ago · -6,144 vs yesterdayROTATION51 domains moved DNS from koaladns.com to magpiedns.com, 51 moved backa rotation loop, not a migration · 24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,869 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,346 sites429 rate-limit / 403 bot-block, a posture signal

edash.eu

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

This reading of edash.eu was taken 4d ago

edash.eu is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting edash.eu 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 edash.eu Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Secured bySectigo
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 04:02 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 edash.eu actually stands on - every host below is a signed observation
edash.eu
A / AAAA
91.195.241.232
Cloudflareserves the site
TLS
edash.eu
Sectigo Limitedissued its certificate

DNS Records

A 1

  • 91.195.241.232

TLS Certificates (3)

Common NameIssuerExpires
edash.eu C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36 Sat, 29 Aug 2026 23:59:59 +0000
Sectigo Public Server Authentication Root R46 C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority Mon, 18 Jan 2038 23:59:59 +0000
Sectigo Public Server Authentication CA DV R36 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Fri, 21 Mar 2036 23:59:59 +0000

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_e5b9b66e6e41e8af
Output Hash
1a67663b4d5d06416ed8340bee7d812e3665df4f45ba5788258e41dc665e9ec7
Signature
ed25519:79330361e56b110c8135a60987b2ec9a28d5224015811da8f46fc19ac638427e03a2bdebef489cd18c2a3dcc2785b6f7c3e00b837c36502a6af733c32c46380e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser