CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~2h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,518 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,266 sites429 rate-limit / 403 bot-block, a posture signal

lip5.ru

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

This reading of lip5.ru was taken 6d ago

lip5.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lip5.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 lip5.ru 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-07 18:43 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 lip5.ru actually stands on - every host below is a signed observation
lip5.ru
A / AAAA
104.21.56.52172.67.177.2542606:4700:3031::6815:38342606:4700:3037::ac43:b1fe
2606serves the site
NS
dorthy.ns.cloudflare.comvern.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
lip5.ru
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 104.21.56.52
  • 172.67.177.254

AAAA 2

  • 2606:4700:3031::6815:3834
  • 2606:4700:3037::ac43:b1fe

NS 2

  • dorthy.ns.cloudflare.com
  • vern.ns.cloudflare.com

SOA 1

  • dorthy.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (3)

Common NameIssuerExpires
lip5.ru C=US, O=Google Trust Services, CN=WE1 Fri, 23 Oct 2026 11:55:49 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

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