Check an address before you send
Transfers cannot be reversed, so the only place to catch a wrong address is before you sign. No wallet connection, no sign-in, nothing leaves your browser.
What this catches
Look-alike addresses. Paste the address you were given and the one you meant to use, and the two are compared character by character. The attack this defeats relies on you only ever seeing the first and last few characters, so the comparison shows you the middle.
Token contracts. Sending tokens to a token contract instead of a wallet destroys them in practice. The address is asked directly whether it is one.
Addresses with no history. An address that has never sent a transaction and holds nothing is fine for a new wallet and alarming for anything else.
Altered characters. A mixed-case address encodes a checksum in its own capitalisation, so a single changed character can be detected with certainty and without asking any network.
What it cannot do
It cannot tell you an address belongs to the person you think it does. Nothing on-chain carries a name, and an address with a long, healthy history can still be the wrong one. If the destination came from a message, a support agent or a search result, verify it through a channel you started yourself — this page narrows the ways a transfer can go wrong, it does not confirm that it will go right.
It also sees only the ten EVM chains Bospora covers, and it makes no judgement about Bitcoin or Solana addresses, whose formats are different.
Common questions
What is address poisoning?
An attacker generates an address whose first and last few characters match one you have already sent to, then sends you a worthless transaction from it so it appears in your history. Later you copy the address from that history instead of from the real source. Because wallets display addresses truncated — the first four characters and the last four — the fake looks identical to the real one.
Can this tool tell me an address belongs to a scammer?
No, and no tool should claim to. There is no registry of every scam address, and a brand-new one has no history to judge. What this page does is narrower and more reliable: it reports facts about the address — whether it is well-formed, whether it holds contract code, whether it has ever been used — and shows you exactly where it differs from the address you expected.
Why does sending tokens to a token contract lose them?
A token contract is code, not a wallet, and nobody holds a private key for it. Tokens sent there sit in the contract for good unless its author happened to write a rescue function, which most did not. It happens most often when somebody pastes a token address into the recipient field instead of the token field.
The address shows no activity. Is that bad?
Only relative to what you were told it is. A wallet someone just created is legitimately empty. An exchange deposit address or a wallet described as active should not be — if it is, you are probably looking at a different address than the one you meant.
Does my address get sent to your server?
No. The checks run in your browser and talk directly to each chain public node, the same way the chain status page does. Nothing about your transfer reaches a server we operate.
Which chains are checked?
The ten EVM chains this site covers. The same address usually exists on all of them, which is what makes the comparison useful: a contract on one chain and an untouched address on another is exactly the distinction that decides whether a transfer arrives.
Already sent and waiting? Track a transfer to find out where it is.