This article helps you generate creative domain name ideas for your personal site or small project and provides a self-check list to verify their suitability and availability before registration.

Brainstorming Names for Your Personal Site

Suppose a freelance illustrator is planning a small portfolio site and wants three name candidates before buying anything. The first candidate is “inkandpost,” a two-word joining of the tools and a mailing metaphor; the second is “paperfieldnotes,” a longer descriptive phrase; the third is “mosslantern,” a purely evocative pairing with no obvious meaning. Each is written down here as the author’s own working label, not as a name checked against any registry.

The author’s notebook can hold a three-column table: candidate name, what it suggests, and what it would require. For “inkandpost,” the suggestion is drawing plus sending work out; the requirement is a short spelling that a visitor might still type as “inkandpost” without a hyphen. For “paperfieldnotes,” the suggestion is process sketches and observations; the requirement is accepting a longer string. For “mosslantern,” the suggestion is a quieter, atmospheric portfolio; the requirement is deciding that the obscurity is acceptable. Two sample rows might read: “inkandpost — illustration and dispatch — confirm spelling once by voice on a call; paperfieldnotes — sketch diary — decide whether length is tolerable.” These rows are invented for this example, not records of a real project.

For the overtly descriptive option, the author could set a test pair of addresses to compare in writing. One entry is “paperfieldnotes.example” with a placeholder registry path shown simply as path “/check” and query “name=paperfieldnotes”; the author notes that this entry points to the “public storefront” channel they would first open, and that any response is a placeholder for later research, not a confirmation. The second entry is a shorter variant, “pfn.example,” marked for the same channel and noted only as a comparison. Writing the channel and destination beside each invented entry keeps the comparison honest: the author can see which spelling still reads clearly when spoken aloud, which one fits a business card, and which one invites mishearing.

One choice follows from the table rather than from preference. If the illustrator expects to say the name often at markets, the shorter “mosslantern” wins on pronounceability, while “paperfieldnotes” offers clearer expectations to a first-time visitor. The author writes both reasons in the row, then picks one and marks the other as a fallback. That single decision, made against written criteria, is what this example is meant to show.

Understanding Domain Structure: SLD and TLD

The cited official guide describes a full domain name as having two parts. The prefix, or SLD, is the part you define yourself, illustrated with “nameslink .” The suffix, or TLD, is the top-level domain, with .com, .net, .org, and .co given as common examples.1

The same guide notes that hundreds of top-level domains are available for registration, spanning generic top-level domains, country-code top-level domains, and new top-level domains. It also advises checking local rules, since certain country-code domains may carry special registration requirements that are stated on its query page.1

For the three candidates, you might take each written label and split it where the last dot would fall. With the placeholder second-level label and top-level label separated in your notes, “inkandpost” becomes a second-level label paired with a generic top-level label; “paperfieldnotes” can be recorded the same way; “mosslantern” likewise. The act of splitting is useful because it forces you to notice which part people will actually say aloud and which part they may assume without being told.

Consider keeping a small comparison table with four fields: what the second-level label sounds like when spoken once, whether it is easy to spell after hearing it, whether it suggests the illustrator’s work or remains open, and which top-level label you are pairing it with. A possible filled row reads: label “inkandpost,” spoken sound “ink and post,” spelling risk “the joining may be typed as two words,” suggestion “tools and mailing,” top-level pairing “a generic suffix, noted as a candidate for later checking.” For “paperfieldnotes,” the same row might note a longer spoken form and a higher chance of a typo, while “mosslantern” scores well on sound but carries no descriptive signal.

These are your own working notes, not registry checks. You can choose which column matters most before looking further, and you can leave the top-level pairing column as a question rather than a decision. If a label only works when read silently but fails when spoken, that is a reason to set it aside rather than a verdict about anyone else’s choice.

Choosing the Right Top-Level Domain (TLD)

The cited official guide describes a complete domain as two parts: the prefix (SLD), which is the part you customize, and the top-level domain (TLD), such as .com, .net, .org, or .co. It says the service supports registration of hundreds of TLDs, covering generic, country-code, and new TLDs.1

For choosing a suffix, the guide's own suggestion is to treat .com as the most general choice; if .com is taken, it points to .net, .co, or industry-specific suffixes such as .tech and .app. It also notes that certain country-code domains may carry special registration requirements and advises checking the prompts on the query page before registering.1

For each of the three working labels, you can write out the full address shape twice with different generic endings, then read both versions aloud. “Mosslantern” might appear once ending in a short, memorable suffix and once ending in a longer, more descriptive one; “paperfieldnotes” the same. This is not a registry lookup, just a written comparison. Note which version you would spell without hesitating and which one starts to feel like a sentence when spoken. You can decide for yourself whether the shorter or longer ending suits a name you expect to say often.

A useful self-check is to ask, for every candidate, what the ending promises to a visitor. A descriptive phrase may look natural with a longer, word-like ending, while an evocative pairing may sit more comfortably with a short one. Neither is correct in advance; the question is whether the whole label reads as one choice or as two unrelated parts. If the ending seems to be doing all the describing, the second-level label may be too vague, and you might consider adding a concrete word instead.

You can also keep a small notes table with four fields: candidate, ending tried, spoken impression, and written impression. A filled example might read: “mosslantern — short ending — easy to repeat — looks balanced”; “paperfieldnotes — longer ending — sounds like a heading — feels heavy.” These values are your own working impressions, not verified facts about any ending. Choose which field matters most before you narrow the list further.

Drafting a Shortlist of Candidate Names

Before buying anything, open NamesLink and use the search box to look up each shortlisted candidate—"inkandpost," "paperfieldnotes," and "mosslantern"—one at a time, since the results show the registration status across the various suffixes for the name you enter; if a preferred name is already taken, the service also suggests similar registrable alternatives. To double-check a result by hand, review the listed status for the suffix you want and, where a name appears registered, consult the Whois information before deciding.1

The cited official guide describes the first registration step as a search on the service’s homepage: enter the desired domain name, such as mybrand, in the search box, and the system displays the registration status for each suffix under that name. The guide defines two outcomes here. Registerable means the domain has not been registered and can be purchased immediately. Registered means another party holds it, and you can view Whois information or try to contact the holder to purchase it. The guide adds that when the preferred domain is registered, the service intelligently recommends similar registerable domains to choose from.1

You can start by printing or copying the three working labels into a simple availability-notes sheet, then treat each one as a question to investigate rather than a result. Add four fields for each: the exact spelling you intend to search, the ending you plan to pair it with, the date you looked, and what you found in plain words. If you decide to search the two-word joining first, record it as it would be spoken, then as it would be written without spaces, since a listener may type it differently from how you say it.

For each label, you might prepare a short list of spelling variants you are willing to accept before you search, and mark which one is your first choice. You can note whether the exact spelling matters to you or whether a nearby variant would still work; that decision is yours and can change after you see what is available. A filled example could read: candidate “mosslantern,” first-choice ending a word-like one, accepted variant with a hyphen, date written down, notes saying the shorter form is preferred if both exist.

Keep the same field set for any archived or older listing you happen to consult, so the two kinds of entries stay comparable. For a current listing, the date and note might say the spelling was seen as offered today; for an older archived entry, the same fields can record when that page was dated and what it showed then, rather than implying it still applies. You can choose whether to mark current and archived rows with different colors or a simple prefix in your notes.

Before you act on anything, read your own rows once more and separate what you observed from what you assume. If a field is blank, leave it blank rather than guessing.

Final Pre-Registration Checklist

Write down the one action you will take after reading your notes: for each of the three working labels, list the full address shape you would actually type, using your own chosen second-level label and one generic ending at a time. Keep this as a planning sheet, not a search result. You can place the three written shapes side by side so the differences in length and word breaks are visible before you decide anything.

For each row, add a short reason in your own words about why that shape still suits the project. A filled example might read: label “mosslantern,” shape “mosslantern” plus a short generic ending, reason “short enough to say at a market stall.” Another row might read: label “paperfieldnotes,” shape with a longer word-like ending, reason “describes the work but is long to repeat.” These are your judgments, so you can choose which reason counts most.

Then mark each row with a simple status you assign yourself: keep, revise, or set aside. You might set aside “inkandpost” if the joining reads awkwardly when spoken, or keep “mosslantern” as the first choice while holding “paperfieldnotes” as a backup. The point is to record your own decision rather than leave three equal candidates open.

Before you move from notes to any purchase step, read your rows once more and check that every entry says what you actually wrote rather than what you hope is true. If a reason feels thin, you can revise it or drop the row. Leave any uncertain field blank and note it as a question for later, so your sheet stays an honest record of your choices.

Frequently asked questions

What fields can I keep in a small comparison table for my three name candidates?

Consider keeping a small comparison table with four fields: what the second-level label sounds like when spoken once, whether it is easy to spell after hearing it, whether it suggests the illustrator’s work or remains open, and which top-level label you are pairing it with. A possible filled row reads: label “inkandpost,” spoken sound “ink and post,” spelling risk “the joining may be typed as two words,” suggestion “tools and mailing,” top-level pairing “a generic suffix, noted as a candidate for later checking.”

What fields might I use in a small notes table for each candidate and the ending I tried?

You can also keep a small notes table with four fields: candidate, ending tried, spoken impression, and written impression. A filled example might read: “mosslantern — short ending — easy to repeat — looks balanced”; “paperfieldnotes — longer ending — sounds like a heading — feels heavy.”

What should I write down for each row as a short reason about why the address shape suits my project?

For each row, add a short reason in your own words about why that shape still suits the project. A filled example might read: label “mosslantern,” shape “mosslantern” plus a short generic ending, reason “short enough to say at a market stall.”