CONTINUOUS INTERNET TELEMETRY24H DRIFT64,140 material changesacross 60,105 domains · last 24h · +29,523 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 133,434 sites429 rate-limit / 403 bot-block, a posture signal

recochoku.net

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

This reading of recochoku.net was taken 3d ago

recochoku.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting recochoku.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 recochoku.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 14:56 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 recochoku.net actually stands on - every host below is a signed observation
recochoku.net
A / AAAA
35.79.210.217
unattributedserves the site
NS
ns-126.awsdns-15.comns-1439.awsdns-51.orgns-1698.awsdns-20.co.ukns-797.awsdns-35.net
awsdns-15.com + awsdns-51.org + moreanswers its DNS

DNS Records

A 1

  • 35.79.210.217

NS 4

  • ns-126.awsdns-15.com
  • ns-1439.awsdns-51.org
  • ns-1698.awsdns-20.co.uk
  • ns-797.awsdns-35.net

SOA 1

  • ns-1439.awsdns-51.org awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • v=spf1 +ip4:202.221.214.0/24 +ip4:210.128.88.0/24 ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;pct=100;rua=mailto:infra-rua@recochoku.co.jp

BIMI_RECORDS 1

  • v=spf1 +ip4:202.221.214.0/24 +ip4:210.128.88.0/24 ~all

MTA_STS_RECORDS 1

  • v=spf1 +ip4:202.221.214.0/24 +ip4:210.128.88.0/24 ~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_960cc5337f6b2888
Output Hash
1cd205f9a773d18501ee012a7d9445b492d3a6be8c5b1fbc52f1c4550c77e7b4
Signature
ed25519:08e1447c4b7a2f204c65cff63f12c48ae730229be652450c089e75e0970090648cf8ca01c84647667c687a5ab18426b5651c7367a050f329cc363cc4a5a2b404
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser