CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~60m ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,178 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,838 sites429 rate-limit / 403 bot-block, a posture signal

dumrb.ru

Observed Aug 9, 2026, 17:38 UTC (5h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 17:38 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 dumrb.ru actually stands on - every host below is a signed observation
dumrb.ru
A / AAAA
185.137.233.1072a03:6f00:1::5c35:60f4
2a03serves 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

DNS Records

A 1

  • 185.137.233.107

AAAA 1

  • 2a03:6f00:1::5c35:60f4

MX 1

  • 10mx.yandex.net

TXT 2

  • v=spf1 redirect=_spf.yandex.net
  • _globalsign-domain-verification=O2HHBF2LwYWFBP6E60aAyo-EnYgu82hpv_viRWVaPN

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

  • google-site-verification=sSbvCnPivLIdJ6cmPvtUW7etHKqNiokg2YppX_Zh6OY

DMARC_RECORDS 1

  • google-site-verification=sSbvCnPivLIdJ6cmPvtUW7etHKqNiokg2YppX_Zh6OY

BIMI_RECORDS 1

  • google-site-verification=sSbvCnPivLIdJ6cmPvtUW7etHKqNiokg2YppX_Zh6OY

MTA_STS_RECORDS 1

  • google-site-verification=sSbvCnPivLIdJ6cmPvtUW7etHKqNiokg2YppX_Zh6OY

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_2eca61b4ff2573d2
Output Hash
724e4aefb93904e4df3e9e048369ef48bc43533f07688d9f8da2c5a5e6ae18ce
Signature
ed25519:5b9f6feb56b4e3d3bafacae36a8d436686d9edb1213e6c7f2a87a248d8568d3d3ba48af6e135191ed7b51f80564bac9e22d887bb4a6a4bd1b66e50589900d900
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser