How to read a AMLRegister AML report
Walk through every field of a AMLRegister risk report — what it means, what to check, and when to escalate.
The risk gauge
The circle at the top of every report shows the total risk score from 0 to 100. It's a weighted maximum of the ten category scores, so a single severe signal drives the score even if other categories are clean.
Colour is derived from the score: 0–24 green, 25–69 orange, 70–100 red. Treat the colour as a triage signal, not a verdict — always read the category breakdown before making decisions.
Attribution line
If the wallet has been flagged by our intelligence team, the attribution appears directly under the wallet address (e.g. "Tornado Cash Router"). Attributions are sourced from public designations, incident reports, or internal investigation.
No attribution does not mean "safe" — it means we have no specific label for this address. Always check the category breakdown and counterparty analysis.
Category breakdown
The ten categories are sorted by score. The highest-scoring category usually tells you why a wallet is flagged. Severity badges (critical, high, medium, low, positive) indicate the regulatory weight we assign.
A "clean exchange" score is a positive signal — it indicates the wallet has meaningful interaction with known reputable venues. A near-zero across all categories is our default for untagged wallets.
Transaction list
The ten most recent transactions are shown with hash, direction, counterparty, amount, and timestamp. This is drawn from the live blockchain via our data providers. For wallets with zero on-chain activity, this section will be empty — that is a legitimate finding, not an error.
Analyst notes
If our intelligence team has attached notes to this wallet, they appear in a highlighted box on the result page and in the PDF. Notes typically explain the context of a flag — which incident, which list, which investigation.
Verification hash
Every report carries a 16-character verification hash derived from the report ID and wallet address. You can quote this hash in compliance files; it proves the report was generated against the specific wallet on the specific day, and an auditor can re-derive and compare.
When to escalate
Red scores always warrant a pause. Orange scores warrant a human review — often the finding is correct but context-dependent. Green scores should generally not block a transaction on their own but should be combined with other compliance signals.
If you disagree with a finding, dispute it through the footer link on any report. Our team reviews disputes within one business day.
