Vessel and aircraft searches have narrower coverage

On this page

Type the subject correctly

Use entityType vessel or aircraft and include reliable identifiers when available. An IMO number, registration mark, or serial number should keep its type, meaningful characters, and source authority. Leading zeros must not disappear merely because a value looks numeric.

The matching layer has a tested derived form for an IMO prefix followed by exactly seven digits. That does not justify stripping punctuation or prefixes from every identifier type. The original source value remains separate from any derived search form.

Read source capabilities before screening

The OFAC SDN source includes vessel and aircraft records where published by the authority. Source capabilities and source-specific notes describe the supported fields. Select a source that supports the submitted entity type and review the actual identifiers present in each returned record.

The separate UN designated-vessels list is not integrated. SECO vessel names can be retained while an IMO number embedded in prose remains unstructured. SanctionsKit supplies no AIS tracking, flight data, operator history, flag history, or ownership research. A name-only asset result needs especially careful identity review.

Choosing available coverage

Choose the sources relevant to your workflow from current coverage. The directory shows available sources, record counts, and successful refresh times. The public demonstration and sandbox use invented records; production requests use the coverage you select.

Use source discovery to select named sources or a versioned package. Requested sources that are unknown, unavailable, or too stale cause an explicit error. SanctionsKit does not silently remove them from your request or report an incomplete check as a no-match result.