Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago

domain.hugen.tokyo/domain/full

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://domain.hugen.tokyo/domain/full
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-22 01:53 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-042026-10-18
Figure 1. Probe timeline, last 23 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-18 16:40 UTCGETpass402745 ms—
2026-10-17 13:40 UTCGETpass402716 ms—
2026-10-15 21:40 UTCGETpass4021850 ms—
2026-10-14 15:40 UTCGETpass402750 ms—
2026-10-13 03:40 UTCGETfail—10001 mstimeoutNo response headers arrived within 10 seconds.
2026-10-12 03:40 UTCGETpass402764 ms—
2026-10-11 03:40 UTCGETpass402751 ms—
2026-10-10 03:40 UTCGETpass402694 ms—
2026-10-08 22:40 UTCGETpass402678 ms—
2026-10-07 16:40 UTCGETpass402628 ms—
2026-10-06 22:40 UTCGETpass402713 ms—
2026-10-05 22:40 UTCGETpass402685 ms—
2026-10-04 13:40 UTCGETpass402742 ms—
2026-10-03 16:40 UTCGETpass402626 ms—
2026-10-02 22:40 UTCGETpass402844 ms—
2026-10-02 04:40 UTCGETpass402986 ms—
2026-09-27 10:30 UTCGETpass402210 ms—
2026-09-22 11:24 UTCGETpass402201 ms—
2026-09-18 11:24 UTCGETpass402204 ms—
2026-09-16 11:24 UTCGETpass402560 ms—
2026-09-12 11:24 UTCGETpass402535 ms—
2026-09-08 11:24 UTCGETpass402705 ms—
2026-09-04 11:24 UTCGETpass402741 ms—

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-06relisted{"status":"delisted"}{"status":"active"}
2026-10-06delisted{"status":"active"}{"status":"delisted"}

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.

20–2,000 characters · 0 so far