Dataset · September observation

Ukraine Counterparty Evidence Access Monitor

A reproducible check of whether seven official entry points used in Ukrainian counterparty verification responded to an unauthenticated automated request.

01

What did the September 2026 observation establish?

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.

The seven source classifications are unchanged from the August baseline. The original baseline commentary is retained below.

“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, Co-Managing Partner, Salient One
02

Which sources were checked?

Evidence layerOfficial entry pointObserved responseClassification
Legal identityUkraine Unified State RegisterHTTP 200Accessible
Public procurementProzorro tender searchHTTP 200Accessible
Court recordUnified State Register of Court DecisionsHTTP 200Accessible
Ukraine sanctionsUkraine State Sanctions RegisterHTTP 403Restricted automated access
United States sanctionsOFAC Sanctions List SearchHTTP 200Accessible
United Kingdom sanctionsUK Sanctions List searchHTTP 200Accessible
European Union sanctionsEU consolidated financial sanctions datasetHTTP 200Accessible
03

How was the monitor run?

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.

04

What must not be concluded?

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.

05

How should the monitor be cited?

Suggested citation: Salient One, “Ukraine Counterparty Evidence Access Monitor — September 2026,” Salient One, observed 8 September 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 engage@salientone.eu.

Ukraine evidence system

Use access evidence at the right level.

This monitor tests seven selected technical entry points. Ukraine 1 operates across ten source families. Neither number is a completeness claim, and a successful response is not a verified counterparty finding.

This access monitor is a technical diagnostic, not legal advice, a source-quality score or a conclusion about any entity.