ENS
lookup.

Directions

Both

name → addr · addr → name

Namehash

Local

EIP-137, in-browser keccak

Reverse

Verified

round-trip checked

Auth

None

no wallet, no API key

/24—ENS RESOLVER

awaiting input

▸ /notes

Namehash is pure math.

A name becomes its 32-byte node through recursive keccak-256, no registry involved. That is why the hashes render instantly here while resolution waits on an RPC.

Reverse records can lie.

Anyone can point their reverse record at any name, so displaying it without checking is an impersonation vector. This tool resolves the claimed name forward and only marks the pair verified when it round-trips to the same address.

The resolved address still deserves a checksum.

Once a name resolves, treat the address like any other: the address checker verifies its EIP-55 form and whether it is a wallet or a contract on 11 chains.

▸ /faq

What is a namehash?

The EIP-137 algorithm that turns a name into the 32-byte node ENS contracts use as a key: hash each label with keccak-256 and fold them right to left. It runs locally on this page; only the resolution step touches an RPC.

Why is reverse resolution "verified"?

Anyone can point a reverse record at any name, so a reverse result is only trustworthy if the name also resolves forward to the same address. This tool performs that round-trip and marks the result verified only when both directions agree.

Why does my exotic name give a different result elsewhere?

Full ENS normalization (ENSIP-15) handles emoji, confusable characters, and special casing rules. This tool applies basic lowercasing, which matches standard ASCII names; heavily stylized names may normalize differently in wallet software.

Which records does this read?

The ETH address record (addr) and the primary name record. ENS also stores avatars, content hashes, and text records; those are out of scope here and readable on the official ENS app.

ENSlookup.