ENS Address Checker
Look up an ENS Ethereum receiving address, compare an expected destination and save a report with the checked block and time.
Look up the Ethereum receiving address for an ENS name and compare it with an optional expected destination. The result includes its block and check time.
How to check an ENS receiving address
- Enter the complete public name, including every label and suffix.
- Optionally paste the Ethereum address you expect to receive.
- Run the check and compare the full returned destination.
- Review the same destination in the sending app before using it.
The tool normalizes the name using the ENS name-processing library, then queries the Universal Resolver on Ethereum Mainnet. DNS names imported into ENS are also eligible inputs; the tool does not assume that every supported name ends in .eth.
Understand the result
| Result | Meaning |
|---|---|
| Address resolved | A nonzero Ethereum receiving address was returned at the displayed block. |
| Different from expected | The returned address differs from the optional address you entered. Check the saved record and the expected destination. |
| No address returned | The completed lookup returned no nonzero Ethereum receiving record. Other record types may still exist. |
| No resolver found | The Universal Resolver could not locate a resolver for this lookup. This is not an availability check. |
| Lookup could not be completed | A transport, gateway or resolver request failed. Retry rather than interpreting this as an empty record. |
What this establishes
A receiving record describes a destination. It does not identify the domain’s owner, verify a trademark or establish that another wallet supports the same name. Ethereum, Bitcoin and chain-specific destinations are distinct record contexts.
The expected address is compared in your browser and is not sent as a separate query. If it differs, investigate before publishing the name as a payment instruction. Our address-record guide explains how the saved destination and ownership differ.
Offchain lookups and repeat checks
Some ENS records use an offchain gateway. The tool follows permitted HTTPS gateway responses through the library’s contract-verification callback. A gateway failure is shown as an incomplete lookup. This does not certify every wallet’s implementation or every possible resolver.
Copy or download the report to keep the name, result, network, block and timestamp together. A saved report is a snapshot. Run another check after a record change or before relying on an older result.
Sources and implementation review
Reviewed 23 October 2026. The live implementation was checked against ENS’s documented Universal Resolver and offchain test names. Results are read-only observations of public records at the displayed block.
ENS Universal Resolver and documented integration test ↗ENS name normalization and namehash ↗ENS integration and offchain test cases ↗PublicNode Ethereum Mainnet endpoint ↗