CONTINUOUS INTERNET TELEMETRY24H DRIFT71,617 material changesacross 67,026 domains · last 24h · +37,000 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,860 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 127,610 sites429 rate-limit / 403 bot-block, a posture signal

avp.ru

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

This reading of avp.ru was taken 12d ago

avp.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting avp.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 avp.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
Runs onKaspersky Lab Switzerland
Also usesGoogle Search Console
tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 11: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 avp.ru actually stands on - every host below is a signed observation
avp.ru
A / AAAA
93.159.228.22
Kaspersky Lab Switzerlandserves the site
NS
ns3.kasperskylabs.netns2.kasperskylabs.netns1.kasperskylabs.net
kasperskylabs.netanswers its DNS
MX
mx13.kaspersky-labs.commx14.kaspersky-labs.commx12.kaspersky-labs.commx16.kaspersky-labs.com+1 more
kaspersky-labs.comreceives its email

DNS Records

A 1

  • 93.159.228.22

MX 5

  • 5mx13.kaspersky-labs.com
  • 5mx14.kaspersky-labs.com
  • 5mx12.kaspersky-labs.com
  • 10mx16.kaspersky-labs.com
  • 5mx15.kaspersky-labs.com

TXT 8

  • v=spf1 redirect=kaspersky.com
  • google-site-verification=l18MVZG-kxmN-QJzyf9BIge_rT_lMIInxY6AhdcjAcM
  • Bm+dQwu+u4EWDmvvW25oQ2SoOjxFlFGqpX9leEWzO1U=
  • rjzpym019z6q5t0n77vbtcmtv9z95921
  • v=DMARC1; p=reject; rua=mailto:dmarc-report-rua@kaspersky.com; ruf=mailto:dmarc-report@kaspersky.com; fo=0
  • v=spf1 redirect=kaspersky.com
  • v=spf1 redirect=kaspersky.com
  • v=spf1 redirect=kaspersky.com

NS 3

  • ns3.kasperskylabs.net
  • ns2.kasperskylabs.net
  • ns1.kasperskylabs.net

SOA 1

  • dnsmaster.kasperskylabs.net dnsadmin.kaspersky.com

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