Legacy Base58Check
Mainnet P2PKH addresses commonly begin with 1, while mainnet P2SH addresses commonly begin with 3.
Randommer cryptocurrency-format utility
Bitcoin Address Validation for Base58Check, Bech32 and Bech32m.
Use Randommer Bitcoin Address Validation to check address encoding, checksum, network and script type. Validate legacy Base58Check addresses, SegWit Bech32 addresses and Taproot-compatible Bech32m addresses one at a time or in a batch.
- Legacy, SegWit and Taproot formats
- Mainnet and test-network detection
- Single and batch validation
Three address families
Bitcoin addresses use different encodings for different script types.
Bitcoin Address Validation must identify the encoding before applying the correct checksum and witness-program rules.
SegWit Bech32
Version-0 witness addresses use Bech32 and commonly begin with bc1q on Bitcoin mainnet.
Taproot Bech32m
Version-1 Taproot addresses use Bech32m and commonly begin with bc1p on Bitcoin mainnet.
Network detection
The prefix helps identify the intended Bitcoin network.
Sending funds to an address on the wrong network can cause loss or require specialist recovery.
What does Bitcoin Address Validation check?
Bitcoin Address Validation checks whether an entered address follows a supported Bitcoin encoding and whether its checksum is internally consistent. Randommer identifies Base58Check, Bech32 or Bech32m before applying format-specific rules.
A valid result means the string is syntactically consistent with a supported Bitcoin address type. It does not prove that the address has received funds, belongs to the intended recipient or is controlled by anyone who sent the payment request.
Base58Check validation
Legacy addresses use a restricted Base58 alphabet that avoids visually confusing characters. The decoded payload includes a version byte and a four-byte checksum derived from double SHA-256.
Bech32 validation
Native SegWit version-0 addresses use Bech32. Validation checks the human-readable prefix, character set, case rules, checksum and witness program length.
Bech32m validation
Witness versions 1 through 16 use Bech32m. Taproot addresses use witness
version 1 and commonly begin with bc1p on mainnet.
Mixed uppercase and lowercase
Bech32-family addresses can be all lowercase or all uppercase, but a mixed case string is invalid. Randommer normalizes a valid uppercase address for display without changing its decoded meaning.
Witness-program length rules
Version 0 requires a 20-byte or 32-byte program. Later witness versions allow program lengths from 2 to 40 bytes and require the Bech32m checksum constant.
Network detection is not payment confirmation
The address prefix can indicate mainnet, testnet, signet or regtest. Validation cannot determine whether the sender selected the correct network for the intended transaction.
Address validation does not verify ownership
Only a valid cryptographic signature or a correctly completed transaction can demonstrate control in the appropriate context. A pasted address alone does not prove ownership or recipient identity.
Verify before sending Bitcoin
Compare the complete address through a trusted channel. Malware can replace clipboard content, and visually similar prefixes do not guarantee the full address is correct.
Common formats
Bitcoin address types supported by Randommer.
The opening characters are clues, but the full checksum and decoding rules must still pass.
Legacy pay-to-public-key-hash address using Base58Check.
Mainnet commonly starts with 1
Legacy script-hash address using Base58Check.
Mainnet commonly starts with 3
Version-0 native SegWit address using Bech32.
Mainnet commonly starts with bc1q
Taproot address using witness version 1 and Bech32m.
Mainnet commonly starts with bc1p
Common use cases
Where Bitcoin address validation supports a careful workflow.
Use validation as an initial data-quality step, not as proof that a payment request is legitimate.
Wallet Forms
Reject malformed addresses before a withdrawal request is submitted.
Exchange Interfaces
Check network and address encoding before deeper transaction review.
Quality Assurance
Test valid, invalid and wrong-network address examples.
Database Cleanup
Flag malformed wallet-address records during migration or import.
API Validation
Compare browser and backend Bitcoin address validation behavior.
Developer Documentation
Explain legacy, SegWit and Taproot address-format differences.
Valid Format
Is Not
Safe Payment
Is Not
Safe Payment
Never rely on checksum validation alone before sending Bitcoin.
A scammer can provide a perfectly valid address. Validation cannot identify fraud, confirm a recipient’s identity or recover funds sent to the wrong destination.
Verify the full address and network through a trusted channel. For larger payments, use an approved wallet workflow, address allowlist or a small test transaction when appropriate.
Bitcoin transactions are generally irreversible once confirmed, so review every character and network selection before authorizing the transfer.
Related Randommer tools
Continue with checksum, hash and finance utilities.
Use related pages for data integrity, financial calculations and banking identifier checks.
Validate Bitcoin address structure with Randommer.
Check a single address or review a batch, then verify the recipient and network through a trusted payment workflow before sending funds.
Frequently asked questions
Questions about Bitcoin Address Validation.
These answers explain supported formats, checksum checks and payment limitations.
It checks address encoding, checksum, supported network prefix, witness version and program length where applicable.
Randommer supports Base58Check P2PKH and P2SH addresses, Bech32 version-0 SegWit addresses and Bech32m witness-version addresses such as Taproot.
No. A valid address does not prove private-key control, recipient identity or legitimacy of a payment request.
Witness version 0 uses Bech32, while witness versions 1 through 16 use Bech32m. Taproot uses witness version 1.
Yes. Paste one address per line to generate a batch validation report and export it as CSV.
Bech32-family strings can be all lowercase or all uppercase, but mixing the two cases is not permitted.
No. This page does not query a blockchain explorer or wallet service and does not check balances or transaction history.
The validation code in this HTML page runs locally in the browser. Review all analytics and third-party scripts before making a complete privacy claim.
Crypto-safety notice: This page validates address structure
only. Always verify the full recipient address and network before sending
Bitcoin.