CONTINUOUS INTERNET TELEMETRY24H DRIFT48,209 material changesacross 44,537 domains · 24h to ~75m ago · +13,592 vs yesterdaySHIFT65 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,882 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 144,834 sites429 rate-limit / 403 bot-block, a posture signal

zsmspb.ru

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

This reading of zsmspb.ru was taken 2d ago

zsmspb.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zsmspb.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 zsmspb.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 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 12:49 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 zsmspb.ru actually stands on - every host below is a signed observation
zsmspb.ru
A / AAAA
45.130.41.164
unattributedserves the site
NS
ns2.beget.runs1.beget.runs2.beget.prons1.beget.pro+2 more
beget.ru + beget.pro + moreanswers its DNS
MX
mx1.beget.commx2.beget.com
beget.comreceives its email
TLS
zsmspb.ru
Let's Encryptissued its certificate

DNS Records

A 1

  • 45.130.41.164

MX 2

  • 10mx1.beget.com
  • 20mx2.beget.com

TXT 2

  • yandex-verification:2ca4a77710833d30
  • v=spf1 redirect=beget.com

NS 6

  • ns2.beget.ru
  • ns1.beget.ru
  • ns2.beget.pro
  • ns1.beget.pro
  • ns2.beget.com
  • ns1.beget.com

SOA 1

  • ns1.beget.com hostmaster.beget.com

MCP_RECORDS 1

  • v=spf1 redirect=beget.com

DMARC_RECORDS 1

  • v=spf1 redirect=beget.com

BIMI_RECORDS 1

  • v=spf1 redirect=beget.com

MTA_STS_RECORDS 1

  • v=spf1 redirect=beget.com

TLS Certificates (3)

Common NameIssuerExpires
zsmspb.ru C=US, O=Let's Encrypt, CN=YR2 Wed, 21 Oct 2026 06:03:37 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_5a2ee727d2d1dd73
Output Hash
cea842ec502ec746f7b0d649403006bd811c42d8576025da1009cc67132e62c1
Signature
ed25519:23525bcfe71c08665087a99f1a0e1690602fc8225e1eeea3fadb6de8385c2f8fb1b8caf622aa51628ff67318273d8fbd5fe25d899b6ebb99879a614e34f23809
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser