CONTINUOUS INTERNET TELEMETRY24H DRIFT34,617 material changesacross 32,325 domains · 24h to ~2h agoDNS DRIFT49 domains changed DNS providertop destination koaladns.com · +27 vs yesterdayNOW542 curated domains not reachablelast probe, steadySITE ERRORS33,687 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,287 sites429 rate-limit / 403 bot-block, a posture signal

ygyg.kr

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

This reading of ygyg.kr was taken 2d ago

ygyg.kr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ygyg.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 ygyg.kr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured bySectigo
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 11:42 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 ygyg.kr actually stands on - every host below is a signed observation
ygyg.kr
A / AAAA
116.125.140.152
unattributedserves the site
NS
ns2.cafe24.co.krns1.cafe24.comns1.cafe24.co.krns2.cafe24.com
cafe24.co.kr + cafe24.comanswers its DNS
MX
husw7ssd-1056
husw7ssd-1056receives its email
TLS
ygyg.kr
Sectigo Limitedissued its certificate

DNS Records

A 1

  • 116.125.140.152

MX 1

  • 10husw7ssd-1056

TXT 1

  • v=spf1 ip4:116.125.140.152 ~all

NS 4

  • ns2.cafe24.co.kr
  • ns1.cafe24.com
  • ns1.cafe24.co.kr
  • ns2.cafe24.com

SOA 1

  • ygyg.kr postmaster.ygyg.kr

MCP_RECORDS 1

  • v=spf1 ip4:116.125.140.152 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:116.125.140.152 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:116.125.140.152 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:116.125.140.152 ~all

TLS Certificates (3)

Common NameIssuerExpires
ygyg.kr C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36 Tue, 05 Jan 2027 23:59:59 +0000
Sectigo Public Server Authentication CA DV R36 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Fri, 21 Mar 2036 23:59:59 +0000
Sectigo Public Server Authentication Root R46 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_d1aed69ac42d04d0
Output Hash
3470167055e2f8de705582bd279cbed94228a9f94c2788b01bb48d3eec070a90
Signature
ed25519:a0e5bb8ecad810cee41cabf0e404f7de0f230aff005c835f8f6e03ed895ce06ed4124ae80fc90be964c033b496f6ab7ebf67200d0dbbd0c68d429be25c9dcf0a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser