A domain NFT marketplace lets people buy and sell blockchain names, such as ENS .eth names, as tokens. It looks like any NFT marketplace, but names have expiry dates, separate ownership and control roles, and renewal fees, and a marketplace that ignores those details will let buyers pay for names that are about to lapse or still controlled by the seller.
What a domain NFT is
There are two families of tokenized names:
- Web3-native names. ENS on Ethereum is the main example:
alice.ethresolves to a wallet address, content hash or records. Other systems include Unstoppable Domains and chain-specific name services on Solana and other chains. - Tokenized DNS domains. Traditional ICANN domains (like
example.com) represented as NFTs by a registrar, so transferring the token transfers control of the domain. A small number of registrars and projects offer this; the domain still lives under ICANN rules, and the registrar remains a trusted party.
Most marketplace volume is in Web3-native names, so this guide focuses on ENS mechanics.
ENS mechanics a marketplace must handle
Registrant and manager
An unwrapped .eth name is an ERC-721 token in the ENS base registrar; whoever holds the token is the registrant. Separately, the registry records a manager (controller) who can change where the name points. Transferring the NFT does not automatically change the manager. A buyer must reclaim management after purchase, or the seller can keep redirecting the name. Your marketplace should show the current manager, warn when it differs from the owner, and prompt buyers to reclaim.
Wrapped names
The ENS NameWrapper turns names into ERC-1155 tokens and adds "fuses": permissions that can be permanently burned, such as the ability to create subnames or to transfer. A wrapped name with certain fuses burned behaves differently from a plain one. Display fuse state, and block listings that cannot actually be transferred.
Expiry, grace period and premium
Names are registered for a period and must be renewed. After expiry there is a 90-day grace period in which only the previous owner can renew. After that, the name is released with a temporary premium that decays to zero over 21 days, then anyone can register it at the base price. A listed name that expires during the sale is a trap for buyers. Show expiry prominently, warn on names near expiry, and refuse listings for names in grace period. The ENS documentation describes these rules and current pricing.
Subnames
Owners can issue subnames (pay.alice.eth). Projects use them for community identities. A marketplace can support subname sales, but be clear whether the parent owner can revoke them.
Marketplace features specific to names
| Feature | Purpose |
|---|---|
| Expiry and renewal display | Prevents buyers paying for names about to lapse |
| Manager and fuse checks | Ensures the buyer gets full control |
| Name search by pattern | Length, digits only, emoji, dictionary words, palindromes |
| Category tags | Clubs like 3-digit or 4-letter names drive most trading |
| Registration of available names | Lets users register directly, not only buy on the secondary market |
| Bulk renewal | Portfolio holders renew many names at once |
| Homoglyph and impersonation warnings | Unicode look-alikes are a common scam |
Pricing and valuation
Name markets behave differently from art markets. Value tends to cluster around a few properties: shortness, memorable patterns (repeated digits, palindromes), dictionary words and brand potential. Collectors group names into "clubs" such as all three-digit names, and floor prices form per club rather than per collection. A useful marketplace exposes those clubs as filters, shows recent comparable sales, and makes renewal cost part of the price shown, since a name with a high annual fee is a different asset from one with a low fee.
Build notes
- Use an existing order protocol such as Seaport for listings and offers; add validation that checks expiry and manager state before showing an order.
- Index ENS registry, registrar and NameWrapper events, plus resolver records, to keep name state fresh.
- Normalize names with ENSIP-15 rules and flag confusables before listing.
- For tokenized DNS domains, integrate with the issuing registrar's API and make the off-chain dependencies explicit to buyers.
For the general marketplace build, see NFT marketplace development and the OpenSea teardown; for name-based identity in wallets, Web3 wallet development.
Frequently asked questions
Do I own an ENS name forever?
No. You hold it while it is registered and renewed. If it expires and the grace period passes, someone else can register it.
Why did my purchased name still point to the seller's address?
Transferring the NFT changes the registrant, not necessarily the manager or resolver records. Reclaim management and update the records after buying.
Can traditional .com domains be traded as NFTs?
Some registrars tokenize ICANN domains so the token controls the domain. The domain remains subject to ICANN rules and the registrar's terms, so it is not fully decentralized.
Are look-alike names a real risk?
Yes. Unicode characters that resemble Latin letters can make an impersonation name look identical. Normalize names and warn on confusables.