CONTINUOUS INTERNET TELEMETRY24H DRIFT46,719 material changesacross 45,086 domains · 24h to ~6h ago · +12,102 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,814 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 134,598 sites429 rate-limit / 403 bot-block, a posture signal

engeniusnetworks.com

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

This reading of engeniusnetworks.com was taken 3d ago

engeniusnetworks.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting engeniusnetworks.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 engeniusnetworks.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onGoogle
Email byMicrosoft 365
Registered withWeb Commerce Communications Limited dba WebNic.cc
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 14: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 engeniusnetworks.com actually stands on - every host below is a signed observation
engeniusnetworks.com
A / AAAA
35.213.144.238
Googleserves the site
NS
ns-1335.awsdns-38.orgns-1613.awsdns-09.co.ukns-388.awsdns-48.comns-953.awsdns-55.net
awsdns-38.org + awsdns-09.co.uk + moreanswers its DNS
MX
engeniusnetworks-com.mail.protection.outlook.com
Microsoft 365receives its email

DNS Records

A 1

  • 35.213.144.238

MX 1

  • 10engeniusnetworks-com.mail.protection.outlook.com

TXT 2

  • MS=ms41828725
  • v=spf1 include:spf.protection.outlook.com -all

NS 4

  • ns-1335.awsdns-38.org
  • ns-1613.awsdns-09.co.uk
  • ns-388.awsdns-48.com
  • ns-953.awsdns-55.net

SOA 1

  • ns-388.awsdns-48.com awsdns-hostmaster.amazon.com

MCP_RECORDS 2

  • MS=ms41828725
  • v=spf1 include:spf.protection.outlook.com -all

DMARC_RECORDS 2

  • MS=ms41828725
  • v=spf1 include:spf.protection.outlook.com -all

BIMI_RECORDS 2

  • MS=ms41828725
  • v=spf1 include:spf.protection.outlook.com -all

MTA_STS_RECORDS 2

  • MS=ms41828725
  • v=spf1 include:spf.protection.outlook.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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_8c9dd5eec3a08612
Output Hash
abd5f44bcdd4eec3672f1119c9e2e444ec85d4b3d3f2db0d08426419d8ec1e6d
Signature
ed25519:3476abaf99d8961a3e7561342bdeb1591804c4353622055027a6cbfa2572b11411cdd98be25ef4d4648836aaef9664192923cd4d39f834b52fe340ca9f8cfe0c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser