ENS (Ethereum Name Service)
Human-readable names mapped to addresses and records.
ENS, or Ethereum Name Service, is a decentralized naming system that maps human-readable names such as alice.eth to blockchain addresses and other records. It helps users replace long hexadecimal destinations with recognizable labels. ENS runs through smart contracts on Ethereum, while wallets and applications choose whether and how to support its records.
An ENS name has an owner or manager that can configure a resolver. The resolver answers queries for addresses, text fields, content hashes, and other supported data. Reverse resolution lets an address select a primary name, so compatible applications can display that label instead of the raw address. Forward and reverse records should agree to reduce impersonation and display errors.
ENS matters because address mistakes can be irreversible. A known name is easier to communicate and verify than a 42-character Ethereum address. Projects also use names for contract references, decentralized websites, contributor identities, and subnames. A company could issue names under its parent domain for employees without requiring each person to register a separate .eth name.
Readable names introduce new risks. Attackers register lookalike characters, misspellings, or familiar brand names. An ENS name is not proof of legal identity, official affiliation, or a safe destination. Records can be changed by whoever controls the name. Before a valuable transfer, confirm the name through a trusted channel and check the resolved full address on the signing device.
.eth registrations expire unless renewed, and registration cost depends partly on duration, name length, and Ethereum gas. Losing control of the owner wallet or missing renewal can make the name unavailable or transferable under protocol rules. Calendar reminders, longer registrations, and secure ownership through a hardware wallet or multisig reduce operational risk.
Use the official ENS application, verify contracts and network, and review every ownership or resolver transaction. Avoid placing private data in public text records. Organizations should separate name ownership from routine record management and document succession. ENS improves usability and identity continuity, but users still need full-address verification, secure key management, and awareness that the underlying records remain changeable.
Applications integrating ENS should handle expired names, resolver failures, unsupported coin types, and stale cached records safely. Displaying the resolved address alongside the name gives users an additional verification opportunity.
Frequently asked questions
- Use the official ENS application from a verified domain, connect an Ethereum wallet, search for an available name, and review registration and network fees. Choose the registration period and confirm the owner address carefully. After registration, configure resolution and primary-name settings if needed. Record the expiry date and protect the controlling wallet like any valuable asset.
- ENS names can store addresses for supported cryptocurrencies, text records, content hashes, and other resolver-defined data. Common text fields include a website, email, avatar, or social profile, but all records are public and may become outdated. Verify the resolver and avoid publishing sensitive personal information. Applications decide which record types they read and display.
- Yes. A name owner can create subnames such as alice.example.eth and assign ownership or management rights to another address. Permissions depend on the registry, resolver, and any name-wrapper configuration. Organizations should document who can create, update, revoke, or renew subnames. A parent-name expiry or compromised controller may affect names beneath it, depending on the setup.