Identify the exact legal entity
Connect a trading name to the relevant registration number and register.
Caution: A similar name may refer to another company.

Open editorial reference · 2026
A structured starting point for checking an identity, domain, message, review, piece of evidence or decision. Each check states its useful question and the conclusion it cannot support alone.
How to read it
IIS editorial reference. Priorities 1 to 3 indicate a usual reading order, not a universal risk score. Adapt each check to scope, applicable law and the facts.
Priority 1 covers basic identity, destination or evidence checks; 2 helps test context and attribution; 3 supports follow-up. A priority number never replaces an assessment of harm.
Interactive reference
Results: 36
Connect a trading name to the relevant registration number and register.
Caution: A similar name may refer to another company.
Return to an official source or channel separate from the received message.
Caution: A public profile does not prove who controls the account.
Compare several matching identifiers before attribution.
Caution: Name and city alone are insufficient.
Separate declared ownership, directorship and operational control.
Caution: A shared address does not prove common management.
Read the main domain before subdomains and paths.
Caution: A padlock does not confirm site identity.
Record issuance, covered names and observation time.
Caution: An old certificate does not prove a current service.
Check whether an address or provider is shared.
Caution: Technical proximity does not establish ownership.
Compare spelling, context and official channels.
Caution: Similarity alone does not prove fraud.
Inspect the full address without replying to the message.
Caution: The visible name can be chosen freely.
Identify the main domain and redirects before visiting.
Caution: Link text can hide another destination.
Use a previously known or officially published contact.
Caution: The number in a doubtful message may be controlled by its sender.
Separate payment, secrets, installation and document sharing.
Caution: Claimed urgency is no substitute for confirmation.
Account for seasonality, volume and service incidents.
Caution: A single spike does not establish a campaign.
Separate the original source from republications.
Caution: Ten copies are not ten confirmations.
Compare timing, wording and distribution links.
Caution: Simultaneous repetition may be spontaneous.
Address verifiable facts where a correction will help.
Caution: An overly broad response can amplify marginal content.
Keep the full address and apparent publisher.
Caution: A context-free screenshot cannot establish origin.
Separate publication, consultation and modification.
Caution: A capture date is not the date of the event depicted.
Limit transformations and record necessary ones.
Caution: A hash alone does not prove initial authenticity.
Show what was not observed between events.
Caution: No trace is not proof of absence.
Separate established, probable, possible and unknown with reasons.
Caution: Do not turn a judgement into an invented percentage.
Describe plausible consequence, urgency and people affected.
Caution: A dramatic signal is not always the highest priority.
Link measure, deadline and evidence of correction.
Caution: An ownerless recommendation is difficult to execute.
Revisit after a change in asset, actor or context.
Caution: A dated finding does not remain valid indefinitely.
Separate published role, signing authority and permission for this request.
Caution: A real job title does not automatically authorise action for the entity.
Obtain details from a known site or register independently of the message.
Caution: A contact card copied into the message is not an independent channel.
Record public responses and time before linking a domain to a service.
Caution: Current DNS answers may not describe the state when the event happened.
Identify when a page or service changed, while recording archive gaps.
Caution: No archive does not prove no page existed on that date.
Compare sender, request and format with the expected process without running the file.
Caution: A familiar filename or visible extension may conceal the actual content.
Check why a conversation moves from a known channel to a new chat service or URL.
Caution: A switch may be legitimate but still needs independent confirmation.
Preserve the sponsored creative, displayed advertiser and final destination.
Caution: A displayed advertiser name does not prove the brand owner approved it.
Compare the earliest traceable post with later crops and captions.
Caution: The earliest version found may still be a later repost.
Keep the original time and zone before building a shared timeline.
Caution: Silent conversion can reverse the apparent event order.
Record export, copy, conversion, redaction and responsible person for each item.
Caution: A hash calculated after conversion does not describe the original.
State a plausible alternative and the observation that would distinguish it.
Caution: One coherent story can conceal weak attribution.
Define what is enough to decide, what remains unknown and when to reopen the case.
Caution: Searching without a precise question can add data without improving the decision.
No check matches these filters.
Put it to work
FAQ
No. Priorities describe a usual order of attention, not a universal score. The actual impact and urgency depend on the case.
No. Select the checks relevant to the decision and record which ones were not applicable or could not be completed.
The CSV and JSON files can be reused with attribution to IIS and preservation of their cautions and version date.
IIS editorial reference, not a statistical dataset. Recommendations and scores are case-dependent reference points, not scientifically validated measurements.
Dataset version: . Stable record IDs connect the bilingual JSON and CSV exports. Keep the caveats with each definition or recommendation.