14 July 2026 · Kenya Web Studio
.co.ke domains, hosting and business email: an ownership guide
Know who controls your Kenyan domain, DNS, hosting and email before a launch or supplier change. These accounts should stay with the business.
A domain is an address, not the website itself
The domain is the name customers type, such as example.co.ke. DNS records tell browsers and mail systems which services handle that name. Hosting stores and runs the website. Email may sit with the same supplier or a separate provider.
These parts can move independently. Replacing a website does not always require transferring the domain. Changing hosting should not break email if the person editing DNS understands which records belong to mail.
Register the domain for the business
Kenya’s .ke namespace is managed by KeNIC through accredited registrars. Use a registrar account tied to a monitored business address, record the registrant details accurately and keep recovery information current.
A web studio can help with registration and DNS, but one employee or contractor should not be the only person able to recover the name. Put renewal responsibility on a calendar and store the invoice. Domains are commonly lost through ignored renewal notices, not clever technical attacks.
Business-controlled registrar login
Accurate registrant and billing details
More than one trusted recovery route
Renewal reminders outside the registrar inbox
A record of every person with access
Treat DNS changes like production work
A short DNS record can take down a website or stop email. Export or screenshot the current zone before editing it. Label what each record does, especially MX, SPF, DKIM and verification records for mail and outside services.
Do not replace the whole DNS zone just to point the website at a new host. Change the records the host requires and preserve unrelated entries. Allow for cached results during a move, then test the public website and incoming and outgoing email.
Choose hosting by workload and support
A five-page marketing site and a busy online shop do not need the same setup. Ask how the platform handles backups, software updates, traffic spikes, logs, staging work and recovery. Find out which tasks the host handles and which remain with the developer.
Server location is one input, not the entire performance plan. Image weight, caching, database work and third-party scripts often matter more. Use a content delivery network where it helps, but fix oversized pages as well.
Set up business email with authentication
An address at the company domain looks consistent and stays with the business when staff change. Create named accounts for people and shared addresses such as sales or accounts where several staff need continuity. Avoid sharing one password across a whole office.
Configure SPF and DKIM for the systems that send mail. Add DMARC with a policy the business can monitor and tighten over time. These DNS records help receiving systems assess legitimate mail, but they need care when the website, newsletter platform and office mail use different senders.
Know what happens when a supplier changes
The handover should list the registrar, DNS host, web host, repository, deployment account, database, storage, analytics and email provider. Change personal agency contacts to business contacts where practical. Remove old access after the move is stable.
Request a current backup and test that it can be used. A zip file with no database or an export missing uploaded media is not a recovery plan. Document the restore steps and who has permission to run them.
Account and service inventory
Named owners and renewal dates
Current website and database backup
DNS zone copy
Access removal checklist
A ten-minute ownership check
Ask one director or manager to log in to the registrar without help. Then locate the hosting invoice, email administrator and latest backup. If nobody inside the business can do that, fix access before the next redesign or staff departure.
Do not publish passwords in the handover document. Use a password manager and give each person their own access where the service supports it. The document should say where credentials are stored, not reveal them.
Related guides
Read next: Web design services in Kenya
Read next: Website maintenance service
Read next: Ask about a website handover
Read next: KeNIC website