A domain can be available and still be a poor purchase. The name may be hard to say, easy to mistype, awkward in an email address, too close to an existing brand, or cheap only for the first year. Availability answers one question: can you register it now? A business needs several more answers before it builds on the name.
Imagine a small consultancy choosing between NorthlineOps.com and a shorter, less familiar spelling. Both appear available. The shorter name looks clever on a logo, but three people spell it differently after hearing it once. One candidate also resembles an established software brand in the same market. The registration fee is the cheapest part of the mistake; changing the name after proposals, email accounts and backlinks exist costs much more.
This 20-minute test turns a domain idea into a recorded decision. It does not guarantee trademark clearance or commercial success. It exposes ordinary risks early enough to reject a weak name without becoming attached to it.
Prepare a one-page Domain Decision Card
Write the candidate exactly as you intend to register it. Add the intended audience, countries where the business will operate, the product or service category, preferred extension, first-year price and renewal price. Leave four boxes at the bottom: Buy, Reserve defensively, Reject, and Needs professional review.
Use a maximum of three candidates in one session. Comparing ten names encourages shallow checking. Three names are enough to reveal trade-offs while keeping the test practical.
| Minute | Test | Evidence to keep |
|---|---|---|
| 0–3 | Say and type | How three people heard and spelled it |
| 3–6 | Inbox and trust | Email-address reading and visual-confusion notes |
| 6–10 | Registration and history | RDAP result, registrar and observed prior use |
| 10–14 | Brand collision | Search terms, markets and records reviewed |
| 14–17 | Renewal and control | Renewal price, registrant and recovery owner |
| 17–20 | Future fit | Three plausible future uses and final decision |
Minutes 0–3: run the Say and Type Test
Say the name aloud once without spelling it. Ask three people to type what they heard. Do not correct them during the test. Record every variation. A name does not automatically fail because one person makes a mistake, but repeated confusion predicts repeated explanation in calls, podcasts, referrals and customer support.
Then type the name on a phone keyboard. Look for doubled letters, missing vowels, hyphens, ambiguous word boundaries and characters that can be mistaken for numbers. Read it in lowercase because domain names are normally encountered that way. A phrase that looks clear in a styled logo may become confusing when every character has the same weight.
Pass: most people reproduce it correctly and the correction is simple. Review: one predictable variation may justify registering a defensive spelling. Reject: several equally plausible spellings would force the business to explain the address every time.
Minutes 3–6: test the name inside an inbox
A business domain becomes more than a website address. Put it into three realistic email addresses: hello@candidate.example, billing@candidate.example and a staff name. Read each address aloud. Check whether the words run together into an unintended phrase, whether a customer could copy it from an invoice, and whether the extension makes sense for the audience.
Also compare the candidate with obvious lookalikes. A name containing a lowercase “l”, uppercase “I”, zero or the letter “o” can be visually misread in some fonts. The issue is not aesthetic perfection. It is whether a customer can distinguish a legitimate message from a convincing imitation.
Minutes 6–10: check current registration data and past use
Use the ICANN Lookup tool for generic top-level domains. ICANN’s current tool uses the Registration Data Access Protocol, or RDAP, and displays available registration data received from registries or registrars. Privacy rules mean some contact fields may be redacted, so a blank owner name does not prove that a domain has never been used.
If the name is registered, record its registrar, status and relevant dates rather than relying on a marketplace banner. Do not contact a private registrant or make an offer just because the name looks inactive. First decide whether the business has a sound reason and budget for an aftermarket purchase.
If the name appears available, search the exact domain and inspect public web archives for visible prior use. Look for a former business in a conflicting industry, spam pages, misleading downloads or content that could confuse returning visitors. Archive gaps are common; “no snapshot” is an unknown, not proof of a clean history. Record what you checked and the date.
Minutes 10–14: look for brand collision
Search the exact words, close spellings and phonetic equivalents in ordinary search engines, app stores and the markets where the business will operate. Then use the WIPO Global Brand Database. WIPO notes that its database covers many collections but may not replace searches in national or regional intellectual-property registers.
A matching word does not automatically make a domain unusable; trademarks are connected to territories, goods, services and the likelihood of confusion. The practical rule is simple: if the candidate resembles an established name in the same field or intended market, stop and obtain qualified trademark advice. A domain registration is not permission to use a brand.
Record the search terms and databases reviewed. Screenshots alone age quickly; a dated note explains what the buyer actually checked.
Minutes 14–17: price the renewal and assign control
Write down the checkout price, standard renewal price, transfer price if published, taxes and any required privacy or email add-ons. Treat an undisclosed future price as unknown, not zero. ICANN advises registrants to understand the registrar’s expiration terms, keep contact details current and renew before expiration. Losing the domain can also interrupt the website and every email address that depends on it.
Decide who will be the registrant, who owns the registrar login, who receives renewal notices and who holds the recovery method. The client or operating company should normally retain control of a client domain. A developer can have delegated access without becoming the accidental owner.
Minutes 17–20: run the Future Fit Test
Write three realistic sentences that begin, “In three years this business may…” The company may add a second service, expand to another country, sell a product, or hire staff. Ask whether the name still makes sense in each scenario. A narrow name can be useful when specialization is permanent; it becomes expensive when the business already expects to grow beyond it.
Check whether the name works as a spoken referral, a browser address and an email identity. Social-handle consistency is helpful but should not force a weaker domain. Handles can change and platforms can disappear; the domain is the asset the business can control directly.
Score the candidate without hiding a serious risk
| Test | 0 points | 1 point | 2 points |
|---|---|---|---|
| Say and type | Repeated confusion | One manageable variation | Clear on first attempt |
| Inbox and trust | Misleading or awkward | Minor concern | Clear and credible |
| History | Material harmful conflict | Unknown or mixed | No material issue found |
| Brand collision | Same-field conflict | Needs professional review | No material conflict found |
| Renewal and control | Unknown or uncontrolled | One unresolved item | Documented and owned |
| Future fit | Already too narrow | Works with a limitation | Fits planned direction |
A score of 10–12 is a strong operational candidate. A score of 7–9 needs a written fix before checkout. Six or below should normally be rejected. Do not let the total overrule a zero in brand collision or control; those are stop signs, not small deductions.
Make the purchase reproducible
If the candidate passes, save the Domain Decision Card with the legal name of the registrant, registrar, renewal price checked, billing owner, recovery owner and test date. Enable multifactor authentication, confirm renewal notices reach a monitored address and store recovery information in the organization’s password manager.
The goal is not to find a magical name. It is to choose a usable name with visible risks, recorded ownership and a renewal plan. Twenty careful minutes before registration can prevent years of explaining, rebranding or recovering an asset that the business assumed it controlled.
How we researched this guide
This guide uses ICANN’s RDAP and renewal guidance and WIPO’s trademark-search resources. It is a practical screening process, not legal advice or a complete trademark clearance. Policies and prices change; verify the current registrar terms and relevant national or regional registers before purchase. No affiliate links appear in this article.
