Analyst organising source and decision checks in a physical matrix

Open editorial reference · 2026

Digital verification matrix.

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.

CSV · 24 checks JSON · bilingual details

How to read it

Choose the checks that answer the real question.

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

Explore 24 checks in six categories.

Search Category Priority

24checks displayed

Identity and entities · Priority 1Identify the exact legal entity

Connect a trading name to the relevant registration number and register.

Caution: A similar name may refer to another company.

Identity and entities · Priority 1Confirm the correspondent’s role

Return to an official source or channel separate from the received message.

Caution: A public profile does not prove who controls the account.

Identity and entities · Priority 2Rule out namesakes

Compare several matching identifiers before attribution.

Caution: Name and city alone are insufficient.

Identity and entities · Priority 2Qualify control relationships

Separate declared ownership, directorship and operational control.

Caution: A shared address does not prove common management.

Public infrastructure · Priority 1Check the registrable domain

Read the main domain before subdomains and paths.

Caution: A padlock does not confirm site identity.

Public infrastructure · Priority 2Date the observed certificate

Record issuance, covered names and observation time.

Caution: An old certificate does not prove a current service.

Public infrastructure · Priority 2Avoid attribution by shared hosting

Check whether an address or provider is shared.

Caution: Technical proximity does not establish ownership.

Public infrastructure · Priority 1Spot a lookalike domain

Compare spelling, context and official channels.

Caution: Similarity alone does not prove fraud.

Messages and channels · Priority 1Compare display name and actual sender domain

Inspect the full address without replying to the message.

Caution: The visible name can be chosen freely.

Messages and channels · Priority 1Read a link destination

Identify the main domain and redirects before visiting.

Caution: Link text can hide another destination.

Messages and channels · Priority 1Call back using an independent number

Use a previously known or officially published contact.

Caution: The number in a doubtful message may be controlled by its sender.

Messages and channels · Priority 1Classify a sensitive request

Separate payment, secrets, installation and document sharing.

Caution: Claimed urgency is no substitute for confirmation.

Reputation and narratives · Priority 2Compare reviews with a baseline

Account for seasonality, volume and service incidents.

Caution: A single spike does not establish a campaign.

Reputation and narratives · Priority 2Find the original claim

Separate the original source from republications.

Caution: Ten copies are not ten confirmations.

Reputation and narratives · Priority 2Test relay independence

Compare timing, wording and distribution links.

Caution: Simultaneous repetition may be spontaneous.

Reputation and narratives · Priority 3Choose a response channel

Address verifiable facts where a correction will help.

Caution: An overly broad response can amplify marginal content.

Evidence and timeline · Priority 1Preserve URL and source

Keep the full address and apparent publisher.

Caution: A context-free screenshot cannot establish origin.

Evidence and timeline · Priority 1Date observation and time zone

Separate publication, consultation and modification.

Caution: A capture date is not the date of the event depicted.

Evidence and timeline · Priority 1Preserve original and working copy

Limit transformations and record necessary ones.

Caution: A hash alone does not prove initial authenticity.

Evidence and timeline · Priority 2Mark unknown timeline intervals

Show what was not observed between events.

Caution: No trace is not proof of absence.

Decision and response · Priority 1Assign a confidence level

Separate established, probable, possible and unknown with reasons.

Caution: Do not turn a judgement into an invented percentage.

Decision and response · Priority 1Connect the signal to impact

Describe plausible consequence, urgency and people affected.

Caution: A dramatic signal is not always the highest priority.

Decision and response · Priority 2Assign an action owner

Link measure, deadline and evidence of correction.

Caution: An ownerless recommendation is difficult to execute.

Decision and response · Priority 3Set a review trigger

Revisit after a change in asset, actor or context.

Caution: A dated finding does not remain valid indefinitely.

Put it to work

Guides applying these checks.

Verify a job offer and recruiterIdentity and channels → Assess online reviewsReputation and evidence → Verify a fundraising appealEntity and payment →

FAQ

Using the matrix responsibly.

Is this a risk score?

No. Priorities describe a usual order of attention, not a universal score. The actual impact and urgency depend on the case.

Must all 24 checks be performed?

No. Select the checks relevant to the decision and record which ones were not applicable or could not be completed.

Can the dataset be reused?

The CSV and JSON files can be reused with attribution to IIS and preservation of their cautions and version date.