Open any name in ENS Explorer and you get its page: an overview up top, tabs down the left, and an Extend button top right. Here's what each part is for.

One thing to know first: the tabs adapt to the name. ENSv2 names show a Roles tab; names wrapped under ENSv1 show a Fuses tab in the same spot. Everything else is common to both.

All of it is public. Anyone can read every tab on any name, wallet connected or not. You only need to connect to change something — do that and the edit buttons appear on the names you own.

The at-a-glance card: avatar, expiry and registration dates, owner, parent, resolver, subregistry (ENSv2), protocol version, plus counts of subnames, role holders and records, and a preview of recent history.

Everything the name stores — its addresses, text records (avatar, socials), and content hash. Owners get an Edit records button — see how to edit your name's records.

The contract that answers questions about the name. For most names this is an instance of the official ENS Permissioned Resolver (audited), shown with its address, an Etherscan link, and the record types it supports. Owners can Change resolver: enter a custom resolver address, deploy a fresh permissioned resolver, or pick an existing one.

The record types are listed under Interfaces: Address resolver, ABI resolution for contracts, Text records, Content hash resolution, and Interface detection. Each one links to the contract source. If a record type you need isn't on that list, the resolver can't serve it.

Registration and expiry dates, the name's owner, and its parent, followed by a History section listing recent activity on the name.

Roles: who holds which management permissions, with Add user for owners — see who can manage my name. Fuses: the one-way permission locks burned on a wrapped name, each shown with its scope (Parent or Owner) and whether it's burnt.

The name's children (like pay.yourname.eth) and who owns them. Creating subnames on an ENSv2 name first requires deploying a subregistry — Explorer offers a Deploy subregistry button when the name doesn't have one.

For the curious: the chain of ENSv2 registry contracts behind the name — from the root registry through .eth to the name's own subregistry — with addresses and creation details.

Where the name points, network by network. A row for Default, Mainnet, and each supported L2 (Optimism, Base, Arbitrum, Linea, Scroll), with the address recorded for that network and a Reverse match column showing whether the address points back at this name. Networks you haven't set show null. A Primary name tag appears on any row where this name is the address's primary.

This is the forward direction — name to address. The reverse direction lives on the address page, under Reverse Resolution; see how to set your primary name.

The name as an NFT: token standard (ERC-1155), contract, and token ID, plus a breakdown of how the name normalises and hashes — useful when you need exact technical identifiers.

The timeline of everything that's happened to the name — registrations, transfers, record changes — with links to each transaction on Etherscan.