CONTINUOUS INTERNET TELEMETRY24H DRIFT22,591 material changesacross 20,783 domains · 24h to ~60m agoROTATION56 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,530 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,011 sites429 rate-limit / 403 bot-block, a posture signal

liquimoly.ru

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

This reading of liquimoly.ru was taken 6d ago

liquimoly.ru is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting liquimoly.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 liquimoly.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 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 21: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 liquimoly.ru actually stands on - every host below is a signed observation
liquimoly.ru
A / AAAA
79.174.81.16
unattributedserves the site
NS
ns3-l2.nic.runs4-l2.nic.runs8-l2.nic.runs4-cloud.nic.ru+1 more
nic.ruanswers its DNS
MX
mail.liquimoly.ru
liquimoly.rureceives its email
TLS
liquimoly.ru
Let's Encryptissued its certificate

DNS Records

A 1

  • 79.174.81.16

MX 1

  • 10mail.liquimoly.ru

TXT 2

  • n7yh3swlsvjbz5ydyjlg21mgg1n5qbcr
  • v=spf1 ip4:194.67.67.234 +a +mx ~all

NS 5

  • ns3-l2.nic.ru
  • ns4-l2.nic.ru
  • ns8-l2.nic.ru
  • ns4-cloud.nic.ru
  • ns8-cloud.nic.ru

SOA 1

  • ns3-l2.nic.ru dns.nic.ru

MCP_RECORDS 1

  • v=spf1 ip4:194.67.67.234 +a +mx ~all

DMARC_RECORDS 1

  • v=spf1 ip4:194.67.67.234 +a +mx ~all

BIMI_RECORDS 1

  • v=spf1 ip4:194.67.67.234 +a +mx ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:194.67.67.234 +a +mx ~all

TLS Certificates (3)

Common NameIssuerExpires
liquimoly.ru C=US, O=Let's Encrypt, CN=YR1 Fri, 02 Oct 2026 05:28:27 +0000
YR1 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_56e9540fc836f81e
Output Hash
db0a42286dfdd2a8370cd81181ce05757d2a6d9130d755977b9b5cbd7786f7c2
Signature
ed25519:6947d55c042eecf9f17ac1302da95515b8a221a57d84e85e916d48184f5c7711f2bc1ec976d27f39ed61b0adce51060b088f35920608af25c00459aec358e30d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser