# How to Choose a Domain Name for Your Business: A Practical Guide

> Learn how to choose a domain name for your business by testing brand clarity, trademark risk, domain endings, renewal costs, and long-term control.

- Canonical: https://zeroraised.com/blog/how-to-choose-a-domain-name-for-your-business
- Published: 2026-10-18
- Updated: 2026-10-18
- Author: ZeroRaised Team (https://zeroraised.com/blog/authors/zeroraised)
- Publisher: ZeroRaised (https://zeroraised.com/)
- Section: Growth
- Tags: domain-names, branding, business-launch

To learn **how to choose a domain name for your business**, start with a legally clear business name that customers can hear, spell, and remember, then select the extension by audience, rules, renewal cost, and long-term control. Do not buy an awkward name merely to fit a preferred ending: Google says new generic top-level domains receive no search advantage from keywords in the extension, while ICANN says registration terms, fees, transfers, and renewals are governed by your registrar agreement ([Google Search Central](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level) and [ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en), checked 18 Oct 2026).

**Disclosure:** [ZeroRaised](https://zeroraised.com/) publishes this guide. It is a launch and discovery site for bootstrapped indie makers with no institutional VC or accelerator equity. This article gives an editorial selection process, not legal advice or a promise that a domain will rank, convert, or avoid a dispute.

## TL;DR

| Decision | Default choice | Choose differently when | Check before paying | First-party source |
|---|---|---|---|---|
| Business name | A distinctive name that is easy to say, spell, and connect with the offer | A descriptive modifier makes an unfamiliar brand clearer without trapping the business in one feature | Similar trademarks and real commercial uses, not just the exact string | [USPTO clearance-search guidance](https://www.uspto.gov/trademarks/search/comprehensive-clearance-search-similar-trademarks), checked 18 Oct 2026 |
| Extension | `.com` when the clean exact name is available at a price the business can justify | A relevant generic extension reads naturally, or a country-code domain matches a deliberately local market | Registry operator, eligibility rules, renewal price, premium classification, transfer support, and geographic implications | [IANA Root Zone Database](https://www.iana.org/domains/root/db) and [Google international-site guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026 |
| Search considerations | Choose for human clarity and brand fit | A country-specific site intentionally needs a strong country signal | Google treats new generic extensions like other generic extensions and says a keyword in the ending adds no ranking advantage | [Google on new top-level domains](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level), checked 18 Oct 2026 |
| Price | Compare the full holding cost, including renewal and transfer | A genuinely valuable premium name has a documented business case and capped budget | Introductory price, standard renewal, premium renewal, transfer charge, taxes, and add-ons | [ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en) and [Porkbun pricing definitions](https://porkbun.com/products/domains/pricing), checked 18 Oct 2026 |
| Control | Register through a business-controlled account with current recovery details, multistep authentication, lock, and auto-renewal | More sensitive domains justify extra approval controls or registry-lock options | Legal registrant, account owner, recovery route, payment method, expiration date, DNS access, and transfer code process | [ICANN account-protection guidance](https://www.icann.org/news/blog/do-you-have-a-domain-name-here-s-what-you-need-to-know-part-4) and [ICANN renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026 |

The short version is to eliminate names that fail any non-negotiable test before comparing style. A memorable name is not useful if another company has a confusingly similar mark for related services, the extension has eligibility terms you cannot maintain, or one former contractor controls renewal.

## How to choose a domain name for your business in 10 steps

Use these steps in order. The first five reduce naming and legal risk; the last five reduce cost, technical, and continuity risk.

1. Write the customer, offer, market, and likely expansion in one paragraph.
2. Generate business names before searching extensions.
3. Remove candidates that fail the spoken and typed tests.
4. Search similar trademarks, businesses, products, and domains.
5. Choose the type of extension that fits the market.
6. Verify the registry and registrar terms.
7. Compare the full holding cost, not the first-year banner.
8. Test email, international, and visual-confusion cases.
9. Put registration and recovery under business control.
10. Record the decision and launch with a migration plan.

The rest of this guide turns each step into a check you can complete. Treat the result as a business asset decision, not a naming contest.

## First, define what the domain has to carry

Before making a list, write four facts:

- **Customer:** who needs to understand and type the name?
- **Offer:** what category or job should the name suggest, if any?
- **Market:** is the business local to one country, regional, or intended for several countries?
- **Expansion:** which adjacent products, locations, or customer groups are plausible?

This is ZeroRaised editorial advice. It prevents the extension from deciding the company strategy by accident. A country-code domain may be a useful signal for a business focused on that country, but Google says most country-code top-level domains are a strong country signal. Google separately lists several repurposed country codes, including `.ai`, `.co`, `.io`, `.me`, and `.tv`, that it treats as generic for Search; Google notes that this list can change ([Google international-site guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026).

The expansion question matters because a narrow product word can age faster than a broader brand. Do not predict every future feature. Ask only whether the candidate would become misleading after one realistic next move. Compare distinctive names, familiar words, two-word compounds, brand-plus-modifier forms, and descriptive phrases by the same brief. These are editorial patterns, not legal categories.

## A dated warning from the `.name` discussion

**Recent hook, 14 Oct 2026:** a Hacker News post titled “Tell HN: Remember to migrate away from .name domain” warned holders of third-level `.name` registrations about the service's planned removal and asked whether people would move to `.com` or take another chance on an alternative extension. When rechecked on 18 Oct 2026, the post showed 149 points and 90 comments. Those counts describe that one thread, not general market sentiment ([Hacker News thread](https://news.ycombinator.com/item?id=50089577), checked 18 Oct 2026).

The underlying change is documented outside the discussion. Verisign asked ICANN to approve removal of third-level `.name` registrations, and ICANN's published approval requires Verisign to give supporting registrars at least 90 days' notice, another reminder at least 30 days before discontinuation, and customer-service support through the process. ICANN notes that registrars manage communications with their registrants ([ICANN approval letter](https://itp.cdn.icann.org/en/files/consensus-policies/fessenden-to-kane-2-28-07-2026-en.pdf), checked 18 Oct 2026). The older `.name` agreement explicitly allowed registrations in forms such as `string.string.name`, which is different from a business controlling a normal subdomain under a second-level registration it holds ([ICANN `.name` registration restrictions](https://www.icann.org/en/about/agreements/registries/name/appendix-11-25mar11-en.htm), checked 18 Oct 2026).

The useful lesson is not “all alternatives are unsafe.” Every top-level domain has an operator, policies, and a place in the DNS root. The lesson is to identify what you are actually registering, who operates the suffix, which agreement controls it, and whether the business can move if the rules change. IANA's Root Zone Database publishes the delegation details and registry information for top-level domains, while ICANN explains that registries maintain each top-level-domain database and registrars sell registrations under agreements with registrants ([IANA Root Zone Database](https://www.iana.org/domains/root/db) and [ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en), checked 18 Oct 2026).

This distinction also prevents a common terminology error. In `shop.example.com`, `example.com` is normally the registered name and `shop` is a subdomain controlled through its DNS. In a public-suffix structure such as `example.co.uk`, the registrable part spans the label immediately before `co.uk`; the Public Suffix List describes public suffixes as the part not controlled by the individual registrant and names `com` and `co.uk` as examples ([Public Suffix List](https://publicsuffix.org/list), checked 18 Oct 2026).

## Step 1: build a name brief before checking availability

Write a one-page brief naming the primary customer, core offer, geographic scope, two useful brand qualities, meanings to avoid, nearest plausible expansion, maximum purchase price, and maximum acceptable renewal. Separating purchase and renewal matters because registrar offers and recurring terms can differ. ICANN says fees and renewals are governed by the registrar agreement and advises registrants to read those options and terms carefully ([ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en) and [ICANN renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026).

Generate names without opening a registrar search for the first round. Availability grids encourage tiny spelling changes that may make a name harder to say or too close to an existing brand. Produce a short list that fits the brief, then investigate it.

## Step 2: run the spoken, typed, and memory tests

Give each candidate to several people who resemble the intended customer, one at a time. Do not show the spelling first.

1. Say the complete domain once.
2. Ask the person to write it.
3. Ask what they think the business does.
4. After discussing other topics, ask them to recall it.
5. Show the written domain and ask how they would pronounce it.

This is ZeroRaised editorial testing, not a statistical study. Record the errors rather than turning a handful of responses into a percentage. Repeated omission of a modifier, confusion between singular and plural, or disagreement about where words divide is more useful than a generic score.

Challenge the name as an email address, lowercase text, a browser tab, a phone mention, a support exchange, and a plain-text invoice. Include non-native speakers when they are part of the audience.

Avoid treating shortness as the only goal. A slightly longer domain that has one obvious spelling can be easier to transmit than a compact invented string with several plausible spellings. That is an editorial judgment you can test with the exercise above.

Hyphens and digits are not automatically invalid, but demand a reason. Ask whether people will say “hyphen,” whether a spoken number will be typed as a digit or a word, and whether the punctuation creates a lookalike for another business. Remove a candidate when explanation becomes part of every introduction.

## Step 3: clear the name before you become attached to it

Domain availability is a technical result, not legal clearance. The USPTO says registering a domain does not prevent a later requirement to surrender it if it infringes someone else's trademark rights. It recommends searching federal records plus state trademark and business registries, the internet, and other sources for confusingly similar marks used with related goods or services ([USPTO trademark process](https://www.uspto.gov/trademarks/basics/trademark-process) and [USPTO comprehensive clearance search](https://www.uspto.gov/trademarks/search/comprehensive-clearance-search-similar-trademarks), checked 18 Oct 2026).

For every surviving candidate, search:

- the exact name and close spellings;
- joined and separated versions of compound words;
- phonetic equivalents and likely misspellings;
- the name with the product category;
- trademark databases in every jurisdiction that matters;
- company and business-name registers where the business will operate;
- app stores, software directories, and major social platforms used by the intended customers;
- the exact domain and nearby variants in ICANN's registration-data lookup where applicable.

The search categories are editorial process. The legal standard and appropriate jurisdictions depend on the business. The USPTO says a comprehensive U.S. clearance search includes similar marks and common-law use, not only exact federal registrations; ICANN provides an RDAP-based lookup for publicly available domain registration data ([USPTO clearance guidance](https://www.uspto.gov/trademarks/search/comprehensive-clearance-search-similar-trademarks) and [ICANN Lookup](https://lookup.icann.org/), checked 18 Oct 2026).

Create an evidence log with the query, source, date, result, and unresolved question. A clear search result is not a legal opinion. Pay for qualified trademark advice when the name is central to the business, the category is crowded, the launch crosses jurisdictions, or a similar mark appears for related goods or services.

ICANN's Uniform Domain-Name Dispute-Resolution Policy matters after registration too. It provides an administrative route for trademark holders alleging abusive domain registrations to seek transfer or cancellation through an approved provider ([ICANN UDRP](https://www.icann.org/dndr/udrp), checked 18 Oct 2026). Do not register a close version of a known brand as a shortcut to attention.

## Step 4: choose the extension by market and rules

The part after the final dot is not a decoration. It can carry geographic meaning, technical requirements, eligibility conditions, and a separate price schedule. Use this comparison as a decision guide, then verify the specific suffix in IANA and on the registry's own site.

| Extension route | Good fit when | Main benefit | Risk to verify | Named example |
|---|---|---|---|---|
| `.com` | The clean brand match is available or reasonably acquirable and the business wants a general-purpose global address | It does not impose a country target and leaves the brand before the dot intact | Purchase price, confusing neighbors, premium status, and whether a modifier is clearer than an expensive exact match | [Gumroad](https://gumroad.com/) uses `gumroad.com`; Google classifies `.com` as generic in its [international-site guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), both checked 18 Oct 2026 |
| New generic extension such as `.app` | The full phrase reads naturally and the registry requirements fit the product | The ending can communicate context without changing the brand label | Registry policy, renewal price, audience comprehension, and technical requirements; `.app` requires HTTPS in browsers | [Linear](https://linear.app/about) uses `linear.app`; [Google Registry](https://registry.google/policies/registration/app) documents the `.app` HTTPS requirement, both checked 18 Oct 2026 |
| Country-code domain | The business deliberately serves one country or needs a local namespace | A country code can signal geographic focus | Local-presence rules, registry dispute policy, transfer process, and whether future expansion needs separate sites | Google says most ccTLDs are a strong country signal in [its international-site guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026 |
| Repurposed country code such as `.ai`, `.co`, or `.io` | The intended audience already reads it generically and the business accepts the country registry's rules | A concise brand match may be available | Registry jurisdiction and policy, renewal pricing, customer interpretation, and future changes | Google currently lists `.ai`, `.co`, and `.io` among ccTLDs it treats as generic for Search in [its current documentation](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026 |
| Multi-label public suffix such as `.co.uk` | The business wants the recognized registration structure for that market | It can align the domain with an established local namespace | Confirm which label is registrable, the eligibility terms, and who controls each label | The [Public Suffix List](https://publicsuffix.org/list) identifies `co.uk` as a public suffix, checked 18 Oct 2026 |

`.com` is the practical default in this guide when it is clean and affordable, not because Google gives it a ranking bonus. Google says new generic TLDs are treated like established generic TLDs such as `.com` and `.org`, and a keyword in the ending creates neither an advantage nor a disadvantage in Search ([Google Search Central](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level), checked 18 Oct 2026).

That removes one bad reason to buy a name. Do not choose `brand.keyword` because someone promises the ending will rank the site. Choose it only when the complete address is clear to users and the registry, renewal, and operating terms work.

For an internationalized domain name, test both the local-script display and its encoded form in every important system. Google says it treats an IDN hostname's Punycode version as equivalent to the unencoded version for crawling and indexing ([Google Search Central](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level), checked 18 Oct 2026). ICANN explains that IDNs can contain Latin letters with diacritics or characters from scripts such as Arabic and Chinese ([ICANN on IDNs](https://www.icann.org/news/multimedia/3563), checked 18 Oct 2026). The product decision is whether customers, staff, email systems, and support workflows can use the chosen form reliably.

## Step 5: understand what is available and what is for sale

A registrar result may represent a standard registration, a registry-designated premium name, an aftermarket listing from a current registrant, or a registered name with no supported sale route. Verify registration, renewal, transfer, eligibility, included privacy, and add-on costs for the first case. For a premium name, determine whether renewals and transfers stay premium. For an aftermarket name, verify seller control, payment protection, transfer timing, disputes, and the renewal after transfer. Namecheap's own guidance confirms that some premium names carry higher renewal and transfer costs, not only a higher purchase price ([Namecheap premium-domain guidance](https://www.namecheap.com/support/knowledgebase/article.aspx/9990/35/how-to-get-a-premium-domain/), checked 18 Oct 2026).

Use [ICANN Lookup](https://lookup.icann.org/) to identify the registrar and inspect available public data for an existing generic domain. Privacy redaction can limit the contact details shown, so do not treat a hidden name as evidence of abandonment. Set a maximum price from the domain's specific value and the cost of an acceptable alternative, not the seller's demand. ICANN says the registrant receives rights for a registration term under the registrar agreement rather than buying a domain forever ([ICANN renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026).

Buffer offers a useful real example of sequencing. Its team says the product began at `bfffr.com`, moved to `bufferapp.com`, and later acquired `buffer.com` after the company was established ([Buffer's account of acquiring Buffer.com](https://buffer.com/resources/acquired-buffer-com/), checked 18 Oct 2026). It is one company history, not proof that every business should buy its exact `.com` later. It shows that a clear modifier can keep a launch moving while an exact domain remains a separate decision.

## Step 6: compare the full cost of keeping the domain

For each finalist, collect a written quote or screenshot for:

1. first-year registration or purchase price;
2. standard renewal price;
3. premium renewal price, if applicable;
4. transfer-in and transfer-out terms;
5. restoration fee after expiration;
6. privacy or proxy service;
7. DNS, DNSSEC, email forwarding, and certificate add-ons;
8. taxes and registry or ICANN fees;
9. the price for any defensive variants you genuinely need.

This is an editorial cost checklist. Registrar pricing models differ. Porkbun's current matrix, for example, separates registration, renewal, and transfer and says its displayed figures are for non-premium one-year terms; Cloudflare says its registrar charges the registry and ICANN costs without markup ([Porkbun domain pricing](https://porkbun.com/products/domains/pricing) and [Cloudflare Registrar documentation](https://developers.cloudflare.com/registrar/), checked 18 Oct 2026). These links document two named models, not an endorsement or a claim that either is cheapest for your suffix.

Multiply the known renewal by the planning period, add the purchase and required services, then mark every amount that can change. Do not present the result as a guaranteed lifetime cost. Registry and registrar prices and terms can change, so keep the source and check date with the decision record.

You probably do not need every spelling and extension. Buy a defensive variant when it prevents a specific, likely confusion and you have a clear redirect or protection purpose. Skip speculative portfolios that create recurring bills without reducing a named risk. That is editorial cost control.

If domain or hosting costs constrain the release, the [maker perks page](https://zeroraised.com/perks) links to current first-party terms for relevant tools and credits. Verify the current offer and eligibility on the provider's site before depending on it.

## Step 7: test the domain as an email address and product identifier

A business domain may appear in employee and support email, receipts, OAuth callbacks, app records, APIs, status pages, invoices, and customer allowlists. Test forms such as `founder@candidate.tld`, `support@candidate.tld`, `app.candidate.tld`, and `api.candidate.tld`. A phrase that looks clever as a homepage can become confusing beside `@` or as a subdomain. This is editorial infrastructure advice.

Do not send production email until the domain's mail setup is authenticated and tested. Google's current sender guidance requires all senders to Gmail accounts to use SPF or DKIM, and applies additional SPF, DKIM, and DMARC requirements to senders above its stated volume threshold ([Google email sender guidelines](https://support.google.com/a/answer/81126), checked 18 Oct 2026). Those requirements are about sending configuration, not a reason to prefer one ordinary generic extension over another.

For `.app`, account for HTTPS before expecting the website to work in browsers. Google Registry's registration policy requires registrars to warn buyers that HTTPS is required for `.app` names to function in web browsers because the suffix is on the HSTS preload list ([Google Registry `.app` policy](https://registry.google/policies/registration/app), checked 18 Oct 2026).

## Step 8: choose the registrar for control, not only checkout price

ICANN distinguishes registries, which maintain a top-level domain's registry, from registrars, which register names for registrants. Resellers can sell registration and related services but are not themselves ICANN-accredited; the sponsoring registrar remains accountable for required registrar services ([ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en), checked 18 Oct 2026).

Use the [ICANN accredited registrar list](https://www.icann.org/registrar-reports/accredited-list.html), checked 18 Oct 2026, to identify the sponsoring registrar for a generic extension, then compare:

| Control | Question to answer before purchase |
|---|---|
| Registrant record | Can the business be named as registrant with accurate contact information? |
| Authentication | Does the account support multistep authentication, and can recovery avoid one employee's personal inbox? |
| Locking | Is transfer lock easy to enable and clearly explained? Is a registry-lock option justified for a high-impact domain? |
| Renewal | Can auto-renew use a business payment method, with notices sent to more than one monitored contact? |
| Transfer | Can the registrant obtain the required authorization code through a documented process? |
| DNS | Can authorized staff export records, enable DNSSEC where appropriate, and change providers without transferring the registration? |
| Support | Is there a documented route for account compromise, lost access, and time-sensitive transfer problems? |
| Exit | Can the domain be transferred without first untangling unrelated hosting, email, or agency accounts? |

These questions are editorial due diligence. ICANN advises registrants to consider multistep authentication, registrar lock, and accurate registration data. Its transfer guidance says an AuthInfo code is required to transfer a generic domain and explains circumstances in which 60-day locks can apply ([ICANN domain-account protection](https://www.icann.org/news/blog/do-you-have-a-domain-name-here-s-what-you-need-to-know-part-4) and [ICANN transfer guidance](https://www.icann.org/resources/pages/about-transfer-policy-2017-10-10-en), checked 18 Oct 2026).

Put the registration in an account the business controls. If an agency, employee, or technical co-founder performs the purchase, document the registrant, account owner, recovery contacts, payment method, and handover. Never leave the only recovery route on an email address that uses the same domain without a separate recovery path.

Enable auto-renewal, but do not treat it as the whole continuity plan. ICANN says registrars must send renewal reminders around one month and one week before expiration, and it advises keeping contact and payment information current ([ICANN renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026). Add an internal calendar reminder well before expiration and assign a named owner to verify the renewal rather than assuming a card will work.

Score customer clarity, spelling, legal clearance, extension fit, cost, control, and migration as pass, concern, or fail. This is ZeroRaised editorial advice. A legal, eligibility, or control failure removes the candidate; a concern needs an owner and action before registration. Record the winner, check date, evidence, costs, responsible owner, and migration fallback.

## What to do when the exact `.com` is taken

Use this order of options:

1. **Keep the brand and add a clear modifier.** A product or action word can work when customers will remember the complete phrase. Buffer's earlier `bufferapp.com` is a real example of a modifier used before the company acquired `buffer.com` ([Buffer](https://buffer.com/resources/acquired-buffer-com/), checked 18 Oct 2026).
2. **Keep the brand and use a relevant generic extension.** Linear uses `linear.app`, and Google treats `.app` as a generic TLD for Search while the registry requires HTTPS ([Linear](https://linear.app/about), [Google Search Central](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level), and [Google Registry](https://registry.google/policies/registration/app), checked 18 Oct 2026).
3. **Use a country namespace for a deliberately local business.** Confirm local eligibility and accept the geographic signal. Google says most ccTLDs tell its systems that a site is probably more relevant in the corresponding country ([Google Search Central](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026).
4. **Choose a different brand.** Do this when every available form creates spelling problems, legal risk, audience confusion, or recurring cost beyond the business case.
5. **Approach the current registrant with a capped acquisition plan.** Verify the registration, seller control, transfer route, and payment protection before disclosing a maximum budget.

Test any added verb or prefix for what people omit, and do not choose an extension only for wordplay. A taken `.com` is a constraint, not a deadline.

## How to buy an already registered domain more safely

First, confirm the domain's registrar and visible registration status through [ICANN Lookup](https://lookup.icann.org/), checked 18 Oct 2026. Then contact the registrant only through a credible published route, registrar contact form, or established marketplace. Do not infer ownership from a logo, a social profile, or the sender address in one unsolicited email.

Before payment, document the exact domain, seller authority, total price, protected payment conditions, receiving account, current locks, disputes, renewal date and classification, DNS handover, and rollback plan. For an internationalized name, include both the Unicode and Punycode forms.

ICANN says generic-domain transfers use an AuthInfo code and lists denial reasons including certain 60-day periods, fraud evidence, and a UDRP action. It also notes that changing registrant information can trigger a 60-day lock under applicable policy and registrar choices ([ICANN transfer FAQ](https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en), checked 18 Oct 2026). Ask both registrars about the exact case before changing contacts or scheduling a release around the transfer.

## Plan the future domain migration before you need it

A good first domain does not have to be permanent, but the business should retain the ability to move. Keep content URLs understandable, avoid hard-coding the hostname where configuration would work, maintain an inventory of third-party callbacks, and record every system that sends from or trusts the domain. These are editorial engineering practices.

If the business later changes domains, Google recommends preparing and testing the new site, mapping old URLs to corresponding new URLs, using server-side permanent redirects, and monitoring both old and new sites. Its guidance says to keep redirects for as long as possible, generally at least one year from Google's perspective, and warns against redirecting many old pages to an irrelevant destination ([Google site-move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes), checked 18 Oct 2026).

The complete business migration is broader than Search:

| System | Migration action |
|---|---|
| Website | Map each valuable old URL to its new counterpart, update canonical references and sitemaps, and test redirects |
| Email | Add the new domain, authenticate sending, retain old receiving addresses, and update account recovery routes |
| Authentication | Update OAuth callbacks, passkeys, SSO identifiers, and allowlists without locking out administrators |
| Product | Replace API endpoints, webhooks, asset hosts, package metadata, and hard-coded links through a versioned plan |
| Commercial records | Update invoices, payment descriptors, contracts, app listings, support portals, and vendor profiles |
| Search and analytics | Verify the new property, submit the move where supported, annotate the change, and monitor errors on both hosts |
| Customers | Explain what changes, what remains valid, and how people can verify legitimate new email and links |

The table is editorial migration scope except for the linked Google requirements. Keep the old domain renewed while it handles redirects, mail, or verification. ICANN warns that if a registration is not renewed it may be released for someone else to register, and services attached to it can stop working ([ICANN renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026).

This is the sharpest lesson from the third-level `.name` warning. The difficult part of a move is rarely the new homepage. It is every address, reset email, identity record, integration, and trusted link attached to the old name. Choose for durability, then keep an exit route anyway.

## A domain decision checklist before launch

Complete this list before publishing the address widely:

- [ ] Intended customers can hear, spell, recall, and correctly interpret the complete domain.
- [ ] The name fits the nearest realistic expansion and has passed relevant trademark and commercial-use checks.
- [ ] The suffix, registry operator, eligibility, dispute, renewal, restoration, and transfer terms were verified and saved with a check date.
- [ ] Registration, renewal, transfer, premium, privacy, and required add-on costs fit the documented budget.
- [ ] The business is the registrant where applicable and controls the registrar account, recovery routes, and payment method.
- [ ] Multistep authentication, domain lock, auto-renewal, and an independent renewal reminder are configured.
- [ ] DNS, HTTPS, website, email receiving, and authenticated email sending were tested.
- [ ] The domain is correct in invoices, support addresses, callbacks, metadata, and launch assets.
- [ ] A named owner maintains the registration record, recovery procedure, and migration inventory.

The checklist combines the editorial tests in this guide with ICANN's guidance on registration, transfers, renewal, and account protection ([ICANN registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en), [transfer guidance](https://www.icann.org/resources/pages/about-transfer-policy-2017-10-10-en), [renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), and [account-protection guidance](https://www.icann.org/news/blog/do-you-have-a-domain-name-here-s-what-you-need-to-know-part-4), all checked 18 Oct 2026).

Once the domain, first-use path, and launch page work together, use the [pre-launch waitlist guide](https://zeroraised.com/blog/how-to-build-a-waitlist-before-launch) if access is still limited or the [bootstrapped app launch guide](https://zeroraised.com/blog/how-to-launch-a-bootstrapped-app) if people can use the product. Eligible makers can then [submit a launch to ZeroRaised for free](https://zeroraised.com/submit), checked 18 Oct 2026. Review the current form and terms before submitting; inclusion is not guaranteed.

If the business model still needs evidence before registration, use the [SaaS idea validation guide](https://zeroraised.com/blog/how-to-validate-a-saas-idea-before-building) before committing the name to public launch assets.

The final choice should feel unsurprising when read aloud: a clear name, an extension that fits the market, terms the business can maintain, and control that survives a staffing or vendor change. The best domain is not the cleverest string still available. It is the one the business can lawfully explain, reliably renew, securely operate, and carry into its next release.

## Sources

- [ICANN domain name registration process](https://www.icann.org/resources/pages/domain-name-registration-process-2023-11-02-en), checked 18 Oct 2026
- [ICANN domain transfer guidance](https://www.icann.org/resources/pages/about-transfer-policy-2017-10-10-en), checked 18 Oct 2026
- [ICANN domain renewal FAQ](https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en), checked 18 Oct 2026
- [IANA Root Zone Database](https://www.iana.org/domains/root/db), checked 18 Oct 2026
- [USPTO comprehensive clearance search guidance](https://www.uspto.gov/trademarks/search/comprehensive-clearance-search-similar-trademarks), checked 18 Oct 2026
- [Google handling of new top-level domains](https://developers.google.com/search/blog/2015/07/googles-handling-of-new-top-level), checked 18 Oct 2026
- [Google international and multilingual site guidance](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites), checked 18 Oct 2026
- [Google site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes), checked 18 Oct 2026

## Frequently asked questions

### What makes a good domain name for a business?

A good business domain is easy for the intended customer to hear, spell, type, and connect with the brand. It also passes trademark checks, has acceptable renewal terms, and can be controlled securely by the business.

### Does a business domain need to end in .com?

No. A relevant generic extension or a country-code domain can work when it fits the audience and business plan. Google says new generic extensions do not receive a ranking advantage or disadvantage simply because of the extension.

### Should I put a keyword in my domain name?

Use a descriptive word only when it makes the name clearer and still leaves room for the business to grow. Google says a keyword in a top-level domain does not create a search ranking advantage.

### What should I check before registering a domain?

Check exact and similar trademarks, existing businesses, the registry and registrar rules, registration and renewal prices, premium status, transfer support, and the account security and recovery options.

### What if the domain I want is already registered?

Consider a clear modifier, a relevant alternative extension, or a different brand name. If buying from the current registrant, verify control, use a documented transfer process, and set a firm budget before negotiating.