Enter Zimbabwe market with a .CO.ZW Domain

No. The registry says so plainly: organisations outside Zimbabwe may register, and non-residents are free to choose either a local or a foreign registrar. There is no local address, agent or trustee requirement; the application template asks only for a physical address for service of legal notices, and that address need not be in Zimbabwe. What the extension is not, however, is a free-for-all: ZISPA reviews every application and wants to be satisfied that the name you picked is not somebody else's company name or trademark. An application for a well-known organisation's name may be asked to produce authorisation from that body. Geography is not the deciding factor here; the name itself is.

Your registrar will ask for two things. The first is identity: a copy of your national identification if you are an individual, or your certificate of incorporation if you are a company. That request is not ZISPA's own preference but a consequence of POTRAZ regulations requiring accurate registrant details; the registrar must keep those copies securely and produce them to the regulator on demand. The second is an application letter: on company letterhead for an organisation, signed by an authorised person whose name and position are spelled out, or accompanied by a certified copy of your identification if you are an individual. The letter must name the domain and the registrar you are appointing, and confirm that you accept ZISPA's terms.

Registration in this zone is still a manual process; the automated EPP machinery familiar from other registries does not exist here. Your registrar sends a completed co.zw template to ZISPA as a plain-text email attachment. A separate email is required for each domain, and the subject line must state both the action and the fully qualified domain name. ZISPA checks the template by hand, then writes the name to its own name server and to secondary servers located around the world. The registry states that it aims to process every application within one working day, usually within about an hour during office hours, and at least once a day outside them. You receive a manual reply first, then an automated confirmation.

The unusual part is that your name servers must be working before you apply. Before processing the template ZISPA checks one by one that the servers actually exist, that they answer queries, that their answers carry the authoritative flag, and that they list at least NS and SOA records for the domain; all of them must report the same serial number and be identified by unique address records, with alias records refused. An application that falls short is not rejected immediately: it is reviewed every hour for twenty-four hours and turned down only if it is still incomplete. If your server names sit under your own domain, their addresses must be lodged with ZISPA separately and updated whenever they change.

The grace and redemption chain you know from generic extensions does not exist here. The rules allow a single payment window: the annual maintenance fee falls due within thirty days of the anniversary of the registration's effective date. If payment does not arrive in that window, the registry may, without prejudice to its other rights under the agreement and without notice, de-register the name. The practical consequence is blunt: a delay of a month is not a recoverable delay in this zone, it can mean losing the name for good. The safest approach is to track renewal in your own calendar rather than leaving it to the registrar alone, and to keep the recorded contact address working.

The registry reserves the right to take it back. ZISPA's terms treat a holder's failure to make regular use of the name for ninety days or more as an express ground for withdrawal, and leave the measure of regular use to ZISPA's own reasonable discretion. A warranty given at application time points the same way: the applicant declares a bona fide intention to use the name on a regular basis on the internet. The upshot is that this extension is a poor fit for stockpiling names against future need; the name is expected to be attached to a live site or mail service. ZISPA also warns that registrations whose recorded email addresses bounce are liable to be cancelled.

There are two separate operations, and each follows a written procedure. For a change of registrar you approach the new provider and ask the old one to confirm to them that it releases the domain; the new registrar then sends ZISPA a single email carrying the template, your own message confirming the transfer, and the previous registrar's release. There is no authorisation-code mechanism — those written confirmations are the verification. For a change of owner the new holder supplies a signed application letter, exactly as for a fresh registration, together with evidence that the previous holder has released the name. You can start the process on the domain transfer page.

They are not, because this extension has no online whois service at all; the registry states as much on its own site and asks for enquiries to be sent to it by email instead. Its lookup screen shows only whether a name is registered, which registrar manages it and what its name servers are — no holder name, no address, no dates. Do not read that as a privacy guarantee, though: the terms record your advance consent to the registry publishing the information supplied in the application, and if an infringement claim is evidenced ZISPA reserves the right to give the complainant the applicant's name and address. For other extensions, use the whois search page.