boo-log.com

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

This reading of boo-log.com was taken 1d ago

boo-log.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting boo-log.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 boo-log.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onKDDI CORPORATION
Registered withGMO Internet Group, Inc. d/b/a Onamae.com
Also usesGoogle Search ConsoleGlobalSign
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for boo-log.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

INFRASTRUCTURE MAPwhat boo-log.com actually stands on - every host below is a signed observation
boo-log.com
A / AAAA
106.184.98.198
KDDI CORPORATIONserves the site
NS
ns01.clog.jpns00.clog.jp
clog.jpanswers its DNS
MX
mailas02.clog.jp
clog.jpreceives its email

DNS Records

A 1

  • 106.184.98.198

MX 1

  • 10mailas02.clog.jp

TXT 3

  • v=spf1 include:spf.clog.jp ~all
  • google-site-verification=6rw4NsDp0pHi7Z5jMe50EVWO7iT9ZnZ5kOgCU1EuUB4
  • _globalsign-domain-verification=obanItdekfjnTmo7uB7QW-I1lmEhE50Fm1V4biVT67

NS 2

  • ns01.clog.jp
  • ns00.clog.jp

SOA 1

  • ns00.clog.jp root.ns00.clog.jp

CAA 2

  • issuewild "globalsign.com"
  • issue "globalsign.com"

MCP_RECORDS 1

  • v=spf1 include:spf.clog.jp ~all

DMARC_RECORDS 1

  • v=spf1 include:spf.clog.jp ~all

BIMI_RECORDS 1

  • v=spf1 include:spf.clog.jp ~all

MTA_STS_RECORDS 1

  • v=spf1 include:spf.clog.jp ~all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-17 07:27 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works

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_6f0ebcbf231230b8
Output Hash
a961d2e282dc417b586339b9a44682126b5b618e8c69319380f0cfc4a662c059
Signature
ed25519:f6198218dfd90eee2d64b106da83240e94474294a04e84ce7833ac39dbef1cf90df1df7bda7bf048d0493259b2a16207b7bc9478a71bfcb50d1e68f1423d5107
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT41,016 material changesacross 38,841 domains · 24h to ~2h ago · +1,776 vs yesterdayROTATION77 domains moved DNS from magpiedns.com to kirklanddc.com, 76 moved backa rotation loop, not a migration · 24hEMAIL DRIFT7 domains switched email provider24hNOW491 curated domains not reachable-100 vs yesterdaySITE ERRORS33,664 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,860 sites429 rate-limit / 403 bot-block, a posture signal