When selecting a domain for a personal blog, you must navigate technical naming conventions while aiming for a memorable identity. This article outlines how to evaluate candidate names against standard registration rules, ensuring your chosen address is both valid and distinct without getting lost in overly complex or prohibited structures.
Scenario: A Blogger Drafting Three Candidate Names
This is a hypothetical situation: a blogger who writes short essays about city walking and old bookshops is preparing a first site and wants three workable name candidates rather than one perfect name. On the desk are a notebook of working titles, a list of recurring themes (footpaths, secondhand shops, tram stops), and a blank table headed "candidate, why it fits, what to check." The blogger deliberately treats the table as a record of choices made for this exercise, not as evidence about any existing site.
The first candidate is a compact coinage made from two theme words, "pathlore" — short enough to say aloud once, distinctive enough to avoid a generic phrase, and easy to spell after hearing it. The second is a two-word descriptive form, "tramnotes," which favors clarity over surprise; the blogger notes that descriptive names are simpler to explain but competing uses may be harder to distinguish. The third is a fuller title, "thebookshopwalker," chosen to test whether a longer name still reads cleanly when written in lowercase. The table records a deliberate trade-off: the blogger keeps the coinage as the primary candidate because brevity wins for spoken mentions, while holding the descriptive form as a fallback if the first proves awkward in writing.
The next columns are about what to verify rather than what to prefer. Against each candidate the blogger writes two checks: whether the spelling survives being read over the phone, and whether the name still makes sense if the blog later adds topics beyond walking. A separate column lists the suffix choice, recorded as a decision to revisit rather than settled here; the note says only that the shorter form and the two-letter country form will be compared on how they read in print. No claim is made about availability, and the notebook explicitly marks the table as an invented planning aid.
A fourth row is added almost as a control: a single common word, "marginalia," which the blogger likes but flags as likely to be shared by many other writers. Its purpose in the table is to show why uniqueness is being weighed at all — a familiar word is memorable but hard to own, while an invented one is ownable but needs repeating. The draft ends with a short list of the three candidates in the order they would be mentioned to a friend, with the coinage first, the descriptive form second, and the longer title third, each paired with the one check that matters most for it.
Verifying Character Sets and Length Limits
For an English-language domain, the documented rules allow only letters a–z (case-insensitive), digits 0–9, and the hyphen. Spaces and characters such as !, $, and & are not supported. The hyphen cannot be registered on its own or placed at the start or end, and whether consecutive hyphens are permitted depends on the top-level domain and the registry system's actual support.1
Length is capped at 63 characters. For .hk names, a separate limit applies: the total must not exceed 15 characters. Chinese-language domains follow a different rule, requiring at least one Chinese character while the rest may include letters, digits, or hyphens.1
Hyphen placement can also vary by suffix. Under .com and .net, the hyphen cannot appear consecutively in the second and third positions of the prefix, while other consecutive positions are allowed. Under .cn, .中国, .公司, and .网络, consecutive hyphens are not permitted at any position.1
For your own shortlist, you can start by writing each candidate in plain lowercase and then counting its characters without spaces or punctuation. If you are weighing a two-word coinage, note the letters-only version as one entry and the version with a joining particle as another, so the comparison stays honest. You might also say each name aloud once and write down where you hesitated; that small note often matters more than a neat column of numbers.
For a personal blog about city walking and old bookshops, a hypothetical blogger could keep “pathlore” as the compact choice and add a longer alternative such as “pathandlore” beside it. In a simple table, the fields might be: candidate, letters only, spoken once, likely misspelling, and my preference. A filled row could read: pathlore, eight letters, easy to say, “pathlor” when heard quickly, keep. A second row might read: pathandlore, eleven letters, slightly rushed, “pathandlore” with the middle blurred, hold. These are demonstration values, not measurements of any real name or service.
You can also choose how strictly to treat length. One reader may decide that anything above ten letters feels tiring to repeat, while another may accept a longer name if it is distinctive. Neither rule is universal, so it is worth writing your own cutoff beside the table and checking whether your preferred candidate survives it.
For each candidate, consider recording the characters you are unsure about: doubled letters, vowels that could be swapped, and any sequence that looks awkward in lowercase. You can mark whether the uncertain spot sits near the beginning, where readers notice it, or near the end, where it may be less disruptive. Keep this as your own working note rather than a fixed requirement, and let the strongest two entries move forward to the next comparison.
Balancing Memorability with Technical Constraints
Use NamesLink to look up the registration rules, character restrictions, and naming conventions for any top-level domain you are considering, so that a short and distinctive name also fits the technical limits of its extension. To check a candidate manually, compare each label against the character restrictions shown for the chosen TLD before you settle on a final domain.2
Handling Hyphens and Special Position Rules
For a blog domain that uses a hyphen, the documented naming rules depend on the suffix. With generic top-level domains such as .com and .net, a hyphen cannot appear together in the second and third character positions of the domain prefix, though it can repeat in other positions. With .cn, .中国, .公司 and .网络, a hyphen cannot appear consecutively at any position. A hyphen also cannot be registered alone or placed at the beginning or end, and the domain length is capped at 63 characters.1
Adding a hyphen between or around restricted words does not change the restricted-domain determination for terms such as “中国”, “国家”, “中华”, “全国” and their equivalents like China, chn and sino. Registrations containing these require an authorized rights holder.1
For the hyphen question, you can take your existing shortlist and add one comparison column: how the name reads when the hyphen is spoken aloud. A hypothetical blogger with “city-walk-notes” might write the spoken form as “city walk notes” and notice that listeners will probably drop the punctuation anyway. That entry can stay on the list as a viable second choice, but it is worth marking whether the unhyphenated spelling would still be recognizable if someone typed it from memory.
Then you might try a small rewrite exercise on each candidate that contains a hyphen or a digit. Write the name twice in plain lowercase, once as you intend it and once as a hurried reader might type it, and set the two versions side by side. For “old-book-shop,” the hurried version might come out as “oldbookshop,” which is still readable, or as “oldbooksshop,” which is not. The point of the exercise is not to eliminate every risky name but to decide which misspellings you could tolerate pointing out later.
If two candidates survive that check, consider a simple position test rather than a rule. Write each name at the start, middle, and end of three ordinary sentences you might actually use, such as an introduction, a recommendation to a friend, and a closing line. A name that feels clumsy at the end of a sentence may still work at the start, and you can note that preference next to the entry. Keep the notes short, and let the column you filled earlier decide the final order.
Checking Top-Level Domain Specific Restrictions
For a personal blog, checking a candidate against top-level domain restrictions comes before assuming any name is open. Alibaba Cloud's registration guide states that character type and length rules vary by suffix, and that different registries treat consecutive hyphens differently. Its documented example: for general suffixes such as .com and .net, a hyphen cannot occupy the second and third character positions consecutively, while other positions may repeat it; for .cn, .中国, .公司 and .网络, hyphens cannot appear consecutively at all.1
The guide also records suffix-specific eligibility rather than naming style. A .商标 domain requires a qualifying trademark registration certificate, and .gov.cn is limited to Chinese party and government bodies and units lawfully exercising their functions. It notes that domains containing words such as 中国, 国家, 中华, 全国, china, chn or sino must be registered by the relevant rights holder; for these suffixes, adding a hyphen does not change the restricted-domain determination.1
You can take your existing shortlist and add a column for the top-level ending you are considering, then record what you would need to confirm before committing to it. For example, a blogger comparing “pathlore.com” and a country-code ending might write: candidate, intended ending, who appears eligible to register it, whether a local presence is required, and what the renewal terms appear to be. The point is not to settle those questions from memory but to note which ones remain open for each candidate.
This same set of columns can serve an archived announcement as well as a live one. Suppose an older post lists a name with a country-code ending that was common years ago; you can record it beside the current candidate and mark the eligibility and renewal cells as “check against the current registry statement” rather than copying the old post’s wording forward. That keeps the two entries comparable without treating the archive as proof of what applies now.
You might also note, per candidate, whether the ending suggests a particular audience or region, and whether that fits a blog about city walking and old bookshops. If a restricted ending seems appealing but you cannot quickly confirm the conditions, you can keep it as a secondary option and give the plainer ending a first-place mark for now. The record stays yours to adjust as you verify each row.
Final Validation Before Registration Attempt
Before you register anything, set the shortlist beside one final page of notes and read your own decisions back in one sitting. This is a review of your material, not a fresh search: you are checking whether the choices you already made still hold when they sit next to each other. A hypothetical blogger with "pathlore," "pathlore-walks," and a longer "oldbookshopwalks" entry might write the three names in one column, the chosen ending in the next, and a short reason in a third. If the reasons start repeating the same vague phrase, that is a signal to choose rather than collect more candidates.
For each candidate, you can note the one thing that made you keep it. Maybe "pathlore" survives because it is easy to say once and hard to misspell; the hyphenated version survives because it names the activity clearly; the long entry survives because it matches the blog's subject most exactly. Write what you would lose by dropping each one. A hypothetical note might read: "pathlore — loses the walking cue; hyphen version — loses compactness; long version — loses ease of typing." Seeing the losses in plain words often settles a tie faster than another round of comparison.
It also helps to decide, in advance, what would make you walk away from a name. You can set your own conditions: a spelling you would have to correct every time you say it aloud, a name that reads awkwardly when someone repeats it back to you, or a version you keep wanting to shorten. The blogger might decide that any candidate needing a spoken clarification fails, and that is a legitimate choice, not a rule others must share.
Finally, treat the whole page as a snapshot and date it. Write the date at the top, list the candidates in the order you now prefer them, and mark one as your first choice. This is preparation for a registration attempt you have not yet made; the page records your reasoning so that if you return in a week or a month, you can see why you ranked them that way and decide whether you still agree.
Frequently asked questions
How can I begin comparing candidates on my own shortlist by counting their letters?
For your own shortlist, you can start by writing each candidate in plain lowercase and then counting its characters without spaces or punctuation. If you are weighing a two-word coinage, note the letters-only version as one entry and the version with a joining particle as another, so the comparison stays honest.
What can I add to my shortlist to check how a hyphenated name sounds when spoken aloud?
For the hyphen question, you can take your existing shortlist and add one comparison column: how the name reads when the hyphen is spoken aloud. A hypothetical blogger with “city-walk-notes” might write the spoken form as “city walk notes” and notice that listeners will probably drop the punctuation anyway.
What can I note for each candidate about the one thing that made me keep it?
For each candidate, you can note the one thing that made you keep it. Maybe "pathlore" survives because it is easy to say once and hard to misspell; the hyphenated version survives because it names the activity clearly; the long entry survives because it matches the blog's subject most exactly.
如何注册域名-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Domain Registration | NamesLink . Retrieved 2026-11-19. ↩︎