CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 14,396 material changesacross 13,841+ domains · 24h to ~10h ago · a floor, 14h of 24 walkedSHIFT6 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signal

ys-clean.co.kr

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

This reading of ys-clean.co.kr was taken 1d ago

ys-clean.co.kr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ys-clean.co.kr 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 ys-clean.co.kr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 14:05 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 ys-clean.co.kr actually stands on - every host below is a signed observation
ys-clean.co.kr
A / AAAA
183.111.183.88
unattributedserves the site
NS
ns3.ys-clean.co.krns2.ys-clean.co.krns1.ys-clean.co.krns.ys-clean.co.kr
ys-clean.co.kranswers its DNS
MX
rmw-002.fmcity.com
fmcity.comreceives its email

DNS Records

A 1

  • 183.111.183.88

MX 1

  • 10rmw-002.fmcity.com

TXT 1

  • v=spf1 ip4:211.34.104.37 ~all

NS 4

  • ns3.ys-clean.co.kr
  • ns2.ys-clean.co.kr
  • ns1.ys-clean.co.kr
  • ns.ys-clean.co.kr

SOA 1

  • ys-clean.co.kr postmaster.ys-clean.co.kr

MCP_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_6b309dccd8d4b3e1
Output Hash
ebcb8449c6f084e06b5874e9597f1b6fa0c95bd96c13c4d990212492db5dad5a
Signature
ed25519:4d51bb88e298875bad21d2230b6cdbd0b72cfc6446964ecd0e9396823560d6329718f2ef38169b8245969adbd7ba6ab6c966e5e3f7a72cb4ff528c2c8d351409
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser