CONTINUOUS INTERNET TELEMETRY24H DRIFT25,322 material changesacross 24,507 domains · 24h to ~14h ago · -12,700 vs yesterdayROTATION55 domains moved DNS from kirklanddc.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW563 curated domains not reachable+32 vs yesterdaySITE ERRORS33,717 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,858 sites429 rate-limit / 403 bot-block, a posture signal

docvirt.com

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

This reading of docvirt.com was taken 5d ago

docvirt.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting docvirt.com 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 docvirt.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
Also usesGoogle Search Console
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 21:58 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 docvirt.com actually stands on - every host below is a signed observation
docvirt.com
A / AAAA
187.115.4.105
unattributedserves the site
NS
static-2.no-ip.comstatic-1.no-ip.comstatic-3.no-ip.com
no-ip.comanswers its DNS
MX
mail.docvirt.com
docvirt.comreceives its email

DNS Records

A 1

  • 187.115.4.105

MX 1

  • 5mail.docvirt.com

TXT 1

  • google-site-verification=h0FC8Sku6XBeFiFsvCn--KuBwjr062CLcY4qHdHUr8M

NS 3

  • static-2.no-ip.com
  • static-1.no-ip.com
  • static-3.no-ip.com

SOA 1

  • static-1.no-ip.com hostmaster.no-ip.com

MCP_RECORDS 1

  • google-site-verification=h0FC8Sku6XBeFiFsvCn--KuBwjr062CLcY4qHdHUr8M

DMARC_RECORDS 1

  • google-site-verification=h0FC8Sku6XBeFiFsvCn--KuBwjr062CLcY4qHdHUr8M

BIMI_RECORDS 1

  • google-site-verification=h0FC8Sku6XBeFiFsvCn--KuBwjr062CLcY4qHdHUr8M

MTA_STS_RECORDS 1

  • google-site-verification=h0FC8Sku6XBeFiFsvCn--KuBwjr062CLcY4qHdHUr8M

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_4177bc0b2a6da5da
Output Hash
8d2dc1c78defd12e8af9d69d632b7cf9cb93dcb4d0cd1c97563c3c31054faec1
Signature
ed25519:1ac7a9f1fb994ccd650ee498153a1f3d0829837d27702f1ed4f685b4eb79b310d1d811733813ad024eceb7357bc9f8fcc1575b3f110c1dfc78c09b4f32128408
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser