Bech32 address fails
check for mixed uppercase/lowercase, an incorrect human-readable prefix or a Bech32/Bech32m mismatch.
Bitcoin Address Validator
Identify a Bitcoin address format, network prefix and checksum while keeping format validity separate from ownership and payment safety.
Crypto & SecurityRead the full guideDirect answer
A Bitcoin address validator checks encoding, prefix, payload and checksum rules for supported legacy Base58Check, SegWit Bech32 and Bech32m formats. It can identify likely network and address type, but it cannot prove ownership, balance, activity or recipient identity. Validates legacy P2PKH and P2SH Base58Check forms.
1
→Paste Address
Enter a Bitcoin address to validate
2
→Validate Format
Verify format, checksum and network
3
Review Result
See status and address details
Validate Address
Paste a Bitcoin legacy, SegWit, or Bech32 address.
Validation Result
Network, format, checksum, and normalized address.
Valid Bitcoin Address
The address is properly formatted and valid.
- Network
- Bitcoin Mainnet
- Format
- Legacy (Base58Check)
- Prefix
- 1
- Length
- 34 characters
- Checksum
- Valid (Base58Check)
- Address Type
- P2PKH (Pay to Public Key Hash)
1BoatSLRHtKNngkdXEeobR76b53LETtpyT
This tool validates formatting only. It does not prove ownership or account balance.
Starts with valid prefix
Expected 1, 3, m, n, 2, bc1, tb1, or bcrt1.
Character set valid
Legacy addresses must use the Base58 alphabet.
Checksum passed
Base58Check checksum must match the payload.
Length valid (34)
Decoded legacy payload should contain one version byte and 20 hash bytes.
How to use it
Enter the source data: Paste the full address exactly as supplied. Preserve case for Bech32-family validation and reject mixed-case strings.
Choose the relevant settings: Let the tool identify Base58Check, Bech32 or Bech32m and show the candidate network/type separately.
Review and verify the result: Review checksum status, then independently verify the recipient and network before sending bitcoin.
Key capabilities
- Validates legacy P2PKH and P2SH Base58Check forms.
- Checks SegWit Bech32 addresses.
- Checks Bech32m/Taproot-style addresses when supported.
- Identifies mainnet/testnet prefixes and address type.
- Builds a network-aware explorer link and structured result.
Best use cases
- Catch copy errors in a Bitcoin address.
- Identify whether an address is legacy, SegWit or Taproot-style.
- Validate parser implementations against known good and bad vectors.
Limits and safety notes
- A valid checksum only reduces accidental transcription errors. It does not prove the recipient, ownership, spendability, balance or safety. Always confirm the full address through a trusted channel.
- The core transformation runs in the current browser component. Browser extensions, clipboard history, downloaded files and site-wide diagnostics remain separate exposure points, so never enter production secrets unless you have reviewed the complete environment.
Troubleshooting
Base58 address fails
look for visually similar characters and verify the checksum without “correcting” the address.
Wrong network reported
validate the prefix rules and do not reuse an explorer mapping across mainnet and test networks.
Frequently asked questions
What Bitcoin address formats are supported?
The current scope includes legacy Base58Check P2PKH/P2SH, SegWit Bech32 and Bech32m/Taproot-style formats. Exact witness-version and test-network coverage must pass official BIP test vectors.
What is the difference between Bech32 and Bech32m?
They use different checksum constants. Bech32 is used for earlier SegWit witness versions, while newer witness versions such as Taproot use Bech32m under BIP350 rules.
Does a valid Bitcoin address prove the recipient owns it?
No. Format and checksum validation cannot establish identity, ownership, balance or intent.
Is it safe and private?
The calculation runs in this browser component, but that alone is not a complete privacy guarantee. Use non-production data unless you have also reviewed extensions, clipboard history, downloads and site diagnostics.
Does it work on mobile?
The layout adapts to narrow screens. File selection, camera access, clipboard actions and downloads still depend on the permissions and capabilities of the mobile browser.
Related tools
Use the tool
Check encoding, network and checksum, then confirm the destination independently before making a payment.