Startups often struggle to find a domain that is both available and aligned with their brand identity. This article outlines practical steps for generating name candidates, checking their real-time availability through standard registration platforms, and verifying the final status of a registered domain to ensure it meets business needs.

Defining Your Startup's Naming Criteria

Imagine a founder drafting a naming brief before checking any registrar. Their raw material: a one-page product sketch, two customer interview notes, and a short list of words the team keeps repeating. From these they write three candidates: Fieldnote, Bramble Ledger, and Quiet Atlas. Fieldnote suggests a record-keeping tool; Bramble Ledger hints at thorny accounting work; Quiet Atlas implies calm navigation of complex data. The founder sorts each into two columns, clear-fit and stretch-fit, and notes which word carries the meaning if the rest were removed.

Next they turn the brief into a small comparison sheet, still as an illustration rather than tested policy. Columns: proposed name, spoken form, written form, likely misspelling, and the meaning a stranger might guess. Two example rows show how the sheet works. Row one: "Fieldnote, said as two equal beats, written as one word, often mistyped as Feildnote, guessed as a note-taking app." Row two: "Quiet Atlas, said with stress on Qui-, written as two words, sometimes mistyped as Quite Atlas, guessed as a mapping or research service." The founder marks which misspellings would still resolve to the same idea and which would send a visitor somewhere unrelated.

Then comes a deliberate trade-off. Fieldnote is easy to say but generic enough that the founder worries it will disappear in search results. Quiet Atlas is more distinctive but longer to type. They choose to keep Fieldnote for the working brief and set Quiet Atlas aside as a backup, reasoning that early users will mostly arrive through a direct link or a shared message rather than a typed guess. This is the founder's own judgment, not a finding from user research.

Finally they fix the channels for each link example so the destination is unambiguous. The launch note goes to a project page at the example host startup-demo.test, path /fieldnote, with the link shared in a team chat and repeated in a one-page handout. A press-style mention points to the same host, path /about, and appears only in an email signature. Writing the host and path separately keeps the record readable and avoids implying that any outside service has accepted or reserved these names.

Generating and Filtering Domain Name Candidates

You can take your own naming brief and turn it into a shortlist you actually trust. Start by writing down five or six candidate names beside the words your customers already use, then say each one aloud twice. A name that you stumble over on the second try is worth marking down, even if it looks tidy on paper.

Next, build a small comparison sheet for yourself. Useful columns might be: proposed name, spoken form, written form, a likely misspelling, whether the spelling stays obvious when heard once, and a column for your own fit note. Filled in as an illustration: "Fieldnote" reads plainly and is easy to spell from hearing it; "Quiet Atlas" sounds distinctive but invites the question of whether it is one word or two. Your notes can stay rough; the point is to compare candidates on the same lines rather than by feel alone.

Then sort the shortlist into two piles: names you would defend in a customer conversation, and names you would quietly retire. You might keep three in the first pile and let the rest go. When two names feel close, consider which one leaves room for the products you plan to add later, and which one you would still be comfortable saying a year from now.

Last, before you settle, check each remaining candidate against your own brief rather than against outside approval. You can ask whether the spelling survives being spoken once, whether the written form matches how you say it, and whether the name points at your actual product rather than at a category. Keep the sheet with your brief so the reasons behind each choice stay visible when you revisit it.

Checking Real-Time Availability via Registration Platforms

On a registration platform, the first step is to enter the candidate domain in the search box and click to query it. The result page then indicates availability: a “register now” button appears when the domain can be registered, while a domain already held by someone else may still be listed as purchasable if it is for sale.1

One platform also offers a bulk query page. There, you enter domains one per line, up to 1,000, choose among more than 60 suffixes, and start the query to see the registrable status of those domains. Spelling must follow the naming rules, which cover permitted characters, length limits, and hyphen placement.1

Take your shortlist and check each remaining candidate on a registrar's search page yourself, one name at a time. You can open the page, type the exact spelling you wrote in your comparison sheet, and read the result for the suffix you actually want rather than the first offer shown. If a name comes back taken, note it beside the entry and consider whether a variant spelling still matches what customers would say aloud.

For each result, record what you saw and the date in the same sheet: proposed name, suffix checked, status shown, and any premium price flagged. Filling a sample row might look like this: Fieldnote, .com, taken, no price shown. That single row lets you compare later without relying on memory, and you can repeat it for every candidate before narrowing further.

You might also check the other suffixes on your list separately, since a name free in one ending can be held in another. Keep those rows distinct so the sheet shows which spelling and which ending you would actually pursue.

Understanding Status Codes After Registration

Status codes appear in WHOIS results, and a domain can carry several at once. Codes beginning with “client” are set by the registrar; those beginning with “server” are set by the registry. Use the published code explanations to read what each one means and what action is suggested.2

Some codes describe normal states rather than faults. “ok” is the basic healthy state and is typically hidden when other statuses are attached, so its absence does not mean the domain is unusable. “clientTransferProhibited” is described as a normal security state that blocks transfer to another registrar; it must be turned off before a transfer. The same source notes that some newly registered or recently transferred domains are locked against transfer by the registry for 60 days, after which the lock lifts automatically.2

Other codes need attention. “clientHold” means the registrar has suspended resolution and the domain cannot be accessed; the cause must be checked and the registrar contacted. “inactive” usually means no valid DNS servers were entered at registration, and DNS server addresses must be set in the domain console before the domain can resolve. “pendingVerification” means owner verification is incomplete and must be submitted within five days of registration, after which the domain is placed on serverHold and resolution is paused.2

If a checked result shows a status you do not recognize, you can record the exact wording in your sheet and leave the interpretation open until you have read the registry or registrar explanation yourself. A practical field to add is: status shown, plain-language guess, and what would change your plan. For example, one row might read “registered, renewal unknown, would drop if the name reads as generic”; a second row might read “premium price flagged, would shorten by one syllable if cost stays high.” These are illustration values, not verdicts.

When you compare current and archived notices for the same name, you can use the same fields twice and note the date beside each entry. A current entry and an archived entry may show different status wording; noting both lets you see what shifted without assuming why. You might mark the archived row “context only” and keep your decision tied to the current row.

You can also separate suffixes into their own rows so a free ending does not mask a held one. Before committing, revisit the shortlist and ask whether a status label changes your brand-fit judgment or only your timing.

Verifying DNS Configuration and Access Readiness

A WHOIS lookup is the practical next check for access readiness. The Name Server field shows the domain's current DNS servers; if a site is unreachable, the documented step is to verify that the DNS server addresses listed there are configured correctly, and the page points to modifying DNS servers where changes are needed.2

Domain status also matters for access. A domain in ok status is usable and unlocked, though ok is hidden when other statuses apply. A domain showing inactive has no valid DNS servers set at registration and must have correct DNS server addresses configured in the domain console, otherwise it will not resolve. Status codes beginning with client are set by the registrar; those beginning with server are set by the registry. For statuses you don't recognize, the source provides a status-code reference rather than one fixed interpretation.2

Before you move from a shortlisted name to planning a launch, you can prepare a small readiness note that records what you still need to confirm, rather than assuming it is already in place. Use the same comparison sheet you have been building, and add four columns: access I control, DNS record to change, where the change is made, and a status column you fill only after you have seen the result yourself. Leave the status column empty for now; this note is a plan, not evidence.

For a sample entry, you might write the proposed name Fieldnote with suffix example, access listed as the account you expect to hold, the record described as a single web address entry, the place noted as wherever that account manages settings, and status marked as not yet checked. A second entry could be for the same name in another suffix, kept as its own row so one ending does not hide the other.

You can also write two plain sentences for your own reference: one describing what a correct setting would look like, and one describing what you would do if the account access turns out to belong to someone else. Deciding those in advance keeps the choice yours when you get there.

Final Checklist for Brand Fit and Operational Security

Take the shortlist you have already narrowed and give it one last pass against your own brand brief, not against outside approval. You can reread each candidate beside the three or four phrases your customers actually use, and note whether the name sounds like something a customer would repeat or something you would have to explain. This is a judgment call you make, not a score anyone else assigns.

For the operational side, you might prepare a short readiness note for each name that survives that pass, listing only what you still need to confirm rather than what you have already done. Useful fields could include: proposed name (Fieldnote), suffix to check (example), the account you expect to hold it, the record type you anticipate, and one sentence on what a correct setting would look like to you. Fill one row as a sample, then leave the rest for later.

You can also write two plain sentences in your own words for each row: one describing the healthy state you would recognize, and one describing what you would do if the status or record looks different from that. These are notes to yourself, not commitments, and you might revise them once you know more.

Before you treat any candidate as settled, reread your brief one more time and ask whether the name still fits the words your customers use, or whether it only fits the words you like. You can set aside any name that fails that question and keep the rest, deciding later which suffix and path to pursue. The checklist is yours to keep, fill, and change as your own judgment develops.

Frequently asked questions

How can I turn my own naming brief into a shortlist I trust?

You can take your own naming brief and turn it into a shortlist you actually trust. Start by writing down five or six candidate names beside the words your customers already use, then say each one aloud twice.

What columns might I include in a small comparison sheet for myself?

Next, build a small comparison sheet for yourself. Useful columns might be: proposed name, spoken form, written form, a likely misspelling, whether the spelling stays obvious when heard once, and a column for your own fit note.

How can I sort my shortlist into two piles?

Then sort the shortlist into two piles: names you would defend in a customer conversation, and names you would quietly retire. You might keep three in the first pile and let the rest go.