Security · Validation
Ethereum address checksum (EIP-55).
Paste an Ethereum address to check its EIP-55 mixed-case checksum, or convert a lowercase address to its checksummed form. It works for every EVM chain that uses Ethereum addresses. This checks format and checksum only: it cannot tell you whether an address exists, holds funds, or who controls it. Everything runs in your browser; nothing you type is transmitted or stored. Never paste a private key or seed phrase.
Inputs
Result
Enter an Ethereum address and press Check.
How the EIP-55 checksum works
An Ethereum address is 20 bytes, written as 40 hex characters. EIP-55 hides a checksum in the capitalization of the letters a-f, so it stays a valid address for software that ignores case. The steps: lowercase the hex (without 0x); take the Keccak-256 hash of that lowercase ASCII string; then for each character, if it is a letter a-f and the corresponding hex digit of the hash is 8 or higher, write it in uppercase, otherwise lowercase. Digits are unchanged.
Keccak-256 is not SHA3-256. Ethereum uses the original Keccak submission (padding byte 0x01); the NIST SHA3-256 standard changed the padding to 0x06 and gives different output. Browsers do not provide Keccak in WebCrypto, so this page includes its own implementation, tested against the empty-string hash c5d24601…a470 and the eight address vectors listed in EIP-55.
What each result means. Mixed case that matches: the address passes the checksum. Mixed case that does not match: a character was changed or the case was altered, so do not send funds to it. All-lowercase or all-uppercase: well-formed, but carries no checksum, so a typo cannot be detected; the page shows the checksummed form to use instead. Because the checksum only depends on the address bytes, it is the same on Ethereum mainnet and on EVM chains such as Polygon, Arbitrum, Optimism and BNB Chain (chain-specific variants like EIP-1191 are not checked here).
Sources: EIP-55: Mixed-case checksum address encoding, cross-checked against eth-utils to_checksum_address and ethers.js getAddress, which implement the same rule.
What a passing checksum does and doesn’t tell you
A valid checksum only proves the address is well-formed and free of typos. It does not confirm the address exists on any chain, has ever held funds, is controlled by anyone, or belongs to the person you intend to pay. Transactions are irreversible, so verify the address with the recipient by a second channel. This tool runs entirely in your browser: nothing you type is transmitted, stored, or logged. It never asks for a private key or seed phrase, and you should never enter one anywhere.
Why Ethereum addresses have a checksum at all
An Ethereum address is 40 hexadecimal characters with no built-in error detection. Original hex addresses had no check digit, so one mistyped character produced another perfectly valid address, and funds sent to it are gone. EIP-55, proposed to fix this without changing the address format, hides a checksum in the capitalization of the letters a to f. Software that ignores case still reads the same 20 bytes, while software that understands EIP-55 can compare the case it sees against the case it expects. A wrong letter, or a swapped one, will usually make the pattern disagree.
How strong the protection is
EIP-55 reports that, on average, an address carries 15 check bits (only the letters a to f can carry a bit, and about 15 of the 40 characters are letters), and that the probability that a randomly mistyped address still passes is 0.0247%. The proposal calls that about 50 times better than the ICAP scheme but not as good as a dedicated 4-byte check code. In plain terms, the checksum catches the great majority of typing errors but not all of them, and it does nothing against a correct address that belongs to the wrong person.
Worked example
One of the test vectors in EIP-55 is 0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed. Paste it and the tool reports a matching checksum. Now change one thing and see how the result responds:
- Change the case of one letter (for example turn the first
aafter the prefix intoAor back). The address bytes are unchanged but the case no longer matches what the hash dictates, so the result is "mixed case, does not match". - Change a different character (for example a
3to a4). The hash of the lowercase string changes completely, so the expected capitalization changes and the existing case almost certainly no longer matches. About 1 in 4,000 such random errors would still pass, which is the 0.0247% figure. - Lowercase the entire address. It is well formed but now carries no checksum, so a typo cannot be detected. The tool shows the checksummed form to copy instead.
Which results to trust
- Mixed case, matches: the format is right and any single-character slip is very likely excluded.
- Mixed case, does not match: either a character was changed or something altered the case (some chat apps and spreadsheets do). Do not send funds. Get the address again from the source.
- All lowercase or all uppercase: no checksum to verify. Convert it with this tool and compare it with the source.
- Wrong length or non-hex characters: not an Ethereum address. It must be 40 hex characters, with or without the
0xprefix.
Same address on other chains
The checksum depends only on the 20 address bytes, so the same account address has the same EIP-55 form on Ethereum and on other EVM-compatible chains that use Ethereum addresses. That also means the checksum cannot tell you which network an address is meant for. Sending a token on the wrong network is a separate mistake that no address check can catch. Some chains define their own chain-specific checksum variants; this tool checks only EIP-55.
What this tool does not cover
It does not look anything up on a blockchain, so it cannot tell you whether an address exists, holds funds or is a contract. It does not resolve ENS names. Never paste a private key or recovery phrase into any web page. For a different address checksum, see the Bitcoin Address Validator, and for a hash demo see the Hash Generator.
Frequently asked questions
What is EIP-55?
EIP-55 is the Ethereum proposal that defines the mixed-case checksum for addresses. It capitalizes each hex letter a to f according to the Keccak-256 hash of the lowercase address, so the address stays valid while typos become detectable.
How do I know if an Ethereum address is valid?
It must be 40 hexadecimal characters, optionally starting with 0x. If it uses mixed case, the capitalization must match the EIP-55 pattern. If it is all lowercase or all uppercase, it is well formed but has no checksum to confirm.
How reliable is the EIP-55 checksum?
EIP-55 states that an address carries on average 15 check bits and that a randomly mistyped address would pass the check with a probability of 0.0247%. It is a strong typo detector, not a guarantee, and it cannot confirm who owns an address.
Why does my address fail when I only changed the capitalization?
The capital letters are the checksum. If any a to f letter has the wrong case, the address bytes are the same but the pattern disagrees. Copy the address again from its original source, or use the checksummed form this tool outputs.
Is Keccak-256 the same as SHA3-256?
No. Ethereum uses the original Keccak submission, while NIST's SHA3-256 changed the padding byte and gives different output. That is why you cannot compute an EIP-55 checksum with a standard SHA3-256 function.
Does a valid checksum mean the address exists or holds funds?
No. It only proves the string is well formed and free of typos. The tool does not query any blockchain, so it cannot say whether the address is in use, who controls it, or whether it is a contract.
Does this work for Polygon, Arbitrum, Optimism and BNB Chain addresses?
Yes for the standard EIP-55 form, because these chains use the same 20-byte addresses. The checksum cannot tell you which network the address is intended for, so check the network before you send.
Sources
- EIP-55: Mixed-case checksum address encoding: algorithm, 15 check bits, 0.0247% false-pass probability, test vectors, comparison with ICAP (retrieved 2026-10).
- ERC-1191: Add chain id to mixed-case checksum address encoding: chain-specific checksum variant (not checked by this tool) (retrieved 2026-10).
- NIST FIPS 202: SHA-3 Standard: SHA3-256 appends the suffix 01 to the message, so it differs from original Keccak-256 (retrieved 2026-10).