CONTINUOUS INTERNET TELEMETRY24H DRIFT34,178 material changesacross 31,769 domains · 24h to ~65m agoDNS DRIFT54 domains changed DNS providertop destination koaladns.com · +32 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,680 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,156 sites429 rate-limit / 403 bot-block, a posture signal

yju.ac.kr

Observed Jul 27, 2026, 22:05 UTC (8d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of yju.ac.kr was taken 8d ago

yju.ac.kr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yju.ac.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 yju.ac.kr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 15:36 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 yju.ac.kr actually stands on - every host below is a signed observation
yju.ac.kr
A / AAAA
210.101.228.170
unattributedserves the site
NS
ns.yju.ac.krns4.yju.ac.krns2.yju.ac.kr
ac.kranswers its DNS
MX
sol9.yju.ac.kr
ac.krreceives its email

DNS Records

A 1

  • 210.101.228.170

MX 1

  • 10sol9.yju.ac.kr

TXT 8

  • google-site-verification=RDWiF4VCn5Kqre-82uJVHUUm-FOAHDglrVwSgVrrrN8
  • globalsign-domain-verification=soWKL6q2z9Hs9J50RYn9qN8kkh2XE0XIc6vIvlNv_S
  • v=spf1 ip4:210.101.225.41 ip4:210.101.225.150 ip4:210.101.228.167 ip4:210.101.228.171 ip4:210.101.228.172 ip4:210.101.228.175 ip4:210.101.228.141 ip4:210.101.228.13 ip4:210.101.228.14 ip4:210.101.225.73 ip4:210.101.228.221 -all
  • MS=70C9980F981F4375A0FE0C430618797F6D1AB395
  • globalsign-domain-verification=soWKL6q2z9Hs9J50RYn9qN8kkh2XE0XIc6vIvlNv_S
  • globalsign-domain-verification=soWKL6q2z9Hs9J50RYn9qN8kkh2XE0XIc6vIvlNv_S
  • globalsign-domain-verification=soWKL6q2z9Hs9J50RYn9qN8kkh2XE0XIc6vIvlNv_S
  • globalsign-domain-verification=soWKL6q2z9Hs9J50RYn9qN8kkh2XE0XIc6vIvlNv_S

NS 3

  • ns.yju.ac.kr
  • ns4.yju.ac.kr
  • ns2.yju.ac.kr

SOA 1

  • ns.yju.ac.kr root.ns.yjc.ac.kr

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_914eddc397df7774
Output Hash
2f25d83afdbe0c693d69ccdb7a3606698c8e0a5dffcd5cb20103ac9aaec4b6bd
Signature
ed25519:567851ddfc4a0280c057fabe9c99c39eb07ae7a5e8585d9d261979af67ae519d4e753c273755498b0068a3f122c009cbcd0e1c03ff41e9612826c3cabfd5e709
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser