Crypto Address Format Checker
Paste an address you are about to send to. This tool checks its format and built-in checksum, the way wallets do, so a mistyped or altered character is caught before you send. It runs on your device: the address is not sent anywhere.
- Result
- –
- Address type
- –
- Network
- –
- Checksum
- –
- Why it is not valid
- –
Checked Bitcoin BIP-173: Base32 address format for native v0-16 witness outputs (bech32) All sources
How it is calculated
- Bitcoin bc1… (BIP-173, BIP-350): the bech32 checksum over the prefix and data must equal 1 for SegWit v0, or 0x2bc830a3 (bech32m) for v1 and later
- Bitcoin 1… and 3…, and TRON T… (Base58Check): the last 4 bytes must equal the first 4 bytes of SHA-256(SHA-256(the rest)); the first byte tells the type (0x00, 0x05, 0x41…)
- Ethereum-style 0x… (ERC-55): each letter is upper case exactly when the matching hex digit of Keccak-256(the lower-case address) is 8 or more
- A valid format does not prove the address belongs to the person you mean, or that it is on the network you will send on
Worked example
A test address from BIP-173 itself (a native SegWit v0 address).
| You enter | |
|---|---|
| Address | bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 |
| You get | |
| Result | Valid format |
| Address type | Bitcoin native SegWit (P2WPKH) |
| Network | Bitcoin mainnet |
| Checksum | Matches |
| Why it is not valid | – |
The format and checksum are correct for a Bitcoin native SegWit (P2WPKH). That does not prove who owns it: compare the first and last characters with the source before you send.
Questions
Is my address sent anywhere?
No. The check runs in your browser. The address is not put in the page link when you copy it, is not saved on your device, and is shortened on "Share as image".
An Ethereum address in all lower case says "None" for the checksum. Is it wrong?
No. ERC-55 adds a checksum through upper- and lower-case letters. An all-lower-case (or all-upper-case) address is still valid, but a typo in it cannot be detected, so check it carefully.
Can I send USDT on TRON to an Ethereum address, or the other way round?
No. TRON (T…) and Ethereum-style (0x…) addresses belong to different networks. Choose the same network as the receiving address in your wallet or exchange, or the funds may be lost.
What does "Valid format" not tell me?
It does not prove the address is the one you meant. Malware can replace a copied address with a different valid one. Compare the start and end with the original.
Sources and checks
- Bitcoin BIP-173: Base32 address format for native v0-16 witness outputs (bech32)
- Bitcoin BIP-350: Bech32m format for v1+ witness addresses (its address test vectors are tests here)
- Bitcoin Core: Base58Check (src/base58.cpp) and its address test data (src/test/data/key_io_valid.json, tests here)
- ERC-55: Mixed-case checksum address encoding (its test addresses are tests here)
- TRON developers: Encoding addresses and data (0x41 prefix, Base58Check; its example addresses are tests here)
Last checked: 22 October 2026. This tool passes 37 automatic tests before every release. How we check our tools
Your numbers never leave your device: the calculation runs in your browser and nothing you type is sent or stored.
A format and checksum check only. It cannot tell who owns an address, whether it is on the network you will send on (an EVM address looks the same on every EVM network), or whether it has been swapped for a look-alike by malware. Always compare the first and last characters with the source, and send a small test amount first for large transfers. This is not financial advice. Results are estimates for information only and are not financial, investment, tax or legal advice. Crypto prices move fast and leveraged trading can lose more than you expect. Check figures on your exchange or wallet before you act.