Add to Preferred Sources
A domain transfer moves your .co.za domain from one accredited registrar to another — it does not touch your DNS zone, your website files, or your email configuration by default. Understanding the full cost of running a South African website means knowing which pieces are linked and which are independent, and your registrar and your DNS hosting are routinely bundled together when they actually work better decoupled.
South African businesses on Google Workspace, Microsoft 365, or cPanel-hosted mail frequently discover after a transfer that email has stopped — not because the transfer broke it, but because the old registrar was also serving their DNS zone. Move the domain without recreating those records at the new host, and the MX records that tell the internet where to deliver your mail simply vanish.
That is the distinction this guide resolves, alongside the exact steps for a co.za domain transfer South Africa operators need — under the ZARC EPP system — and the timing rule that blocks more transfers than anything else.
This post covers the complete process: what a registrar transfer actually changes, the three scenarios that determine your email risk, the step-by-step ZARC procedure, and the DNS records to screenshot before you begin. If you are moving a domain for the first time, read this before you initiate anything.
Quick Answer
A domain transfer changes which registrar manages your .co.za domain — it does not automatically change your DNS, hosting, or email. Email breaks only when a nameserver change is made without first recreating DNS records (especially MX, SPF, DKIM, and DMARC) at the new location.
The ZARC process includes removing the transfer lock, obtaining an EPP authorisation code, submitting the request at the new registrar, and approving a voting email within 24 hours. The full process takes up to 48 hours — allow 5–7 working days. You cannot initiate a transfer within 60 days of registering, last transferring, or changing your registrant contact details.
Jump to a Section
Rebuilding a site around a new domain?
Send us your current setup and we will identify the DNS and hosting changes needed before you start — saving you the email outage most operators discover after the fact.
Get a Free Pre-Transfer ReviewWhat Moving Registrars Actually Changes — and What It Doesn't
A domain transfer changes one thing: the registrar on record with ZARC (ZA Registry Consortium), the non-profit body that manages .co.za, .net.za, .org.za, and .web.za domains. ZARC holds a delegation table pointing your domain to specific nameservers. That delegation table is not touched by a registrar transfer — it stays exactly as it was until you explicitly update nameservers.
| What a Registrar Transfer Changes | What It Does NOT Change |
|---|---|
| Which company manages your domain billing and renewal | Your nameserver delegation at ZARC |
| Where you log in to update domain contact details | Your DNS zone records (A, MX, CNAME, TXT, DKIM) |
| Which control panel you use to unlock/lock the domain | Your website hosting or web server |
| Which registrar charges your annual renewal fee | Your email configuration or mail server |
The confusion arises because most SA hosting packages bundle the registrar, DNS hosting, and web hosting into one account. When you "transfer your domain" to a new registrar, you leave behind the DNS zone that was sitting in the old account — including the MX records your email depends on.
Key Distinction
Email depends on MX records in your DNS zone, not on who your registrar is. The registrar transfers the domain's administrative control. DNS records live wherever your nameservers point. These are two separate systems that often look like one.
Three Transfer Scenarios — and Which One Risks Your Email
Which domain transfer scenario you are in determines your email risk and the actions you need to take before you touch anything. The table below maps the three common situations to their actual risk level and the required sequence of steps.
| Scenario | What You're Doing | Email Risk | Required Pre-Transfer Actions |
|---|---|---|---|
| Registrar change only Nameservers stay at current registrar or a third-party DNS host | Changing who bills you for the domain; nameservers unchanged | Low — DNS zone remains live | Confirm the current registrar will keep DNS active after the domain leaves. Some cancel the DNS zone on departure. Verify before initiating. |
| Registrar + same-host DNS move Domain and DNS both move to the new registrar's nameservers | Changing registrar and switching DNS to the new registrar's servers | High if records aren't recreated first | Screenshot every DNS record. Recreate them at the new registrar's DNS before switching nameservers. Lower TTLs to 300 seconds 48 hours before the nameserver switch. Verify MX resolves at new nameservers before proceeding. |
| Registrar + independent DNS host Domain moves to new registrar; DNS stays at or moves to a separate host such as Cloudflare | Separating registrar from DNS hosting — the recommended long-term setup | Low if done in the correct order | Set up DNS zone at the independent host first. Lower TTLs. Point nameservers at the independent host. Confirm all records resolve. Then initiate the registrar transfer — by this point, email is already running from the independent DNS and is unaffected. |
The .co.za Domain Transfer Process, Step by Step
A .co.za domain transfer follows the ZARC EPP process, which includes a mandatory voting window and a transfer lock mechanism introduced in April 2025. The voting mechanics below are documented from ZARC's published EPP transfer framework; for EPP-to-EPP moves between two accredited registrars, the exact sequence is similar — confirm the specific steps with your receiving registrar before initiating.
- Check the 60-day restriction. You cannot initiate a transfer within 60 days of first registering the domain, completing a previous transfer, or making a change to your registrant contact details (name, company, or email). A WHOIS contact update can trigger an additional 7-day lock at the registry. If your domain is inside this window, wait it out — there is no override.
- Screenshot your DNS records. Before anything else, log into your current registrar and record every DNS entry: A records, MX records, SPF TXT record, DKIM TXT record, DMARC TXT record, CNAME records, and any other TXT records. You will need these if you also change nameservers. See the section below on which records to capture.
- Remove the transfer lock. Since 1 April 2025, ZARC enables the Domain Transfer Lock on all .za domains by default — mapped to the standard EPP clientTransferProhibited status. This security feature blocks any transfer request at the registry level. Log into your current registrar's control panel, find the domain settings, and disable the lock. Most SA registrar panels label this clearly, and the WHOIS status will update within minutes.
- Request your EPP authorisation code (TAC). Once unlocked, request the Transfer Authorisation Code from your current registrar. This is a unique alphanumeric string proving your ownership. It has a 14-day validity window once issued — initiate the transfer promptly. Some SA registrars deliver this via email; others show it directly in the control panel.
- Initiate the transfer at the new registrar. When you transfer domain to new registrar, log into the new provider's control panel, enter your domain name, and submit the request using the TAC when prompted.
- Approve the ZARC voting email. ZARC sends a voting email to all contacts on the domain's WHOIS record — registrant, administrative, billing, and technical. At least one of those four contacts must cast an Accept vote within 24 hours, and no contact may cast a Deny. A single Deny from any contact cancels the transfer. If nobody votes at all, the transfer also fails — check spam folders for all four contact addresses. Non-response by the registrant alone does not cancel the transfer if another listed contact has voted Accept. If any contact email address is outdated, update it at your current registrar first (then wait out the 7-day lock period before attempting the transfer).
- Wait for completion and update nameservers if needed. Once approved, the transfer completes within 48 hours. Allow 5–7 working days for full resolution across all DNS systems. If you are also changing nameservers (Scenario 2 or 3 above), do that as a separate step — do not change nameservers and transfer the registrar simultaneously.
The DNS Records to Screenshot Before You Start
Capturing your current DNS configuration before any transfer is the single action that prevents the most common post-transfer problems. These are the records you need, what each one does, and why losing it causes the specific failure it causes.
| Record Type | What It Does | What Breaks If Lost |
|---|---|---|
| MX (Mail Exchange) | Points inbound email to the correct mail server | Inbound email stops. Senders receive bounce or delivery failure notifications. |
| SPF (TXT record) | Specifies which servers are authorised to send email from your domain | Outbound email from your domain may be rejected or marked as spam by recipients. |
| DKIM (TXT record) | A digital signature that authenticates outgoing email | Email authentication fails. High risk of deliverability issues, especially with Google and Microsoft mail. |
| DMARC (TXT record) | Policy governing how recipients handle mail that fails SPF/DKIM checks | Authentication reporting breaks; unauthenticated mail may be rejected depending on policy. |
| A record | Maps domain to your web server's IP address | Website goes down. |
| CNAME records | Aliases for subdomains (e.g. mail, webmail, www) | Subdomains stop resolving — including webmail portals. |
If you use Google Workspace or Microsoft 365 for email, your MX, SPF, and DKIM records were set by the provider during initial setup — they are not stored at your web host and must be re-entered at the new DNS location verbatim. The email domain authentication checklist covers what each record should look like and how to verify it is resolving correctly after a change.
Lowering TTL — the One Technical Step That Prevents Hours of Downtime
TTL (Time to Live) tells the internet how long to cache a DNS record before checking for updates. A common default is 3,600 seconds (one hour) or 86,400 seconds (24 hours). If you change nameservers with a 24-hour TTL, the old records stay cached globally for that full period — meaning email and website disruptions persist even after the new records are correct.
Lower your MX, A, and TXT record TTLs to 300 seconds (five minutes) at least 48 hours before switching nameservers. After the change is confirmed, raise TTLs back to a normal value. MX record propagation typically takes 30 minutes to 4 hours once the TTL is low; NS record propagation takes 24–48 hours regardless.
For a full walkthrough of how DNS works on a South African business website, see DNS basics for business owners.
What Can Block a .co.za Transfer
Several conditions will cause a .co.za domain transfer request to be rejected outright or automatically cancelled. Check all of these before initiating.
- 60-day restriction: The domain was registered, last transferred, or had its registrant contact changed within the past 60 days. No override exists — wait until the window passes.
- Transfer lock still active: The clientTransferProhibited flag is enabled (default for all .za domains since April 2025). Remove it at your current registrar before initiating.
- Anniversary Period: The domain cannot transfer during the three days before its expiry date through to the 6th of the following month. Transfers attempted in this window are automatically blocked by ZARC.
- Domain not yet one month old: Domains in their first month of registration cannot be transferred.
- Outstanding renewal fees: Unpaid domains are blocked from transfer and may enter ZARC's deletion process. Renew before attempting to move.
- Registrant email is unreachable: The voting email goes to the address on WHOIS. If that address is defunct — a previous employee's mailbox, for example — you will not receive the approval link. Update the registrant email first, but remember the 7-day lock that a WHOIS change triggers.
- Expired or wrong TAC: The Transfer Authorisation Code has a 14-day validity window. If you wait too long between requesting the code and submitting the transfer, request a fresh code.
If your website is being rebuilt on a new domain as part of the process, the costs and dependencies are covered in detail on the website cost South Africa guide. The domain itself is usually one of the smaller line items — the DNS configuration that keeps everything else working is where the real risk sits.
Planning a site rebuild or platform migration?
Tell us your timeline and we will map the domain, DNS, and hosting dependencies before your launch date — so nothing goes live until the transfer is confirmed clean.
Get a Launch-Ready AssessmentWhy South African Businesses Choose Growth Pulse Media
Growth Pulse Media handles domain moves, DNS configuration, and website builds as a single managed sequence — so the DNS records are verified live before nameservers switch, not discovered missing after the fact. The operators who get into trouble are usually mid-build, updating nameservers for a new site, and finding afterwards that the MX records didn't follow. At Growth Pulse Media's web design service, DNS verification is part of every build — not a separate line item or an afterthought.
Growth Pulse Media is run by Dirk van Greuning, who built and scaled a large South African ecommerce business before founding the agency. That background means the advice here comes from having paid the invoices, managed the registrars, and dealt with the support tickets — not from a theoretical checklist. All work is executed in-house, with a limited client load that keeps senior attention on every project. Platforms we work with regularly include Xneelo, Domains.co.za, Afrihost, Cloudflare, Google Workspace, and cPanel hosting environments.
What to Ask Any Agency Handling Your Domain Transfer
Before handing over access: ask explicitly whether DNS records will be documented and recreated before nameservers switch, and who is responsible for verifying email is live after the change. If you don't get a clear "us" as the answer, handle the DNS documentation yourself first.
Who This Is NOT For
Not sure which scenario applies to your domain?
Share your current registrar and hosting setup and we will tell you exactly which transfer path carries the least risk before you start.
Get a Free Setup ReviewFrequently Asked Questions
Does a domain transfer break email in South Africa?
A registrar transfer alone does not break email. Email delivery depends on MX records in your DNS zone, not on which company holds the registrar contract. Email breaks when a nameserver change is made at the same time as the transfer without first recreating DNS records — specifically MX, SPF, DKIM, and DMARC — at the new DNS host. If your nameservers are not changing, your email is not at risk.
How long does a co.za domain transfer take?
The ZARC voting window runs for 24 hours after the transfer request is submitted. Once approved, the transfer itself completes within 48 hours. However, DNS propagation across the internet can add further time — allow 5–7 working days from initiation before expecting everything to resolve globally. This timeline assumes the domain is not inside a 60-day restriction window and the transfer lock has been removed.
What is the .co.za transfer lock and how do I remove it?
The Domain Transfer Lock — mapped to the standard EPP clientTransferProhibited status — was introduced by ZARC in April 2025 and is automatically applied to all .za domains. It prevents any unauthorised transfer request from being processed at the registry. To remove it, log into your current registrar's control panel, find your domain settings, and toggle the lock off — most SA registrar panels label this clearly and the change takes effect within minutes.
What is the EPP authorisation code (TAC) for a co.za domain?
The TAC (Transfer Authorisation Code), also called an EPP code or auth code, is a unique alphanumeric string that your current registrar generates on request. It proves your ownership of the domain and is required by the new registrar to submit the transfer request to ZARC. The code has a 14-day validity window — request it only when you are ready to initiate the transfer. Obtain it from your current registrar's control panel or by contacting their support team.
Can I transfer a co.za domain I just registered?
No. ZARC does not allow a transfer within the first month of registration, and the broader 60-day restriction means no transfer is possible within 60 days of initial registration. If you need to move the domain quickly, contact your registrar — in some cases they can facilitate an internal account move without a full registry-level transfer, which is not subject to the same restrictions.
Need a Website That Survives the Move?
Growth Pulse Media handles domain transfers, DNS configuration, and full website builds for South African businesses — Google Workspace, Microsoft 365, Xneelo, cPanel, and Cloudflare environments included. All work is executed in-house, with no outsourced DNS surprises. No obligation — we will get back to you within 24 hours.
Talk to Us About Your Domain Setup