Address format validator

Paste an address and see which chain it belongs to and whether the format holds up. It cannot catch "the address is real but belongs to the wrong person" — it does catch the two most common accidents: a paste that went wrong, and the wrong chain.

Paste the address here Nothing you type leaves your browser

Verdict

—

Paste an address to begin.

A valid format is not the same as a safe transfer What this tool can confirm is that the string conforms to some chain's address specification. What it cannot confirm: that the address exists, that it belongs to the person you intend to pay, that the receiving platform supports this chain, or whether a memo or tag is also required. Those are yours to verify. For a first transfer to any new address, always send a small test amount first.

What it actually checks, and what it cannot (expand)

What gets verified

Tron addresses (T…) and older Bitcoin addresses (1…, 3…) — the last few characters are a check code calculated from the rest, and the tool recalculates it to see whether it still matches. A swapped or dropped character fails here.
Bitcoin addresses starting with bc1 (bc1q… and bc1p…) — the built-in check code is fully recalculated, and the address structure is checked against the Bitcoin address rules (BIP 173 / BIP 350). Addresses that mix upper and lower case are rejected, because the rules require that.
Ethereum-style (0x…) — format only: the 0x prefix and 40 hexadecimal characters. See the limitation below.

The Ethereum limitation, stated plainly

An Ethereum-style address has no mandatory check code. EIP-55 defines an optional one hidden in the letter casing, but verifying it needs an algorithm browsers do not include, and this page does not add one. So for a 0x… address the tool confirms the shape and nothing more.

There is a second, more important limit for this family: Ethereum and BNB Chain use the same address format, so no amount of inspection of the string can tell you which network the recipient expects. That has to come from the recipient. The network picker asks that question first for exactly this reason.

A correction that changed the behaviour of this page

An earlier version checked bc1 addresses by appearance only — the opening characters, the allowed letters and the length — without recalculating the check code. That produced a specific wrong answer: the Bitcoin address rules (BIP 173) explicitly list mixed-case bc1 addresses as invalid, and a look-only check happily called such an address "correctly formatted". An address the rules say must be rejected was being reported as fine.

It now fully recalculates the check code and checks that the address structure is consistent, and mixed case is rejected outright. Before it went live, the tool was tried against the sample addresses published with the Bitcoin rules (BIP 350): all eight valid samples were recognised correctly, and every deliberately broken one — old and new check-code styles swapped, a version number or length outside the rules, mixed case, and damaged endings — was rejected with the specific reason rather than a generic failure.

What it cannot tell you

Whether the address exists or holds anything. A validator computes; it does not query a chain. Any well-formed string passes, whether or not anyone controls it.
Whether it belongs to the right person. This is the actual risk and no format check touches it. Compare the first and last characters against the source you were given, and be aware that clipboard-hijacking malware substitutes a valid address for a valid address.
Whether a memo or tag is required. That is a property of the receiving platform, not of the string.
Which network to use for a 0x… address. As above.

Where the data comes from

Everything happens in your browser. The page looks nothing up online, and what you paste is never sent anywhere or stored — closing the tab discards it. For Tron and older Bitcoin addresses the check uses an encryption feature built into your browser; if your browser does not offer it (for example when the page is saved and opened as a local file), the tool says the check code was not verified rather than pretending it passed.