Short answer
Choose a plain name and register it to the company; keep auto-renewal on, and keep the registrar and DNS logins on a shared company address. Pick the hosting type by what the site does, set up HTTPS, backups and business email from the start, and plan a move so that DNS changes last.
One morning the website will not open. Customers are phoning and emails bounce. You look: the domain name has expired. The account at the registrar is tied to the personal address of the person who built the site five years ago, and the renewal warnings went there. People ask how to choose a domain name and hosting as if it were a question of which package. But the real trouble sits outside the package: whose name it is in, whose account it is under, who renews it and who can move it. This guide splits the choice into nine steps and ends with the order of work for moving a site without downtime.
If a team is building the site for you, the contract side is in how to commission a website, including the ownership clause. Which pages a company site needs is the subject of what a company website needs. We do not repeat either here; this is about the domain and the hosting themselves.
1. Choose the domain name
The domain name will be the address of the site, the email and every printed item, and changing it later means correcting all of them. Three questions are enough:
- Can it be said aloud and typed? Someone who hears it on the phone should be able to spell it. Addresses with Turkish characters can cause trouble in email and some systems; many organisations make the plain-letter spelling the main address and redirect the other.
- Does it match your brand? The company’s trading name or well-known brand is the choice with the fewest surprises. Hyphens and digits cause errors when the address is passed on by voice.
- Do you know which rules you depend on? ICANN says country-code domains are generally registered through their own operators. The rules in this guide from ICANN are for generic extensions such as .com. For a country extension, registration, transfer and renewal rules are set by that extension’s own registry, so read them on the registry’s own site. For businesses in North Cyprus, we look at .ct.tr, .nc.tr and .com.tr separately in our guide to North Cyprus domain names.
2. The company itself should be the registrant
When you buy a domain you sign a contract with a registrar. According to ICANN, the person or organisation making that contract is the registrant, and the rights and duties are theirs. ICANN says they are solely responsible for registering and using the name, they keep the published contact details accurate, and they answer the registrar’s enquiries within fifteen days. The person or organisation named at registration is the registrant; who opened the account and who the registrant is can differ, so check both.
For a company site the registrant should not be your agency, the founder’s personal account or someone who has left. The company’s legal name should be shown, the account should sit on a shared company address (a mailbox several people read, such as info@ or it@), and the login should not depend on one person’s phone. ICANN also notes that resellers are not accredited by ICANN, although the registrar remains responsible for the registrar services its resellers provide. If you buy through a reseller, know who your contract is with.
3. Auto-renewal and the registrar lock
An expired domain stops both the site and the email. Two settings prevent that:
- Auto-renewal. Keep it on. ICANN’s list of responsibilities says that anyone who chooses automatic renewal must keep their payment details current; if the card has expired, the renewal does not go through. Also write the renewal date in a calendar and send the reminders to more than one person.
- Registrar lock (transfer lock). ICANN’s transfer policy describes a registrar placing a domain in “ClientTransferProhibited” status at registration or at the registrant’s request; it is the lock that prevents an unauthorised transfer. Keep it on until the day of the move, then remove it. If the registrar does not let you manage the code and the lock yourself, the policy requires it to provide the code and remove the lock within five calendar days of your request.
The transfer code (AuthInfo) you need for a move works like a key to the domain; share it only with someone the registrant has authorised.
4. DNS in plain words, and who should hold access
DNS is the system that translates domain names into the numeric addresses of servers. Your domain’s DNS records decide three things: which server the site opens from, where the email goes, and where the authentication details that prove an email came from you are kept. One wrong record can stop the site or the email, and changes do not reach everywhere at once.
The place where the records are kept does not have to be the place where you bought the name. The registrar, the hosting company or a separate DNS service can manage DNS. All you need is to know where your records are managed today.
This split of access works well:
| Who | What they should be able to do | Why |
|---|---|---|
| The company (owner account) | The registrar account, renewal, lock and transfer code | The real authority of a registrant |
| The web team or agency | Add and change DNS records | To build the site and the email |
| Another team (email tool, advertising) | Only their own verification record, on a written request | So they cannot break another record by accident |
| Everyone | A note recording every change | For the day, a year on, when someone asks what a record is |
5. Choose the hosting type by what the site does
Hosting is keeping a site’s files and database on a server open to the internet. The types below are listed by what they suit; there are no prices on purpose, because the right type comes from what the site does, not from a price list:
| Type | Suits best | What to watch |
|---|---|---|
| Shared hosting | Brochure sites with few visitors and simple blogs | You share the server with other sites; it may slow down at busy times |
| Virtual server (VPS) | Custom software and sites that need their own settings | Server maintenance and security patches fall to you or to a management contract |
| Cloud hosting | Sites and applications with changing traffic | Growing resources is easy; it needs configuration knowledge |
| Edge hosting for static sites | Sites without a database that should open fast | Content that changes often needs a publishing workflow |
| A ready-made platform’s own hosting | Ready-made systems such as a shop or bookings | The platform runs the infrastructure; how freely you can move depends on its rules |
Ask two questions when choosing: does the site have a database or scheduled jobs, and how many people are on the site at once on your busiest day? Server response time affects page speed; for the detail see how to speed up a website. A server close to your visitors, or a CDN, is a separate setting; ask the provider.
The account, like the domain, should be opened in the business’s own name. If the hosting stays in the agency’s account, the handover and panel access should be in writing.
6. The HTTPS certificate
SSL/TLS encrypts the connection between the browser and the site; a site with a valid certificate has an address that starts with https. A certificate authority will not issue one until you show control of the domain: Let’s Encrypt’s documentation describes its certificates as domain-validated (DV) and explains that the proof can be a DNS record or a file on the site. That is why DNS access and hosting access are both needed when you install a certificate.
Certificates are issued for a limited period and have to be renewed. Check two things:
- Does the hosting install and renew the certificate itself? Ask whether renewal is automatic and who receives the warning.
- Do all pages redirect to https, and is any mixed content left (an image or script still called over http)?
7. Backups
A backup should not be something remembered only when things go wrong; make it a habit before every update. Get three answers in writing:
- How often is a backup taken, and how many older versions are kept?
- Does it cover only the files, or the database too?
- Who restores it, and how quickly? Has it ever been tried?
A backup that sits on the same server goes down with that server, so keep one copy elsewhere. If the hosting has no backup, or the backup is not yours, take your own copy (files and database) regularly and try one restore in a test environment.
8. Business email on your own domain
Messages to customers should come from name@yourcompany. That relies on records in your domain’s DNS: the MX records that say which server the email goes to, and the SPF, DKIM and DMARC records that authenticate the sender. Google’s Gmail guidelines ask every domain that sends to Gmail to set up SPF or DKIM, and those sending more than 5,000 messages a day to set up SPF, DKIM and DMARC. Each time you add a new email tool or form plugin, the SPF record may need updating, so a record of which tool sends in your domain’s name should sit with whoever manages DNS. The detail of bulk sending is covered by our email service.
9. Moving a site without downtime
Changing hosting, or handing a site to a new team, can go unnoticed by visitors if done in the right order. The rule: the DNS record changes last, and the old server closes last.
- Back up and note down the DNS records. Take a full list of the records: site, email (MX), verification records. The email records are the ones most moves forget.
- Lower the DNS cache time (TTL). This time decides how long the old value stays cached after a DNS record changes. If you shorten it before the move, the switch settles faster. Check your registrar’s or DNS provider’s documentation for how.
- Build a copy on the new hosting. Leave the old server alone; the two will run side by side for a while.
- Test on a temporary address. Try the pages, the forms, the payment and email sending. Make sure the certificate is installed on the new server.
- Point the DNS record to the new server. The site record changes in this step; the email records should stay as they are.
- Monitor; keep the old hosting running. Watch forms, orders and email for a few days. Close the old account only once you are sure nothing is wrong.
Building and launching a site falls under our web and software service. If the address structure changes too, redirects and search visibility are a separate job; we described the order in keeping SEO through a site rebuild. If you are also moving the domain between registrars, do it on a different day from the site move: prepare the lock and the transfer code first, and make sure the registrant details are right. ICANN’s policy defines locks that can hold a transfer back after a change of registrant or after a new registration, so do not leave correcting the registrant to the day of the move.
Common mistakes
- Leaving the domain in the agency’s, a former employee’s or the founder’s personal account.
- Sending the renewal warnings to one person’s email.
- Choosing hosting without asking about backups and restores.
- Changing DNS during a move without having written down the MX and verification records; email can then stop arriving.
- Closing the old hosting before the new site has been tested.
- Not knowing who has access to DNS.
Common questions
Should the domain name and the hosting be bought from the same company?
It is not required. Buying from one place makes management easier; keeping them apart makes it easier to move one when the other causes trouble. Whichever you choose, keep the registrant and the account in the company’s name and keep the renewal date written down.
What happens if an agency keeps the domain in its own account?
If the registrant shows your company, and you have access to the registrar account or a written right of transfer, there is no problem. If the registrant shows the agency, getting the domain back when you part depends on the agency’s cooperation.
Will the site be unreachable while I change hosting?
If DNS is changed last and the old server is kept running, visitors usually see no outage. The time it takes depends on the DNS cache setting and on the preparation.
The first thing you can do today: sign in to your domain’s registrar account and look at three things. Who is the registrant, who holds the renewal date and the warning email, and is auto-renewal on? Then copy a dump of your DNS records into a document. The work is short, and the day you need it, what you would have been hunting for is already in your hands.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.