Call To Action

In a bid to create more awareness around COVID-19 Government has called on all .za domain name holders that have an associated website to create a landing page with a visible link to For more details see section 5.1.4 of Regulation No. 43164 published on 26 March 2020.

Frequently Asked Questions

If you have a question not listed below please contact us and we will respond as soon as possible.


It is envisaged that Accredited Registrars will not pay more than they are currently paying. It is envisaged that the Legacy Registrar may in the future increase domain name prices once a competitive Registrar market is established.

ZACR currently applies an Accreditation fee for the zone. Registrars wanting to integrate with the EPP system will have to pay the Accreditation Fee prior to being provided with access to the OT&E server.

Yes, they can. There is no distinction drawn between domestic and foreign entities as far as access to the new Registry System is concerned. Any foreign Registrar is bound by the same policies and procedures as domestic Registrars, including (for example) the exclusive jurisdiction of the South African courts, and the inclusion of the minimum terms and conditions for Registrants.

From a costing perspective the only amount that has to be paid to the Registry is a once-off Accreditation Fee. The purpose for the fee is as follows:

- Administrative and technical procedures to create and provide constant, around the clock access to a test and development environment that matches the Production environment
- Creation of financial and technical accounts that will be used if Accreditation is obtained
- Provision for document and legal procedures for Legal Accreditation
- Provision for Technical Support during the Technical Accreditation Phase
- Set off costs incurred by the Registry to accredit a registrar

The cost of the Accreditation Fee is easily outweighed by the financial benefits of becoming accredited, taking into consideration the following price difference between the Legacy System and the new EPP system:

- The price of registration on the Legacy System will be increased to R65.88 per domain (excl VAT) as of 1st March 2013
- The current cost of registering a domain on EPP is R35 (excl VAT) which is lower than the current Legacy registration price, with no proposal to increase the tariff
- Payment for domains is done automatically through our systems and prepaid model, invoicing every week rather than monthly

Taking the billing and the changes to come into consideration, a registrar can easily recuperate the accreditation fee from the savings by switching to EPP. An example is as follows:

200 Domains costing R35 (EPP) = R7000 p/a
200 Domains costing R42 (Legacy) = R8400 p/a
200 Domains costing R65.88 (Legacy from 1st March 2013 = R13,176 p/a

From the above example, the Accreditation fee can be recuperated within the first year of operation, with additional savings, assuming a minimum of 200 sponsored domains.

Alternative forms of income can also be obtained through a reseller model. If a registrar has obtained Technical Accreditation, they can then resell their system or provide services through their system at a competitive rate to new or existing registrars and/or resellers. There are numerous Accredited registrars on the market who already offer reseller services at competitive prices to registrars that are unable to pay the Accreditation Fee or develop their own system. The full list of accredited registrars may be found here.

Please also note that once a domain has been moved over to EPP or has been registered on the EPP system, it cannot be transferred back to the Legacy System, allowing registrars on the EPP system to have a faster, more reliable, response automated system for registering and maintaining domains around the clock.

The ZACR does not implement differential Value Added Taxation (VAT) on any fees payable by national and foreign entities within the .za domain name space. Such fees include but are not limited to domain name fees and Accreditation Fees.

This is consistent with prevailing South African legislation governing revenue issues as applied to the nature of the services rendered by the ZACR.

This means that national and foreign entities are charged domain name fees subject to VAT at the standard rate of 14%. This may be revisited in the future if the 'place of supply' rules, which are under consideration in many jurisdictions and which provides that supply is deemed to take place where the recipient is, are adopted within the South African regulatory framework. Until such a time, all domain name fees will attract VAT at the rate prescribed above.



You can start your Technical orientation after you have completed the initial Registrar application process and made the itintial Accreditation Fee of ZAR 5000 (Five Thousand South African Rands). A username and password will be issued for the OT&E server upon payment. For information on how to make a payment, please see our banking details section

Please view the Banking Details section here for all the information regarding payments and payment queries.

As a registrar on the EPP system, you have your own Contact object. This allows you to update that contact object like any other Contact you have created on the system. To change your registrar information, please perform a Contact Update command and use your username in the contact:id element. The command can be found here and the order for parent/child elements can be found here

An EPP password may be changed through a Contact Update command. Alternatively it can be performed mauch easier through the Login Command as outlined here.

Only on completion of the accreditation tests will registry accreditation be considered. The Technical Accreditation criteria are outlined here. You can check your progress by clicking at the top right hand of the page on the Registrar Panel heading. Until Technical Accreditation is complete, a status of [PENDING ACCREDITATION] will be shown, and there will be red crosses next to each test. If a test has been passed, the red cross will become a green tick mark indicating completion of test. Once all tests have been passed, login and send a request to Tech Support to have your SSL Certificate and originating IP Address configured. Once uploaded, an e-mail will be sent to your account providing you with a new username and password for the live system.

The new system will generate Invoices and Credit Notes on a weekly basis.
These are all avilable for download from your Registrar Panel under the link "Financial Docs".

Statements are not yet available on a routine basis. If you would like a statement, please request one by creating a ticket here.
Please see below examples of an Invoice as well as a Credit note:

Credit Note

The CSV files are statements of all invoices and credit notes for a given period. The filenames are in the format:
<rarname>-<period>-<statement number>.csv
Eg: examplerar-201228-000009.csv
"rarname" is the username of the registrar used to log into EPP.
"period" is the name used for the financial period in question. In the case above. Its the 28th week of 2012.
The final number indicates that this is the 9th financial statement available for "examplerar".
For processing, "statement number" is the best way to ensure that all transactions have been captured.
The csv file itself is a standard "comma separated values" file. It can be opened using Excel as well as various other libraries that can process CSV files.
The columns in the file are as follows:
Type -- Either "invoice" or "refund"
Number -- The invoice or credit note number, Eg: INV0001009
Date -- The date the invoice was generated
Product Name -- The product name used for the billing, currently one of: co.za_renew, co.za_transfer, coza_new
Domain -- The domain name effected, Eg:
Description -- A text description of the transaction. Eg: "Time: 2012-07-28 19:21:15, MessageID: EXAMPLE-12345678". The example includes the time the transaction was recorded on the EPP system and the clTRID transaction id
Unit Price -- The value of the transaction in ZAR, excluding tax
Tax -- The value of the VAT in ZAR  Eg: 4.90
Line Total -- The amount including tax, Eg:  39.90

Example CSV file: Download

The EPP system makes use of the pre-paid model for billing. This means that every Accredited Registrar will be provided with a billing account by the registry, which must maintain a positive balance in order for new domains to be registered and renewed.

Money therefore has to be present in the Accredited Registrar's account prior to any billing action occurring.

The minimum payment required is R2000, the money will only be allocated to the registrar's account once it reflects on our statements. Payment must be made into the correct account to avoid incorrect allocations / delays. Banking details are available here.
Once paid, the money is then available for registrations and/or renewals.

Once you have registered/renewed a domain name the fee due is deducted from the balance on your account.  Every Monday you will receive an invoice for all the transactions on your account for the preceeding week.
If there is no money in your account you wont be able to transact on the EPP system.

The ZACR does not provide a process for bulk transfers from Legacy to EPP. This is to protect the rights of the registrant in deciding whether to stay on the Legacy system or migrate their domain to the management of the EPP system. The current allowance for transfers is 500 concurrent Legacy transfer requests.
Domains that have delegated nameservers that are not in the CO.ZA zone must be updated with the relative registry in accordance to their specification and interface. Please note that due to caching issues, some changes in the IP addresses might take longer than others.


Domain, Contact and Host Objects

Yes it can. A Cancel Pending Action can be performed, canceling the Pending Suspension or Deletion. If the pending suspension was due to domain expiry, canceling the pending action will result in domain renewal and standard fees will apply. 
Please click here to see how to perform the command.

The test system is used by registrars for testing their systems against the registry. Domains are often created without nameservers being configured for these domains. This causes the test system to repeatedly check that the nameservers have been configured causing additional stress on the test system and on the network resources. It has been decided to delete any domains which have been waiting for nameservers to be configured 7 days after domain creation. An appropriate poll message will be queued.

Nameserver checks will only happen for the duration of a week due to unnecessary resource consumption. If the nameservers are not responsive after a week, please perform a Domain Update command to remove and reapply them; the domain will then be unsuspended upon a successful check.

If a registered domain has passed 10 nameserver checks, it will keep its registration statuses until the nameservers are updated to working ones. If the registered nameservers are not working after the 10th try, please issue an EPP Domain Update request whereby the registered nameservers are added and removed in the same request.

If the nameservers are still not resolving even though changes were made to the servers, please use the following free online tool available at INTODNS to verify the current status of the domain. The ZACR does not endorse the facilities at INTODNS.

The reason for a domain name not resolving is due to its nameservers not being properly configured.
Please ensure that the assigned nameservers are authoritative for the domain.

If a domain has a status of clientHold, serverHold or inactive, then the domain name has not been resolved. If any of the 3 statuses exist, the domain will not be published.
If it is a nameserver failure, a poll message will be queued after a week indicating that the nameservers are not responding.

The creation of a domain using "admin", "billing" and "tech" contact types is not supported and a result code of 2306 will be returned by the server. is a thin registry where admin, billing and tech contacts must be maintained by the respective registrar.

When trying to register a domain, certain constraints are put in place to ensure that domain names are registered properly. If attempting to register a domain name and the value did not pass the regex check, it means that something in the domain name is not accrording to required specification. To avoid the error, please make sure that the domain name is as required. For more information on what the regex is and how a domain name should look when registering it, please see our Domain Constraints.

Poll messages older than 30 days will be marked as "expired" on the registry system, meaning that they will not be able to be collected from the queue. Please collect all poll messages in a timely manner so as to avoid messages becoming stale. 

If a domain has expired, it enters the deletion phase. To re-instate the domain, a Cancel Pending Action has to be performed. Please see here on how to perform the action.
Please take note that if you cancel a Pending Deletion or Pending Suspension event leading from a domain expiry, the domain will be renewed and your registrar account will be charged.

Closed Redemption is a state that a domain enters once it has expired and gone through the Deletion Phase. The Closed Redemption Phase lasts a total of 20 consecutive days from the end of the Pending Deletion Phase, and is terminated if the domain is reinstated. The process is as follows:

1. The domain will expire
2. The domain will go through the Pending Suspension and Pending Deletion Phases
3. After the Pending Deletion phase is over, the domain enters the Closed Redemption Phase
4. In the Closed Redemption Phase a domain can be reinstated at the cost of the Closed Redemption Fee
5. If a domain is not reinstated in the Closed Redemption Phase, it will be deleted at the end of the phase

Please take note of the following consideration related to Closed Redemption:

* A domain may be reinstated at the cost outlined in the respective name space Fee Schedule.
* To reinstate the domain an EPP Renew Command may be issued or an EPP Cancel Pending Action where the action is PendingClosedRedemption
* Domains that have been reinstated during Closed Redemption will reflect with the product code "co.za_closed_redeem" in the invoices
* A domain will not be published when in Closed Redemption
* A domain will have the statuses "inactive", "pendingDelete", "serverHold", "serverTransferProhibited" with the message "Domain in closed redemption"
* A domain may only be reinstated by the current sponsoring registrar
* A domain will not enter the Closed Redemption Phase if a manual EPP Delete command was issued prior to its expiration date
* A domain may be manually deleted through instruction from a third-party

To add credit for either of the provisioned test accounts please log into your registrar panel and use the "Add Test Credit" button.

The migration of domains from Legacy creates a duplicate of the existing contact on the EPP system.
Some Contact objects have both "loc" and "int" address formats assigned to them in the Legacy System. This was due to an update performed towards the end of 2010.

From the update, the contact is migrated to EPP with both "loc" and "int" address formats.
As part of the EPP specification, all notifications get sent to the Internationalised contact information (int). If internationalised information does not exist for the contact, the system will use Localised information by default (loc).

This means that there exist some contacts that have 2 different names associated, so the email sent out to the registrant will address a different individual. Please note that the email address will never be affected, only the addressing name.

If this has occured, please "blank" the Internationalized information as outlined here.

The ZACR stores all time information in SAST in its local databases. This is represented as "UTC+2 hours" . All dates in responses are represented in ZULU format (UTC).



SSL is required for the Live server and a certificate will need to be provided via uploading through this portal.
The server requires dual SSL authentication, thus a certificate is required (X509).
The certificate can be either self signed or verified by a Certification Authority.

Upon completion of Technical Accreditation you will be prompted with instructions on how to upload your SSL Certificate.

The OT&E server is SSL enabled but it is not a requirement. If however you do wish to begin your integration using SSL from the beginning, please submit a request for SSL Certificate inclusion on the OT&E server by creating a ticket and attaching your certificate here.

Please see the links below for OT&E and Production Server Certificates if required:

OT&E Server Certificate

Co.Za Production Server Certificate;

Org.Za Production Server Certificate

Web.Za Production Server Certificate ; Intermediary Certificate

Net.Za Production Server Certificate

An SSL certificate is required for live server access. The certificate must be in X509 certificate format. Please do not submit a private key or a combination of private/public key.
The X509 certificate may be signed by a Certification Authority or the certificate can be self signed. An example of a certificate can be seen by downloading the file below:
Example Signed SSL X509 Certificate

If the certificate that was provided has been loaded and installed on our end but there are still some SSL problems when connecting to our server, please log a ticket here and include the results of the following command:
openssl x509 -noout -in CERT_FILE -fingerprint -md5
where "CERT_FILE" is the certificate that you are using to connect.

Minimum SSL Requirements
The minimum requirements include:
1. A key strength/length of 1024 bits
2. A maximum key expiry date of 5 years from creation with a minimum of 1 year

Recommended SSL Requirements
The recommended requirements include:
1. A key strength of 2048 bits
2. A key expiry date of 1 year from creation

An EPP session will persist for a maximum of 24 hours.

At most 2 concurrent sessions may be established. Across both connections, a cumulative token bucket of 200 tokens is available every 20 seconds. If the available tokens expire, a mesage stating "No remaining command tokens. Please wait Xms" will be returned, where X is in milliseconds. Another command cannot be issued until X milliseconds has expired.

If the connection is idle for more than 20 seconds a disconnect will occur.
To keep a connection open, simply send through a 'Hello' EPP command to the server.

The OT&E server does not currently have any form of whitelisting of IP addresses. Testing can be done by any registrar that has been provided with an OT&E username and password.

The live server has a strict Access Control List (ACL). To get an IPv4 address or IP range ( /24, /32) whitelisted, please provide the IP address as well as its range when prompted for after completion of Technical Accreditation. If your incoming requests are from an IPv6 server, please also provide the IPv6 address as well as its IP range ( /128 or below).

Please note that all provided IP addresses must be static.

The port 43 Whois service can be accessed through .

Idempotency is the ability for an EPP system to handle duplicate requests but not duplicate the processing. All EPP commands are atomic, meaning that there is no partial success or partial failure. 
This means that no message may have the same clTRID as another message.


1. Command A (Domain Update) is sent with clTRID XYZ
2. Command A returns result of 1001.
3. Command B (Domain Transfer Request) is sent with with clTRID XYZ as well.
4. Command B returns result code 2308 (Conflicting Message IDs)

Due to the same clTRID of XYZ, Command A will now have another result appended to it, 2308. This means that Command A will be successful, but the Accreditation Checker will only pick up the result of 2308 and not the initial 1001.

To make sure that no idempotency occurs, a registrar may choose to not send through clTRIDs with their requests and the server will automatically assign a unique clTRID to the message.

The following is an example of how to generate an SSL Certificate. 
The example assumes the use of a UNIX computer with command line access and opensslinstalled. 
Run the following in the command line:
1. openssl genrsa -out epp.key 1024
2. openssl req -new -x509 -key epp.key -out epp.crt -days 1095
3. cat epp.key epp.crt > epp.pem
The 1st command creates your private key.
The 2nd command creates the public certificate that you will upload to our portal.
The 3rd command creates the .pem file that the EPP example files make use of.
Once the key has been generated and you have been prompted by our system, upload the created epp.crt file. The epp.crt file is your public certificate.  
DO NOT send us the .key . Uploading this file will reveal your private key, rendering the use of SSL keys null. If the file is provided, a new key will have to be generated.
To create an SSL Certificate using a Windows computer, please install openssl from here
Run the following commands in the command line:

1. openssl  genrsa -out epp.key 1024
2. openssl req -new -x509 -key epp.key -out epp.crt -days 1095
3. type epp.key > epp.pem
4. type epp.crt >> epp.pem

Once the key has been generated and you have been prompted by our system, upload the created C:\OpenSSL-Win32\bin\epp.crt file.

Any client software that doesn't loop until the entire EPP payload size and payload is read will encounter an 'unpack' error due to the fact that the client SSL libraries have not emptied the buffer correctly.
For more information on how to debug this error please see the OpenSSL Libraries.

The following represents the issue with PHP code:

function read() {
     $lenstr = fread($this->socket,4); #Get the size of the complete EPP Data Unit
     if ($lenstr === false){
       throw EPPTransportError("Socket error");
     $bytes = unpack("Nbytes", $lenstr);
     $bytes = $bytes['bytes']; #PHP unpack returns an assoc array
     $data = fread($this->socket, $bytes-4); #1st 4 bytes have already been read
     if ($data === false){
       throw EPPTransportError("Didn't recieve any XML data?");
     if (strlen($data) != $bytes-4) {
       throw EPPTransportError("Expected $bytes-4 Got " . strlen(data)." bytes instead" );
     return $data;

To fix the issue, please use the PHP code below:

function read() {
     $headerstr = "";
     while (strlen($headerstr) < 4)  {
        $lenstr = fread($this->socket,4 - strlen($headerstr)); #Get the size of the complete EPP Data Unit
        if ($lenstr === false)
          throw EPPTransportError("Socket error");
        $headerstr = $headerstr . $lenstr;
     $bytes = unpack("Nbytes", $headerstr);
     $bytes = $bytes['bytes']; #PHP unpack returns an assoc array
     $data = "";
     while(strlen($data) < ($bytes - 4 ) ) {
        $tmpdata = fread($this->socket, ($bytes-4) - strlen($data)); #1st 4 bytes have already been read
        if ($tmpdata ===false)
          throw EPPTransportError("Didn't recieve any XML data?");
        $data = $data . $tmpdata;
     return $data;

When rolling or switching SSL certificates please log onto the Registrar Panel, access the specific SLD or gTLD you want to roll the certificate of click on "Manage/Upload Certificates on the left-hand side.
Once uploaded, both certificates will be active for a period of 24 hours, after which the old certificate will be deleted and the rollover will be complete. Rolling over a certificate will only roll the certificate for the selected SLD/gTLD.

Issues with connectivity can happen due to multiple reasons including socket errors, closed ports, SSL authentication, servers being offline, and code bugs.
If you experience issues connecting to either the OT&E or Production Server, please follow the steps below for a debug of the connectivity issues. If at the end of it you are still unable to verify the problem, please create a support ticket and provide us with all the output from the specified commands as well as which step you encountered an error.

Step 1: Testing internet connectivity to servers

ping HOST

Where HOST is the server you are trying to connect to. If packets are getting sent through and there is no packet loss, it means that the server is online and the error lies somewhere else. If you cannot PING, there is most likely an internal error on your network.

Step 2: Identifying correct routing and IP whitelisting

traceroute HOST (tracert HOST for Windows)

Where HOST is the server you are trying to connect to.

Step 3: Connecting to our port

telnet HOST PORT

Where HOST is the server you are trying to connect to, and PORT will be 3121. This will test if port 3121 is open and allowing information to flow through it to our port. If you cannot connect to the port using telnet it means that the port is not opened for communication. Please check the permissions on your firewall if you have one active.

Step 4: Connecting using SSL

openssl s_client -connect SERVER:PORT -cert DOTCRTFILE -key DOTKEYFILE

The above applies to all registrars on the Production server, and only registrars who have provided SSL certificates for the OT&E server.
The above command uses the opensource "openssl" libraries to connect to our server. If you cannot connect to the server using the abovementioned command, it means that either you have not provided us with your key (so we cannot accept the SSL handshake) or you have provided the incorrect files in the command. To resolve this, please make sure that the following has been completed:

1. Our server key loaded on your side if your server requires SSL authentication from our server. The file can be downloaded further up in this FAQ.
2. You have provided your certificate and private key on connection, as our servers require Dual SSL. That is usually the .pem file. Please see here on how to generate keys. Different operating systems and server configurations require different files. Please make sure that when using a specific software, the correct keys and files have been loaded correctly.

Step 5: Debugging of code

Please note that we do not provide any form of support for specific code or programming languages.

A "2001" result code means that there is a syntactical error in the requesting XML. The result message will contain the line number and character that is at fault, as well as an indication of what the requirements are compared to what was provided.

The registry makes use of various EPP response codes to represent the meaning of "Success", "Failure" and "ERROR". The following are the general guidelines for the codes:

1000: A result code of 1000 indicates immediate success. This means that the command that was performed has been considered and its effect was immediate. For example, a Contact Create or a Transfer Cancel.

1001: A result code of 1001 indicates the success of a command, of which the eventual result is pending processing or awaiting approval. For example, a Domain Update to change the registrant, or a Transfer Request that must now wait for voting. Responses of 1001 will always provide a message on the poll queue for collection. The message indicates the eventual success or failure of the result of the command.

2xxx: A result code in the 2000 range, such as 2304 or 2301, indicates an failure in the processing of the command. This is always indicitive of either a status blocking the command or the information provided being incorrect. For example, a nameserver failure for a Domain Update, or an incorrect date specification for a Domain Renew. All 2xxx results are followed by an indepth message explaining why the failure happened.

: A result code of 2400 is an ERROR. If you ever receive a result code of 2400 please create a support ticket and notify the registry as soon as possible, including in the ticket as much information as possible relating to the task that was performed to obtain a 2400 result.

If you are attempting to connect to the server but are only receiving several Bytes and not the server greeting, please make sure that you are reading the response correctly.

Every connection (to the OT&E or Live server) requires that the socket be wrapped, regardless if you are providing an SSL certificate or not. Please ensure that you are wrapping the socket.



The existing registration system will be viewed and treated as a Legacy Registrar. This effectively means that UniForum SA will be fulfilling the role of both Registry (dealing with Accredited Registrars) as well as Legacy Registrar (dealing with Registrants). In practice this means that for all domain records on the existing registration system, UniForum SA will be tagged as the default Legacy Registrar. New Accredited Registrars will then be able to move their existing domain names away from the Legacy Registrar by means of the Registrar Transfer Procedure.

The renewal of domains on the EPP system happens in one of two ways:
  1. EPP Renew Command
  2. Autorenewing of Domains

EPP Renew Command
The EPP Renew command extends the expiry date of a domain by 1 additional year from date of expiration.
When issued and successful, the billing for the renewal will be done instantly against the registrar's account. The renewal will then reflect on the invoice that gets sent out on the following Monday. This will reflect on the invoice with a product code of "coza_renew" next to the domain name.

Autorenewing of Domains
When a domain is registered on the EPP system, it has an Autorenew Flag set to it. The flag is automatically set to "True".
This means that when the domain reaches its expiry date it will automatically be renewed within a 24 hour period for an additional year. The action of Autorenewing automatically charges the account of the registrar. The autorenewal will reflect on the invoice that gets sent out on the following Monday. This will reflect on the invoice with a product code of "coza_renew" next to the domain name.

If the Autorenew Flag is set to "False" for a domain then upon expiry the domain will enter the Pending Suspension Phase.

. A domain can not be renewed using the EPP Renew command if there are no available funds in the registrar's account.
2. If a domain has the Autorenew Flag set to "true" and it expires but the registrar has no available funds, the domain will enter a Pending Suspension Phase.
3. Sending the EPP Domain Renew command while a domain is in the Suspension/Deletion Phases will renew the domain, extend the expiry date by 1 year and charge the registrar's account.

CO.ZA is a "thick" model registry. We maintain the rights and related information of the registrant within a central registry repository. By doing this, we effectively maintain the minimum required information to allow the continuation of the domain name in the event that a sponsoring registrar cannot be reached. Furthermore, we delegate the responsibility of the associated admin/tech/billing contacts to the registrar. Our WHOIS is also representative of a thick registry as it displays information pertainng to the registrant, domain statuses (including autorenew), hosts, etc. 

In contrast, registries that support a "thin" model only store the domain and name server information within the registry; contact information is stored at each registrar. As a result, each registrar must operate its own WHOIS server in order to provide access to this information.


No. If you want to become an Accredited Registrar you will need to apply to the Registry.

You can follow the process outlined in the Published Policies relating to Transfer between Registrars.

You are able to establish a reseller relationship with any Accredited Registrar which offers reseller services. There is no need to become a Registrar to provide registration services in

The restrictions on when domains are eligible for transfer from the legacy system is due to a fundamental difference between the legacy system and the EPP system:

The legacy system only invoices for domains at the end of the month in which the registration occurred, while the EPP system is a real-time billing system, with invoices being batched on a periodic (weekly) basis.

Unfortunately, because the systems are separate loosely coupled systems, the only way to ensure that we do not double bill is to put this restriction in place.

The facility at may be used to obtain domain information sorted by registration (anniversary) date to see which domains are due for renewal in the month before they were registered, ie. before these domains fall into the billing cycle of the legacy system.

The OT&E server acts as a platform for quick testing of system integration. For this purpose the OT&E server timing for Grace Period, Delete and Update commands are as follows:
   1. Grace Period: 7 minutes
   2. Update Period: 5 minutes
   3. Suspension Period: 5 minutes (Domains Only)
   4. Deletion Period: 5 minutes (Domains Only After Suspension Period)
   5. Closed Redemption Period: 20 minutes (Expired Domains Only After Deletion Period)
   6. Transfer Period: Immediate, up to 5 minutes depending on voting (Domains Only)

For the Live environment the timings are as follows:
   1. Grace Period: 7 days
   2. Update Period: 5 days
   3. Suspension Period: 5 days (Domains Only)
   4. Deletion Period: 5 days (Domains Only After Suspension Period)
   5. Closed Redemption Period: 20 days (Expired Domains Only After Deletion Period)
   6. Transfer Period: Immediate, up to 5 days depending on the voting (Domains Only)

The ZACR does provide an RSS Feed for all its Noticeboard messages, keeping you up to date with all announcements regarding changes, updates or any general news the ZACR thinks you should be aware of.
The feed is available at


Last update: 16-05-2018 03:58:04

festive season

As the end of the year approaches, please keep in mind the following information to avoid any frustrations over the holiday period.


Closure Date:

Our offices will be closed from the 21st of December 2020 and will reopen on the 4th of January 2021. We will have skeleton staff on standby to attend to urgent customer queries.


Contact details:
EPP and Legacy Support:
EPP and Legacy Accounts: 


Happy holidays and let us continue to maintain social distancing as we approach this peak time!




Technical Support

All issues and questions relating to the EPP Registry Registrar System must be raised in the Contact/Support pages through the Registrar Portal. This is to ensure that our support department tracks and addresses all issues. Log in to the Registrar Portal and submit a support request online.


Registrar Noticeboard

Click here for the latest status updates.