Check a BNB Smart Chain address

What the check covers on BNB Smart Chain

A BSC check reads the account's transfers and counterparties: sanctions designations, scam and rug-pull token distributions, drainer wallets and phishing infrastructure, mixing services, bridges, stolen-funds trails, no-KYC exchanges and mule networks. Where the address holds USDT, USDC or FDUSD, the check also reports whether it appears on a stablecoin issuer freeze list.

The verdict is CLEAN, LOW, MEDIUM, HIGH or CRITICAL, with a recommendation and the decision drivers named. On BSC that naming does real work. Transaction fees here are low enough that scam projects spray worthless tokens across thousands of wallets, so an ordinary user can accumulate junk they never asked for. A result that says which flows drove the verdict lets you tell an unwanted airdrop apart from a wallet that actually interacted with the scam.

For sanctions the reference is OFAC's own material: definitions in FAQ 559, the blocking obligation on the virtual currency FAQ topic page.

Address format on BNB Smart Chain

BSC is EVM-compatible, so an address is 0x plus 40 hexadecimal characters — the same shape as Ethereum, including the EIP-55 checksum carried in the capitalisation. An example: 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed.

That identical shape is the single biggest source of lost funds on this chain. The same string is a valid address on Ethereum, Polygon, Arbitrum and Base, and the balances do not travel with it:

• A BEP-20 transfer sent to an exchange's ERC-20 deposit address arrives on the wrong chain. Some venues recover it manually, many do not.
• A clean result on Ethereum says nothing about the same address on BSC. Each network keeps its own history.
• BEP-20 has no memo or tag. If a deposit screen asks for one, you are looking at a different network.

What gets frozen on BNB Smart Chain

BNB itself has no issuer and cannot be frozen. The stablecoins can. Tether's terms let it "freeze any Tether Tokens held by you" (Section 2) and, on suspected prohibited use, freeze or confiscate tokens and "blacklist Digital Token Addresses" (Section 8) — tether.to/en/legal. Circle reserves the equivalent right for USDC, including blocking "the transfer of USDC to and from an address on chain as permitted under the blocklisting policy" — circle.com/legal/usdc-terms. Those powers apply on the networks where each issuer has deployed its token.

The more common event is a venue hold. An exchange sees where a BEP-20 deposit came from and pauses it pending review; that is their control, and a check before you send is what avoids it. See the pre-deposit notes for Binance and Bitget.

Before you send, after you receive

1. Screen the counterparty address on BSC specifically, not on whatever chain you checked last.
2. Confirm the network on the deposit screen. The address shape will not tell you.
3. Do not judge a wallet by its token list. Unsolicited scam tokens land in wallets that did nothing; the reason line separates received junk from actual interaction.
4. If your address comes back HIGH or CRITICAL, keep the funds where they are and document how they arrived. Bridging to another chain does not detach the trail — screening follows it across the bridge.
5. Answer any venue request for information with that record, and check the sender before you accept the next transfer.

Free check vs workspace

Individual transfers: the Telegram bot. High-volume BEP-20 deposit flow: the API, reviewed in the workspace.