This article outlines how to generate concise domain ideas and verify their availability using standard registration tools.
Assuming a Personal Blog Launch with Short Name Constraints
As a worked example, suppose a hypothetical author is planning a personal blog about weekday cooking for one and wants a short, easy-to-spell name. She keeps a paper list with three columns: candidate, why it fits, and what to check before registering. Her first three candidates are PantryPane, OnePotNotes, and SkilletLog. PantryPane is her favorite because the two words are common, the total is short, and the pronunciation is obvious on first reading; OnePotNotes is clearer about the topic but longer to type; SkilletLog is memorable but “log” could suggest something technical rather than recipes. She writes the trade-off next to each name instead of only circling a winner, so the list still works if her first choice turns out to be taken.
For checking, she turns the list into a small form with these fields: candidate as written, all-lowercase version, spoken aloud once, words that sound similar, intended suffix, and the exact place where registration status will be confirmed. Two fictional records show how the form is used. The first reads: candidate PantryPane; lowercase pantripane; spoken aloud “pantry pane”; similar-sounding pantrypain; intended suffix dot com; check performed at the registrar’s own search page, with the result copied beside the record. The second reads: candidate OnePotNotes; lowercase onepotnotes; spoken aloud “one pot notes”; similar-sounding one-pot note; intended suffix dot org; check performed through the same registrar search, with the date noted. The second record is deliberately kept even though the author prefers the first, because a shortlist of one is not a shortlist.
She also writes out each address in full before deciding: the protocol, the host name, and the path for a sample post, so she can see how the name looks in a browser bar and in a sentence she might email to a friend. In this example, she decides the dot-com form of her first choice is the one she would want, and she notes that if it is unavailable she will compare the dot-org form of the same name against the dot-com form of her second choice rather than switching suffixes at random. These names, fields, and records are invented for this explanation; they are not a real blog, a real registration, or evidence about any existing site. The point is to show how a short constraint produces a visible set of choices and a place to record what still needs checking.
Generating Candidate Names via Keyword Combination
For keyword combinations, start from one relevant term and join it with a short word to form a name. The source gives examples such as combining Sunday with clothing to get sundayclothing.com, Diane's with candles to get dianescandles.com or candlesbydiane.com, and Cosmik with masks to get cosmikmasks.com. It says relevant keywords help search engines understand what a site is about, which can improve discoverability especially when starting out, and suggests using tools like Google Keyword Planner to see what people search for and weaving those terms naturally into domain ideas.1
The same source also offers an advanced prompt format for ultra-short names: ask an AI tool to generate 20 domain names combining one keyword with a second keyword and under 12 characters. It advises aiming for a list of at least 15–20 ideas, and treating AI as a starting point before evaluation. Its simple-pattern guidance favors one or two words at most, invented words, or unexpected combinations of existing short words, while avoiding long compound phrases that are hard to remember or spell.1
You can start with a two-column keyword sheet for your own subject rather than inventing names in your head. In the left column, jot the concrete words you would naturally use to describe the project; in the right, note a shorter or more vivid substitute for each. For a hypothetical weekday-cooking blog, that might look like: “supper” for evening meal, “single” for one person, “quick” for under half an hour. Three or four rows are enough to begin.
Next, try combining one word from each row rather than stacking all three. You might write suppersolo, quicksupper, oneskillet, or weekdaysolo and then read each aloud once. Consider where the join falls: “quicksupper” reads cleanly, while “suppersolo” may sound like four syllables with an awkward pause. If a pairing needs explaining, you can set it aside and keep the clearer ones.
Keep a short secondary list of names that use a verb or a small number, such as cookonce or twoevenings, and compare them against your first list. Ask yourself which one you could say to a friend without spelling it, and which one you might confuse with a different phrase. You can mark your favorites rather than ranking everything.
Before you settle, check how each candidate looks in lowercase and in ordinary sentence text, and note any near-homophones you hear when saying it aloud. This is preparation for later checks, not a verdict; you can carry two or three names forward and decide after you have compared them more closely.
Evaluating Memorability and Spelling Simplicity
For the shortlist, the source recommends giving each domain a score of 1–5 on five criteria: memorability, spelling, length, brandability, and flexibility. It frames memorability as whether someone would remember the name after hearing it once, and spelling as whether the average person could spell it correctly without help. Names scoring higher should move onto the shortlist.1
The same source advises discarding anything long, clunky, or difficult to pronounce, along with names containing hyphens, numbers, or doubled letters, which it says make things confusing. In its example, swiftship.com scored 23/25 and was kept, while quick-shipping-solutions.com scored 12/25 and was cut.1
Before you settle on a name, consider giving yourself a short task many people skip: say each candidate out loud once, then type it into a plain text line exactly as you would say it, and compare the two versions. For the hypothetical weekday-cooking author, that could mean listing “quick supper,” “suppersolo,” and “oneskillet,” reading each aloud, and writing beside each one the spellings a listener might guess. If she hears “supper” as “super” when spoken, she might mark it as a risk rather than removing it; the note helps her compare later. This step belongs in your own preparation, not in a form you submit anywhere.
You can also test whether the name survives ordinary sentence text. Try placing each candidate in a sentence such as “I found this on suppersolo and bookmarked it,” then read the line as if you had no outside context. A name that looks clear alone may become tangled when a nearby word repeats a syllable or when lowercase letters blur together, so note which candidate you stumble over. This is a writing and reading judgment, not a grading rule.
Another option is to compare two shortlists side by side instead of choosing from one long list. For the cooking blog, that might mean putting “oneskillet” next to “quick supper” and writing one sentence about each: which one you would repeat to a friend, and which one you would spell letter by letter. These notes are yours to keep or discard, and they can help you decide which spelling risk feels acceptable for a personal project. You might also mark which name you would still recognize after seeing it once. The point is to notice the evidence in your own reactions before you move on.
Selecting Appropriate Top-Level Domain Extensions
To compare suffix options before committing, enter your chosen name in the search box on the NamesLink homepage and use the status shown for each extension to decide which top-level domain fits your blog or project, keeping in mind that .com is the most general choice and that .net, .co, or industry-specific extensions such as .tech and .app are alternatives when .com is already registered. If a status is unclear, cross-check it by visiting the query page again and reviewing the availability and registration notice displayed there.2
Checking Real-Time Availability in Registrar Search
The cited official guide says to start by visiting the provider's homepage and entering the desired name, such as mybrand, in the search box. The results then show the registration status for each suffix under that name: registerable means the domain is not yet registered and can be purchased immediately, while registered means another party holds it, with the option to view Whois information or try to contact the holder to buy it. The guide adds that if the first-choice domain is registered, the service suggests similar registerable domains to choose from. It also notes that some country-code domains may have special registration requirements, which the query page's notices describe.2
Take your shortlist—those three or four names that survived saying aloud and reading in a sentence—and try looking each one up in a registrar's search box, one at a time, in the same sitting. Treat that search as a reading task rather than a decision: you are only checking whether the exact spelling you wrote is shown as taken or open, and whether the space-bar-free version matches what you intended.
For the cooking example, the hypothetical author might open the search box and type oneskillet first, note the result in a fresh column labeled “search result, date checked,” and then repeat for quicksupper and suppersolo. She keeps her original spelling beside the result so she can see whether a lookup quietly suggested a different ending or hyphen. If a name returns nothing close to what she typed, that is a prompt to recheck her letters, not to abandon the name.
You can decide how much weight to give each column. One reader might mark a candidate “keep” simply because the exact form appeared free; another might set it aside if the surrounding suggestions drift toward a longer or hyphenated variant she would not want to say aloud. Either choice is yours, and you can record the reason in a phrase so a later review does not reopen the same question.
When two candidates both look open, you might search them once more in a single pass and compare the results side by side before choosing. Keep the checked date with each note, since availability can change and your record is what lets you tell a fresh lookup from an old one.
Finalizing the Shortlist Before Registration
You can turn the shortlist you have already assembled into a single decision sheet before you open any registration page. Take the three or four names that survived saying aloud and reading in a sentence, and give each one a row with these columns: candidate as written, why it survived, what would make you drop it, and a final verdict of keep, maybe, or drop. Filling the row is not a commitment; it is a way to see whether your reasons are consistent across candidates.
As a worked example, suppose the cooking blogger has narrowed her list to three: oneskillet, quicksupper, and suppersolo. In the "why it survived" column she writes "reads as one pan, easy to spell" for oneskillet, "short but sounds like quick supper, may be misheard" for quicksupper, and "clear meaning, but the double s looks odd in lowercase" for suppersolo. Her "what would make you drop it" entries are more specific: a near-homophone she cannot shake, a spelling she would have to correct every time she gives it aloud, or a form she cannot picture in a sentence without explaining it. You might find that writing the drop condition first makes the keep reasons feel less like affection for a name you have already grown used to.
The same field set can serve current and archived entries if you keep an older candidate list. For a name you are still considering, the verdict column reads keep or maybe and the row stays active. For a name you set aside months ago, the same columns apply, but the verdict reads dropped, and the "why it survived" cell records the original reason rather than a new one. That way you can compare a fresh candidate against a retired favorite without reopening the whole brainstorm.
You can decide how much weight each column carries. One reader might treat an unresolved mishearing as an automatic drop; another might keep a candidate that fails only the lowercase test and plan to live with it. Neither choice is wrong, but writing down which condition you treat as decisive helps you avoid changing the rules between candidates.
When two rows both end in keep, consider one last side-by-side pass: read the two names in the same sample sentence and notice which one you stumble over. Keep the checked date in the row so a later review knows how old the judgment is.
Frequently asked questions
What two columns can I start with to collect words for my own project name?
You can start with a two-column keyword sheet for your own subject rather than inventing names in your head. In the left column, jot the concrete words you would naturally use to describe the project; in the right, note a shorter or more vivid substitute for each.
What can I do to compare two shortlists side by side instead of choosing from one long list?
Another option is to compare two shortlists side by side instead of choosing from one long list. For the cooking blog, that might mean putting “oneskillet” next to “quick supper” and writing one sentence about each: which one you would repeat to a friend, and which one you would spell letter by letter.
How can I turn my existing shortlist into a single decision sheet before opening any registration page?
You can turn the shortlist you have already assembled into a single decision sheet before you open any registration page. Take the three or four names that survived saying aloud and reading in a sentence, and give each one a row with these columns: candidate as written, why it survived, what would make you drop it, and a final verdict of keep, maybe, or drop.
How To Choose a Domain Name: Steps & AI Prompts - DreamHost . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎
域名注册入门指南 | NamesLink . Retrieved 2026-11-19. ↩︎ ↩︎