CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

vetmanager.cloud

Observed Aug 3, 2026, 00:57 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of vetmanager.cloud was taken 3d ago

vetmanager.cloud is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vetmanager.cloud 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 vetmanager.cloud Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 13:21 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 vetmanager.cloud actually stands on - every host below is a signed observation
vetmanager.cloud
A / AAAA
45.136.180.121
unattributedserves the site
NS
henry.ns.cloudflare.comruth.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
emx.mail.ru
mail.rureceives its email

DNS Records

A 1

  • 45.136.180.121

MX 1

  • 10emx.mail.ru

TXT 5

  • _globalsign-domain-verification=Dxvd6pasrNu6f8UpUgBOoX4DoEfszTqUgAyjWi9zWT
  • _globalsign-domain-verification=Oq1TfsWEajVOuXBW7Lkbl3W-36uBoo6rE4wgTmCcUQ
  • mailru-domain: aWYaiJYG4oYIWni4
  • v=spf1 redirect=_spf.mail.ru
  • zoho-verification=zb43755856.zmverify.zoho.com

NS 2

  • henry.ns.cloudflare.com
  • ruth.ns.cloudflare.com

SOA 1

  • henry.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 include:spf.mandrillapp.com ?all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:1c53153c5a0445369d9207b27371d490@dmarc-reports.cloudflare.net;

BIMI_RECORDS 1

  • v=spf1 include:spf.mandrillapp.com ?all

MTA_STS_RECORDS 1

  • v=spf1 include:spf.mandrillapp.com ?all

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_738f0cf437e02f2f
Output Hash
c472da0936cdc22e77079a3bb7c835c1f7b30b96c4839fa4674f3b511ee418c6
Signature
ed25519:0c3a4cc7b240f907d9824edab011641b77cf5bbb33703218e01e081b37f9bcfdde14641418d011a50f7df0f5ad19a8b0e034fcf5fdbcec84a0a84dc6321aea0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser