CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · last 24hSHIFT18 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,263 sites429 rate-limit / 403 bot-block, a posture signal

ushakov.org

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

This reading of ushakov.org was taken 2d ago

ushakov.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ushakov.org 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 ushakov.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 12:24 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 ushakov.org actually stands on - every host below is a signed observation
ushakov.org
A / AAAA
31.177.76.3231.177.80.32
unattributedserves the site
NS
dnsproxy1.fm.nic.rudnsproxy2.fm.nic.ru
nic.ruanswers its DNS
MX
nomail.nic.ru
nic.rureceives its email

DNS Records

A 2

  • 31.177.76.32
  • 31.177.80.32

MX 1

  • 0nomail.nic.ru

TXT 1

  • de7a2c3c1b49d124b949e2acdd64e9792f541ed6

NS 2

  • dnsproxy1.fm.nic.ru
  • dnsproxy2.fm.nic.ru

SOA 1

  • dnsproxy1.fm.nic.ru hostmaster.nic.ru

MCP_RECORDS 1

  • de7a2c3c1b49d124b949e2acdd64e9792f541ed6

DMARC_RECORDS 1

  • de7a2c3c1b49d124b949e2acdd64e9792f541ed6

BIMI_RECORDS 1

  • de7a2c3c1b49d124b949e2acdd64e9792f541ed6

MTA_STS_RECORDS 1

  • de7a2c3c1b49d124b949e2acdd64e9792f541ed6

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