Choosing the right domain name is a critical first step for any independent website. This article explores strategies for balancing brand recognition with ease of recall, featuring a specific case study and actionable steps for verifying availability.
Case Study: The 'Lumen' Brand Dilemma
For a concrete picture of the trade-off, suppose the author is building an independent site for a small photography-and-writing project and has settled on the working name Lumen. The task on the desk is not a full registration plan but a short list of candidate domains to compare on brand fit and memorability. Three self-invented candidates might look like this:
lumenfieldjournal.com — two-word compound, descriptive, long to type.
lumen-journal.net — hyphenated, shorter, but the hyphen invites dictation errors.
getlumen.org — prefix pattern, short to say, weaker as a brand phrase.
None is a real registered domain; they exist only to show how the author classifies options. The compound keeps the meaning transparent, so a reader hearing it once can guess the spelling. The hyphenated form is easier to say aloud but splits the name at a boundary the listener may drop. The prefixed form reads fast on a card yet pulls the brand word away from the start of the address, which makes it less distinctive when written beside similar sites.
To choose, the author applies one explicit test: say each candidate once to a friend, have the friend type it, and count the wrong attempts at the name part. The imagined friend misspells "lumenfieldjournal" as "lumin" and drops the second word, and writes "getlumen" correctly but asks whether it is a company. That single trade-off—reliable recall of the whole phrase versus a short spoken form—settles the first decision: the author keeps the compound in the shortlist and sets the prefixed form aside as a backup to reconsider if the name later proves hard to spell.
The suffix question is handled the same way, as part of the same list rather than a separate policy. The author's notes pair each name with one destination for a link example: the compound entry is noted for the project's own home page on the .com, and the backup is noted for the same home page on the .org, with no third party named as a recipient. These are the author's own labels for comparison, and the spellings are only how this example records them; they say nothing about whether any registrar search, registration page, or résumé link checker would accept them. The point of the exercise is the reasoning visible in the list: a name the listener can reproduce beats a shorter one that needs repeating, and a suffix choice should be attached to a named destination before it is kept.
Defining Core Keywords for Your Brand Identity
You can start with the three Lumen candidates already on the desk, but treat them as raw material for a keyword exercise rather than a final decision. List the words you actually want a visitor to associate with the project — for this example, perhaps “journal,” “photography,” “writing,” “notebook,” and “field.” Then mark which words appear in each candidate: the compound carries two of them, the hyphenated form carries one plus the working name, and the prefix version drops the descriptive words entirely. That simple mapping tells you which names will need extra explanation later.
Your own keyword list can come from three places you already control: the words you use when describing the project aloud, the headings you have drafted for the first few pages, and the phrases you would put in a one-line introduction. Write them in a single column, then score each on a small scale you choose — say, one for “visitors will understand it without help,” two for “it sounds like the project,” and three for “it can survive being remembered after one hearing.” The scores are yours to set; the point is to make the comparison visible instead of relying on a feeling about the names.
A filled example could look like this, using fields you might record for each candidate: candidate name, core keyword present, keyword strength, spoken clarity, and planned use. For lumenfieldjournal.com the keyword is “field journal,” the strength is high because both words are familiar, spoken clarity is medium because the name is long to dictate, and the planned use is the main site. For lumen-journal.net the keyword is “journal,” strength is medium, spoken clarity is lower because the hyphen must be explained, and the planned use is a secondary project page. For getlumen.org the keyword is only the working name, strength is low, spoken clarity is high, and the planned use is a short redirect. These are author-made illustrations, not results from testing.
You might also separate brand words from descriptive words and decide which side should dominate. A name built mostly from descriptive words is easier to explain but harder to own as an identity; a name built mostly from the working name is the reverse. There is no single correct balance, so consider writing one sentence for each candidate that states what you want a first-time visitor to understand before reading anything else. If the sentence feels strained, that candidate probably asks too much of your later writing.
Evaluating Top-Level Domain Options Beyond .com
The cited official guide lists .com, .net, .org and .co as common top-level domains and calls .com the most general choice. If a .com name is already registered, the guide suggests considering .net, .co or industry-specific suffixes such as .tech and .app. The same guide also notes that it supports hundreds of top-level domains, covering generic, country-code and new top-level domains, and that some country-code domains may carry special registration requirements to check on its query page.1
You can narrow the suffix question by holding the name part constant and changing only the ending across your own shortlist. Using the Lumen examples, you might write three paired lines: lumenfieldjournal.com next to lumenfieldjournal.org, lumen-journal.net next to lumen-journal.org, and getlumen.org next to getlumen.net. The point of the exercise is not to rank suffixes in general but to see whether a particular ending changes how you say the name aloud or how easily someone else repeats it. You can also note whether the ending makes the phrase read as a description rather than a name, which is a judgment you make for your own project.
For a filled example of fields you might keep per candidate: candidate name, suffix under test, spoken once from memory, how you would say it to a friend, whether the meaning survives without seeing it written, and your own one-line reason for keeping or dropping it. A sample row could read lumenfieldjournal.org, org, said as three words, meaning clear, kept as a comparison point only. None of these are registered names; they are placeholders you write for yourself.
When you move from current working lists to archived correspondence or old notes, the same fields apply, but you can add a "source" value such as "current shortlist" or "archived note, date written." Compare the archived row against the current one for the same name part, and you may find the earlier note valued a suffix for reasons that no longer fit. You can decide which row governs the next draft and mark the other as reference only.
Checking Domain Availability and Resolving Naming Conflicts
Enter each candidate name into the search box on the NamesLink homepage to see the registration status of each extension, distinguishing domains that are available from those already registered. If a preferred domain turns out to be registered, review the similar available domains the system suggests rather than settling on the first result. When you want to confirm a status by hand, review the Whois information for the registered name on the same query page.1
Applying Memorability Tests to Shortlisted Names
Take the three Lumen candidates you have already written down and run each one through a small, repeatable scoring sheet before you let any of them advance. The point is not to crown a winner today but to make your shortlist explainable to yourself. You can record five fields for every candidate: the name as written, whether the meaning survives when spoken once, how many characters a listener would need to be told, whether the word part or the suffix carries the recognition, and one sentence on why you would keep or drop it.
A filled example might read: candidate lumenfieldjournal.com, meaning transparent on first hearing, twenty-one characters to dictate, recognition carried by the descriptive words, keep for now because the reading is unambiguous. For lumen-journal.net you might write: meaning clear, hyphen position uncertain when dictated, recognition split between words and punctuation, hold until you decide whether the hyphen is worth the friction. For getlumen.org: meaning depends on the prefix being heard correctly, short to say, recognition sits in the verb rather than a noun, keep as the compact option. These are your own judgments, not verdicts from anyone else.
The same five fields work when you turn to an archived note or an old message about a name you once considered. You can label each row's source as current shortlist or archived note, then compare the two sets side by side. A name that scored well in an old message may now read differently simply because your project description changed; noting that shift is more useful than deleting the old entry.
You might also test your list aloud in the order you would actually use it: introduce the project, then spell the name. If you stumble on the same candidate twice, that is a signal worth recording rather than arguing with. You can decide for yourself whether a stumble is fatal or tolerable, but write the reason down so the choice stays visible later.
Finalizing the Registration Process
Once the shortlist is settled, the cited official guide describes registration as a four-step sequence. Start by visiting the homepage and entering the desired name in the search box. The results show the registration status for each suffix: available means it can be bought now, while already registered means another party holds it. The guide notes that if a first choice is taken, similar available names are suggested.1
When buying, click the register button beside the target domain and select a term of one to ten years. Choose a registrant information template, or the default template generated from your account information is used. The guide states that under ICANN rules the registrant details — name or organization, email, phone, and full address including country, region, city, street, and postal code — must be genuine and valid, and that Whois privacy is enabled automatically.1
Before paying, check the order details: domain list, registration term, registrant information, and add-on services. If the account wallet balance is sufficient, payment is deducted automatically; otherwise the page directs you to top up first. After payment, registration usually completes within minutes to 24 hours, according to the guide.1
Before you commit to a registrar, take the five-field scoring sheet you already filled in and add one more column for "registration readiness." You can prepare this column on paper or in a note for each shortlisted name, without pretending any of it has been tested against a live service. A filled example might read: candidate lumenfieldjournal.com, registration readiness "high — meaning obvious from the name, no explanation needed on a business card," renewal note "remind myself of the annual date in a personal calendar," transfer note "keep the account email separate from the site's contact address," and DNS note "list the name servers I plan to point at before I begin." This is only a working example; your own values should reflect what you can actually confirm about your setup.
You can then apply the same readiness column to an archived entry from your notes, labeling its source as "old message" or "archived draft." For instance, an earlier idea like lumen-journal.net might get a readiness value of "medium — hyphenated, so I would spell it on the phone," a renewal note about checking the registration date, and a DNS note that marks it as "not yet chosen." Keeping current and archived rows in one table lets you see why a past candidate stayed behind, rather than revisiting the same trade-off from scratch.
When the readiness column is filled, you can sort your shortlist by how confidently you would complete each row. If a name still has unclear renewal or transfer details, you might place it below one where the notes are complete. The final pick is yours; the sheet simply keeps your reasoning visible for when you return to register.
Frequently asked questions
How can I use the three Lumen candidates on my desk as raw material for a keyword exercise?
You can start with the three Lumen candidates already on the desk, but treat them as raw material for a keyword exercise rather than a final decision. List the words you actually want a visitor to associate with the project — for this example, perhaps “journal,” “photography,” “writing,” “notebook,” and “field.”
Where can my own keyword list come from, and how do I write and score it?
Your own keyword list can come from three places you already control: the words you use when describing the project aloud, the headings you have drafted for the first few pages, and the phrases you would put in a one-line introduction. Write them in a single column, then score each on a small scale you choose — say, one for “visitors will understand it without help,” two for “it sounds like the project,” and three for “it can survive being remembered after one hearing.”
How can I separate brand words from descriptive words and decide which side should dominate a name?
You might also separate brand words from descriptive words and decide which side should dominate. A name built mostly from descriptive words is easier to explain but harder to own as an identity; a name built mostly from the working name is the reverse.