GOXEVA cost & mechanics desk
English
English Kiswahili Français

Crypto address format checker

Paste an address before you send to it. This page reads the format and tells you which family of networks that format belongs to — Bitcoin, Tron, or the EVM family that Ethereum, BNB Smart Chain and Polygon all share. It cannot tell you which individual chain an address is meant for, because for the EVM family that information is not in the address at all.

Runs entirely in your browser Nothing you paste is transmitted

Address

format check
Looks like
—
Length
—
How strong is this check
—

A format family, not a specific chain. Only the receiving side can tell you which network to send on.

    What this actually checks, and what it cannot

    Two different levels of confidence

    Be clear about which one you are getting, because they are not comparable.

    A checksum and witness-format check applies to Bitcoin addresses beginning bc1 or tb1. This page checks the bech32/bech32m checksum, witness version, program length and padding. A failed check means the string does not meet these address rules. Passing catches many copying errors but does not establish who controls the address; a substituted address can pass too.

    A format check applies to everything else: Ethereum and BNB Smart Chain addresses, Tron addresses, and older Bitcoin addresses beginning 1 or 3. It confirms the prefix, the length and the character set. It does not confirm the address is real, and it will not catch a typo that happens to leave the shape intact. Those formats use checksums that need a cryptographic hash to verify, and this page does not ship one.

    What a pass does not mean

    • Not that the address exists. Most well-formed strings on most chains are simply unused.
    • Not that it belongs to who you think. Nothing here can tell you that, and clipboard-replacement malware substitutes valid addresses, not broken ones.
    • Not that the receiving side will credit it. A valid address on a chain your exchange does not support for that asset is still a lost transfer.

    The specific mistake this is for

    Ethereum and BNB Smart Chain use the same address format, so one string is valid on both. That is convenient and it is also the trap: the same address exists on both chains and the assets on them do not mix. Sending a BEP20 token to an exchange that only credits ERC20 at that address produces a transfer that confirmed, is visible on a block explorer, and is not in your account.

    Tron is the opposite case. Its addresses start with T and are visibly unlike an 0x string, which is why network mix-ups involving Tron are usually caught by eye and mix-ups between the two EVM chains are not.

    The habit worth having instead

    Copy the address from the deposit screen with the network already selected, paste it into the withdrawal form with the same network selected, and compare the first and last several characters after pasting. Then send a small amount and wait for it to be credited before sending the rest. That sequence catches more real failures than any validator can.

    Related

    Choosing a network covers what the standards are and why the same ticker on two chains is not the same asset. The missing-deposit triage covers what is recoverable when this goes wrong. The network picker works through the decision before you copy anything.