ENS lookup

The ENS registry and the name’s resolver on Ethereum mainnet, through Wardcrest’s own RPC connections. The same contracts every wallet reads. Names without a resolver of their own, or with records kept off-chain, are read through the ENS Universal Resolver. Nothing is taken from a third-party index.

An address can set a “reverse record” claiming a name. Anyone can claim any name that way, so a claim only counts when the name also points back to the address. Wardcrest checks both directions and warns you when they disagree.

Some names keep their records off Ethereum, on another chain or a company’s server, and their resolver points to a gateway that serves them (CCIP-Read, EIP-3668). Many app-issued subnames work this way. Wardcrest asks that gateway for you over HTTPS only, never at a private network address, with a five-second limit and a size cap, and uses an answer only once the name’s resolver contract on Ethereum has accepted it. The result names the gateway it asked.

A resolver set on a parent name, such as example.eth, that answers for every name below it, so alice.example.eth resolves without being registered on its own (ENSIP-10). The result says when a parent’s resolver answered.

It may be unregistered or expired, or have no Ethereum address set. If its records are off-chain and the gateway could not be reached, or points somewhere Wardcrest will not fetch from, the result says so instead.