CONTINUOUS INTERNET TELEMETRY24H DRIFT36,140 material changesacross 33,159 domains · 24h to ~2h agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW559 curated domains not reachablelast probe, steadySITE ERRORS33,449 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,636 sites429 rate-limit / 403 bot-block, a posture signal

yesungdesign.co.kr

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

This reading of yesungdesign.co.kr was taken 9d ago

yesungdesign.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 yesungdesign.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 yesungdesign.co.kr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Secured byGoGetSSL
1 subdomain · 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:30 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 yesungdesign.co.kr actually stands on - every host below is a signed observation
yesungdesign.co.kr
A / AAAA
112.175.85.195
unattributedserves the site
NS
ns2.cafe24.comns.cafe24.com
cafe24.comanswers its DNS
MX
yesungdesign.co.kr
yesungdesign.co.krreceives its email
TLS
yesungdesign.co.kr
GoGetSSLissued its certificate

DNS Records

A 1

  • 112.175.85.195

MX 1

  • 10yesungdesign.co.kr

TXT 5

  • v=spf1 mx a ip4:116.122.158.82 include:cafe24.com ~all
  • v=spf1 mx a ip4:116.122.158.82 include:cafe24.com ~all
  • v=spf1 mx a ip4:116.122.158.82 include:cafe24.com ~all
  • v=spf1 mx a ip4:116.122.158.82 include:cafe24.com ~all
  • v=spf1 mx a ip4:116.122.158.82 include:cafe24.com ~all

NS 2

  • ns2.cafe24.com
  • ns.cafe24.com

SOA 1

  • yesungdesign.co.kr postmaster.yesungdesign.co.kr

TLS Certificates (3)

Common NameIssuerExpires
yesungdesign.co.kr C=LV, L=Riga, O=GoGetSSL, CN=GoGetSSL RSA DV CA Thu, 10 Dec 2026 23:59:59 +0000
GoGetSSL RSA DV CA C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority Tue, 05 Sep 2028 23:59:59 +0000
USERTrust RSA Certification Authority C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority Mon, 18 Jan 2038 23:59:59 +0000

Subdomains (1)

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