CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 14,165 material changesacross 13,628+ domains · 24h to ~10h ago · a floor, 14h of 24 walkedSHIFT10 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signal

yeglive.ca

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

This reading of yeglive.ca was taken 1d ago

yeglive.ca is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yeglive.ca 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 yeglive.ca Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Email byGoogle Workspace
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 13:08 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 yeglive.ca actually stands on - every host below is a signed observation
yeglive.ca
A / AAAA
178.128.227.20
unattributedserves the site
NS
ns1.digitalocean.comns2.digitalocean.comns3.digitalocean.com
digitalocean.comanswers its DNS
MX
alt2.aspmx.l.google.comalt1.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.com+1 more
Google Workspacereceives its email

DNS Records

A 1

  • 178.128.227.20

MX 5

  • 5alt2.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com

TXT 1

  • v=spf1 +a +mx +include:_spf.google.com ~all

NS 3

  • ns1.digitalocean.com
  • ns2.digitalocean.com
  • ns3.digitalocean.com

SOA 1

  • ns1.digitalocean.com hostmaster.yeglive.ca

MCP_RECORDS 1

  • v=spf1 +a +mx +include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:postmaster@yeglive.ca

BIMI_RECORDS 1

  • v=spf1 +a +mx +include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 +a +mx +include:_spf.google.com ~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_500c27618af70351
Output Hash
114f9f5dba5573ad9a04131cb1b7278fc04e001edab7422652f2c1194be2e595
Signature
ed25519:e0cf7cac0190c739137c192ed3bd27798dd50f8427a27a130092f991e6e0375fd2f9b0ad91ca415935280ff38dede4ff11d7b8e5c3943b21c6c0cc4b0b95bd03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser