CONTINUOUS INTERNET TELEMETRY24H DRIFT37,653 material changesacross 34,127 domains · 24h to ~20m agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,351 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,386 sites429 rate-limit / 403 bot-block, a posture signal

ecssr.com

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

This reading of ecssr.com was taken 2d ago

ecssr.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ecssr.com 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 ecssr.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-03 00: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 ecssr.com actually stands on - every host below is a signed observation
ecssr.com
A / AAAA
5.195.192.98
unattributedserves the site

DNS Records

A 1

  • 5.195.192.98

TXT 2

  • v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s
  • v=spf1 -all

CAA 1

  • issue ""

MCP_RECORDS 2

  • v=spf1 -all
  • v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s

DMARC_RECORDS 2

  • v=spf1 -all
  • v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s

BIMI_RECORDS 2

  • v=spf1 -all
  • v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s

MTA_STS_RECORDS 2

  • v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s
  • v=spf1 -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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_ce7ed16d80e0689f
Output Hash
c241853da073931cb808613e4d1b49b76e2dc205c18071c2aa9852033b2dfd06
Signature
ed25519:07d7bb14c06d1e414b54e19b2c9cb6f96074c1bd8989a76d8a7f6612835c340a09169c19868dde195408281bb663e0cbfbde521932c1dfe07f6a32bf0206a900
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser