OceanAltOceanAlt

Q&A

A brand-new address with no history: how do you judge whether to pay it?

You can't judge it from the address alone. A new address has no list record and no behavioural history, and no tool can read risk out of a freshly generated string. OceanAlt returns "insufficient data" for this case instead of inventing a number. What you can do is move the judgment off the address itself: screen the channel that gave you the address (the endpoint/domain) for phishing, send a small test amount, ask the counterparty to prove ownership verifiably, and keep monitoring after you pay.

Why fresh addresses are standard scam kit

Generating an address costs nothing, so professional scams rotate to a fresh payee address almost every job, which dodges lists and cuts links to past cases. So a "clean" new address proves nothing.

Four substitute moves

① Screen the channel: run the URL that handed you the address through endpoint screening (lower on the oceanalt.com/en/check page); a spoofed site's address is always fresh, but its domain is often already in the malicious corpus. ② Send a small test amount and have the counterparty confirm it. ③ Ask them to prove ownership: sign a message from the address, or return a transfer of a specified amount. ④ After paying, put the address on a watchlist so you hear first if it goes bad.

The same logic applies to agents: in an agent's payment policy, "payee address has no history" should trigger extra verification (endpoint check, amount cap, human confirmation) rather than a default pass.

"Insufficient data" is still information

When a screening tool answers "insufficient data / UNCERTAIN" for a new address, it means this dimension can't help and you need evidence from another one. That is more honest than a made-up 85/100 and more useful, because it points you to the endpoint, the test transfer and the counterparty's identity.

Where to start: free address check · API docs · watch an address

Limits of this page: a screening "clear" only means no match in the data held, never a safety guarantee; this page is not legal or compliance advice.