This guide helps you assess naming options by searching for available combinations of your brand term with various top-level domains, using a registrar's lookup tool to check status.
Setting Up Your Naming Evaluation Scenario
As a hypothetical illustration, imagine an independent designer in Leeds preparing a small product page for a service called “Hartline,” a made-up name used only here. She keeps a working folder with a shortlist of suffix pairings written as plain text, not as live addresses. Her three entries look like this: Hartline studio site, Hartline works site, Hartline journal site. She records the full host shape for each, notes that the first and third use a common suffix she can spell aloud, and marks the second as the one she would pick if she wants a quieter, less crowded spelling. That is an example choice, not a recommendation, and the reasoning is only her own preference for a name clients can repeat without a second attempt.
Next she makes a small comparison sheet with columns for candidate name, suffix, spoken form, written form, and a note on ambiguity. Two fictional rows show how it works. Row one: “Hartline Works,” suffix “.studio,” spoken as “Hartline dot studio,” note “reads clearly on a business card.” Row two: “Hartline Journal,” suffix “.site,” spoken as “Hartline dot site,” note “short, but sounds like a publication rather than a portfolio.” She writes the second row as a discard and keeps the reason beside it so she can revisit the decision later.
She then drafts a short directory page for her own use, with headings that a reader could copy: Name, Suffix, Intended use, How it is said aloud, Where enquiries should go, Renewal reminder date. Under “Where enquiries should go,” she fixes each example to one channel rather than leaving it vague: for the studio row she writes “email to the studio inbox,” and for the journal row she writes “contact form on the journal page.” These are her own arrangements, not verified recipients.
To test the suffixes themselves, she compares three lookup paths in her notes: typing the candidate into a registrar’s availability field, checking the same string in a search engine to see what already appears, and asking two colleagues to spell it back after hearing it once. The third check is the one she weights most, because a suffix that fails spoken repetition will fail in conversation regardless of what a lookup returns. She does not treat any lookup result as proof of ownership or future availability, and she leaves the actual registration step for later in the process.
This scenario is only an explanatory example; the names, rows, and outcomes are invented to show how a shortlist, a comparison sheet, and a directory skeleton fit together before any purchase decision is made.
Using Registrar Search Tools to Check Suffix Availability
The cited official guide describes checking availability through the registrar's homepage search field: enter the desired domain name, and the system displays the registration status for each suffix under that name. Statuses are shown as available for registration or already registered; for an already registered name, the guide says you can view Whois information or try to contact the holder. It also notes that if the preferred domain is taken, similar registrable domains are suggested. Separately, the guide advises preparing two or three candidate names and checking any stated requirements for certain country-code suffixes on the query page before registering.1
For the Hartline sheet, you can turn the comparison notes into a small search plan before looking anything up: one column for the exact spelling you would type, one for the suffix, one for the spoken form, and one for what you expect the result to tell you. Filling the expectation column first keeps a disappointing lookup from quietly reshaping the shortlist; a row that says “check whether Hartline with this suffix is already claimed” is easier to judge than a blank that later seems like a rejection.
You might also record which spelling variant each lookup covers. If you planned to search “hartline” with one suffix and “hart-line” with another, note that the two rows are testing different strings, not the same one twice. When you compare suffixes across several candidate names, keep a separate row per pairing so a gap in one combination does not read as a verdict on the name itself. Readers weighing spoken clarity can note beside each row how the pairing sounds when said aloud, which is a writing judgment rather than a search result.
When results come back, consider pencilling a status beside each row, such as “appears open for now,” “claimed,” or “needs a second look,” and date the note. Availability is a snapshot, so the sheet stays useful only if you can see when it was taken. Leave a final column for your own decision: keep, drop, or hold until you have compared more suffixes. That keeps the directory skeleton a record of choices you made, not a list of answers you were handed.
Interpreting Registered vs. Available Status Results
The cited official guide describes how a registrar’s availability results distinguish two states. After you enter a desired name, such as mybrand, in the home-page search box, the system shows the registration status for each suffix: “可注册” means the domain has not yet been registered and can be purchased immediately, while “已注册” means another party holds it, with options to view Whois information or try to contact the holder about a purchase. The guide also says that if the preferred domain is already registered, similar registerable domains may be recommended. These status labels support a row-by-row reading of availability; the guide does not describe other result states or how to interpret them.1
For the Hartline rows you have already drafted, the next step is to decide what each status note is allowed to mean before you act on it. You can mark a row as “registered” when a lookup returns an existing record for that exact spelling and suffix, and as “no record returned” when the lookup shows nothing. Keep these two as separate observations rather than translating either into a verdict about who owns the name or whether it is safe to use.
You might add a short note beside every row explaining which spelling and which suffix the result actually covered. A blank result for “hartline” with one suffix tells you nothing about “hart-line” with that same suffix, so record the exact string you searched. If you later widen the search to another combination, treat that as a new row with its own date rather than editing the earlier one.
Consider keeping a small “before I rely on this” column with your own reminder, such as “check the record directly” or “ask whether the displayed status is current.” For the Hartline example, one invented row might read: name hartline, suffix example, status no record returned, checked date, note “spelling only; variant not searched.” Another might read: name hart-line, suffix example, status registered, note “record exists; do not assume it is for sale.”
These notes are your own working record, not an official finding. You can decide how much weight to give each row, and you might revisit a row after a short interval to see whether the same lookup still returns the same result. Recording the date and the exact string is what lets you compare later without guessing what changed.
Brainstorming Alternative Brand-Suffix Combinations
In NamesLink , use the homepage search box to enter each candidate brand term and review the registration status shown for every suffix, which lets you compare alternatives such as .com, .net, .co, .tech, and .app side by side before choosing combinations to pursue. Prepare two or three backup name options beforehand so the availability check can cover the whole set. When a preferred combination is already registered, read the WhoIs information or try contacting the holder, and use the similar available domain suggestions the system displays to widen the list. To verify results by hand, cross-check the status and Whois details shown for each name and suffix.1
Documenting Candidate Names and Their Lookup Outcomes
You can keep one shared record template and fill it twice: once for a name you are considering now, and once for a name you remember from an older announcement or archived note. The same columns work for both, but the meaning you assign to a filled value changes with the source. For example, a current candidate row might read: Name “Hartline,” Suffix “.studio,” Intended use “small product page,” Spoken form “HART-line,” Written form “hartline,” Lookup date “this week,” Status “appears open for now.” An archived row using the same fields might read: Name “Hartline,” Suffix “.studio,” Intended use “earlier campaign page,” Spoken form “HART-line,” Written form “hart-line,” Lookup date “the date shown on the archive entry,” Status “unknown; record not checked today.” Writing both rows side by side lets you see that the older entry is a historical note, not a statement about the present.
For each row, you might add a short column headed “What this entry can support.” In the current row, you can write “helps me decide whether to look further.” In the archived row, you can write “tells me only what was said then.” This keeps a historical mention from quietly becoming evidence about availability or use today. You can also note which spelling each lookup covered; if the older entry pairs the hyphenated form with one suffix and your current candidate uses the unhyphenated form, treat them as two separate records rather than merging them into one.
When you review the template, consider a few choices of your own. You might decide whether a blank lookup field means “not yet checked” or “checked, no result recorded,” and write that convention at the top of your notes. You can also choose how often to revisit a row before relying on it for a decision, such as checking the record again after a short interval. These are your working conventions, not findings about any name. The value of the template is that it keeps your current shortlist and your older references visibly distinct while letting you compare them field by field.
Finalizing the Shortlist Based on Search Findings
When finalizing the shortlist, the cited official guide limits what a lookup result can tell you. Its availability step says the system shows, for the entered name, the registration status of each suffix: registrable means the domain is not yet registered and can be purchased, while registered means another party holds it and you can view Whois information or try to contact the holder.1
The guide also notes that when a preferred domain is already registered, its lookup suggests similar registrable names. Before acting, also check the guide's note that certain country-code domains may have special registration requirements and that the lookup page displays prompts for them.1
You can turn the search findings into a shortlist by applying a simple rule to each row: keep, hold, or drop, with a written reason. For the invented “Hartline” sheet, one row might read: candidate “hartline,” suffix example, status “appears open for now,” reason “spelling matches the spoken form I would use in an enquiry.” Another might read: candidate “hart-line,” same suffix, status “needs a second look,” reason “the hyphen may be dropped when someone types it from memory.” A third could be marked “hold” because the result covered only one spelling variant.
When two rows feel equally usable, you might weigh how easily each one survives being said aloud and written down by someone else. If a listener would likely write a different form from the one you planned to use, that is a reason to rank it lower rather than discard it outright. You can note this beside the row in plain words, such as “heard correctly, but often written without the hyphen.”
You might also group the rows by intended use before deciding. A name you want for a small product page and a name you might mention in an email enquiry do not have to meet the same bar, so you can write a one-line threshold for each group and keep only rows that clear it.
For the final pass, consider giving each surviving row a dated note saying what you would check next and why. That keeps the shortlist a record of your own reasoning rather than a verdict, and you can choose how many rows to carry forward.
Frequently asked questions
What columns might I use to compare candidate names and suffixes side by side?
Next she makes a small comparison sheet with columns for candidate name, suffix, spoken form, written form, and a note on ambiguity. Two fictional rows show how it works.
What status notes could I pencil beside each row when lookup results come back, and should I date them?
When results come back, consider pencilling a status beside each row, such as “appears open for now,” “claimed,” or “needs a second look,” and date the note. Availability is a snapshot, so the sheet stays useful only if you can see when it was taken.
When reviewing my record template, what convention might I write for whether a blank lookup field means not yet checked or checked with no result?
When you review the template, consider a few choices of your own. You might decide whether a blank lookup field means “not yet checked” or “checked, no result recorded,” and write that convention at the top of your notes.