ERPSCAN

• SanctionsRecords foundSanctioned by 1 authority: OFAC. Confirmed present in a source snapshot within the last 90 days.
• Debarment & exclusion— Checked, nothing found16 sources read, none holding a record for this company.
• Ownership & controlRecords foundControlled by a designated company: DIGITAL SECURITY.
• People— Not assessedNothing has been read for this company on this dimension.
• Identity & registration— Not assessedNothing has been read for this company on this dimension.
• JurisdictionRecords foundRussia is named on a jurisdiction designation list — European Commission, EU list of high-risk third countries (AMLD Art. 9), section IV: “High-risk third countries which are not identified as being subject to calls for action or increased monitoring by the FATF, but whose membership in that international standard-setter is suspended”. The designation is of the jurisdiction, not of this record.
• Court records— Not assessedNothing has been read for this company on this dimension.

• OFACActive

  CYBER2

  Designation date not published by this authority · OFAC SDN

No people recorded against this company. Officer and ownership data comes from national business registers, and the registers this system reads cover a different set of countries from the sanctions lists — so a sanctioned company frequently has none.

Legal name

ERPSCAN

Also known as

ERPSCAN

Jurisdiction

RU

First recorded here

28 Aug 2026

1. Parent company recorded: DIGITAL SECURITY

   11 Sept 2026 · OFAC SDN

2. Sanction listed: OFAC — CYBER2

   28 Aug 2026 · OFAC SDN

3. Alias recorded: ERPSCAN

   28 Aug 2026 · OFAC SDN

4. First recorded: ERPSCAN

   28 Aug 2026 · OFAC SDN

No ownership test is on file for this company. The test reads who holds a company's shares from its shareholder register, and it is run each day for companies with a number in Estonia's, Latvia's or Poland's register. For a company anywhere else, no register read here states its shareholders, so the test cannot be run.

No people recorded against this company. Officer data comes from national business registers, and a company outside those jurisdictions will have none here even when its officers are publicly known elsewhere.

4 companies, 3 recorded links, up to two steps from this record. Open the full graph ›

No address has been read for this company, so this was never checked — which is not the same as finding nothing.

Each reading is kept with the methodology version that produced it. A later reading is not a correction of an earlier one — it is a different question asked of more sources.

• Fact

  erpscan

  Legal name

  Evidence

  24652

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  RU

  Jurisdiction

  Evidence

  24652

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  OFAC — CYBER2

  Designation

  Evidence

  24652

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

Records from these sources are matched into one company only on a shared identifier, or by a human reviewer — never on name similarity alone. How this works. Not legal or compliance advice: check the originals before acting on anything here.

TRUE

A source states it. Rendered as a fact, with the source attached.

FALSE

A source explicitly denies it. Rare, and never inferred from silence.

UNKNOWN

Checked, nothing found. Rendered as an em dash, never as 0 or "no".

NOT_ASSESSED

Never checked — nothing was read here. Excluded from coverage, and not counted as clean.

2 records on this company — identifiers, aliases, officers, listings, figures — each carry the source that wrote them and are shown beside their own entries. The fields above are different: the entities table has no source column, so what is shown is every source whose stored payload contains the value verbatim. That is strong evidence, not proof of which write landed it, and where nothing contains the value the row says so instead of naming a plausible source.