CONTINUOUS INTERNET TELEMETRY24H DRIFT49,366 material changesacross 43,517 domains · 24h to ~80m ago · +14,960 vs yesterdayROTATION54 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW618 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,884 sites429 rate-limit / 403 bot-block, a posture signal

echoutcome.eu

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

This reading of echoutcome.eu was taken 7d ago

echoutcome.eu is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting echoutcome.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 echoutcome.eu Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 10:39 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 echoutcome.eu actually stands on - every host below is a signed observation
echoutcome.eu
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
echoutcome.eu
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns1.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
echoutcome.eu C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Mon, 08 Feb 2027 22:06:30 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 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_b4f2aa26a7cf7c12
Output Hash
21f82a8e012e6d6c755eb99c2f060bea783bccedc07a6a60f02547ea7928636f
Signature
ed25519:92e7cf2d639121f7f424524fddc69d96cc93a4a0c5472cbc25b5c454953b3e20bd7cf43eec3755f47f6cd772e9ca4690c3992700181c07a3a6c0533ee6f96408
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser