Learn how to choose the right domain extension and craft a memorable name for your online presence.
Defining Your Brand's Digital Identity
This is a hypothetical scenario: an independent ceramics studio, run by one potter, is preparing a small website and a short printed catalogue. The potter’s working notes are the only material here. The notes contain three name variants, three suffix options, and one sample directory entry for the catalogue, all invented for this example.
The name variants are “Kiln & Co.,” “Kiln and Company,” and “Kilnhouse Ceramics.” The first reads smoothly in a logo, the second is the unambiguous version for print and legal text, and the third is the most distinctive spoken aloud. A reasonable choice is to lead with “Kilnhouse Ceramics” and treat “Kiln & Co.” as a secondary label. The reason is practical: the ampersand invites spelling variants in handwritten notes and spoken introductions, while the single compound word gives a customer one obvious thing to type. The potter writes the chosen form on the catalogue cover and keeps the shorter label for a stamp on the base of each piece, so the two are visibly related but not interchangeable.
For suffixes, the notes list three candidates: a country-code suffix, a generic short suffix, and a longer descriptive suffix. The potter narrows this by deciding where most customers will come from. If nearly all sales are local, the country-code suffix reinforces place and is easy to say in the studio. If the plan includes shipping elsewhere, the generic short suffix reads as neutral and is less likely to be mistaken for a geographic restriction. The longer descriptive suffix is kept only as a fallback because it adds characters to every spoken mention. One example trade-off: the country-code version is shorter to dictate, but the generic version is easier to explain to a customer who is not local. The potter chooses the generic option for the main address and reserves the country-code option for a later redirect if local traffic becomes the clear majority.
The catalogue’s studio directory entry shows how the notes are meant to be used rather than merely discussed. Three columns are planned: Display name, Spoken form, and Address role. Two invented records appear as follows. First record: Display name “Kilnhouse Ceramics”; Spoken form “Kilnhouse Ceramics, one word, then ceramics”; Address role “main site address.” Second record: Display name “Kiln & Co. (studio stamp)”; Spoken form “Kiln and Company”; Address role “redirect to main.” The first record is the public name, the second is the shorthand that appears on packaging and correspondence.
The notes also settle how the address is written and where each link points. The main address is recorded in full with its protocol, host, and path, and the redirect address is recorded separately, so the catalogue never mixes the two. The potter adds a line stating that the spelling “Kilnhouse” is this studio’s own record and is not a claim about what any registration or search field will accept. These are working examples, not results from a completed trial.
Understanding Top-Level Domain Options
The cited official guide describes a domain as two parts: a prefix (SLD) that is the customizable name, and a suffix (TLD) such as .com, .net, .org, or .co. It states that the registrar supports registration of hundreds of top-level domains, covering generic, country-code, and new TLDs.1
On suffix choice, the guide calls .com the most general option. If .com is already registered, it suggests considering .net, .co, or industry-specific suffixes such as .tech and .app. It also notes that some country-code domains may have special registration requirements and advises checking the prompts on the query page before registering.1
For the potter’s three candidates, the guide supplies background rather than a decision: a country-code suffix may carry extra requirements, a generic short suffix fits the .com/.net/.co examples, and the longer descriptive option aligns with the industry-specific suffix category the guide mentions.1
For the suffix comparison, you can take the three candidates already in the potter’s notes and score them against written-down priorities rather than gut feeling. A simple author example is a five-row table with these fields: Candidate suffix, Best fit reason, Main worry, Pairing name, Choice status. One filled row might read: country-code suffix, signals where the studio is based, may confuse buyers ordering from elsewhere, paired with “Kilnhouse Ceramics,” hold. Another: generic short suffix, easy to say aloud, less specific to the craft, paired with “Kiln & Co.,” shortlist. Another: longer descriptive suffix, spells out the trade, makes the full address long for print, paired with “Kiln and Company,” hold. The potter can adjust any row as the catalogue text firms up.
You might also record the spoken form beside each written form, since a name that survives being said over the phone is worth more than one that only looks tidy on paper. A filled line could read: written “Kilnhouse Ceramics,” spoken “Kiln House Ceramics,” likely misspelling “Kilnhouse,” decision: keep as fallback. Doing this for each candidate makes the weak ones obvious before anything is printed.
Once a candidate moves from hold to shortlist, the notes should say what happens next, and this is where you can keep current and archived entries on the same fields. For a current entry, Choice status reads “shortlist” or “selected,” and the field for where it is used names the live site and the catalogue. For an archived entry, the same fields are reused, but Choice status reads “retired” and the usage field names the old catalogue edition only, so a reader can tell at a glance that the address is no longer the main one. You can decide which of these two states applies before filling anything in.
The point of the exercise is not to produce a perfect grid. It is to leave yourself a record you can read in a month and still understand why one suffix was kept and another set aside.
Brainstorming Memorable Name Candidates
Use NamesLink to check whether each candidate name you wrote down is actually available: enter the name in the search box on the homepage, and the results show the registration status for each suffix, so you can see whether your preferred suffix is still open. If your first choice is taken, the same results offer similar names that remain available. You can then compare those against the suffixes you are considering before deciding which name-and-suffix pair to register.1
Checking Availability Across Suffixes
According to the cited official guide, availability checking starts on the homepage: enter the desired domain name, such as mybrand, in the search box. The system then shows the registration status for each suffix under that name. The guide defines two statuses: available, meaning the domain has not yet been registered and can be purchased immediately; and registered, meaning another party holds it, in which case you can view Whois information or try to contact the holder about a purchase.1
The guide adds that if the preferred domain is already registered, the provider recommends similar available domains. It also notes that certain country-code domains may carry special registration requirements, which should be checked in the prompts on the query page before registering.1
You can extend the potter’s suffix notes into a working comparison without deciding anything yet. Take the three candidates already listed and, for each one, write a single line under a heading such as “Availability check — date.” Record what was consulted, what was found, and whether the candidate stays on the list, moves to a hold pile, or is struck out. Keeping the date beside each line matters more than it seems: the same written form may read differently once a catalogue deadline approaches, and a dated note lets you see what you knew when you chose.
For a filled-in example, the potter might write: “Variant — Kilnhouse Ceramics; suffix — short generic; checked — wide search plus two registry lookups; result — clean written form, but spoken form blurs with an existing garden centre; outcome — hold.” A second line could read: “Variant — Kiln & Co.; suffix — country-code; checked — registry lookup only; result — unfamiliar abroad, familiar locally; outcome — shortlist, pending print test.” A third: “Variant — Kiln and Company; suffix — longer descriptive; result — unambiguous when spoken, long in a logo; outcome — shortlist for the catalogue footer only.” These are illustrative values, not findings.
You might also give each entry a “next action” field with a concrete date, for instance “review before the printer’s deadline” or “ask two people to spell it back.” That field turns a loose preference into something you can act on later, and it keeps the comparison honest when one suffix is familiar and another merely sounds distinctive.
Before closing the notes, read each line as if a month had passed. If a line still explains why the candidate was kept, held, or dropped, the comparison is doing its job; if it only records a feeling, add the reason beside it. You can choose how many candidates to carry forward, but a dated record of each decision is what makes the shortlist usable when the catalogue and site work begin.
Evaluating Industry-Specific Extensions
The cited official guide lists sample generic and industry-specific suffixes: .com, .net, .co, and industry-specific options such as .tech and .app. It presents .com as the most general choice and suggests considering .net, .co, or an industry-specific suffix if .com is already registered. Keep this as guidance rather than a ranking.1
The guide also notes that some country-code domains may have special registration requirements and recommends checking the prompts on the query page before registering. After searching a name, the results show the registration status for each suffix, distinguishing available from already registered. These prompts are where the documented suffix note points next.1
You can start by revisiting the potter’s suffix notes and adding one question beside each of the three candidates: “does this suffix still make sense if the studio sells to a shop rather than a visitor?” That question is about positioning, not about any technical claim. Write the answer in the potter’s own words, even if it is a guess, then date it.
For the ceramic studio, a filled example might read: “Suffix candidate — short generic; kept because the printed catalogue lists shops as buyers; dropped reason — none yet; next action — ask the two stockists how they would say it aloud, before the catalogue deadline.” Another line could read: “Suffix candidate — country code; held because the notes show both local and mail-order buyers; next action — decide after the first wholesale enquiry is answered.”
You might also add a column for how the suffix sits with the display name. The potter can write the name and suffix together once, then read it aloud and note whether the pairing feels like a studio or like a directory entry. A short note such as “reads tidy in print, awkward in speech” is enough; you do not need a score.
If the potter later moves one candidate from hold to shortlist, keep the earlier line rather than deleting it. Add a second line with a new date and the reason for the move, such as “promoted after stockist reply; kept the spoken-form note.” That way the notes stay readable in a month.
None of this commits the potter to a suffix yet. It simply leaves a trace of the reasoning, so the eventual choice can be explained to a printer, a stockist, or a future collaborator without reconstructing it from memory.
Finalizing Registration Details
The cited official guide walks through purchase as its own step: in the query results, you click the register button beside the target domain, choose a registration period of one to ten years, and settle the domain holder information template. If you do not select a contact template, the default template generated from your account information at sign-up is used, and you can add a template and change which one is default.1
The guide states that ICANN rules require registration details to be genuine and valid, listing holder name or organization name, email address, phone number, and full address with country, region, city, street, and postal code. It adds that privacy protection is switched on automatically to hide personal information.1
Order confirmation comes next: check the domain list, registration years, holder information, and add-on services, then pay. The wallet balance is deducted automatically when sufficient; otherwise the page directs you to top up first. After payment, the guide says registration usually completes and takes effect within minutes to 24 hours.1
You can turn the potter’s draft directory entry into a registration worksheet before the first line of the catalogue is typeset. Start with the display name already in the notes, “Kilnhouse Ceramics,” and add four fields beside it: suffix candidate, written address, spoken form, and next action. For the short generic suffix, the row might read: display name — Kilnhouse Ceramics; written address — kilnhouse with the chosen suffix; spoken form — “kiln house”; next action — review before the printer’s deadline. You might fill a second row for the country-code option using the same four fields, changing only the suffix and keeping the display name fixed so the comparison stays honest.
The potter can then read each row aloud and note where the spoken form drifts. If “Kilnhouse” is heard as “Kill House,” that belongs in the row rather than in a separate memory. You could add a short “why kept” note under each candidate, written in plain words the printer or a stockist would understand. A filled example might say: short generic suffix — kept because the catalogue names shops as buyers and the address reads cleanly in print; country-code suffix — held until the studio decides whether local identity matters more than brevity.
When one candidate moves from held to shortlist, keep the earlier row and add a dated line beneath it explaining the shift. This is the same field set used for an archived entry: display name, suffix, written and spoken forms, decision, and date. For an archived name the potter has dropped, the decision field reads “dropped” with the reason, while a current entry reads “shortlist” or “hold.” You can choose how many rows to keep, but leaving the old ones intact gives a record you can still follow later.
Frequently asked questions
How can I turn the potter's suffix notes into a working comparison without choosing anything yet?
You can extend the potter’s suffix notes into a working comparison without deciding anything yet. Take the three candidates already listed and, for each one, write a single line under a heading such as “Availability check — date.”
How should I record the spoken form next to each written name?
You might also record the spoken form beside each written form, since a name that survives being said over the phone is worth more than one that only looks tidy on paper. A filled line could read: written “Kilnhouse Ceramics,” spoken “Kiln House Ceramics,” likely misspelling “Kilnhouse,” decision: keep as fallback.
How can I check that my comparison entries still explain my decisions a month later?
Before closing the notes, read each line as if a month had passed. If a line still explains why the candidate was kept, held, or dropped, the comparison is doing its job; if it only records a feeling, add the reason beside it.