For first-time website builders, choosing a domain name involves more than just picking a word. You need to know if your desired name is free under common endings like .com or .org. This article clarifies what a domain extension is, how availability works, and provides a simple method to check candidates for your small business service site.
Hypothetical Scenario: Checking 'GreenLeafServices' for Availability
This is a hypothetical situation, not a record of a real business or a completed availability check. A first-time builder imagines a small local service site and writes down three name candidates before touching any registrar search box. The first is GreenLeafServices under a common generic ending such as .com; the second is the same words under a shorter country or generic ending like .net or .org; the third is a slightly adjusted spelling, GreenLeaf-Services, in case the plain form reads awkwardly. The question is not only whether each string differs from the others, but whether one name can sit under several extensions at once and what that would mean for the site address.
Two choices remain open. The builder has not decided whether to reserve only one main address or to hold a matching pair so a common misspelling does not lead elsewhere. They also have not checked whether a hyphen changes how people say and type the name. Before any search, the useful step is to list each candidate as a separate string, extension included, and mark which one would be the primary address if more than one is available. Availability is checked per name under each extension, so an answer for one gives no assurance for another; the hypothetical builder treats each row as its own lookup and leaves the results blank until actually tested.
Understanding Domain Labels and Extensions
A domain name is read from right to left, separated by dots, and each part carries meaning. The top-level domain, or TLD, sits at the far right and tells users the general purpose of the service behind the name. Generic TLDs such as .com, .org, and .net require no particular criteria, while some TLDs enforce stricter policies: local TLDs like .us, .fr, or .se can require a service in a given language or hosted in a certain country, .gov is only for government departments, and .edu is only for educational and academic institutions.1
The labels follow the TLD. A label is a case-insensitive sequence of one to sixty-three characters containing only the letters A through Z, digits, and the hyphen, which may not be first or last. A label may itself be a single letter or a longer string, and a name need not have three labels—informatics.ed.ac.uk is valid. Because each extension is a separate TLD with its own policies, an availability check covers the full name including its TLD, not the label alone.1
You can apply this to your own shortlist by splitting each candidate into two parts: the label before the final dot and the extension after it. For example, write “harborlight” beside “.com” and “harborlight” beside “.net”, then compare the pairs aloud. Consider whether the same label remains easy to spell in each pair, and note any you would drop. If one extension makes the name read like a different word or adds an unwanted pause, you might mark that pairing lower rather than treating every extension as interchangeable.
How to Check Availability Using WHOIS
To check availability, the MDN guide says you can go to a domain name registrar's website, since most of them provide a whois service that tells you whether a domain name is available. As an alternative, if you use a system with a built-in shell, you can type a whois command into it for the name you have in mind.1
The same page shows what such a lookup returns. For an already registered name, the output lists details including the creation date, the registry expiry date, the sponsoring registrar and the registrant organization, which is why that name could not be registered.1
For a name with no matching record, the example output is simply "NOT FOUND," and the page states that because the domain does not exist in the whois database, it could be asked for registration. Run the check on each candidate name and extension before deciding.1
You can treat a WHOIS lookup as a second opinion, not a verdict: it shows registration data, while whether a name is actually purchasable still depends on the registrar you choose. For your own shortlist, note which extensions you checked, the date, and whether each returned “no match” or an existing record. For instance, if one spelling shows a record and another shows none, you might keep both in your notes and mark the second as “worth trying at checkout” rather than “available.”
If a record appears, read its creation date and registrar field before deciding anything. A listing you cannot interpret is still useful as a question to carry to the registrar’s own search page.
The Difference Between Buying and Renting a Domain
MDN states plainly that you cannot buy a domain name. Instead, you pay for the right to use it for one or more years, and you can renew that right; renewal has priority over other people's applications. You never own the name, which lets unused names eventually return to the pool.1
The page explains why this matters for availability: registrars, which use domain name registries, track the technical and administrative information connecting you to your domain. It also notes that for some names a registrar is not in charge — every name under .fire, for example, is managed by Amazon.1
You can take your shortlist and put each name beside the extension you would most like to use, then note which pairing you would actually build the site on. Suppose the label “harborlight” fits your project; write “harborlight” next to one preferred extension and decide whether the other extension is a nice-to-have or a real alternative. If the second pairing is only a fallback, you might keep it on the list but not let it delay your main choice. That single written comparison helps you see whether you are choosing one address or planning two.
Organizing Your Candidate List Before Registration
Start with the plainest version of your own shortlist: one column of names, one column of the endings you would accept, and a third column for the pairing you would actually build on. Take your five favorite names and write each one out twice—once with the ending you want most, once with a fallback. For example, a small repair service might write "maplefix" beside a short familiar ending, and "maplefix" beside a two-letter country ending as a backup. You can then see at a glance which names survive in more than one column and which depend on a single ending.
Consider marking each pair with a simple reason rather than a score. "Reads cleanly aloud," "short enough to say on the phone," and "still matches the service if the ending changes" are the kinds of notes a first-time builder can defend later. A note like "someone else already owns it" belongs in a separate column, because ownership is a fact you look up, not a preference you rank. A hypothetical builder hesitating between two finalists might write: "maplefix.example reads better, but the backup ending version still sounds like the same business—keep both, drop the third name."
You might also test the pairing in a sentence you would actually say: "You can find us at maplefix, spelled m-a-p-l-e-f-i-x." If the name needs spelling out twice for a listener to catch it, that is a reason to move it down your list, not to discard it outright. Whether you keep one pairing or a matching pair for a common misspelling remains your choice; the list only makes the trade-off visible before you commit to any lookup.
Common Misconceptions About Domain Uniqueness
A common misconception is that a name is either “taken” or “free” everywhere. The documented TLD material does not describe a single global availability rule spanning extensions. It explains that a TLD is the final component of a domain name, such as “org” in developer.mozilla.org, and that ICANN designates organizations to manage each TLD.2
That source also says an administrating organization may be strict, and that a TLD often serves as a clue to a website’s purpose, ownership, or nationality. So the name before the final dot and the extension after it are separate parts; the page does not say a result for one extension settles another.2
For a name you are seriously considering, you can apply one more reading pass to your own shortlist. Take a single pair, say a short service label ending in one common extension, and write it beside the same label with a country-code extension. Then ask yourself which version you would say out loud to a customer, and whether the other would cause confusion if both later pointed to different sites.
You might also note what you would do if the second extension turns out to be unavailable after you have chosen the first. Neither choice is required; the point is to decide now whether you would change the name or accept a mismatched pair. Write the reason in your own words, so a later reread shows whether your preference still holds.
Frequently asked questions
How can I reorganize my shortlist by splitting each name into its label and extension?
You can apply this to your own shortlist by splitting each candidate into two parts: the label before the final dot and the extension after it. For example, write “harborlight” beside “.com” and “harborlight” beside “.net”, then compare the pairs aloud.
How can I note which name-and-extension pairing I would actually build my site on?
You can take your shortlist and put each name beside the extension you would most like to use, then note which pairing you would actually build the site on. Suppose the label “harborlight” fits your project; write “harborlight” next to one preferred extension and decide whether the other extension is a nice-to-have or a real alternative.
How should I annotate each shortlisted name pair with a simple reason instead of a score?
Consider marking each pair with a simple reason rather than a score. "Reads cleanly aloud," "short enough to say on the phone," and "still matches the service if the ending changes" are the kinds of notes a first-time builder can defend later.