CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 14,396 material changesacross 13,841+ domains · 24h to ~10h ago · a floor, 14h of 24 walkedSHIFT6 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

zenrus.ru

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

This reading of zenrus.ru was taken 1d ago

zenrus.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zenrus.ru 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 zenrus.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 15:40 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 zenrus.ru actually stands on - every host below is a signed observation
zenrus.ru
A / AAAA
81.163.28.15
unattributedserves the site
NS
ns4.timeweb.orgns1.timeweb.runs3.timeweb.orgns2.timeweb.ru
timeweb.org + timeweb.ruanswers its DNS
MX
mx.yandex.net
yandex.netreceives its email
TLS
zenrus.ru
Let's Encryptissued its certificate

DNS Records

A 1

  • 81.163.28.15

MX 1

  • 10mx.yandex.net

TXT 1

  • v=spf1 include:_spf.timeweb.ru ~all

NS 4

  • ns4.timeweb.org
  • ns1.timeweb.ru
  • ns3.timeweb.org
  • ns2.timeweb.ru

SOA 1

  • ns1.timeweb.ru dns.timeweb.ru

MCP_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

DMARC_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

BIMI_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.timeweb.ru ~all

TLS Certificates (4)

Common NameIssuerExpires
zenrus.ru C=US, O=Let's Encrypt, CN=YE1 Mon, 19 Oct 2026 07:16:48 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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_70019b1cabdf1b4b
Output Hash
e1994f2912213b0966ac899f5260a998cc70e7a7a88d8051273f667a2fbf5718
Signature
ed25519:bdbe3391c73a362d6b7f3a147a7040855381900299c4662090c210f449c00b3da09c004421b6fdd1ad2262aee03242cbd120b09d48270fa3cc8015c9bfce8c0a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser