CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~3h ago · +33,471 vs yesterdayROTATION56 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

v100v.net

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

This reading of v100v.net was taken 3d ago

v100v.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting v100v.net 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 v100v.net 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
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 06: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 v100v.net actually stands on - every host below is a signed observation
v100v.net
A / AAAA
172.237.146.39172.237.146.46172.237.146.18
unattributedserves the site
NS
ns1.parklogic.comns2.parklogic.com
parklogic.comanswers its DNS
MX
mx156.hostedmxserver.com
hostedmxserver.comreceives its email

DNS Records

A 3

  • 172.237.146.39
  • 172.237.146.46
  • 172.237.146.18

MX 1

  • 10mx156.hostedmxserver.com

TXT 1

  • v=spf1 -all

NS 2

  • ns1.parklogic.com
  • ns2.parklogic.com

SOA 1

  • ns1.parklogic.com hostmaster.v100v.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -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_8d814d991b5ea52a
Output Hash
9a7a3765044bbe0a4f30a099cc32f6ea62e0c59cc4aa85e96441615cefbba49b
Signature
ed25519:0db2c96cac74dff3b66cf0d254d9812d245051bf00451117164a97d04921d1d8846ce1b10eaa878a259969e821dafbcd5eaf3e59f2b3dbea5a8fe173f114c800
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser