Dataset · Baseline release
A reproducible check of whether seven official entry points used in Ukrainian counterparty verification responded to an unauthenticated automated request.
6 of 7 official entry points returned a successful HTTP response. The Ukraine State Sanctions Register returned HTTP 403 to the monitor's request. The other six entry points returned HTTP 200.
This establishes only how those URLs responded from Salient One infrastructure at the observation time. It does not establish data completeness, freshness, legal availability, human-browser access, or permission for automated reuse.
“In Salient One’s 6 August 2026 baseline, six of seven official counterparty-evidence entry points responded successfully to an unauthenticated automated request. Technical access is not the same as evidentiary completeness.” — Pietro Scarpa, Managing Partner, Salient One
| Evidence layer | Official entry point | Observed response | Classification |
|---|---|---|---|
| Legal identity | Ukraine Unified State Register | HTTP 200 | Accessible |
| Public procurement | Prozorro tender search | HTTP 200 | Accessible |
| Court record | Unified State Register of Court Decisions | HTTP 200 | Accessible |
| Ukraine sanctions | Ukraine State Sanctions Register | HTTP 403 | Restricted automated access |
| United States sanctions | OFAC Sanctions List Search | HTTP 200 | Accessible |
| United Kingdom sanctions | UK Sanctions List search | HTTP 200 | Accessible |
| European Union sanctions | EU consolidated financial sanctions dataset | HTTP 200 | Accessible |
The monitor sent an unauthenticated HTTP GET to each configured URL from Salient One infrastructure, followed redirects, identified itself as SalientOne-Evidence-Monitor/1.0, and used a 25-second timeout. Responses from 200 through 399 are classified as accessible. HTTP 401, 403 and 429 are classified as restricted automated access. Network failure or timeout is classified as no response.
The configuration is versioned. Each release preserves the observation time, final URL, response code, response time and any request error in JSON and CSV. A later change can therefore be distinguished from a change in narrative.
A successful HTTP response does not prove that the source exposes every necessary record, that its data is current, that the interface may be scraped, or that a result supports a legal conclusion. A restricted automated response does not prove that the source is unavailable to a person using an ordinary browser or an authorised interface.
This monitor is a diagnostic for the evidence environment. Counterparty decisions still require identifier resolution, source-specific interpretation, documented limitations and, where necessary, direct verification. See the full verification method.
Suggested citation: Pietro Scarpa, “Ukraine Counterparty Evidence Access Monitor — August 2026,” Salient One, observed 6 August 2026, https://salientone.eu/intelligence/ukraine-counterparty-evidence-monitor.
Reuse is permitted under CC BY 4.0 with attribution and the methodology limitation retained. Corrections can be sent to [email protected].