Who Actually Owns Your .ke Domain? How to Check, and How to Get It Back

A business calls us because they want their website changed. Somewhere in the first ten minutes we ask who the domain is registered to. There is a pause. Then: "the guy who built the site has all that."

That conversation happens most weeks. The business has paid for the domain every year, has its name printed on the domain, uses it on every invoice and business card, and does not hold it. The name is theirs commercially and somebody else's administratively, and those two things only look the same until the day you need to move.

This is a plain guide to the difference, how to check which side of it you are on, and what to do if the answer is the wrong one.

Three Roles People Mix Up

Almost every argument about a domain comes from treating three separate things as one. They are:

• The registrant. The person or company the domain is registered to. This is the closest thing to ownership. If this is not your business name, your business does not hold the domain.
• The registrar account. The login at the company you buy the domain through. Whoever holds this account can move the domain, change its settings, or let it expire, whatever the registrant field says.
• The DNS. The settings that point the name at your website and your email. Changing these is day to day work. Holding them is not the same as holding the domain.

A developer can quite reasonably run your DNS for you. A developer holding the registrar account, with their own name in the registrant field, is a different situation, and it is the one that causes trouble.

In Kenya, .ke names are managed by KeNIC, the national registry, and sold through registrars it accredits. KeNIC's own figures reported for June 2026 put .ke domains under management at around 129,000, up roughly 16 per cent on the year before, so a lot more businesses are about to have this conversation for the first time.

Why This Goes Wrong So Often Here

It is rarely malice. The usual story is ordinary and avoidable.

A business wants a website. The developer says he will "sort out the domain and hosting", because that is genuinely easier than walking a client through a registrar signup. He buys it on his own account, often alongside twenty other clients' domains, and puts his own email as the contact because the verification email has to go somewhere he can read. The site goes live. Everybody is happy. Nobody writes anything down.

Two years later the business wants to move, or the developer has changed careers, changed numbers, or had a falling out over an invoice. Now the domain, the email addresses that run on it and every link anyone has ever shared are all behind somebody else's login.

The painful part is that the business usually did pay for it. Paying for something and being registered as holding it are different facts, and only one of them is in the registry.

How to Check in Two Minutes

You do not need anybody's cooperation to find out where you stand. Three checks, in this order.

Reading What You Find

There are three realistic outcomes, and they need different responses.

Worth checking at the same time: the contact email on the domain. If it is an address nobody reads, or an address at a company that no longer works with you, then renewal warnings and transfer approvals are going somewhere you cannot see. That single field causes more lost domains than any dispute.

Getting Control Back

Start pleasantly, because most of the time it works. Most developers hand things over without fuss when asked directly and specifically.

1. Ask in writing, and be specific. Not "can I get my domain details" but "please change the registrant to [business name], change the contact email to [your address], and send me the login for the registrar account." Vague requests get vague answers.
2. Give a date. A week is reasonable. An open ended request drifts for months.
3. Settle what you owe first. If there is an unpaid invoice, pay it or agree it. It removes the only defensible reason to hold on, and it makes the next step cleaner if you need it.
4. Escalate to the registrar. If you get nowhere, the registrar is the next stop, and for a .ke name KeNIC is above them. Bring evidence: payment records, your registration documents, email showing the arrangement. Registries deal with this category of dispute and will tell you what they need.

What does not help is changing DNS to point at a new site while the registration stays in someone else's name. That treats the symptom. The domain can still be moved or dropped out from under you.

Moving It to an Account You Hold

Once the registrant details are right, move the domain somewhere you control. The shape of a transfer is the same everywhere.

1. Open an account in your own business name at a registrar you choose. For a .ke name, use one KeNIC accredits.
2. Unlock the domain at the registrar it currently sits with, and get the authorisation code. Different registrars call it an auth code, an EPP code or a transfer key. It is the same thing.
3. Start the transfer at the new registrar using that code.
4. Approve the confirmation email. This is why the contact address has to be one you can actually read before you begin.
5. Check your DNS records afterwards, especially the mail records. A transfer that moves the name but loses the email settings takes your email down, and that is the most common way this goes wrong.

Transfers also tend to carry conditions, like a domain being too recently registered or too recently transferred to move again. Your registrar will tell you if one applies. Prices change and differ between registrars, so check the current figure with the registrar itself rather than trusting a number in any article, including this one.

Expiry Is the Real Danger

Disputes are unpleasant but slow. Expiry is fast and final, and it is what actually takes businesses offline.

A domain that lapses stops serving your website and, worse, stops serving your email. Nothing bounces usefully, people assume you are ignoring them, and if the name is attractive enough somebody else may pick it up. The usual cause is not neglect, it is that the renewal notice went to an address nobody monitors.

If you want this looked after rather than remembered, it is part of what website maintenance covers for our clients. The useful bit is not the renewal itself but somebody noticing in advance.

What to Insist On Before Anyone Builds You a Site

You can avoid this whole article on any future project by settling four things at the start. None of them is unreasonable, and anyone who objects to all four is telling you something.

1. The domain is registered to your business name, with your business address and a contact email you control. The developer can be a technical contact. The registrant is you.
2. You hold the registrar login. Share it with whoever does the work, but hold it.
3. Hosting is in your name too, or at least you know exactly whose account it is and what happens if that relationship ends.
4. You get a handover note: where the domain is, where the hosting is, where the DNS is managed, what the admin logins are, and when things renew. One page is plenty.

We register domains in the client's own name as a matter of course, and we hand over that note whether or not anybody asks for it. Not out of generosity. It is simply what a business should be left holding after paying for a website, and it saves the conversation this article is about.

Frequently Asked Questions

How do I find out who owns my .ke domain?

Run a WHOIS lookup on the name, starting with KeNIC's own site for a .ke domain. It shows the registrant the domain is registered to, the registrar it sits with and the expiry date, though some contact details may be withheld for privacy. Then apply the practical test: try to log in to the registrar account yourself without asking anybody. If you cannot, you do not control the domain, whatever the registrant field says. Our free hosting checker at wpfoss.ke/who-is-hosting-this-website will also tell you which host and network your site is actually on, which is often the first thing you need to know.

My web developer registered my domain in his own name. What can I do?

Ask in writing for three specific things: the registrant changed to your business name, the contact email changed to an address you control, and the login for the registrar account. Give a date, and settle any outstanding invoice first so there is no reason to hold on. Most developers comply when the request is that specific. If you get nowhere, escalate to the registrar, and above them to KeNIC for a .ke name, with your payment records and registration documents. Do not just repoint the DNS at a new website; that leaves the registration with somebody else who can still move or drop it.

What is the difference between a registrant, a registrar and a host?

The registrant is who the domain is registered to, which is the closest thing to ownership. The registrar is the company you buy and manage the domain through, and whoever holds that account can move or drop the name. The host is where the website files actually sit. They are frequently three different parties, and a developer running your DNS or hosting is not the same as a developer holding your domain. Problems almost always come from treating the three as one thing.

How do I transfer a .ke domain to another registrar?

Open an account in your own business name at a KeNIC accredited registrar. At the registrar the domain currently sits with, unlock it and get the authorisation code, sometimes called an auth or EPP code. Start the transfer at the new registrar with that code, then approve the confirmation email, which is why the contact address has to be one you can read before you begin. Afterwards check your DNS records, especially the mail records, because a transfer that loses them takes your email down. Some conditions can block a transfer, such as the domain having been registered or transferred very recently.

What happens if my domain expires?

Your website stops loading and, more damagingly, your email stops working, so enquiries disappear without anybody bouncing a useful message back. If the name is desirable somebody else may register it once it becomes available. The usual cause is not neglect but a renewal notice going to an address nobody monitors, which is why the contact email on a domain matters as much as the expiry date. Keep auto renewal on, keep the expiry date in a shared calendar, and make sure more than one person can get into the registrar account.

Should my web designer hold my domain for me?

They can manage it, and running your DNS is normal. They should not be the registrant, and you should hold the registrar login even if you share it with them. The test is simple: if that relationship ended badly tomorrow, could you still move your own domain? If the answer is no, the arrangement is wrong, regardless of how much you trust the person today.