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
All words are matched, in any order, regardless of accents or case. Combine the search with the filters below.
Results: 75
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.
Identify the service that added the results and confirm the trust boundary with the mail team.
Caution: A third-party header can mislead; pass does not authorise a payment.
Record Last-Modified or ETag alongside URL, consultation time and a representation copy.
Caution: An ETag can be weak; Last-Modified does not necessarily date publication.
Keep eventAction, eventDate, domain and queried service together.
Caution: Last changed does not prove a change of owner.
Calculate file SHA-256, record the algorithm and compare with a separately obtained reference.
Caution: A hash alone proves neither author nor date; conversion may change the bytes.
Link the score to the vector, CVSS version and product actually installed.
Caution: Do not compare two scores without their threat and environmental assumptions.
Record direct or ultimate parent, period and reported exception.
Caution: Accounting consolidation is not a complete ownership chart.
Record exact file, tool, signer and provenance validation result.
Caution: A signature does not establish scene truth; absence does not establish fabrication.
Record dataset, version, format, covered period and licence.
Caution: Update time is not a substitute for the measured period.
Compare scheme, host and effective port after local parsing.
Caution: The result checks neither DNS, certificates nor site content.
Retain OSM type, identifier and version with consultation time.
Caution: A map edit does not date the geographic event.
Compare id, relayed object, published and updated where available.
Caution: Do not apply this vocabulary to a platform that does not expose it.
Check of servers authorised for a domain’s SMTP identity.
Caution: Alone it validates neither the displayed author nor the request.
Signature connecting a signing domain with parts of a message.
Caution: The signing domain can belong to an intermediary.
Mechanism relating the From domain to aligned SPF or DKIM results.
Caution: It does not establish transaction authority.
Field specifying a proposed reply destination.
Caution: It can differ from From without alone proving fraud.
Message identifier intended to distinguish an instance in mail systems.
Caution: It does not authenticate authorship and can be copied.
DNS record making one name an alias of another.
Caution: It does not establish common ownership or management.
Number identifying an autonomous system in Internet routing.
Caution: It identifies neither a person nor every network customer.
Protocol used to exchange routing information between autonomous systems.
Caution: An announced route does not identify content ownership.
Certificate infrastructure for Internet number resources.
Caution: Route validation does not authenticate a website.
DNS extensions supporting data authentication and integrity.
Caution: Alone it neither encrypts queries nor certifies a company.
Certificate extension that can identify covered names.
Caution: A list of names is not a corporate ownership chart.
File describing vulnerability-disclosure contacts and practices.
Caution: Its presence does not grant blanket testing permission.
Identifier for a vulnerability in the CVE programme.
Caution: It is neither a score nor proof of presence on an asset.
Structured naming scheme for classes of IT products.
Caution: Name matching requires version and configuration checking.
Integration of a fix into an older maintained branch.
Caution: An older upstream version does not automatically establish missing patches.
Memento resource describing links to historical states.
Caution: Its coverage does not guarantee a capture of every change.
Header associating a Memento representation with its historical datetime.
Caution: It is not necessarily the first-publication time.
Format aggregating web resources and associated collection information.
Caution: It does not guarantee complete replay of every interaction.
Persistent object identifier resolvable to information about it.
Caution: It is not a guarantee of scientific quality.
Identifier used to distinguish researchers and connect contributions.
Caution: Record information can have different origins.
Organisation identifier in the Research Organization Registry.
Caution: An organisation record does not confirm a person’s current employment.
Publication identifying a document change or correction.
Caution: Read its scope before rejecting the entire document.
Work version circulated before possible final editorial publication.
Caution: Do not automatically assign it the status of the final version.
Address a publisher presents as a content’s main reference.
Caution: A canonical declaration does not authenticate authorship and may be wrong.
Interval and conditions within which a phenomenon was examined.
Caution: Absence outside that window cannot be inferred.
Have the responsible administrator review sessions, authorised applications and delegations.
Caution: A password change does not establish revocation of all permissions.
Record request, approval, order and execution with available references.
Caution: A recovery request does not guarantee returned funds.
Record platform, period, exclusions and examined-item count.
Caution: A displayed total does not replace an inventory of reviewed items.
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 reference can be reused with attribution to IIS and preservation of its cautions and version date.
Reading pathway

Break down the question: entity existence, account connection and request authorisation are three distinct issues.

For each check, identify the expected evidence and what a missing result would leave unknown. Avoid checked boxes without findings.

Stop when the issue is sufficiently clarified for the stated decision, or document why an additional check is needed.
IIS editorial reference, not a statistical dataset. Recommendations and scores are case-dependent reference points, not scientifically validated measurements.
Dataset version: . Each definition and recommendation should be read together with its interpretation limits.