How this tool works
Select the intended network and paste a public address. The local check distinguishes a recognized encoding from a checksum failure. No ownership, balance or recipient identity is inferred.
Check alphabet and decoded length; verify Base58Check, Bech32/Bech32m or mixed-case ERC-55 when applicableA worked example
The published Bitcoin genesis address 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa has a valid Bitcoin mainnet Base58Check encoding. That does not give the user control of it.
Good to know
Supported mainnet address encodings only. No network query, name resolution, chain-specific EIP-1191 checks or ownership check. Uniform-case EVM format acceptance does not establish checksum protection. Shared version bytes cannot identify one network uniquely.
Reference: Bitcoin BIP 173 address encoding (opens in a new tab) ↗
A checksum checks a string, not a recipient
Address encodings include structural rules and, for many formats, error-detecting checksums. These checks can reject a mistyped address before a transfer is attempted. A valid encoding alone cannot tell you who controls the address or whether it belongs to the intended recipient.
Compare the entire address through a trusted channel. A lookalike prefix or suffix is not enough. An attacker can supply another address whose encoding and checksum are perfectly valid, so a green format result must never substitute for recipient verification.
The Merkle tree calculator uses SHA-256 to commit to an ordered list and verify inclusion proofs. A wallet address checksum checks an address encoding instead; the two checks establish different things.
Know which check applies
Bitcoin legacy addresses use Base58Check. Native witness addresses use Bech32 for version zero and Bech32m for later witness versions. The version, program length, alphabet and checksum must fit together. Mixed upper and lower case is not permitted within one Bech32 string.
Ethereum-style addresses contain twenty bytes written as forty hexadecimal characters after 0x. Mixed-case ERC-55 adds an error-detecting capitalization convention. A uniform-case address can be structurally accepted without making the same checksum claim. Chain-specific checksum variants and human-readable names are outside this tool.
Select the intended network independently
Some address formats and version bytes are shared. EVM networks commonly use the same textual address shape, and a format check cannot establish which network a recipient or exchange supports. A balance on one chain also says nothing about the same string on another.
This tool performs no network requests and needs only a public address. Never paste a private key or recovery phrase. The crypto mining profit calculator models a separate economic scenario; neither its numbers nor a format check establishes an entitlement to any funds.
A few questions, answered
Does format accepted mean safe to send?
No. Confirm the full recipient address, asset and network independently.
Are balances checked?
No. No blockchain request is made.
Can I enter a seed phrase?
No. This tool needs only a public address.