CONTINUOUS INTERNET TELEMETRY24H DRIFT65,987 material changesacross 60,872 domains · last 24h · +3,911 vs yesterdayROTATION55 domains moved DNS from magpiedns.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,744 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 122,719 sites429 rate-limit / 403 bot-block, a posture signal

zapchastrf.ru

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

This reading of zapchastrf.ru was taken 4d ago

zapchastrf.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zapchastrf.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 zapchastrf.ru Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Guarded by a firewall
Secured byLet's Encrypt
57 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 18:13 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 zapchastrf.ru actually stands on - every host below is a signed observation
zapchastrf.ru
A / AAAA
193.39.168.161
unattributedserves the site
NS
c.ns.selectel.rub.ns.selectel.rua.ns.selectel.rud.ns.selectel.ru
selectel.ruanswers its DNS
MX
mx.yandex.net
yandex.netreceives its email
TLS
zapchastrf.ru
Let's Encryptissued its certificate

DNS Records

A 1

  • 193.39.168.161

MX 1

  • 10mx.yandex.net

TXT 4

  • yandex-verification: 3fc310bd20c42f1a
  • unisender-go-validate-hash=02a9099b61ebc400ff0f84d7a08a2b3f
  • v=spf1 include:_spf.yandex.net include:spf.unisender.ru ~all
  • yandex-verification: cdc55c3b7eb4a0a7

NS 4

  • c.ns.selectel.ru
  • b.ns.selectel.ru
  • a.ns.selectel.ru
  • d.ns.selectel.ru

SOA 1

  • a.ns.selectel.ru support.selectel.ru

MCP_RECORDS 14

  • yandex-verification: 077abf165823f0ef
  • yandex-verification: 4236ef37da2ae36c
  • yandex-verification: e0ed9a9824b650c3
  • yandex-verification: 7a9ec34427d07f0a
  • yandex-verification: bb42c92c75b3e03e
  • yandex-verification: 7c91f1b3b24058b3
  • yandex-verification: 3fc310bd20c42f1a
  • yandex-verification: dfd233380403e09d
  • yandex-verification: 7547c358b47e1ebe
  • yandex-verification: fe7b7524f9be4431

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:dmarc@reporting.unisender.com

BIMI_RECORDS 14

  • yandex-verification: 9b82f4863f7fccdd
  • yandex-verification: 7a9ec34427d07f0a
  • yandex-verification: 7d175cba5cb12b6d
  • yandex-verification: 3fc310bd20c42f1a
  • yandex-verification: 077abf165823f0ef
  • yandex-verification: 6a10680f71e07a97
  • yandex-verification: bb42c92c75b3e03e
  • yandex-verification: dfd233380403e09d
  • yandex-verification: 7c91f1b3b24058b3
  • yandex-verification: 4236ef37da2ae36c

MTA_STS_RECORDS 14

  • yandex-verification: fe7b7524f9be4431
  • yandex-verification: 7d175cba5cb12b6d
  • yandex-verification: e0ed9a9824b650c3
  • yandex-verification: 6a10680f71e07a97
  • yandex-verification: 077abf165823f0ef
  • yandex-verification: cdc55c3b7eb4a0a7
  • yandex-verification: 7a9ec34427d07f0a
  • yandex-verification: 7c91f1b3b24058b3
  • yandex-verification: 7547c358b47e1ebe
  • yandex-verification: bb42c92c75b3e03e

TLS Certificates (4)

Common NameIssuerExpires
zapchastrf.ru C=US, O=Let's Encrypt, CN=YE2 Mon, 21 Sep 2026 02:28:28 +0000
YE2 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 (57)

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_5740a0b5939a3f9d
Output Hash
797d2de3639c8bc1fc23b995e5632783114999821afb67b9d2b7755b4c80fb14
Signature
ed25519:4ee0e52d0921c5f072c7cccf4ef10da1a21cf202d62afce99e5ba5d33d6a0c52db9c6616344ca1bc680407006f7c8066f1ec11aca142ba6c2604d2bf2eaf4406
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser