How to choose and organise your company’s domain name
The domain accompanies the website, email addresses, documents and links customers keep. Choosing it involves language and continuity: someone needs to be able to say it, write it and renew it. This guide ends with a decision worksheet and responsibility map so the company retains control even when suppliers change.
By the end, you can:
- Compare names with specific criteria
- Separate registration, DNS, website and email
- Prepare ownership, recovery and renewal
Test the name away from the screen
Make a shortlist of candidates and try each in real communication situations: spoken over the phone, written in a quote and shown in an email address. Ask someone else to write it after hearing it without showing the correct option. Record difficulties: swapped letters, a forgotten hyphen, a confused word or an assumed extension. This trial discovers friction; it does not produce a preference percentage.
Choose a name that will still make sense if the company adds a service. An address tied to one product, city or year may require another change later. A descriptive name may help understanding, but accumulating keywords does not compensate for a hard-to-recognise brand. Also check how joined words read: sequences that seem clear separately can become ambiguous in a domain.
Compare the extension and confirm availability
The extension is part of the name. Assess the context in which the address will be communicated and the registration rules applying to each option. A company serving several countries may prefer a broad address; another may want a territorial domain consistent with its presence. Neither choice removes the need for suitable content, service and configuration. Confirm rules with the responsible registry or provider instead of assuming every extension works the same way.
Check availability when deciding and confirm it again before buying. An available domain does not mean the name is free of third-party rights. Search the trademark in the relevant scope and clarify doubts before investing in identity, packaging or advertising. If someone already owns the desired name, compare readable alternatives; do not build the brand around a variant customers easily confuse.
Separate the four parts of the operation
Registration keeps the domain associated with its registrant. DNS indicates where services for that domain operate. Hosting makes the website available. The email service receives and sends messages. They may be with the same or different suppliers, but should appear separately in the inventory. A website change does not, by itself, mean changing email inboxes.
Before changing nameservers or DNS settings, inventory what already exists. Records used by email, service verification and subdomains need preserving or deliberate replacement. Request a copy of the configuration and a rollback plan. During a change, check both the page and message receipt: seeing the website open does not demonstrate that every domain service remains operational.
- Registration
Registrant, renewal and account recovery.
- DNS
Service destinations and verifications.
- Website
Hosting, HTTPS and pages.
- Email
Inboxes, sending and receiving messages.
Define who controls and who administers it
Register the domain with the correct registrant’s details and confirm who receives notifications. A provider can administer configuration without owning the digital identity. ICANN distinguishes the registrant from registration intermediaries; for territorial domains, also consult the respective operator’s rules. Keep proof and identify the account where the domain appears.
Assign individual access when the platform allows it and enable additional account protection. Recovery must not depend exclusively on an inbox on that same domain: if that infrastructure fails, recovery may also be blocked. Document where credentials are kept in an appropriate manager without copying them to the public project worksheet. Agree who authorises transfers, DNS changes and registrant changes.
Completed example: a fictitious workshop
Fictitious workshop Cais Oficina is choosing between three ways to communicate its brand. The names below use the reserved .example extension: they are writing examples, not available offers. The team chooses caisoficina.example for the exercise because it matches the brand and can be dictated without an extra instruction. A real decision would require checking availability, rights and registration terms.
In the operational worksheet, the registrant would be the company itself; management would approve changes, the technical team would administer DNS and an independent recovery inbox would receive alerts. Review would not end at purchase: HTTPS, intended address variants and email sending/receipt would be tested. The example therefore addresses both choosing a name and continuity of operation.
| Illustrative candidate | Advantage | Point to test |
|---|---|---|
| caisoficina.example | Matches the brand | How the joined words are understood |
| cais-oficina.example | Visual separation | Need to dictate the hyphen |
| reparacoes-cais.example | Explains an activity | Suitability if the offer expands |
Organise renewal and avoid hidden dependencies
Compare the initial price with renewal, the contracted period and transfer terms. Check currency, applicable taxes and any additional services. Automatic renewal helps but depends on valid payment and received notices. Record a review before expiry, with a substitute owner; do not place all continuity on one person or a card that may stop working.
Common errors include buying several domains without defined destinations, forgetting an old domain still used for email and changing DNS without preserving services. For every secondary address, state whether it will be kept and where it redirects. If replacing the main address, treat it as a migration with a URL map and monitoring. The transition should retain useful paths customers already know.
The worksheet to approve and hand over
Complete this worksheet before registration and add operational details afterwards. Attach proof and approved configuration in an access-controlled area. The document should let another authorised person understand the service, find the owner and follow recovery procedures without guessing where it was contracted.
Worksheet for your project
Brand and activity: Chosen domain and alternatives considered: Dictation test and difficulties found: Availability and name checks, with date: Registrant and person approving changes: Registration provider and responsible account: DNS / hosting / email, with owners: Renewal: date, confirmed cost and payment method: Alerts and independent recovery contact: Where access details and proof are kept: Variants and old domains to preserve: Website, HTTPS and email tests: Next review and substitute owner:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
