How to Check a Wallet Address for Risk with AEGIXE
Before accepting a USDT payment, you can screen the sending address for relevant on-chain risk signals. This guide shows how to use AEGIXE to select a network, enter a public wallet address and interpret the information
Before accepting a USDT payment, you can screen the sending address for relevant on-chain risk signals. This guide shows how to use AEGIXE to select a network, enter a public wallet address and interpret the information returned.
Screenshots show the English AEGIXE address risk checker, captured on 12 November 2026. The submission and result-navigation workflow was checked earlier that day in the Chinese interface. Result labels quoted below refer to that earlier check.
Figure 1. Open the official tool and have the full public address and its network ready.
1. Prepare the address and network
Use the full public address and confirm its network. A payment wallet, token contract and shared exchange address are different objects. The checker requires a public address, without a wallet connection or private key.
Figure 2. Choose the network the address belongs to. This screenshot shows part of the available network list.
2. Run a check
- Open the tool and select the actual network under βBlockchain networkβ. The interface currently states 19 networks; use the current list. This does not establish equal data coverage across networks.
- Paste the full address into βWallet addressβ. Check all characters and remove unwanted spaces.
- Click βCheck addressβ. Wait while βζ£ε¨ζ£ζ΅β¦β is shown; avoid duplicate submissions.
- After βε°εζ£ζ΅η»ζε·²ζ΄ζ°β, verify the network, full address and detection time before interpreting results. The Chinese interface labels times as Beijing time.
Figure 3. β Select the network. β‘ Paste the full public wallet address. β’ Click βCheck addressβ. No screening result is shown.
3. Read each module
| Module | How to read it |
|---|---|
| Risk summary / ι£ι©ζθ¦ | Read the level, original level, score and address labels together. Do not invent score thresholds or treat a score as a probability of wrongdoing. |
| Balance, transaction count, total inflows/outflows | Check the value, retrieval status and data time. Missing does not mean zero. |
| Risk sources and exposure / ι£ι©ζ₯ζΊδΈζ΄ι²ζη» | The chart shows a subset of supplied monetary entries. Click βε±εΌζη»οΌcountοΌβ for entity, risk type, exposure type, hops, USD amount and share. Sort available columns and page through entries where applicable. |
| Transaction behavior | Compare categories and incoming/outgoing activity; absent counts are not zero. |
| Main counterparties | Identified entities only, rather than a complete transaction history. |
| Activity time | Check data time and coverage. Recent activity alone proves neither identity nor source of funds. |
Modules may succeed, fail or be unsupported independently. Exposure can include direct or indirect links and overlapping entries; do not add them to infer total risk. A direct link alone does not establish intent or wrongdoing.
4. Common situations
- Upstream analysis timeout / βδΈζΈΈεζθΆ ζΆοΌθ―·η¨ειθ―β or retrieval failure / βθ·εε€±θ΄₯β: observed during the workflow check. Keep affected fields unknown and retry later. Successful modules do not validate failed ones.
- Address/network unsupported: a coverage limit, not a clean result.
- Unclear labels, amounts or objects: first check whether you queried a token contract rather than a payment wallet. Cross-check transaction records and reliable sources; preserve uncertainty rather than repeating a label as a fact.
- No risk warning: no relevant signal was identified within that check's data and coverage. This does not guarantee absence of issuer restrictions or exchange acceptance.
5. Keep your own record
Record the network, full address, query time, field status, original warning text and unresolved questions in an appropriate internal system. Keep this record private; do not publish personal payment information.
The web workflow was checked; label attribution and data accuracy have not undergone independent technical verification. Results reflect the check time. Material transactions need further verification. USDT payment reference Β· Contact AEGIXE
Published by AEGIXE and prepared with AI assistance. Screenshots and workflow checks are dated 12 November 2026. Automated results support risk assessment; they do not guarantee safety. Learn more about AEGIXE at aegixe.com.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.