Everyone in this industry has heard some version of the same story. A business wants to switch developers, nothing dramatic, maybe the old one’s slow to reply or just gone quiet for good. So they ask for the domain to be handed over. And suddenly there’s a delay, or a fee that wasn’t mentioned before, or a developer who suddenly needs “a few days to sort out access.”
It’s common enough that most business owners have either lived through it or know someone who has. And it usually comes down to one confusion. People think whoever built the site owns the domain. It’s actually much simpler than that, and much more in your favour than most owners realise.
Ownership And Management Are Two Different Things
A domain has a registrant. That’s the legal term for whoever’s name is on file with the registry, and it’s what actually determines who owns it. For a .co.za domain, that record sits with the local registry. Nothing about who built the website changes it. Nothing about who’s been paying the renewal invoice through their developer changes it either. It comes down to whose name is on that one field.
Separate from that is who manages the domain day to day, renewals, DNS records, pointing it at hosting. A developer handling that side is completely normal. It’s the same relationship you’d have with an accountant managing your books without owning your business. The problem only starts when management quietly becomes the same thing as ownership, usually because nobody ever checked which one was actually true.
When we register a domain for a client, the client’s business goes down as the legal owner. We just handle the operational side so renewals and technical changes don’t land on their desk.
What Happens If You Want To Leave
If the domain’s registered correctly, in your name, you don’t need anyone’s permission to take it with you. You ask, and a developer acting in good faith unlocks it and sends over what you need, usually within a day.
If they’re not cooperating, you don’t actually need them to be. You can go to the registrar directly, the company the domain sits with, confirm you’re the registrant on record, and they’ll help you from there. It doesn’t depend on your developer’s mood.
And even before either of those steps, the registry itself has a safeguard built in. Any transfer of a .co.za domain triggers a confirmation email from the registry straight to whoever’s listed as registrant. That person has to approve it before anything moves. If that’s you, nobody, including your developer, can shift your domain without your say so. It’s not a favour anyone’s doing you. It’s just how the system’s built.
Why Some Agencies Do It Differently
Some developers register client domains under their own company details instead, usually just because it’s simpler on their end when they’re juggling dozens of renewals. It’s not always a red flag by itself. But it creates a dependency that shouldn’t exist. If that agency goes quiet, shuts down, or you just want to move on, you’re now negotiating for something that should have been yours from the start.
Registering it correctly costs a developer nothing extra. It just means the paperwork matches reality, your business, your domain.
For .co.za domains specifically, ZADNA runs a formal Alternative Dispute Resolution process for situations where a registrant won’t release a domain that should belong to someone else. It’s slower than a cooperative handover, but it exists because this comes up often enough to need one.
If a developer hesitates when you ask who owns your domain, that hesitation is the answer. Before you sign with anyone new, ask the question up front, and check what to ask before you hire a developer so ownership’s settled before there’s ever a reason to argue about it.
