This article helps you generate candidate domain names that are easy to remember and likely available. It covers basic naming principles, checking availability, and handling suffix variations without assuming specific brand tools.

Defining Your Project's Core Identity

Suppose a solo developer is preparing a small internal tool for tracking freelance invoices and wants a domain name that a client could retype from memory. She writes down three candidate labels before touching any lookup tool: LedgerLoop, ClearQuill, and StudioSum. Each is a two-word compound, spelled the way it sounds, with no doubled letters at the join. That last detail matters to her because a doubled consonant is where people most often drop a character when typing from memory.

To decide which label leads, she builds a one-page identity sheet with columns for the candidate name, the project role it serves, the spelling risk, and the renewal budget she is willing to commit. Her two example records look like this. LedgerLoop, primary public name, low risk (both words common, single L at the join), budget capped at roughly the cost of two coffees a year. ClearQuill, backup name, medium risk (Quill is less common and may be misspelled as Quil), same budget. StudioSum sits outside the table for now because she has not decided whether the tool belongs to a studio identity at all, and adding it would blur the sheet's purpose.

The choice she makes is to keep LedgerLoop as the working label and hold ClearQuill in reserve, because the first one describes the function — a loop of records — while still sounding like a name rather than a description. StudioSum is dropped for this round, not because it is weak but because it answers a different question about who owns the project. This is a private example she wrote for herself to explain the trade-off; it is not drawn from any real business, user feedback, or completed availability check.

She also writes a one-sentence identity statement at the top of the sheet: "A plain-spoken invoice tracker for one-person studios, memorable on first hearing, short enough to say on a call." That sentence becomes the filter for every later candidate, so a name that needs explaining fails immediately. She notes the intended spelling of each label beside it, since a name she cannot spell consistently in her own notes will not survive a client repeating it back. The sheet stays deliberately short — name, role, spelling risk, budget, one-line statement — so she can compare candidates at a glance instead of re-reading paragraphs.

Applying General Rules for Memorability

You can test each candidate against a short set of ordinary memory rules before spending time on any lookup. A practical starting point is to read the name aloud once, then type it from memory a few minutes later without looking at your notes. If you hesitate at the join between two words, or if you cannot decide whether a letter is single or doubled, that is useful evidence about the label itself rather than about your typing. LedgerLoop passes this check for most people because the two halves are familiar words and the seam is a clean single consonant. A name like LedgerrLoop would fail, since the ear hears one r but the eye must remember two.

You might also compare candidates by how many ways a listener could plausibly spell them after hearing the name once. ClearQuill is short and rhythmic, but the q in the second half invites a c substitution, so a client might try ClearCwill or ClearQuil. That does not disqualify it; it simply tells you the name carries a small spelling tax. StudioSum has a milder risk: the double s at the join is easy to hear but easy to type as one. If you keep a candidate with a known risk, you can decide in advance whether that risk is acceptable for your audience or whether a plainer alternative would serve better.

A third rule is to separate the name's job from your attachment to it. Write one sentence describing what the label should signal, then check whether each candidate actually does that work. For the invoice tool, "a loop of records" and "a plain-spoken tool for solo studios" are two different signals, and LedgerLoop leans toward the first while StudioSum leans toward the second. Neither is wrong, but you can choose which signal matters more for the people who will see the name first.

You can record these judgments on a single sheet with columns for the candidate, the spoken test result, the likely misspellings, and the signal it carries. Filling in the same fields for a name you have already used elsewhere, such as an old project label, gives you a baseline for comparison. The aim is not to score names mechanically but to make your reasons visible, so that when you later compare a current candidate with an archived one, you can see whether you are applying the same standard or simply preferring the newer option.

Generating Candidate Name Variations

Write down your three candidate labels—LedgerLoop, ClearQuill, and StudioSum—on paper, then open NamesLink and enter each label in the homepage search box one at a time to check the registration status shown for its available suffixes. Keep the 2–3 name variations noted before you begin the lookup, and compare what the results display for each candidate before choosing. To verify manually, reread each label aloud and type it yourself to confirm the spelling matches what you intended, especially at the join between the two words.1

Understanding Top-Level Domain Choices

The cited official guide describes a domain name as two parts: an SLD, the custom name portion, and a TLD, the suffix such as .com, .net, .org, or .co. It says the service supports hundreds of top-level domains, covering generic, country-code, and new top-level domains. For suffix selection, the guide calls .com the most general choice and suggests .net, .co, or industry-specific suffixes such as .tech and .app if .com is taken. It also warns that certain country-code domains may have special registration requirements, and directs readers to the notes on its query page before registering.1

You can extend the same identity sheet with a top-level domain column, adding one row for each ending you are considering. For the invoice tool example, the sheet might read: candidate LedgerLoop; intended suffix dot com; what the suffix signals to a client seeing it for the first time; the spelling or pronunciation risk it adds; and the annual renewal cost you expect. Fill the same fields for ClearQuill and StudioSum, and for each alternative ending you want to weigh, such as a shorter country-code ending or a descriptive newer ending.

For the LedgerLoop row, a dot com entry might be judged familiar and quiet but possibly taken, while a country-code entry might be marked as shorter to type but harder for an overseas client to predict. Write your own reasoning in the cell rather than a score, because the judgment depends on who will retype the name. ClearQuill’s row may show a different trade-off: the ending you prefer could make the spoken name and the written name drift apart, so note whether the whole address still reads cleanly aloud.

When you compare endings, keep the suffix attached to the label on the sheet and read the pair aloud as one phrase. If LedgerLoop plus a longer descriptive ending runs past a comfortable breath, you might mark it as a weaker memory candidate even if the words themselves are clear. You can choose to keep a suffix in reserve rather than discard it, and record the condition that would bring it back — for instance, if the familiar ending turns out to be unavailable when you eventually check.

Use the same fields for any name you have already set aside. If you later return to ClearQuill, the sheet still shows which ending you paired with it and why, so you are comparing like with like instead of starting over. You might add a final column for the order in which you would try the suffixes, so the first lookup attempt follows your stated preference rather than whichever ending you happened to think of last.

Verifying Registrability Before Committing

Before committing to a label, check availability through the specific entry described in the cited official guide: enter the chosen name in the search box on the home page, and the system displays the registration status for each suffix under that name. The guide distinguishes two outcomes: registrable, meaning the domain is not yet registered and can be purchased; and registered, meaning another party holds it, with a note that Whois information can be viewed or the holder contacted about a purchase. The guide also states that when a preferred domain is already registered, it offers similar registrable domains to choose from.1

The guide advises preparing two to three alternative names in advance, and it treats suffix choice as part of preparation rather than availability checking: dot com is described as the most general option, with dot net, dot co, or industry-specific suffixes such as dot tech and dot app suggested when dot com is taken. It also notes that certain country-code domains may carry special registration requirements and directs readers to the prompts on its query page, without specifying which suffixes or requirements apply.1

You can take the LedgerLoop row from your identity sheet and treat the “check before committing” step as a separate pass with its own columns: candidate label, ending you paired with it, your planned use (project site, client-facing tool, placeholder), what you would replace if it turns out unavailable, and when you plan to look. Filling this in for LedgerLoop, ClearQuill, and StudioSum is preparation for later decisions, not a conclusion about availability. The point is to decide in advance which names matter enough to pursue and which you are happy to abandon.

For each row, you might record two decisions rather than one: the name you would use if the label is free with your preferred ending, and the fallback if it is not. For LedgerLoop, the fallback could be the same label with a different ending; for ClearQuill, it might be switching to StudioSum entirely because the first choice was a passing preference. Writing both outcomes now keeps you from improvising under pressure later.

You can also note what each candidate would need after a positive check, in your own words: a short description of the project that would sit alongside the name, and a note on whether the label reads well in that description. For the invoice tool, the test sentence is “LedgerLoop keeps a loop of records for one-person studios” — if that sentence feels strained once the name is attached, the row can carry a flag to revisit the label before you go further.

Keep the sheet in one place alongside the identity notes, so that when you do return to it, the pairing between label and ending is already visible. A dated line at the top of the pass, such as the month you plan to run it, helps you see which rows are still fresh. Nothing on this sheet is a promise about what you will find; it is a record of your own preferences, ordered so that the first available match is also an acceptable one.

Preparing Registration Details

Before starting a registration, the cited official guide advises preparing two or three candidate names that are concise, memorable, and related to the brand, and confirming the suffix type. It notes that .com is the most common choice, while .net, .co, or industry-specific endings are options if .com is taken.1

Registration information must also be ready: name, email address, phone number, and address, used to create a domain holder information template. The guide adds that certain country-code domains may have special registration requirements, so the prompts on its lookup page should be checked beforehand. It states that registration details must be genuine and valid under ICANN rules, covering holder name or organization, email address, phone number, and full address including country, region, city, street, and postal code.1

Take the LedgerLoop row from the identity sheet and give it a separate registration-preparation pass, with its own columns: candidate label, chosen ending, the person or role who would approve the spend, the renewal date you want to remember, and a plain note on what the label is meant to do. You can fill the first two fields from the work already done, then leave the rest as prompts to answer before any lookup, so the sheet reflects a decision rather than a wish.

For each row, you might record two outcomes instead of one: the pairing you would commit to if the label is free with your preferred ending, and the fallback you would accept if it is not. For LedgerLoop, a filled example could read “commit: LedgerLoop plus the familiar ending; fallback: LedgerLoop plus a shorter ending if the first is unavailable.” A second row for ClearQuill might say “fallback: hold, do not substitute a longer descriptive ending.” Writing both down keeps a later rushed choice from quietly becoming the plan.

You can also add a short field for what the name would need after a positive check, in your own words — for instance, “one-line description for invoices and records” — so the label stays tied to its job rather than to the excitement of availability. Leaving the approval and renewal columns blank on purpose is fine; the point is that they are visible questions, not assumptions.

Keep this pass on the same sheet as the identity notes and date the line you add. When you come back to it, the label, ending, fallback, and the reason for each will sit together, and the remaining blanks will tell you exactly which choices still belong to you.

Frequently asked questions

What three candidate labels might a solo developer write down before using any lookup tool?

Suppose a solo developer is preparing a small internal tool for tracking freelance invoices and wants a domain name that a client could retype from memory. She writes down three candidate labels before touching any lookup tool: LedgerLoop, ClearQuill, and StudioSum.

What columns could I put on a one-page identity sheet to compare candidate names?

To decide which label leads, she builds a one-page identity sheet with columns for the candidate name, the project role it serves, the spelling risk, and the renewal budget she is willing to commit. Her two example records look like this.

What could I write as a one-sentence identity statement to filter later candidates?

She also writes a one-sentence identity statement at the top of the sheet: "A plain-spoken invoice tracker for one-person studios, memorable on first hearing, short enough to say on a call." That sentence becomes the filter for every later candidate, so a name that needs explaining fails immediately.