ENS Lookup

Resolve an ENS name to an address, or an address to its primary ENS name.

ENS names are just a friendly pointer to an address

Under the hood, an ENS name like vitalik.eth is a record in a smart contract on Ethereum mainnet, mapping the name to an address (and vice versa via a separate reverse record). This tool reads both directions of that mapping directly from the contract.

How it works

Name → address uses ENS’s standard resolution contract calls; address → name reads that address’s reverse record, if one has been set. Both happen via a public RPC call from your browser — no indexing service or API key involved.

Frequently asked questions

If the input matches an address (0x followed by 40 hex characters), it does a reverse lookup for that address's primary ENS name. Otherwise it treats the input as an ENS name and resolves it to an address.

An address can be the target of many ENS names, but only one can be set as its primary (reverse record) — the one that shows up when an app displays a friendly name for that address instead of the raw 0x string. If none is set, the reverse lookup returns nothing.

ENS itself lives on Ethereum mainnet — this tool resolves against the canonical ENS registry there. Some other chains have their own separate naming systems (e.g. Basenames on Base), which aren't the same thing and aren't covered here.