Is this payee address safe?
Before you pay, paste the payee address and screen it, free, for sanctions, mixers and scam risk. Usually takes a few seconds. We don't hand you a black-box score: what it hit and why is laid out for you to verify.
How is the risk score computed? (0–100)
A 0–100 score (not 1–10): higher = riskier, mapped to three verdicts:
- 0–29 clear: no list hit, no high-risk signal.
- 30–69 caution: risk signals present (new address / receive-only / unusual activity), proceed only within your mandate.
- 70–100 risky · decline: sanctions/mixer/scam list, frozen by Tether/USDC, or one-hop tainted by illicit funds.
Examples: issuer-frozen +92 · list hit → 100 · one-hop taint +60–65 · brand-new empty +24 · new (<7d) +12. Every verdict ships with verifiable evidence.
Batch screening
Next time, skip the page and send the address to the bot
Same verdict, same evidence. Paste an address in a DM, @-mention it in a group, or type @OceanAltTrust_Bot plus an address in any chat to send the result inline — no need to add it anywhere.
- 1. Send it an address. Result in seconds
- 2. To keep watching, tap Watch it under the result
- It tells you when the verdict worsens, no need to ask again
- Endpoints too: just send it a URL
Is the URL you are about to call a phishing host?
When an endpoint is spoofed, the payee address it hands back is freshly generated and clean. No address list has ever seen it. This class can only be caught at the endpoint layer.
GET /api/endpoint?url=https://pay.example.com/x402
Receipts, not just a score
Which list, when it was added, the on-chain one-hop path: all verifiable.
No signup · free
Paste and screen. Ethereum / Base / Tron (USDT-TRC20). No email, no KYC.
Agents can call it too
The same verdict is a free API — drop it into your system or an agent's pre-settlement flow.