How to Choose a Web3 Domain: Start with the Job
Choose a Web3 domain by purpose, ecosystem, wallet support, control and costs. Use the decision aid and buying checklist.
Choose a Web3 domain by starting with a job: a readable wallet identity, a business workflow, a community namespace or an earning experiment. Then compare the exact name product, supported apps, control and full cost. A memorable suffix is useful only when the people you want to reach can use it.
Our decision rule: remove any option that fails a required workflow before comparing price or appearance. This is an editorial framework, not a ranking based on paid placement or verified investment returns.
Find your starting point
Choose your purpose and ecosystem. Get a reading path based on those two choices.
Start with the identity you want to use.
Shortlist a name you can say and spell, then check which naming service your intended apps support.
This is an editorial decision aid. It does not check live availability, calculate a purchase quote, certify compatibility or predict earnings. Your selections stay in this page and are not submitted.
First choose the purpose
| Your purpose | What matters most | Read next |
|---|---|---|
| Personal identity | Recognizable spelling, app support and what you make public. | Personal-brand naming guide |
| Business or project | Customer usability, ownership roles and a maintainable handover. | Business buyer’s checklist |
| Resale | A credible buyer, acquisition discipline and selling costs. | Resale versus royalties |
| Extension / community | A reason for other people to register and a service you can maintain. | Earning models and the sales hurdle |
Then choose the system your apps can use
For a .eth identity, begin with ENS. For a name that explicitly identifies you with Base, examine Basenames. For a Solana workflow, check SNS and the current suffix transition. These are starting points for verification, rather than claims of universal support.
If you want a specific Unstoppable extension or a custom Freename Web3 extension, inspect that product’s integration route. A vendor may also sell traditional DNS names. The vendor logo alone does not identify the product or its renewal rules.
Use our compatibility evidence matrix to distinguish name resolution, primary-name display and website access. Paying with a wallet at checkout does not establish that its recipient field recognizes the purchased name.
Use seven checks on the shortlist
| Check | Question to answer |
|---|---|
| Purpose | What will a person actually do with this name? |
| Complete identifier | Is the exact spelling and suffix the identity you want to share? |
| App support | Does the intended app support the intended action on the intended network? |
| Control | Who can transfer the name, edit records and change its destination? |
| Maintenance | Which renewals, parent-name dependencies and optional services matter? |
| Full cost | What is the initial budget and the cost of keeping it useful? |
| Exit or handover | Can you stop optional services or transfer the complete setup cleanly? |
Choose the actual words, not only the extension
Write the complete identifier, read it aloud and ask someone to type it back. Compare an easily spelled longer name with an abbreviated short name before paying a premium for length. Keep a consistent public handle when that helps people recognize you.
Check the exact characters through the official app. Lookalike characters can create different names with similar appearance. The name-selection checklist covers spelling, readability, confusion and an availability record.
Separate useful identity from earning potential
A name can be useful to you without being a liquid resale asset. An extension can offer a royalty program without having customers. Keep two notes: the practical job the name performs and the separate evidence for any revenue assumption.
Resale needs a completed sale. Registration royalties need qualifying registrations. Referrals need attributed qualifying activity, and reseller margins need paying customers after supplier and operating costs. Use the earning overview and model comparison before treating a percentage as a return.
Worked example: one creator, three attractive names
Imagine a creator who wants readers of an Ethereum-focused newsletter to recognize her wallet. She shortlists a clear .eth label, a shorter .base.eth label and a custom-extension name advertised with earning features. She first checks the newsletter audience’s actual wallet workflow. A name that fails that check leaves the shortlist, regardless of its introductory price.
She then compares the remaining full identifiers, three-year costs and maintenance responsibilities. Because her immediate goal is identity, she evaluates royalty tools only as a separate future business idea. This example is a decision process, not a claim that the illustrative names are available or that one provider is always best.
After choosing, make the name useful
Planning a shared namespace?
Follow the Unstoppable workflow
Put the numbers to work
Check the current public records
Sources and review
Official documentation reviewed 23 October 2026. Procedures and compatibility below are documentation-based; no purchase, wallet transaction or payout was performed.
How ENS primary names work ↗Coinbase Basenames FAQ ↗SNS migration FAQ ↗Freename product and custody FAQ ↗Unstoppable product and renewal rules ↗ENS lookalike characters and names ↗ENS pricing and fees ↗