CONTINUOUS INTERNET TELEMETRY24H DRIFT71,617 material changesacross 67,026 domains · 24h to ~50m ago · +37,000 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW533 curated domains not reachablelast probe, steadySITE ERRORS33,847 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 126,417 sites429 rate-limit / 403 bot-block, a posture signal

yhl-jcw.com

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

This reading of yhl-jcw.com was taken 10d ago

yhl-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 yhl-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 yhl-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-04 02:14 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 yhl-jcw.com actually stands on - every host below is a signed observation
yhl-jcw.com
A / AAAA
177.211.55.2
unattributedserves the site
NS
a.share-dns.comb.share-dns.net
share-dns.com + share-dns.netanswers its DNS
TLS
yhl-jcw.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 177.211.55.2

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
yhl-jcw.com C=US, O=Let's Encrypt, CN=YE2 Wed, 09 Sep 2026 06:34:25 +0000
YE2 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_7ed15467a75d9aa0
Output Hash
815e10b071030b9f8f1140f37b2cab1bcc247d04d22ef26a3391ac7073385ed2
Signature
ed25519:132a9150247d219635ce08eecedc4cf39b67d9226d442a0d75260631516567415d7764189fc313aee847dc506ed911bb4d515a0b48a40408426cde69d44d2e06
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser