ENS Name Ownership Explainer

WHAT IT DOES

ENS Name Ownership Explainer takes an ENS domain name (e.g., vitalik.eth) or a transaction interacting with ENS and provides a complete, plain‑language breakdown of the domain’s ownership and configuration state. It reads the ENS registry contract to fetch the current owner, resolver address, and TTL for the domain (using the namehash derived from the domain name). It then queries the resolver contract to retrieve configured records—the ETH address, content hash (IPFS, Swarm, etc.), and common text records (URL, avatar, email, description, Twitter, GitHub). It also queries the ETH registrar contract (for .eth names) to fetch the registration expiry date and determines whether the name is currently registered or expired. Historical ENS events (NewOwner, Transfer, NewResolver, NameRegistered, Renewed) are fetched using chunked, backoff‑aware log scanning to provide context on ownership changes and renewals. The output includes the domain name, current owner, resolver address, ETH address record, content hash, text records, expiry date, registration status, and a plain‑language explanation of the ENS name’s ownership and configuration state.

HOW TO USE

Paste an ENS domain name (e.g., myname.eth) into the input field, select the network, and click "Explain ENS name". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the ENS registry and resolver states. It automatically computes the namehash for the domain and queries the registry for ownership, resolver, and TTL. It then queries the resolver for ETH address, content hash, and common text records. For .eth domains, it queries the registrar to get the expiry date. Historical events are fetched in chunks (500 blocks per request) with automatic backoff and halving on failure to avoid public RPC caps. The AI layer generates a plain‑English summary of the ENS name’s ownership and configuration state. You can click on any address to view it on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR ENS EVENTS

ENS events (NewOwner, Transfer, NewResolver, NameRegistered, Renewed) provide critical context for ownership history, resolver changes, and registration status. However, public RPCs aggressively cap eth_getLogs block ranges; a full‑range request over 10,000 blocks will fail with a "block range too large" error. This tool automatically chunks log requests into 500‑block slices to stay within safe limits for all major RPC providers. If a chunk fails (due to timeout or provider‑specific caps), it halves that chunk and retries recursively—ensuring that even with aggressive caps, the tool reliably retrieves all relevant ENS events. The tool also handles ENS-specific filtering by namehash to reduce log volume, and gracefully falls back if the registrar contract does not support the expiry view function.

WHAT IT CANNOT SEE

This tool cannot detect ENS ownership information that depends on off‑chain state (e.g., DNS‑imported names where ownership is managed by a DNS registrar, or names that are wrapped in a smart contract wallet with custom logic). It cannot predict future ownership changes or transfers that might occur before the transaction is mined—the check reflects the current state, not the future. It cannot verify that the sender intended to transfer or interact with the ENS name—the tool reads what is on‑chain, not the user's intent. It cannot detect ownership of subdomains that are managed by a custom registrar not following the standard ENS registry pattern. It cannot guarantee that an ownership transfer transaction will succeed even if the sender appears to be the owner, as other conditions (e.g., paused state, resolver configuration, or grace period) may also need to be met. It cannot detect if the name is expired or in the grace period unless the registrar exposes a public expiry view function—for names that use a custom registrar, expiry may not be available. It cannot detect if the name is wrapped as an ERC‑721 token (ENSIP‑10) and ownership is held by a wallet rather than directly by the registry. It also cannot detect if the resolver records are stale or if the resolver is configured incorrectly.

PLEASE NOTE

This tool works only for EVM‑compatible chains that support ENS (Ethereum Mainnet, Polygon, BSC, Arbitrum, Optimism, Avalanche, etc.). It relies on the standard ENS registry and resolver interfaces, and the ETH registrar contract for .eth expiry information. It does not support DNS‑imported names or custom registrar implementations that do not follow the standard patterns. All explanations are AI‑generated from data the app reads on‑chain—the AI synthesizes the ownership state, resolver records, event history, and transaction context into plain English, but it does not have special access to private contract logic or off‑chain data. Always review what you are actually signing in your wallet before approving any transaction; an ENS ownership explanation does not replace your own verification of the transaction details, including the target contract and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.