Wallet Address Validator

Checksum validates the bytes you typed/pasted are internally consistent. It does NOT validate the address belongs to the right person. A typo that produces another valid address (chain has billions of addresses; some random typos produce other valid ones) passes checksum but goes to a different wallet. Always verify the full address against the source.

EIP-55 checksum. Capitalizing certain hex characters based on the keccak hash of the lowercase address provides a checksum without changing the underlying bytes. A typo that flips one character's case is detectable; a typo that flips a character's value (a vs b) is also detectable from the case pattern.

Yes. Bitcoin address types are about how the receiver's funds are stored, not the sender's. You can send to any address format from any wallet. The receiver pays slightly more in fees to spend legacy addresses; you pay nothing extra to send to them.

An address with a chosen prefix — e.g., 1Love... or 0xCAFE.... Generated by brute force (try random keys until one produces an address with the desired prefix). Cosmetic; functionally identical to any other address. Vanity addresses are also used for address poisoning attacks.

Almost never. If the address is valid but unowned by anyone (random typo to non-existent key), funds are permanently locked. If it is owned by someone else, you need them to send it back — no protocol-level recourse. Always verify before signing.

Attack: attacker creates an address with a prefix and suffix matching your usual recipient's, then sends a 0-value transaction from it to your wallet. Now your transaction history shows their address; if you copy from history rather than from the original source, you send to the attacker. Prevention: never use transaction history as a source for addresses; always use the original (recipient's shared address, your wallet's contacts).