AES Encryption Explained: How It Works and Why It Matters
Jun 23, 2026
Validate Bitcoin addresses including P2PKH (Legacy), P2SH, Bech32 (SegWit), and Bech32m (Taproot) with checksum verification.
Enter a Bitcoin address to validate. Supports P2PKH, P2SH, Bech32, and Bech32m formats.
Type
-
Network
-
Length
-
Hash
-
All validation is performed 100% client-side in your browser. No address data is sent to any server.
A Bitcoin address is a unique identifier used to send and receive Bitcoin on the blockchain. It functions like a bank account number but is derived from cryptographic keys. There are several address formats, each with a different prefix and encoding scheme:
1. Uses Base58Check encoding. Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa3. Uses Base58Check encoding. Supports multi-signature and other script types.bc1. Uses Bech32 encoding. Native SegWit addresses with lower fees.bc1p. Uses Bech32m encoding. Supports Taproot and Schnorr signatures.| Type | Prefix | Encoding | Length |
|---|---|---|---|
| P2PKH (Legacy) | 1 | Base58Check | 26-35 chars |
| P2SH | 3 | Base58Check | 26-35 chars |
| Bech32 (SegWit) | bc1 | Bech32 | 42-62 chars |
| Bech32m (Taproot) | bc1p | Bech32m | 42-62 chars |
| Testnet P2PKH | m/n | Base58Check | 26-35 chars |
| Testnet P2SH | 2 | Base58Check | 26-35 chars |
| Testnet Bech32 | tb1 | Bech32 | 42-62 chars |
This validator supports P2PKH (Legacy, starts with "1"), P2SH (starts with "3"), Bech32 (SegWit, starts with "bc1"), and Bech32m (Taproot, starts with "bc1p") for mainnet. Testnet variants (starting with "m", "n", "2", or "tb1") are also supported.
Base58Check adds a version byte prefix and a 4-byte checksum (double SHA-256) to the payload. The validator decodes the Base58 string, extracts the checksum, and verifies it matches the double SHA-256 hash of the payload.
Bech32 is a compact, error-detecting encoding format defined in BIP-0173 for native SegWit addresses. It uses a 32-character alphabet and a BCH code checksum that can detect up to 4 character errors.
Bech32m (defined in BIP-0350) is a modified version of Bech32 that fixes a weakness in the original Bech32 checksum. Bech32m is used for Taproot addresses (starts with "bc1p"), while original Bech32 is used for SegWit v0 addresses (starts with "bc1q").
No. A valid checksum only confirms the address is correctly formatted. It does not mean the address has been used on the blockchain or has a balance. For that, you would need a blockchain explorer API.
Blog
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026
Jun 23, 2026