Crypto wallet address validator
Verify a BTC, ETH, LTC, DOGE, BCH, TRX or XRP address against its own checksum before you send.
Nothing leaves your browser. This tool does its work on your own machine — there is no upload, no server request, and nothing is stored.
Why every address carries a checksum
A crypto address is not stored in a directory anywhere. If you send to an address with one character wrong, there is no bank to call, no reversal, and usually no owner — the coins land at a destination nobody holds the key to. So every address format builds a checksum into the string itself, and validating it locally is the only warning you will ever get.
The four schemes, and what each one guarantees
- Base58Check (addresses starting 1, 3, D, L, T, r) appends four bytes of a double SHA-256. It also drops the characters 0, O, I and l from the alphabet entirely, because those are the ones people misread.
- Bech32 (bc1q, ltc1) uses a BCH code that is guaranteed to catch any four errors, and it is all one case so it survives being read aloud.
- Bech32m (bc1p, Taproot) is the same idea with a different constant, introduced because the original had a weakness when an address ended in a certain padding. A Taproot address written with a plain bech32 checksum is invalid, and this tool tells them apart.
- EIP-55 (Ethereum) hides the checksum in the capitalisation of the hex. It is optional, so an all-lowercase address is legal but unprotected — which is worth knowing before you paste one.
The attack a checksum cannot stop
Clipboard hijackers watch for a copied address and replace it with the attacker's own at the instant you paste. The substituted address is perfectly valid, so no checksum anywhere will complain. The only defence is to compare what landed in the box against the source, character by character — at minimum the first six and the last six — every single time.
Address poisoning works the same way from the other direction: the attacker sends you a dust transaction from an address that shares your intended recipient's first and last characters, so that copying from your own transaction history sends the money to them. Never copy an address out of your history. Copy it from the person.
Common questions
Why validate a crypto address at all?
Because the transfer is final. There is no chargeback, no support line and no reversal. Clipboard-hijacking malware swaps a copied address for the attacker's own at the moment you paste, and the two look similar enough to survive a glance.
Does a valid address mean the wallet is trustworthy?
Not at all. It means the string is mathematically well formed. Every scam wallet in existence has a perfectly valid address. To check reputation instead, run the address through the main check on the homepage.
How do I check I pasted the right address?
Compare the first six and last six characters against the source, out loud if you can. A checksum catches a typo, but it will happily accept a completely different valid address that malware substituted.