Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-12 · 14 days ago
vet402Back to the registerMethodology

sanctions-screen.hergertsynthora.com/service

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://sanctions-screen.hergertsynthora.com/service
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x10800a5a5b9d72251566ec651e862a8b4b427de0
Declared price (base units)50000
Catalog statusdelisted (since 2026-09-13 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-12 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-172026-09-12
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-09-12 22:40 UTCPOSTfail402571 msmetadata_mismatch
2026-09-12 04:40 UTCPOSTfail402422 msmetadata_mismatch
2026-09-11 16:40 UTCPOSTfail402363 msmetadata_mismatch
2026-09-10 23:40 UTCPOSTfail402727 msmetadata_mismatch
2026-09-10 14:40 UTCPOSTfail402347 msmetadata_mismatch
2026-09-09 23:40 UTCPOSTfail402860 msmetadata_mismatch
2026-09-09 14:40 UTCPOSTfail402394 msmetadata_mismatch
2026-09-08 17:40 UTCPOSTfail402466 msmetadata_mismatch
2026-09-08 05:40 UTCPOSTfail402614 msmetadata_mismatch
2026-09-07 17:40 UTCPOSTfail402605 msmetadata_mismatch
2026-09-07 05:40 UTCPOSTfail402687 msmetadata_mismatch
2026-09-06 17:40 UTCPOSTfail402507 msmetadata_mismatch
2026-09-06 05:40 UTCPOSTfail402538 msmetadata_mismatch
2026-09-05 17:40 UTCPOSTfail402355 msmetadata_mismatch
2026-09-05 05:40 UTCPOSTfail402481 msmetadata_mismatch
2026-09-04 17:40 UTCPOSTfail402507 msmetadata_mismatch
2026-09-04 05:40 UTCPOSTfail402368 msmetadata_mismatch
2026-09-03 17:40 UTCPOSTfail402422 msmetadata_mismatch
2026-09-03 05:40 UTCPOSTfail402435 msmetadata_mismatch
2026-09-02 17:40 UTCPOSTfail402399 msmetadata_mismatch
2026-09-02 05:40 UTCPOSTfail402479 msmetadata_mismatch
2026-09-01 23:40 UTCPOSTfail402567 msmetadata_mismatch
2026-08-17 10:39 UTCPOSTpass402342 ms—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.

1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
08-17 12:48settled (amount + payee)2000x768cd4ec…81474972 ms
50000 units (≈ $0.05 USDC) · L2 no_declaration

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (sanctions-screen.hergertsynthora.com · measured 2026-08-17)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/50cda4cb-216d-4a0a-b9c7-7846fdc7e288.svg)](https://vet402.com/observatory/e/50cda4cb-216d-4a0a-b9c7-7846fdc7e288)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-13delisted{"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.