Checksum fails
compare the exact mixed-case string with an EIP-55 implementation and do not auto-lowercase it as a “fix.”
Ethereum Address Validator
Check whether an Ethereum-style address has the expected 0x/hex structure and, when applicable, a valid EIP-55 mixed-case checksum.
Crypto & SecurityRead the full guideDirect answer
An Ethereum address validator checks the text format of an address: typically a 0x prefix followed by 40 hexadecimal characters, plus EIP-55 checksum casing for mixed-case addresses. Passing this test does not prove who owns the address, whether it is active, or whether it is safe to send funds.
1
→Paste Address
Enter an Ethereum address to validate
2
→Check Format
Verify checksum and structure
3
Review Result
See status and quick details
Validate Address
Paste an Ethereum wallet or contract address.
Validation Result
Format, checksum, and normalized address.
Check This Address
Enter an Ethereum address to validate.
- Network
- Ethereum
- Format
- Hexadecimal
- Checksum
- -
- Address type
- Format only
No address yet.
This validates formatting only. It does not prove ownership, balance, account activity, or contract status.
How to use it
Enter the source data: Paste the complete address and decide whether leading/trailing whitespace should be rejected or trimmed visibly.
Choose the relevant settings: Choose whether a checksum is required. Keep lowercase/uppercase acceptance distinct from validation of an EIP-55 mixed-case checksum.
Review and verify the result: Review length, hexadecimal characters, case style and checksum status. Verify the destination independently before any transfer.
Key capabilities
- Checks 0x prefix and 40-character hexadecimal body.
- Identifies lowercase, uppercase or mixed-case style.
- Validates EIP-55 casing when checksum checking applies.
- Shows a normalized representation without hiding the original input.
- Copies the result, explorer link or JSON when available.
Best use cases
- Catch a mistyped or truncated Ethereum address.
- Validate EIP-55 checksum casing in a development workflow.
- Normalize test fixtures while preserving the original string for review.
Limits and safety notes
- Format validation is not recipient verification. A correctly formatted address can belong to the wrong person, a scammer, an inaccessible account or a different network context. Explorer links also depend on correct network mapping.
- The core transformation runs in the current browser component. Browser extensions, clipboard history, downloaded files and site-wide diagnostics remain separate exposure points, so never enter production secrets unless you have reviewed the complete environment.
Troubleshooting
Address is rejected because of spaces
show the trimmed candidate separately and require explicit user confirmation.
Explorer opens the wrong network
fix the network selector/mapping before linking.
Frequently asked questions
What does an Ethereum address validator check?
It checks textual structure and, for mixed-case addresses, EIP-55 checksum casing. It does not query ownership, balance or transaction history unless a separate live service is explicitly used.
Can a lowercase Ethereum address be valid?
A 40-hex lowercase address can be syntactically valid, but it does not carry an EIP-55 mixed-case checksum. A “require checksum” option should therefore reject it while a format-only mode may accept it.
Does a valid address mean it is safe to send funds?
No. Confirm the recipient, network and full address through an independent trusted channel, preferably with a small test transaction when appropriate.
Is it safe and private?
The calculation runs in this browser component, but that alone is not a complete privacy guarantee. Use non-production data unless you have also reviewed extensions, clipboard history, downloads and site diagnostics.
Does it work on mobile?
The layout adapts to narrow screens. File selection, camera access, clipboard actions and downloads still depend on the permissions and capabilities of the mobile browser.
Related tools
Use the tool
Paste the address, inspect every validation component and independently confirm the recipient before using it in a transaction.