Free tool

Wallet address checker

A crypto address carries a checksum inside it, so a typo shows up before you send: a wrong address simply fails the check. The network, though, cannot always be told from the address — a 0x… address is identical in Ethereum, BSC, Polygon and other EVM networks, and that is where most lost USDT goes.

Paste an address — we will name the network, verify the checksum and tell you what to watch for.

Examples:

Telling networks apart by the address

Starts withNetworkWhat it is
1…Bitcoinan ordinary address, the oldest format
3…Bitcoina script address, often multisig
bc1q…BitcoinSegWit: cheaper fees
bc1p…BitcoinTaproot, the newest format
0x…Ethereum and every EVM networkBSC, Polygon, Arbitrum, Optimism and others use the very same address form — the network is chosen in the wallet
T…TRONwhere USDT lives as TRC-20
UQ… / EQ…TONa human-readable address
ltc1… / L… / M…Litecoinlooks like Bitcoin, but the network differs

The main trap is in the second-to-last row. Ethereum, BSC, Polygon and a dozen other networks have addresses that look exactly alike, and no tool can say which one you need: that is decided not by the address but by the network picked when sending. Ask the recipient for the network as well as the address — and make the first transfer a small one.

FAQ

guest@404vpn:~$ cat wallet-faq.md
[01] $ Why did a USDT transfer “vanish” when the address was right?
> Most likely the coins went out on a different network. USDT exists on several at once: TRC-20 on TRON, ERC-20 on Ethereum, BEP-20 on BSC, and on TON as well. A 0x… address looks the same in every EVM network, so the wallet accepts the send while the recipient sees nothing: the coins sit on whichever network you chose. Sometimes exchange support can retrieve them; often it cannot.
[02] $ What exactly does the checksum verify?
> In Bitcoin and TRON the last four bytes of the address are a slice of the double SHA-256 of the rest: get one character wrong and the sum will not match. In Ethereum the checksum hides in the letter case (the EIP-55 standard) — that is why capitals and lowercase are mixed. In TON a CRC16 sits inside the address.
[03] $ The address passed — does that mean the money will arrive?
> No. The check only says the address is written correctly and holds no typo. Who owns it, and whether it is the right network, it cannot know. Always verify the address against its source and make the first transfer a small one.
[04] $ Do you keep the addresses I check?
> No. Every check runs in the browser; the address is sent nowhere. The page’s only network request is an anonymous visit counter that knows only the page address.
[05] $ Why is an Ethereum address sometimes capitals and sometimes lowercase?
> Both forms work. An all-lowercase address is the old notation without a checksum; mixed case was added later to catch typos. If the case is mixed but does not match the computed one, it is either a typo or an address from a network with a different rule — check with the sender.