Compare your history with the address you meant to pay and spot poisoned lookalikes.
New
Address Checksum Validator
Runs locallyNew
Use Address Checksum Validator
What it does
Paste one address, a list, or a whole message. Each address found is matched to its network, its checksum is verified and the normalised form is shown.
It runs entirely in your browser: nothing you enter is uploaded.
Example
Test vectors from EIP-55, BIP-350 and Bitcoin Core
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAeD
0xfb6916095ca1df60bb79ce92ce3ea74c37c5d359
bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqzk5jj0
BC1QW508D6QEJXTDG4Y5R3ZARVARY0C5XW7KV8F3T4
1FsSia9rv4NeEwvJ2GvXrX7LyxYspbN2mo
1FsSia9rv4NeEwvJ2GvXrX7LyxYspbN2mp
410000000000000000000000000000000000000000
TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA9 addresses found: 4 with a matching checksum, 2 without a checksum to verify, 1 with the right format (Solana has no checksum), 2 invalid. Do not send funds to an invalid address: it was mistyped or altered. Copy it again from a source you trust.
Checksum OK
EVM (Ethereum and compatible chains)
Hex address
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed
EIP-55 checksum matches.
Invalid
EVM (Ethereum and compatible chains)
Hex address
0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAeD
EIP-55 checksum does not match: the case of 1 letter is wrong. A character was probably mistyped or changed; get the address again from a trusted source.
If only the letter case was altered (some tools do that), the same digits in checksummed form are 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed. If a digit was mistyped, that is a different address.
No checksum
EVM (Ethereum and compatible chains)
Hex address
0xfb6916095ca1df60bb79ce92ce3ea74c37c5d359
Checksummed (EIP-55): 0xfB6916095ca1df60bB79Ce92cE3Ea74c37c5d359
All lowercase: there is no EIP-55 checksum, so a typo cannot be detected. The checksummed form is shown.
Checksum OK
Bitcoin
P2TR (Taproot, SegWit v1, Bech32m)
bc1p0xlxvlhemja6c4dqv22uapctqupfhlxm9h8z3k2e72q4k9hcz7vqzk5jj0
Bech32m (BIP-350) checksum matches.
Checksum OK
Bitcoin
P2WPKH (SegWit v0, Bech32)
BC1QW508D6QEJXTDG4Y5R3ZARVARY0C5XW7KV8F3T4
Lowercase form: bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
Bech32 (BIP-173) checksum matches.
Written in uppercase (allowed, used in QR codes); the lowercase form is shown.
Checksum OK
Bitcoin
P2PKH (legacy, starts with 1)
…The first EIP-55 address passes and its copy with one changed capital fails; the lowercase one has no checksum. Both SegWit addresses pass, the Base58 copy with a changed last character fails, the TRON hex becomes T9yD14Nj9j7xAB4dbGeiX9h8unkKHxuWwb and the Solana program ID passes as format only.
FAQ
Which addresses and checksums does the validator check?
EVM addresses with EIP-55 mixed-case checksums; Bitcoin, Litecoin and Dogecoin Base58Check addresses (double SHA-256); Bech32 and Bech32m SegWit addresses (BIP-173 and BIP-350); TRON addresses in Base58Check and 41 hex form; and Solana addresses.
Does a valid checksum mean the address is safe to pay?
No. A checksum only shows that the address was not mistyped or altered; a scammer's address or a poisoned lookalike passes too. Solana addresses and all-lowercase EVM addresses carry no checksum at all, so only their format can be confirmed.
Is anything sent to a server or a block explorer?
No. Decoding and checksum checks run in your browser, with SHA-256 from the browser's Web Crypto API. The tool does not look up balances, owners or transaction history.