CONTINUOUS INTERNET TELEMETRY24H DRIFT49,366 material changesacross 43,517 domains · 24h to ~80m ago · +14,960 vs yesterdayROTATION54 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW618 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,884 sites429 rate-limit / 403 bot-block, a posture signal

run-jcw.com

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

This reading of run-jcw.com was taken 7d ago

run-jcw.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting run-jcw.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 run-jcw.com 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.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 09:16 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 run-jcw.com actually stands on - every host below is a signed observation
run-jcw.com
A / AAAA
172.236.114.219172.238.170.106172.239.193.33
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.236.114.219
  • 172.238.170.106
  • 172.239.193.33

MX 1

  • 10mx156.hostedmxserver.com

TXT 1

  • v=spf1 -all

NS 2

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

SOA 1

  • ns1.parklogic.com hostmaster.run-jcw.com

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_f90dfe90120c77cd
Output Hash
67b2c2c72d9fe407832d77cdec9fd2b162ce4ac90b0102321cb9a86fd01c7547
Signature
ed25519:a4b40b5271179ac40c23d70e1d075e0fbe1b39c3c8385d00d5226807de2e95b3eca77a80cbfe151eb181c21ad66d51c8e64982b0cda99d2426c0ca47d2fd8d07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser