Buy .ke Domain Name

No. There is no requirement for the registrant to hold an office, a local address or an agent in Kenya. The confusion has a clear source: the registry does mention local presence, but the subject of that sentence is the registrar — a company must have an office in Kenya to be accredited as a seller. No such condition applies to the end user. A company based in Türkiye, a sole trader or a private individual can therefore register a .ke name through an accredited registrar. Registration always runs through those registrars; the registry accepts no applications directly from end users.

Both sit with the same registry, the Kenya Network Information Centre. The difference is level and positioning. A .ke name is a one-part address that carries no specialisation, so nothing in it labels what kind of organisation you are. .co.ke is the third-level space defined for companies, e-commerce sites and retail businesses, and it is the established address format in Kenya. The numbers make the gap plain: regulator figures for 31 March 2026 record 110,687 names under co.ke against 7,871 registered directly at .ke. The two do not block each other, so you can hold the same name at both.

In May 2017. Kenya's extension entered the root zone on 29 April 1993, but from its founding until 2017 the registry sold names only at the third level: every applicant had to take a two-part address such as name.co.ke or name.or.ke. The one-part space opened in May 2017, and names in the form name.ke have been available since. That late opening has a practical consequence: because established Kenyan brands built their addresses at the third level, good names can still be free at the direct second level.

No. A direct .ke registration requires no paperwork and involves no pending approval step. The registry applies a document requirement to only three third-level spaces: go.ke for government bodies, ac.ke for institutions of higher education and sc.ke for lower and middle level schools. In those spaces a registration opens a support ticket, and the name is not published until the documents reach the registry and the ticket is closed. Neither the direct second level nor the commercial co.ke space involves that step; the name is published in the ordinary flow once your registrar submits it.

No. The registry publishes no public field about the registrant at all. A lookup returns the domain name, the registry identifier, the creation, update and expiry dates, the status codes, the name servers and the registrar's details. Fields for the registrant, administrative or technical contact are simply not printed — there is not even a redacted placeholder. The registry's RDAP service behaves identically: only the registrar appears as an entity in the response. You can check your own record on the whois search page.

The registry's rules expressly allow a change of registrar: holders may move their .ke names to the registrar of their choice. Because no single central authorisation-code procedure is published, you obtain the exact steps from your incoming registrar. One point deserves attention: names often carry a transfer lock applied by the current registrar. That is not a registry-wide ban, and you can ask your existing provider to lift it. A change of holder is a separate and slower process, which is why registering the name in the final owner's name from the outset is more practical. Start on the domain transfer page.

The UDRP procedure familiar from generic extensions does not operate here; the registry applies its own alternative dispute resolution policy, and the process has two stages. A complaint is filed with KeNIC on a lodging form; the registry verifies the holder through whois and first invites the parties to mediation. If no settlement is reached, the file moves to arbitration before an arbitrator certified by the registry, and if that produces no outcome the courts remain open. The available remedies are limited: transfer of the name, deletion of the name, or dismissal with the holder keeping it. Kenyan law applies.