When choosing a domain, understanding the basic structure of a URL is essential. This article breaks down the difference between the prefix (SLD) and the suffix (TLD), offering practical advice on how to assess which combination best fits your project's identity while adhering to standard naming conventions.

Assessing Your Initial Domain Candidate

Assume a hypothetical author keeping a plain paper worksheet before any registration decision. Across the top she writes three column labels: “candidate,” “morphology notes,” and “suffix notes.” She fills the first rows with three self-made candidates: calm Harbor Supply (recorded as calmharborsupply), Harbor Calm Co (harborcalmco), and Calm Harbor (calmharbor). These spellings are her own notations for comparison, not claims about what any registry or search field will accept.

For calmharborsupply she notes the joined form runs to sixteen letters and stacks three content words, so a reader must parse “calm,” “harbor,” and “supply” in sequence. Her tentative judgment is that this reads cleanly aloud but invites typos at the harbor-to-supply seam. She leaves the suffix column blank for now, since the second part of the worksheet will compare endings. Next to harborcalmco she writes that the word order reverses the natural phrase and appends “co” directly after “calm,” producing a run of consonants that is easy to mistype as harborcalmcom. The third row, calmharbor, gets a shorter note: two words, fourteen characters total, no doubled letters, and no ambiguity about where one word ends.

A second sheet holds a small classification table the author intends to reuse. Its columns are “entry,” “pattern,” and “reader risk.” One fictional record reads: entry calmharbor; pattern two dictionary words joined without a hyphen; reader risk low, though the boundary between “calm” and “harbor” could be misheard when spoken. A second fictional record reads: entry harborcalmco; pattern reversed phrase plus trailing two-letter fragment; reader risk higher, because the fragment resembles a common suffix and may be retyped as a full word. She marks neither record as tested; they exist only to show how the categories work on paper.

One explicit trade-off appears in the margin. Between calmharborsupply and calmharbor, she circles the shorter one and writes “fewer characters, fewer word boundaries, easier to dictate.” The longer candidate stays on the sheet because it carries more descriptive weight, but she records that the extra word adds length without adding a distinct idea. For suffix comparison she reserves a blank block headed “ending candidates,” where she plans to list several generic endings beside each spelling and note length added and whether the ending repeats a letter already at the join. She also draws a separate box labeled “before committing,” containing only the word “check,” without asserting what any check will return. These are her own working examples, assembled to make the morphology and suffix questions visible before she moves on to preparing the comparison itself.

Understanding the Core Components: SLD and TLD

The cited official guide divides a complete domain name into two parts: the prefix (SLD), described as the name portion the user customizes, and the suffix (TLD), such as .com, with .net, .org, and .co listed as common examples. It presents this split as the basic structure of a domain before any registration step.1

The same guide treats suffix choice as a separate decision from the name itself. It calls .com the most general choice and says that if .com is taken, .net, .co, or an industry-specific suffix such as .tech or .app may be considered. It also notes that certain country-code domains may carry special registration requirements and directs readers to the prompt on its query page.1

You can take your own shortlist and split each candidate into two visible parts before judging it: the label before the final dot and the suffix after it. On a worksheet, write the full candidate in one column, then copy the label alone into the next column and the suffix alone into a third. For a hypothetical entry such as calmharbor.example, that gives one line for the full spelling, one for calmharbor as the label, and one for example as the suffix. Keeping the parts separate helps you notice whether a problem sits in the word you chose or in the ending you attached to it.

Next, you might annotate each part in ordinary words rather than codes. Under the label, note how many content words it stacks, whether any letter pair could be read two ways, and where a reader would pause. For calmharbor, a possible note reads “two words, calm then harbor, no doubled letters, natural pause between the two.” Under the suffix, note only what you can observe from the spelling itself, such as length or whether it repeats a word already in the label. A second candidate, harborcalm, can carry the same fields with reversed order, so you can compare which arrangement reads more smoothly aloud.

You can also keep a small contrast table with three columns: “entry,” “label note,” and “suffix note.” One filled row might read “calmharborco — three content words run together — suffix duplicates the final word.” That row would flag a reading burden without deciding the case for you. If you later compare a shorter form, calmharbor, record it on its own row and note what changed: fewer characters, one less word boundary to parse. The choice between them remains yours; the notes only make the trade-off visible before you commit.

Applying General Rules for Name Memorability

Enter a candidate domain name into the search box on the NamesLink homepage to check its availability across various suffixes. You can manually verify the memorability of your chosen prefix by reviewing the morphology notes and suffix notes you recorded on your worksheet against the results displayed.1

Evaluating Suffix Options Beyond .com

For suffix choices, the cited official guide treats .com as the most general option and suggests .net, .co, or industry-specific suffixes such as .tech and .app when .com is already registered. It also says the query page shows the registration status of each suffix for a name, with available domains marked as registrable and taken ones as registered.1

The same guide notes that certain country-code domains may carry special registration requirements, so its advice is to check the prompt on the query page before proceeding. Its eligibility sections are written for registrations made through that service, not as a universal suffix test.1

You can begin with your own three-candidate worksheet and add one new question to each row: what does the suffix promise the reader before they know anything else? For calmharborsupply, harborcalmco, and calmharbor, keep a “suffix notes” column and fill it with your own impressions, not registry claims. One row might read “calmharbor — suffix to decide — fits a short label; readers may expect a familiar generic ending.” Another might read “harborcalmco — suffix under review — the two-letter ending may look like a company marker to some readers and like an unexplained abbreviation to others.” These are your notes for comparison, not verdicts.

You might then compare three suffix families on separate lines: a familiar generic ending, a country-code ending, and a newer generic ending. For each family, write what a reader could infer from the ending alone and what they would still need the label to explain. Consider whether the ending repeats a word already in the label, whether it changes the pronunciation you intend, and whether it makes the joined form longer than you want to type.

For current versus archived entries, reuse the same fields. A current candidate row could read “calmharbor — suffix notes: familiar ending, label carries the meaning — status: open choice.” An archived row for the same label could read “calmharbor — suffix notes: ending no longer preferred after reviewing alternatives — status: kept for reference.” The comparison stays about your preferences and reading experience, not about availability or performance.

You can also prepare a short spoken test: say each candidate aloud once with its suffix, then write which ending felt natural and which required a pause. Mark that as a preference note, not evidence about how others will react. Keep the final choice open until the notes show which ending best supports the label you already find clearest.

Verifying Availability Through Registrar Tools

The cited official guide describes one availability step: enter the desired name, such as mybrand, into the search box on the homepage, and the system displays the registration status for each suffix under that name. It defines two statuses. “可注册” means the domain has not been registered and can be purchased immediately; “已注册” means another party holds it, and you can view Whois information or try to contact the holder about buying it.1

The same guide adds that if the preferred domain is already registered, the tool recommends similar registrable domains. It also notes that certain country-code domains may carry special registration requirements, which the query page is said to flag, so check those prompts before registering.1

Take your existing worksheet and add one column before you open any lookup: the exact spelling you intend to query, letter by letter. For the row already marked calmharbor, you can write the string once as a plain sequence and count the characters, then repeat the same step for harborcalmco. This gives you a fixed reference you can compare against whatever a search field returns, so a near match is easier to spot than if you typed from memory. You can also note the suffix separately from the label, since a result page may treat them as distinct parts.

For each candidate you might prepare three placeholder lines: “queried string,” “what the first result screen showed,” and “follow-up question.” A filled example for a fictional shortlist could read “calmharbor — queried string: calmharbor — first screen: exact match shown — follow-up: confirm the suffix in the detail view.” This is a proposed way to record your own observations, not a report of any lookup already made. If your first query uses one form of the name, keep a second row ready for a variant spelling rather than overwriting the first, so you can tell which version you actually checked.

When a result looks close but not identical, you can decide in advance how much difference matters to you: a changed letter, an added hyphen, or a different ending. Write that threshold on the sheet before looking, then mark each result against it. The point is to separate a true match from a plausible one while the comparison is still fresh, and to leave yourself a clear next question rather than a yes-or-no note.

Finalizing the Structure Before Registration

Take one row you have already annotated, such as calmharbor, and turn it into a short decision note before you commit: write what the label promises, what the suffix promises, and one condition under which you would drop the candidate. For this row the note might read: label suggests calm and harbor as two content words; familiar suffix signals a general commercial site; drop it if the shortened form collides with a candidate already on the list or if the spoken test keeps producing a pause. You can choose your own fields and phrasing; the value of the note is that it records a reason, not just a preference.

You might then lay the three candidates side by side in a final comparison, one line each, and write a single sentence of justification under the one you favor. A hypothetical comparison could read: calmharborsupply — three content words, sixteen letters, clear but long; harborcalmco — reversed order, shortened suffix, less predictable reading; calmharbor — two content words, shorter, clean separation. The author circle calmharbor and writes: fewer characters, fewer word boundaries, and the suffix does not add an extra word to parse. The other two entries stay on the page as considered alternatives, with the reason each was set aside.

For each candidate you keep, you can add a preparation line that names the exact string you intend to check later, spelled character by character, and note which spelling differences would make a near match unacceptable to you. A filled entry might be: exact string — c a l m h a r b o r; acceptable variation — a different suffix; unacceptable — an added hyphen or a dropped letter that changes the reading. Decide this now, while the morphology notes are fresh, so the comparison later follows a rule you set rather than an impression formed in the moment.

Finally, you can mark which rows are ready to carry forward and which need one more revision at the label level. Read the favored candidate aloud once more in ordinary conversation, then write whether the shortened spoken form still points back to the same written spelling. If it does, move that row to the top of your sheet and date it; if it does not, return it to the revision block with a note on which word boundary confused the reading. The finalized structure, then, is your chosen spelling, its suffix family, and the short justification that keeps both choices explainable when you revisit the sheet.

Frequently asked questions

How can I split each candidate on my own shortlist into visible parts on a worksheet?

You can take your own shortlist and split each candidate into two visible parts before judging it: the label before the final dot and the suffix after it. On a worksheet, write the full candidate in one column, then copy the label alone into the next column and the suffix alone into a third.

How might I annotate each part of a candidate in ordinary words rather than codes?

Next, you might annotate each part in ordinary words rather than codes. Under the label, note how many content words it stacks, whether any letter pair could be read two ways, and where a reader would pause.

How can I run a spoken test on my candidates and record the result as a preference note?

You can also prepare a short spoken test: say each candidate aloud once with its suffix, then write which ending felt natural and which required a pause. Mark that as a preference note, not evidence about how others will react.