CONTINUOUS INTERNET TELEMETRY24H DRIFT50,822 material changesacross 49,512 domains · 24h to ~9h ago · -11,254 vs yesterdayROTATION55 domains moved DNS from magpiedns.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,744 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 122,719 sites429 rate-limit / 403 bot-block, a posture signal

dqm-jcw.com

Observed Jul 26, 2026, 00:55 UTC (11d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of dqm-jcw.com was taken 11d ago

dqm-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 dqm-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 dqm-jcw.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-05 12:01 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 dqm-jcw.com actually stands on - every host below is a signed observation
dqm-jcw.com
A / AAAA
177.211.14.165
unattributedserves the site
NS
a.share-dns.comb.share-dns.net
share-dns.com + share-dns.netanswers its DNS
TLS
dqm-jcw.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 177.211.14.165

NS 2

  • a.share-dns.com
  • b.share-dns.net

SOA 1

  • a.share-dns.com master.share-dns.com

TLS Certificates (4)

Common NameIssuerExpires
dqm-jcw.com C=US, O=Let's Encrypt, CN=YE1 Wed, 09 Sep 2026 06:33:45 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

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_c3172afecd069044
Output Hash
712f98a2c7dc6ce66815cdbd7055838f77bc2c681bf415eae489a87fa37a3196
Signature
ed25519:6ce96d8333352d1e364d181b79a739894c3666e85fd2e601dfbe6e09e80f079be62562f01e68827f45b97b7c39cfc8214f7fcafbb48d8b6e534f7c0038e8cb0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser