Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Company dossiers reviewed before a decision

Topic pathway

Due diligence and reputation decisions

Verify entities and roles, interpret public allegations and reviews, and define decision conditions.

Which unresolved claim could change the decision?

First action

Identify the exact entity and transaction, then rank the material claims to test. Use stable identifiers before linking people, proceedings or companies.

Useful output

A documented identity check, contextual risk findings, missing documents and explicit conditions for proceeding or deferring.

Interpretation limit

An allegation is not a ruling; a shared address is not ownership; a negative review is not automatically manipulation. Retain dates, outcomes and plausible alternative explanations.

Keep the decision traceable

Record the fact being checked, the material reviewed, what remains unknown, the person responsible and the next review trigger. A result is useful when another reader can understand why an action was chosen and what would change it.

Consult primary source portals

Match the situation to a check and a usable output

SituationCheckRecord to keep
Partner existenceConnect trading name and legal identifier in the relevant register.Exact entity, documents and dates; existence separate from solvency.
Director or representativeVerify published role and authority for the transaction.Role source and mandate confirmation.
Public allegationFind origin, updates and the entity’s response.Facts separate from accusations; namesakes excluded.
Sanctions candidateCompare identifiers and current lists for relevant regimes.Candidate, list, date, contradictions and compliance referral if unresolved.

When to pause and escalate

Rank unknowns that could change the decision. A material contradiction warrants a targeted request. Repeated articles with a shared origin cannot compensate for a missing decisive document.

Prepare a source and decision log →

FAQ

Is a registered company a safe partner?

Registration establishes administrative information. It validates neither the offer, payment nor correspondent’s authority.

How should a useful conclusion be written?

Describe established facts, hypotheses, unknowns and pre-decision conditions. Date the note and specify what triggers another review.

Reading technical evidence

Date an RDAP event rather than a website’s activity

An RDAP response pairs an event type with a date. Retain both fields together.

Field or situation and its interpretation
Observed itemWhat it means
eventAction: registrationRegistration event for the object; it does not date the website’s first publication.
eventAction: last changedA change to the registered object; it does not prove a change of owner.
eventDateRead the date with its UTC offset and the response consultation date.

Record the exact domain and queried service. Corroborate the operator’s identity and publication history separately.

RFC 9083, § 4.5

Fictional learning scenario

A director shares a name with someone in an article

A partner search surfaces an article about a person with the same name. It contains no identifier supporting a reliable match.

  1. Observed fact
  2. Missing evidence
  3. Independent check
  4. Decision condition

What is established?

A shared name is observed. Connection to the reviewed entity is unproven; the allegation and any outcome require context.

Which check matters?

Compare roles, periods, jurisdictions and relevant public identifiers. Seek the primary source and any update before repeating the claim.

What changes the decision?

An identity mismatch requires removing the connection. If identity remains uncertain, mark the issue unresolved and specify which document could change the decision.

The shortcut to avoid

A shared name, registered-office address or similar photograph is insufficient to attribute proceedings to someone.

Further reading

Editorial resources on other sites