Understand missing evidence

Unknown #

Unknown means the supported check could not establish its answer. The details should name the gap: a required source could not be read, a mapping is missing, a threshold is unreviewed or the available evidence conflicts.

Unknown does not mean healthy, malicious or safe. It describes the limit of this observation.

Unrecognized #

Unrecognized belongs to the issuer Stock Token provenance panel. It means a completed issuer-registry lookup found no exact chain/address match. It is different from a source failure that prevented the lookup.

A token can have contract metadata, explorer facts or matching market pairs while this panel says Unrecognized. Read those observations separately from the issuer result. Optional project evidence may also establish a published identity match. A familiar name cannot replace an exact address match.

Unsupported #

Unsupported belongs to exposure evidence. It identifies a structure or check outside the current reviewed method. Adding support requires review and an implemented method, not a more confident explanation.

Read whether a check could run #

The report records applicability and outcome for each check. A method can apply to this token, fall outside current support or not apply to its classification. An outcome can contain an observation, a missing match, a source failure, a conflict, a partial read or a check that was not attempted.

These details explain why a panel can lack an answer. A reverted metadata call does not mean the contract has no code. A missing oracle mapping does not mean an existing feed was queried and failed.

Read missing explorer or market data #

A successful lookup with no matching record differs from a failed request. An explorer may not have indexed a contract, and a market provider may have no indexed pair for it. Neither result establishes that the token has no code or cannot trade anywhere.

An unavailable source could not establish whether a record exists. Read its reason and retrieval time, then retry if the problem was temporary. Discovery failures do not erase successful onchain reads or become demo data.

Receipts also list what was never assessed: transfer taxes or honeypot behaviour, code audits, who holds admin keys, third-party liquidity locks, off-chain backing, price history and legal status. Those items are absent by design on every receipt, so their absence is not evidence either way.

What to do next #

Open the panel details and its source links. Check the network and contract address. Compare the requested check with Coverage.

Retry when a source was temporarily unavailable. A retry may still produce Unknown. It creates a new observation and preserves the previous one.

Failures stay visible #

Missing data never becomes a positive default. Live source failures never trigger hidden demo data. A complete-looking page is not evidence that every check succeeded.

For request and source failures, see Source outages.