Wallet Address Validator
Validate Bitcoin (P2PKH, P2SH, SegWit Bech32 and Taproot Bech32m), Ethereum (EIP-55), Litecoin, Dogecoin, Tron, Solana, XRP (classic and X-address), Stellar (incl. muxed) and Cardano (Shelley) addresses — checksum, format, and network detection.
Follows Address encodingsBIP-173/350 · EIP-55 · CIP-19 · SEP-23 · XLS-5d·verified Oct 2026· double-checked Oct 2026— BIP and Core key_io vectors; ~100k generated cases match sipa’s segwit_addr, xrpl-py, stellar-sdk, pycardano and bitcoinjs / bech32
What “valid” means here
A valid result means the string is a well-formed address for that network: the right alphabet, length and version byte, and — where the format has one — a matching checksum. It does not mean the address exists, has funds, or belongs to whom you think: every check runs offline in your browser.
Checksums differ by format. Base58Check (Bitcoin legacy, Litecoin, Dogecoin, Tron, XRP) appends 4 bytes of double SHA-256; Bech32 (BIP-173, SegWit v0) and Bech32m (BIP-350, Taproot and later) use a BCH code that detects any 4 substituted characters, and an address with the wrong one of the two is invalid; Stellar StrKeys end in a CRC-16; Ethereum’s EIP-55 checksum lives in the letter case, so an all-lower-case address has none. Solana addresses have no checksum at all — any 32-byte value is a valid address, so a typo is not detectable.
Some formats are shared. An Ethereum address is valid on every EVM chain, and Litecoin’s legacy 3… and testnet prefixes are byte-for-byte Bitcoin’s — choose the network explicitly to check those. A Stellar S… string is a secret key, not an address: never paste one anywhere.