How to Pick a Web3 Domain Name: A Naming Checklist

Pick a Web3 domain name by testing the complete identifier for recognition, spelling, intended use and maintenance cost. First choose the naming system your apps can use; then compare the actual words and characters you would buy.

Build a shortlist with a purpose

Start with a name you already use, a readable project label and one or two clear alternatives. Put each full identifier on its own line. Keep the suffix visible because name.eth and name.base.eth communicate different identities and are different registrations.

If you are still choosing a provider, use the service-selection guide first. This checklist evaluates the exact name after you know what it needs to do.

Use the say, spell and recognize test

1. Say it. Read the complete name aloud, including the suffix.
2. Spell it back. Ask someone unfamiliar with it to type what they heard.
3. Recognize it. Show the name beside your public identity and ask whether the connection is clear.
4. Read it small. Check how the words separate in a compact wallet or profile view.
5. Repeat later. See which spelling they recall without a prompt.

This is an editorial usability test, not a validated scoring system or a way to estimate market value. Keep the observed mistakes rather than inventing a numerical brand score.

Check lookalikes and the exact string

ENS warns that different characters can look alike while referring to different names and wallets. Copy the exact identifier from the official app and inspect its validity and normalization there. A marketplace image alone is weak evidence of what you are acquiring.

Unusual scripts and emoji may be meaningful to a community, but require deliberate testing with that community’s devices and apps. Do not assume that two strings that look similar are interchangeable.

Shorter is not automatically better

Compare the benefit of a short label with its actual fee tier or acquisition premium. The current ENS cost schedule varies by length. A longer readable identity can be more useful for your purpose than a short label that people mistype or fail to recognize.

For example, a project could compare a familiar full handle with an unclear abbreviation. Test recognition first, then check the exact quote. The ENS fee guide explains the cost categories without assuming that a particular spelling is available.

Keep an availability and purchase record

Do not use brand confusion as a strategy

Avoid choosing a name because it can be mistaken for somebody else’s identity. For a business, check similar marks and related use through appropriate resources. The USPTO’s search guidance explains why an exact-word search alone is not a comprehensive clearance process.

For a personal identity, check whether the label could mislead your audience about affiliation. Availability is only one condition in the decision; it is not evidence of permission or exclusive rights across every naming system.

Choose for your job, then record the tradeoff

Finish the shortlist by writing one sentence: “I chose this complete name because it supports this task for this audience, at this maintenance cost.” If the explanation depends mainly on an imagined future buyer, move to the earning-model decision and evaluate that assumption separately.

Use the personal-brand guide for an individual identity or the business checklist for team ownership and customer use.