CONTINUOUS INTERNET TELEMETRY24H DRIFT12,660 material changesacross 11,816 domains · 24h to ~25m ago · +3,897 vs yesterdayNOW560 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 signalMOVERokta.comNo mail routes in the latest observation

yokosdesigns.com

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

This reading of yokosdesigns.com was taken 1d ago

yokosdesigns.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yokosdesigns.com 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 yokosdesigns.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 08:53 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 yokosdesigns.com actually stands on - every host below is a signed observation
yokosdesigns.com
A / AAAA
103.224.182.253
unattributedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
34hh.store
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10park-mx.above.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns1.abovedomains.com
  • ns2.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
34hh.store C=US, O=Let's Encrypt, CN=YR2 Wed, 28 Oct 2026 08:07:22 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

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