Bitcoin Address Format Detector

Identify a Bitcoin address type from its prefix — mainnet vs testnet

Every Bitcoin address announces its type and network in its first characters. This tool reads that prefix and tells you whether the address is mainnet or testnet and which script type it pays to — useful before pasting an address into a wallet, an exchange withdrawal field or a watch-only tracker.

Mainnet prefixes

• 1 — Legacy P2PKH (Base58Check).
• 3 — P2SH: multisig or wrapped SegWit (Base58Check).
• bc1q — native SegWit (bech32): P2WPKH if short, P2WSH if long.
• bc1p — Taproot P2TR (bech32m).

Testnet prefixes (never hold real value)

• m / n — testnet Legacy P2PKH.
• 2 — testnet P2SH.
• tb1 — testnet SegWit (bech32); tb1p is testnet Taproot.
• Why it matters: the HRP (human-readable part — bc vs tb) is the single most important guard against sending mainnet coins to a testnet address.

Gotchas

• Prefix is detection, not validation: knowing the type doesn't confirm the bech32/Base58 checksum — a wallet must still verify it.
• regtest uses bcrt1: local dev networks have yet another HRP; don't confuse it with mainnet.
• Lightning invoices aren't addresses: a lnbc… string is a payment request, not a Bitcoin address.
• Copy the whole string: truncating an address by even one character changes the checksum and the funds are lost.

FAQ

How do I tell mainnet from testnet at a glance? Mainnet bech32 starts with bc1; testnet with tb1. Legacy mainnet starts 1/3; testnet with m/n/2.

What is the difference between bc1q and bc1p? bc1q is SegWit v0 (bech32); bc1p is Taproot v1 (bech32m) — different checksum constant and script.

Is a recognised prefix enough to send? No — always let your wallet verify the full checksum before broadcasting.