Who holds the keys to your website, and what a handover should include
Guide. Published 17 November 2026.
A website has more than one key: the domain, the DNS, the hosting, the security certificate and the logins. In the handovers and moves we handled in 2026, these usually sat with different people, and that is where the delays came from. This guide shows what went wrong on real projects and what to have in hand.
The five keys
- The domain. The name itself, held in an account at a registrar or hosting company and renewed every year.
- The DNS. The settings that point the name at your website and your email. They often sit with the domain, and sometimes with someone else entirely.
- The hosting. Where the site’s files, database and mailboxes live.
- The certificate. What puts https in front of your address. It can come free with the hosting or be bought separately, and it expires.
- The logins. WordPress, Google Search Console, Google Analytics and any paid plugin licences.
When these sit with different parties, every change waits on someone else. That was the most common cause of delay in our 2026 handovers.
What went wrong on real projects
These all happened in 2026. Details that would identify a client are left out.
- A weekend without https. A paid certificate renewed itself on a Saturday. Proving ownership needed a DNS record that only a separate IT department could add, so the site ran without https until Monday evening. Arranging the next change to that certificate took a week, for the same reason.
- A two-hour job that took a month. A small speed improvement stalled because the hosting login needed a code sent to a staff member who was on holiday.
- A transfer everyone thought was done. A .com transfer started in 2024 never completed. The name kept renewing on the old account for two years. Once a fresh transfer code was issued, it was accepted the same day.
- Half a move. One business had moved its hosting, but the domain stayed behind with the old provider. On another site the pages had moved and the database had not.
- Six weeks waiting for a login. A small campaign site waited from late August to early October for hosting details nobody could find.
- No access at all. For one school we had no hosting or DNS access, and the certificate company wanted phone verification, then a utility bill showing the number.
Two smaller things recur. Clients receive fake “renewal failed” emails; check who actually bills your hosting before you click. And a free certificate from the host gives the same level of validation as a basic paid one, with less to arrange.
Moving a site in the right order
This is the order we give clients and the provider they are moving to:
- Open the new hosting account in the name of whoever will own it.
- Back up and restore the files, the database and the mailboxes.
- Recreate the mailboxes with new passwords and load the old mail into them.
- Only then transfer the domain, so nothing goes down while the name moves.
- Cancel the old package last, once the site and the mail are confirmed working.
What the transfers looked like in practice: for a .com name, the current registrar issues a transfer code, the new host sends the request, the current registrar approves it and the move takes five to seven days. The contact email on the domain must be current, or the request stalls. Between two accounts at the same host, the receiving account orders an internal transfer and the other accepts; the host quoted up to three days. A change of nameservers took effect overnight.
Checking and moving a .co.za name
Two questions come up more than any other: is the name registered to me, and how do I move it? For a .co.za name, this is what the registry’s public record shows and how hosting companies describe the process. We checked both in November 2026; it is not drawn from our own project mail like the rest of this guide.
Who is the name registered to?
A public lookup (WHOIS) of a .co.za name shows which company holds it, when it expires and which nameservers it points to. It does not show the registrant’s name or email address: the record tells you to ask the company listed as the registrar. So the check has two steps.
- Look the name up to see which company holds it and when it expires. Most hosting companies have a lookup on their website.
- Ask that company which name and email address are on record as the registrant. If the answer is your developer, a former employee or a mailbox nobody reads, have it corrected now, while everyone is still on good terms. Allow five days for a correction to take effect.
How a .co.za transfer works
- The company you are moving to starts the transfer. A .co.za name has no transfer code.
- The registry emails the registrant address on record, and only that address can accept. The message comes from srszaticket@registry.net.za, with a subject that starts “ZA Registry Consortium (Pty) Ltd: Domain Transfer Request for”.
- The registrant has five days to accept through the link in that email. If nobody answers, the request lapses and has to be sent again.
- If the company you are leaving is listed as the registrant, it has to accept for you.
- Put the website and the mailboxes on the new hosting first. The nameservers switch when the transfer is accepted, and the change takes about a day to reach everyone.
The usual reason a transfer stalls is a registrant email address that nobody reads any more. That is what held up the .com transfer above for two years, so check the address before you start.
What we ask for when we take over a site
- Hosting access first, ideally cPanel, so we can see the files, the database, the logs and the server settings before we quote.
- A hosting or DNS login for anything to do with email or the domain. A WordPress login does not reach those.
- Who the domain and hosting are with, asked at the start of every new build.
- An invitation as a collaborator where the site runs on a website builder.
- Search Console and Analytics access where the work touches how the site is found.
If you only have a WordPress login, some hosting login was still issued when the site was first set up. Finding it early saves weeks. Share logins through a password manager or a one-time link; an agency we work with sends one-time links and a separate code on request. The redesign checklist lists the rest of what a developer needs.
What a handover should include
This is what we hand over at the end of a project, and what to ask any developer for:
- The WordPress administrator login, once the final payment is made.
- Owner access to Search Console and administrator access to Analytics, in your own Google account.
- Training on editing the site, with a manual and screen recordings to keep.
- A list of what is custom: the theme, any plugin written for you, and the paid plugin licences.
- A note of who holds the domain, the DNS, the hosting and the certificate, and which of them the developer does not control.
When a client moved its site in-house in 2026, the handover was a meeting, a list of the skills its team would need and a server of the same type. Its IT team sent the transfer request and we approved it the same day.
What this work typically costs
- Putting a site behind a content delivery network, with the nameserver changeR500 to R1,000
- Setting up a private test copy of a siteAbout R1,000
- A training pack: manual and screen recordingsAbout R3,000
- Hosting, and a .co.za or .com nameR1,350, R150 and about R300 a year
More prices are in our guide to website prices. If you are about to move a site or take one over, website maintenance explains how we look after sites, and website redesign covers rebuilding one.
Have a project in mind?
A website, an online shop, a logo or a brand, or a feature your site is missing: tell us a little about what you need and we will talk through the options.
Email and WhatsApp both take files.