Validate the format and checksum of Bitcoin (P2PKH, P2SH, SegWit, Taproot) and Ethereum (EIP-55) addresses — entirely in your browser.
Try these examples:
Bitcoin has evolved through several address formats, each with different security and efficiency characteristics:
1. The original Bitcoin address format using Pay-to-Public-Key-Hash. Validated with a double-SHA256 checksum (Base58Check).3. Pay-to-Script-Hash enables multi-signature wallets and other scripts. Also uses Base58Check.bc1q. Native SegWit addresses use Bech32 encoding, which is case-insensitive and error-detecting.bc1p. The newest format (activated 2021) uses Bech32m encoding and supports Schnorr signatures and Merklized scripts.Ethereum addresses are 20 bytes (40 hex characters) prefixed with 0x. The EIP-55 standard introduces mixed-case checksums: certain letters in the address are capitalised based on the Keccak-256 hash of the lowercase address. This allows wallets and tools to detect typos without changing the underlying bytes.
An all-lowercase or all-uppercase Ethereum address is technically valid but non-checksummed. This tool will report the correct checksummed form if the provided address isn't already checksummed.
Sending cryptocurrency to an invalid address results in a permanent, irreversible loss of funds. Address validation catches common mistakes: typos, wrong network (mainnet vs testnet), incorrect format, or a failed copy-paste. Always validate before sending — especially large amounts.
That a Bitcoin or Ethereum address is well-formed and that its checksum is valid: Base58Check for legacy Bitcoin, Bech32 and Bech32m for SegWit and Taproot, and EIP-55 casing for Ethereum.
No. It only means the string is not mistyped. It does not confirm who controls the address or whether it is the one you intend to pay, so always verify the address through a trusted channel.
No. Validation is pure format and checksum math done in your browser. There are no network calls and no balance or history lookup.