.co.za domain names

What .co.za is

.co.za belongs to South Africa and is not a top-level domain in its own right. IANA delegates za, and co.za sits beneath it, so yourname.co.za is a third-level registration. The country code is a linguistic fossil: ZA stands for Zuid-Afrika, the Dutch name for the country, a language that has not been official in South Africa for decades.

Two bodies run the namespace. ZADNA, the .za Domain Name Authority, is the IANA sponsoring organisation and the policy and regulatory authority for the whole namespace — a statutory, not-for-profit regulator whose basis is South Africa's Electronic Communications and Transactions Act of 2002. It decides the second-level structure and runs the dispute framework, but does not sell or operate registrations. ZACR, the ZA Central Registry, is the registry operator for co.za, net.za, org.za and web.za. Founded in 1988 as UniForum SA, it began administering co.za in September 1995 and migrated to a modern EPP platform in 2011. It is Africa's largest registry.

.za itself was delegated on 7 November 1990. One quirk is worth knowing early: the IANA record for za lists neither a WHOIS nor an RDAP server, so tooling that relies on the delegation record for service discovery simply fails on .za.

Who can register .co.za

Nothing is required. .co.za is fully open. There is no South African residence or citizenship test, no requirement for a South African company or CIPC number, no local address, no local agent, and no documentary evidence of any kind. South Africans and non-South Africans register on identical terms, with non-South African registrants typically consenting to South African law and jurisdiction. The co in co.za is nominally commercial and this is not enforced.

What is required is a valid, monitored email address, and this is the one obligation with real teeth. Email verification is required for new registrations, and failure to verify leads to suspension and ultimately deletion. Unlike an eligibility problem in a restricted namespace, which typically surfaces years later, this bites within weeks. Contact details must also be accurate and are handled subject to POPIA, South Africa's Protection of Personal Information Act.

Anyone told they cannot have a South African domain is almost certainly looking at a restricted zone rather than co.za — ac.za is limited to accredited academic institutions, gov.za to government, and edu.za and nom.za have their own criteria and operators. Disputes over co.za names go to ZADNA's alternative dispute resolution framework under the ECT Act regulations, not the UDRP.

What .co.za costs to own

Structurally, co.za is a low, flat, per-year wholesale fee. It has long been among the cheapest country codes in the world, which is a large part of why it dominates the African domain market. There is no registry-level premium tier and no promotional first-year registry pricing, so any first-year discount is registrar marketing.

A ZADNA levy applies to .za registrations to fund the regulator; it is bundled into what registrars charge and is not separately visible to buyers. Transfers between registrars are typically free and carry no registry fee, so if your renewal price has drifted upward, moving costs you nothing at registry level. No ZACR or ZADNA price change has been verified for 2024 to 2026.

Registration terms, renewals, and transfers

Registration terms are the least well documented aspect of .co.za and deserve hedging. Before the 2011 platform migration co.za was effectively an annual product. Post-EPP, multi-year terms are available: a 2026 South African source states one to five years upfront with unlimited renewals thereafter, some registrar platforms advertise up to ten, and ZACR's own terms could not be retrieved. Treat it as commonly one to five years, with one-year terms most widely offered. Auto-renewal generally has to be disabled roughly two days before expiration to stop it firing, and contact updates take five days to process and cannot be amended mid-flight.

The transfer mechanism is the most unusual in the region: there is no authorisation code at all. The gaining registrar initiates at the registry; the registry emails the domain's owner, admin, tech and billing contacts asking for confirmation; at least one must approve. The transfer fails if a contact denies it, or if nobody responds within five days. End to end it typically takes five to ten days, and a domain expiring within 30 days auto-renews on transfer.

This matters more than it sounds. The whole process depends on the email addresses in the registry record being current and monitored, with no code as a fallback. If they are stale — an old agency inbox, a departed employee, a domain whose own email no longer works — you cannot move the domain, and there is nothing you can produce to prove control. Combined with contact updates taking five days and locking while in flight, recovering a .co.za from a stale-contact situation is genuinely awkward.

WHOIS, RDAP, and privacy

WHOIS for co.za is served by ZACR at whois.registry.net.za, not from the IANA delegation record, which lists no WHOIS or RDAP server for za at all. RDAP availability for co.za is unverified, so if a monitoring tool cannot resolve registration data for a .co.za, that discovery gap is the likely explanation.

Privacy is generally not available. Private or anonymous registration is not offered as a standard product. There is no registrant opt-out of the kind Nominet operates for non-trading individuals, and no automatic free privacy for natural persons of the kind Canada and Germany provide. POPIA governs how the registry and registrars process personal information, not whether the record is published. The precise field-level behaviour of ZACR's WHOIS could not be verified from the registry's own documentation, so the safe assumption is that your details are public and privacy services are not available.

Unlike the European country codes, where GDPR produced a split between natural persons and legal entities, .co.za draws no such published distinction: an individual registrant should expect the same exposure as a company, and neither has a privacy product to buy.

Technically the position is better than reputation suggests. DNSSEC is fully deployed and independently verified, with the co.za zone signed and a complete chain of trust from the root through za to co.za. Much older writing about .za predates signing and wrongly assumes it is unsupported. Internationalised domain names are not verified as available; assume ASCII only.

Who .co.za suits, and who should avoid it

.co.za suits any business trading in South Africa. It is the overwhelming local default and outranks .com for local trust, a stronger position than most national extensions occupy at home. It suits African businesses targeting South Africa, and non-South African companies wanting a South African presence, because there is no eligibility barrier of any kind.

Avoid it if you need WHOIS privacy; if you need certainty about long registration terms, which the registry does not clearly publish; if you cannot keep a monitored registrant email current, since both email verification and the transfer model punish that hard; or if your market is not southern Africa, in which case a .co.za signals a locality you do not serve.

Common mistakes with .co.za

• Assuming you need to be South African. You do not. There is no residence, citizenship or company requirement, and buyers regularly pay for local presence or nominee services that serve no purpose whatsoever here.
• Using a throwaway or unmonitored registrant email. New registrations require verification, and failure leads to suspension then deletion. The same address is also the only mechanism for approving a future registrar transfer.
• Asking your registrar for the EPP or auth code. There isn't one. The gaining registrar initiates, the registry emails the contacts, and five days of silence kills the transfer.
• Expecting WHOIS privacy at checkout. It is not generally available, so treat the details you supply as details you are publishing.

How one registry came to own South Africa's namespace

The most striking thing about .co.za is not any single rule but the degree of dominance. ZACR has historically reported that co.za accounts for over 95% of all .za registrations. Very few national namespaces are concentrated that heavily in one second level. In the United Kingdom, .co.uk dominates but sits alongside a direct .uk; in Australia, com.au competes with direct .au. In South Africa the alternatives are marginal: net.za, org.za and web.za are open but have never developed a constituency, and the institutional zones — ac.za, gov.za, edu.za, nom.za — are closed by definition.

Several factors compound. co.za got there first and got there early — UniForum SA took over administration in September 1995 with roughly 400 names, when the commercial internet in South Africa was barely forming, and it has never had a serious rival for general-purpose registration. It is cheap, which matters in a price-sensitive market and removes the incentive to look for a cheaper second level. And it is completely open, so no eligibility gate pushes marginal registrants elsewhere.

The two-body structure explains why guidance about .za is often confusing. ZADNA regulates; ZACR operates. ZADNA is a statutory authority created under the ECT Act of 2002, funded by a levy on registrations, determining what second-level namespaces exist and how disputes are handled. ZACR is the registry business that runs the co.za zone, accredits registrars and processes EPP transactions. Older accounts describing a single South African registry describe a period that ended in the mid-2000s, when administration formally moved on from Mike Lawrie's personal stewardship — the precise handover date is not reliably documented, which is itself characteristic of how informally early .za ran.

ZACR's later trajectory is the part few outside Africa notice. Having migrated co.za to EPP in 2011, it won .africa in partnership with the African Union Commission, launching in 2017, and it operates .joburg, .capetown and .durban under ICANN registry agreements signed in April 2014. A national country-code operator becoming a multi-extension generic registry is rare, and it means the organisation behind your .co.za is a more capable technical operation than its low pricing suggests.