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

virosat.ru

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

This reading of virosat.ru was taken 1d ago

virosat.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting virosat.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 virosat.ru 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.
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 12:14 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 virosat.ru actually stands on - every host below is a signed observation
virosat.ru
A / AAAA
34.41.139.1932600:1900:4001:96e:8000:1:30ae:8dcf
2600serves the site
NS
ns2.hwrn.netns1.hwrn.net
hwrn.netanswers its DNS
MX
mx1.csof.netmx2.csof.net
csof.netreceives its email

DNS Records

A 1

  • 34.41.139.193

AAAA 1

  • 2600:1900:4001:96e:8000:1:30ae:8dcf

MX 2

  • 10mx1.csof.net
  • 10mx2.csof.net

TXT 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

NS 2

  • ns2.hwrn.net
  • ns1.hwrn.net

SOA 1

  • ns1.hwrn.net hostmaster.hwrn.net

MCP_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

DMARC_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

BIMI_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

MTA_STS_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -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_19c4c118b558ca2a
Output Hash
86baea152d6cf52211f0429f1c1c9c682e79275409535a7a467706be0cdcd5ac
Signature
ed25519:981595101eff15d228818aaa214126c4798a73f72439de10b1c92c16a73076f53de080b846104a2285eeb2ea41d6f0795fb86a7b1d2b178f82f7182273f8a006
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser