Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
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.

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 75 checks in six categories.

All words are matched, in any order, regardless of accents or case. Combine the search with the filters below.

Results: 75

Identity and entities · Priority 1

Confirm 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 2

Rule out namesakes

Compare several matching identifiers before attribution.

Caution: Name and city alone are insufficient.

Identity and entities · Priority 2

Qualify control relationships

Separate declared ownership, directorship and operational control.

Caution: A shared address does not prove common management.

Public infrastructure · Priority 1

Check the registrable domain

Read the main domain before subdomains and paths.

Caution: A padlock does not confirm site identity.

Public infrastructure · Priority 2

Date the observed certificate

Record issuance, covered names and observation time.

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

Public infrastructure · Priority 2

Avoid attribution by shared hosting

Check whether an address or provider is shared.

Caution: Technical proximity does not establish ownership.

Public infrastructure · Priority 1

Spot a lookalike domain

Compare spelling, context and official channels.

Caution: Similarity alone does not prove fraud.

Messages and channels · Priority 1

Compare 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 1

Call 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 1

Classify a sensitive request

Separate payment, secrets, installation and document sharing.

Caution: Claimed urgency is no substitute for confirmation.

Reputation and narratives · Priority 2

Compare reviews with a baseline

Account for seasonality, volume and service incidents.

Caution: A single spike does not establish a campaign.

Reputation and narratives · Priority 2

Find the original claim

Separate the original source from republications.

Caution: Ten copies are not ten confirmations.

Reputation and narratives · Priority 2

Test relay independence

Compare timing, wording and distribution links.

Caution: Simultaneous repetition may be spontaneous.

Reputation and narratives · Priority 3

Choose a response channel

Address verifiable facts where a correction will help.

Caution: An overly broad response can amplify marginal content.

Evidence and timeline · Priority 1

Preserve URL and source

Keep the full address and apparent publisher.

Caution: A context-free screenshot cannot establish origin.

Evidence and timeline · Priority 1

Date 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 1

Preserve original and working copy

Limit transformations and record necessary ones.

Caution: A hash alone does not prove initial authenticity.

Evidence and timeline · Priority 2

Mark unknown timeline intervals

Show what was not observed between events.

Caution: No trace is not proof of absence.

Decision and response · Priority 1

Assign 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 1

Connect 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 2

Assign an action owner

Link measure, deadline and evidence of correction.

Caution: An ownerless recommendation is difficult to execute.

Decision and response · Priority 3

Set a review trigger

Revisit after a change in asset, actor or context.

Caution: A dated finding does not remain valid indefinitely.

Identity and entities · Priority 2

Verify the claimed mandate

Separate published role, signing authority and permission for this request.

Caution: A real job title does not automatically authorise action for the entity.

Identity and entities · Priority 1

Find an official contact route

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.

Public infrastructure · Priority 2

Time-stamp an observed DNS configuration

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.

Public infrastructure · Priority 3

Compare archived versions

Identify when a page or service changed, while recording archive gaps.

Caution: No archive does not prove no page existed on that date.

Messages and channels · Priority 1

Assess an unexpected attachment

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.

Messages and channels · Priority 2

Explain a change of channel

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.

Reputation and narratives · Priority 2

Identify a paid ad’s origin

Preserve the sponsored creative, displayed advertiser and final destination.

Caution: A displayed advertiser name does not prove the brand owner approved it.

Reputation and narratives · Priority 2

Find the earliest available media version

Compare the earliest traceable post with later crops and captions.

Caution: The earliest version found may still be a later repost.

Evidence and timeline · Priority 1

Normalise times and zones

Keep the original time and zone before building a shared timeline.

Caution: Silent conversion can reverse the apparent event order.

Evidence and timeline · Priority 2

Log evidence transformations

Record export, copy, conversion, redaction and responsible person for each item.

Caution: A hash calculated after conversion does not describe the original.

Decision and response · Priority 2

Test an alternative explanation

State a plausible alternative and the observation that would distinguish it.

Caution: One coherent story can conceal weak attribution.

Decision and response · Priority 3

Set a review stopping rule

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.

Messages and channels · Priority 1

Check the origin of Authentication-Results

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.

Evidence and timeline · Priority 2

Separate HTTP validator from event date

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.

Public infrastructure · Priority 2

Retain the RDAP event type

Keep eventAction, eventDate, domain and queried service together.

Caution: Last changed does not prove a change of owner.

Evidence and timeline · Priority 2

Compare the hash with a retained reference

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.

Decision and response · Priority 2

Retain CVSS vector and version

Link the score to the vector, CVSS version and product actually installed.

Caution: Do not compare two scores without their threat and environmental assumptions.

Identity and entities · Priority 2

Read the LEI relationship type

Record direct or ultimate parent, period and reported exception.

Caution: Accounting consolidation is not a complete ownership chart.

Evidence and timeline · Priority 2

Separate signature from media context

Record exact file, tool, signer and provenance validation result.

Caution: A signature does not establish scene truth; absence does not establish fabrication.

Evidence and timeline · Priority 2

Identify the consulted distribution

Record dataset, version, format, covered period and licence.

Caution: Update time is not a substitute for the measured period.

Public infrastructure · Priority 2

Compare HTTP or HTTPS origins

Compare scheme, host and effective port after local parsing.

Caution: The result checks neither DNS, certificates nor site content.

Evidence and timeline · Priority 2

Recover a map-object version

Retain OSM type, identifier and version with consultation time.

Caution: A map edit does not date the geographic event.

Reputation and narratives · Priority 2

Separate ActivityStreams publication and relay

Compare id, relayed object, published and updated where available.

Caution: Do not apply this vocabulary to a platform that does not expose it.

Public infrastructure · Priority 2

Record the SPF domain and service reporting the result.

Check of servers authorised for a domain’s SMTP identity.

Caution: Alone it validates neither the displayed author nor the request.

Public infrastructure · Priority 2

Compare the d= domain with the claimed identity.

Signature connecting a signing domain with parts of a message.

Caution: The signing domain can belong to an intermediary.

Public infrastructure · Priority 2

Retain result, From domain and aligned mechanism.

Mechanism relating the From domain to aligned SPF or DKIM results.

Caution: It does not establish transaction authority.

Evidence and timeline · Priority 2

Compare the reply destination with the established channel.

Field specifying a proposed reply destination.

Caution: It can differ from From without alone proving fraud.

Evidence and timeline · Priority 2

Keep Message-ID with the original message, not in isolation.

Message identifier intended to distinguish an instance in mail systems.

Caution: It does not authenticate authorship and can be copied.

Public infrastructure · Priority 2

Date the queried name, target and DNS answer.

DNS record making one name an alias of another.

Caution: It does not establish common ownership or management.

Public infrastructure · Priority 2

Separate observed ASN, registered organisation and website operator.

Number identifying an autonomous system in Internet routing.

Caution: It identifies neither a person nor every network customer.

Public infrastructure · Priority 2

Record prefix, route origin, collector and period.

Protocol used to exchange routing information between autonomous systems.

Caution: An announced route does not identify content ownership.

Public infrastructure · Priority 2

Describe validation without treating it as website reputation.

Certificate infrastructure for Internet number resources.

Caution: Route validation does not authenticate a website.

Public infrastructure · Priority 2

Separate DNS validation from commercial legitimacy.

DNS extensions supporting data authentication and integrity.

Caution: Alone it neither encrypts queries nor certifies a company.

Public infrastructure · Priority 2

Record SAN names and certificate validity bounds.

Certificate extension that can identify covered names.

Caution: A list of names is not a corporate ownership chart.

Decision and response · Priority 2

Check origin, expiry and policy scope.

File describing vulnerability-disclosure contacts and practices.

Caution: Its presence does not grant blanket testing permission.

Decision and response · Priority 2

Connect the CVE identifier to the actually installed product.

Identifier for a vulnerability in the CVE programme.

Caution: It is neither a score nor proof of presence on an asset.

Public infrastructure · Priority 2

Check vendor, product, version and matching conditions.

Structured naming scheme for classes of IT products.

Caution: Name matching requires version and configuration checking.

Decision and response · Priority 2

Compare installed build with the maintained-branch advisory.

Integration of a fix into an older maintained branch.

Caution: An older upstream version does not automatically establish missing patches.

Evidence and timeline · Priority 2

Retain the consulted list and actual selected capture URL.

Memento resource describing links to historical states.

Caution: Its coverage does not guarantee a capture of every change.

Evidence and timeline · Priority 2

Separate representation time from the content’s claimed date.

Header associating a Memento representation with its historical datetime.

Caution: It is not necessarily the first-publication time.

Evidence and timeline · Priority 2

Inventory preserved resources and replay limitations.

Format aggregating web resources and associated collection information.

Caution: It does not guarantee complete replay of every interaction.

Evidence and timeline · Priority 2

Compare DOI, title, authors and publication type.

Persistent object identifier resolvable to information about it.

Caution: It is not a guarantee of scientific quality.

Identity and entities · Priority 2

Examine the origin of the displayed affiliation.

Identifier used to distinguish researchers and connect contributions.

Caution: Record information can have different origins.

Identity and entities · Priority 2

Connect the ROR organisation and affiliation without conflating evidence.

Organisation identifier in the Research Organization Registry.

Caution: An organisation record does not confirm a person’s current employment.

Evidence and timeline · Priority 2

Connect the correction to the cited passage and version.

Publication identifying a document change or correction.

Caution: Read its scope before rejecting the entire document.

Evidence and timeline · Priority 2

Compare received version, published version and documented changes.

Work version circulated before possible final editorial publication.

Caution: Do not automatically assign it the status of the final version.

Evidence and timeline · Priority 2

Retain observed URL and declared reference without hiding differences.

Address a publisher presents as a content’s main reference.

Caution: A canonical declaration does not authenticate authorship and may be wrong.

Evidence and timeline · Priority 2

Specify start, end, platforms and collection exclusions.

Interval and conditions within which a phenomenon was examined.

Caution: Absence outside that window cannot be inferred.

Messages and channels · Priority 2

Review delegations after recovery

Have the responsible administrator review sessions, authorised applications and delegations.

Caution: A password change does not establish revocation of all permissions.

Messages and channels · Priority 2

Separate payment stages

Record request, approval, order and execution with available references.

Caution: A recovery request does not guarantee returned funds.

Reputation and narratives · Priority 2

Define the actually reviewed corpus

Record platform, period, exclusions and examined-item count.

Caution: A displayed total does not replace an inventory of reviewed items.

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 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 reference can be reused with attribution to IIS and preservation of its cautions and version date.

Reading pathway

Choose checks that change the decision

Two people checking a request in a direct conversation — AI-generated photograph
1

A specific claim

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

An external drive and archive boxes arranged on a shelf — AI-generated photograph
2

An interpretable result

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

An association team reviewing a working document — AI-generated photograph
3

A stopping rule

Stop when the issue is sufficiently clarified for the stated decision, or document why an additional check is needed.

Provenance, version and reuse

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.

Primary portals and their scope · Dataset reuse conditions