CONTINUOUS INTERNET TELEMETRY24H DRIFT33,779 material changesacross 31,481 domains · 24h to ~2h agoDNS DRIFT56 domains changed DNS providertop destination koaladns.com · +34 vs yesterdayNOW542 curated domains not reachablelast probe, steadySITE ERRORS33,709 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,223 sites429 rate-limit / 403 bot-block, a posture signal

yukle.tc

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

This reading of yukle.tc was taken 9d ago

yukle.tc is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yukle.tc 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 yukle.tc 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 04:38 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 yukle.tc actually stands on - every host below is a signed observation
yukle.tc
A / AAAA
172.239.194.205172.239.193.31172.232.4.147
unattributedserves the site
NS
ns2.parklogic.comns1.parklogic.com
parklogic.comanswers its DNS
MX
mx156.hostedmxserver.com
hostedmxserver.comreceives its email

DNS Records

A 3

  • 172.239.194.205
  • 172.239.193.31
  • 172.232.4.147

MX 1

  • 70mx156.hostedmxserver.com

TXT 5

  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • ns2.parklogic.com
  • ns1.parklogic.com

SOA 1

  • ns1.parklogic.com hostmaster.yukle.tc

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_4f1de15f739edd94
Output Hash
4985d028f78f25a25dd313eb8b2dc02228ebbdf780177a7cc8c12619f4f3da52
Signature
ed25519:3a6a653f31bcf5ebd219a39ea8c7beb4f872e7a6935dc7b6776ef3b15ae69d6291ca0edf89c62f27bbffd5b49c09565d8ad9f5e310ee9294b0e4d7a6fedc000a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser