Starting a personal project often begins with choosing a domain name. This article outlines how to create a shortlist of potential names, understand the difference between prefixes and suffixes, and use registrar tools to check availability without committing to a purchase immediately.
Defining Your Personal Project's Digital Identity
Imagine a freelance illustrator named Mira planning a portfolio site for editorial work, with a sketchbook, a list of past clients, and a short brief on her desk. She wants a name she can say aloud at a networking event and type from memory. She drafts a working title for the site itself (“Paper Lantern Studio”), then tests how it feels as a domain: the two words are easy to spell, but she notes that the phrase could suit a craft shop as much as an illustrator, so she decides the name should lean on her own identity rather than an evocative image.
She builds a shortlist in a plain document with three columns: candidate name, spelling variant, and a one-line reason. Her first candidates are “miraportfolios,” “mira-illustration,” and “paperlanternmira.” For each she writes the variant she would actually type into a browser address bar, such as the hyphenated form of the second candidate, and records why: the first is short but vague, the second is precise yet longer to dictate, and the third pairs a memorable phrase with a personal marker. This is her own working list for explaining the problem, not a set of verified registrations.
To show how the list would be used, she adds two clearly fictional sample records. One reads “mira-illustration — mirasillustration — hyphen avoids an awkward double letter when spoken aloud.” The other reads “paperlanternmira — paperlantern-mira — keeps the studio title first but risks a misheard hyphen.” She then marks one candidate as her preferred direction and notes the trade-off: “paperlanternmira” is distinctive, but she would have to spell “lantern” every time, so she keeps “mira-illustration” as the fallback for spoken introductions.
She also treats the suffix as part of the identity rather than an afterthought. For each candidate she writes the full form she would share, including the ending she is leaning toward, and compares how the ending reads next to her name. Where she is unsure whether a spelling or ending is conventional, she flags it as an open question for later checking rather than asserting a rule. The result is a short, honest shortlist that reflects her own preferences and her everyday use, ready to be narrowed once she confirms which forms are actually available.
Understanding Domain Structure: SLDs and TLDs
The cited official guide breaks a full domain into two parts: the prefix (SLD), described as the name portion you define yourself, and the suffix (TLD), such as .com, .net, .org, or .co. When preparing a candidate list, the guide advises choosing a concise, memorable name tied to the brand and preparing 2–3 backup options. It also treats the suffix as a separate decision: .com is called the most general choice, and if .com is already registered, .net, .co, or industry-specific suffixes such as .tech and .app are suggested as alternatives.1
You can now take your draft candidate list and add a short structure check for each name before you settle on finalists. The point of this pass is to separate the two halves of every entry: the label you invent and the ending you choose from existing options. Treat the part before the final dot as your own choice, and the ending as a fixed category that carries its own meaning and availability rules. Writing the two parts on separate lines in your notes makes that distinction concrete, and it keeps you from editing the ending as if it were part of your made-up word.
For a candidate such as your illustrator-style example, you might revise the note from one long string into two rows. The first row holds the label as written and a spelling variant you would also check, for example “mira-illustration” and “mirasillustration.” The second row holds the ending alone, with a one-line note on why you would pair it with that label. A second example could read “mira-studio” with the variant “mirastudio,” followed by the ending noted separately as the generic top-level kind. If you are weighing a country-code ending as well, record it on its own row with its own reason; that is a different condition, not a replacement for the first ending.
You might also mark, for each full form, which part you would actually say aloud when introducing the project. That single choice helps you notice where a hyphen or a doubled letter could cause confusion, and it gives you a practical reason to favor one candidate over another. Keep the reasons to one line each; the list is for your own comparison, not for publication.
Brainstorming Criteria for Memorable Names
Start your candidate list by making each name brief, easy to remember, and relevant to your brand, and plan to prepare two or three alternatives. Use NamesLink to test each candidate: enter the name in the search box on the home page and review the registration status shown for each suffix, noting which are available and which are already registered; if your first choice is taken, check the similar available names the results suggest. When you want to check a registered result by hand, look at its Whois information before deciding whether to keep or drop that candidate.1
Using Registrar Search Tools to Check Status
Name.com describes its domain name checker as a way to enter a desired domain name; if that name is taken, the tool recommends available options, including new TLDs or premium domains. The page also says the search tool can be used to check domain availability, and it links separate paths for expiring domains, premium names, and bulk search. It presents a domain search box and indicates that a domain is among the products offered, while registration and transfer are described as separate actions.2
For each shortlisted name, you can use a registrar’s public search box as a quick lookup aid, treating it as one signal rather than a verdict. Copy the exact spelling from your notes, search it, and write down what the result page appears to show for the name and its ending—look for whether a result is presented as available, taken, or requiring a different ending. Keep the wording tentative in your notes, since interface labels and availability displays can differ between registrars and change over time.
You might record the lookup beside the candidate rather than replacing your earlier notes. For a fictional example, a row for “mira-illustration” could gain a short field reading “lookup: name shown as taken; hyphenated form still listed as available.” A second row for the unhyphenated form could read “lookup: shown as available at time of check.” Add the date you looked, and mark any result as unconfirmed until you decide how much weight to give it.
Consider running the same check across two or three registrars, not to force agreement, but to notice whether the display is consistent. If one page is ambiguous, you can write “unclear” and move on; you are gathering clues, not resolving every case. Treat the search page as a starting point for your own comparison, and keep your final choice separate from any single lookup screen.
Handling Taken Names and Alternative Extensions
If a preferred name is taken, the documented material points to extensions as an alternative. Hundreds of top-level domains are listed as available, and the guidance groups options by purpose: for creatives, .design, .art, .studio and .band are among the extensions named; personal blogs are also cited as a use case for a memorable online presence.3
The same source frames the extension as part of identity, noting that typing a .com versus a .net leads to a different place. When your candidate list records full forms, that stated distinction is the documented reason to treat the suffix as a meaningful choice rather than a default.3
When a preferred name is taken, you can treat that as a cue to revise the candidate rather than abandon it. Take one row from your fictional illustrator list, say “mira-illustration — mirasillustration — hyphen avoids an awkward double letter,” and split the reaction into two short notes: the exact string that came back occupied, and the alternate you would now consider. A revised row might read “mira-illustration — occupied in the ending I wanted — consider mirasillustration or a short modifier such as ‘mira-editorial’.” The modifier should describe your actual work, not just crowd out the space.
Extending the same example, you can compare the full forms you would actually say aloud. If “mirasillustration” reads awkwardly in speech, you might favor “mira-editorial” even if it is longer, because you can explain it in one breath. Record the ending in the same cell as the name so the variant and the suffix stay together. This is a choice you make about your own portfolio wording; it is not a judgment about which endings perform better.
As a separate, hypothetical case, suppose a second candidate, “mira-sketchbook,” is available only with an ending you had not considered. You can add a row labeled “alternate ending — not yet checked — consider whether the spoken form still sounds like the project.” Keep that label explicit so you do not later mistake a guess for a confirmed result. Then set the list aside and return to it once, asking which two or three candidates you would be comfortable introducing before you look up anything further.
Finalizing Your Candidate List Before Registration
You can take your working shortlist and turn it into a final set of candidates by writing one last entry per row: the form you would actually register and share, plus a one-line reason you chose it over the rivals beside it. This is the point where the list stops growing and starts narrowing. Keep the earlier spelling variants and spoken-aloud notes in place rather than overwriting them, so your final choice still shows the reasoning that led to it.
For the fictional illustrator example, a final row might read “mirasillustration — no hyphen — spoken form matches written form, short enough to say once.” A competing row for “mira-illustration” could carry the note “hyphen helps reading, but I would have to spell it aloud every time.” You can decide for yourself which of those reasons matters more for your project; the purpose is to make the trade-off visible in your own words, not to follow a rule about hyphens.
It helps to close each row with a short question you would ask before committing: would I be comfortable saying this name in a sentence, and would I be comfortable repeating the spelling to someone? Mark each candidate yes, no, or unsure. Unsure rows are worth one more pass, while clear no rows can stay in the document as a record of what you rejected and why.
If you have several strong finalists, you might order them rather than cut them, numbering first choice through third and noting what would make you move down the list. For example, “mira-sketchbook — second choice — only if the first choice’s ending feels too long when spoken.” That note stays hypothetical until you fill it in with your own judgment.
Before you settle, read the whole final column aloud, one entry after another, and see whether any two candidates look or sound too close to keep both. You can drop the weaker twin or keep it as a backup, whichever feels truer to how you would introduce the project. When the list is short enough that you can name your top pick and explain it in one sentence, the candidate stage is done and registration decisions can begin.
Frequently asked questions
How does she organize her shortlist of candidate names in a plain document?
She builds a shortlist in a plain document with three columns: candidate name, spelling variant, and a one-line reason. Her first candidates are “miraportfolios,” “mira-illustration,” and “paperlanternmira.”
How can I turn my working shortlist into a final set of candidates?
You can take your working shortlist and turn it into a final set of candidates by writing one last entry per row: the form you would actually register and share, plus a one-line reason you chose it over the rivals beside it. This is the point where the list stops growing and starts narrowing.
What short question can I write at the end of each row before committing to a name?
It helps to close each row with a short question you would ask before committing: would I be comfortable saying this name in a sentence, and would I be comfortable repeating the spelling to someone? Mark each candidate yes, no, or unsure.
域名注册入门指南 | NamesLink . Retrieved 2026-11-19. ↩︎ ↩︎
Domain Name Search - Check Domain Availability . Retrieved 2026-11-19. ↩︎
Domain Extensions List | All Top-Level Domains (TLDs) | name.com . Retrieved 2026-11-19. ↩︎ ↩︎