CONTINUOUS INTERNET TELEMETRY24H DRIFT48,244 material changesacross 46,548 domains · 24h to ~5h ago · +13,627 vs yesterdaySHIFT100 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,821 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 135,269 sites429 rate-limit / 403 bot-block, a posture signal

yorutomo.net

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

This reading of yorutomo.net was taken 3d ago

yorutomo.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yorutomo.net 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 yorutomo.net 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.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 07: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 yorutomo.net actually stands on - every host below is a signed observation
yorutomo.net
A / AAAA
172.234.27.233172.239.49.232172.239.193.67
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.234.27.233
  • 172.239.49.232
  • 172.239.193.67

MX 1

  • 80mx156.hostedmxserver.com

TXT 1

  • v=spf1 -all

NS 2

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

SOA 1

  • ns1.parklogic.com hostmaster.yorutomo.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_19d72a6c5d99fc76
Output Hash
d3a0ba73005af26aff77f0d1575da1a0882dcac9bfc3308868ea5f3b696c85af
Signature
ed25519:aee743339d9732038e56bff27369eadbe19ef1b6cb48ee48914da8d9e4f9ae4dc2b22c11939b0e24a113d0778c6d6f0215a861b17af419c92153c35b9ce9d108
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser