If your website stopped working tonight and your developer stopped answering, could you fix it?
For most small businesses I meet, the honest answer is no. The domain is registered in the developer's name. The hosting is on his account, paid with his card. The code is on his laptop. The business paid for the site, but it does not control a single piece of it.
This post gives you the three questions to ask before you pay, the full checklist I use when I hand over a project, and what to do if it is already too late.
What are you actually buying when you pay for a website?
You are buying a digital product. And a website is not just the pages you see.
It is three things:
- The domain. The address, like
yourshop.comoryourshop.dz. - The hosting. The server or the account where the site lives on the internet.
- The source code. The files that make the site work.
The design is what you see. These three are what you own. If one of them stays in someone else's name, the product is not fully yours. You cannot move it, change it, or hand it to another developer without asking permission first.
The 3 questions to ask before you pay 🧠
1. In whose name is the domain registered?
It must be yours, or your company's. The registrant on record is the one with the rights. ICANN is clear that the registrant "will assume sole responsibility for the registration and use" of the domain (ICANN). If that is your developer, the address your clients type belongs to him.
2. Whose account is the hosting on?
The hosting account should be opened with your email and paid with your payment method. The developer gets added as a user. If the hosting is on his account, he decides when it renews, when it stops, and who can log in.
3. Where is the code, and who controls it?
The code should live in a repository you own, on GitHub, GitLab or similar, with the developer invited as a collaborator. Code that only exists on one person's laptop is one broken laptop away from gone.
What can go wrong when the developer owns it?
These are not rare cases. They are the normal way this fails:
- He stops answering. The site goes down, the renewal date passes, and you cannot log in anywhere to fix it.
- He holds the site hostage. Every small change becomes a new invoice, because nobody else can touch it.
- The money gets rerouted. If the payment settings sit in an account he controls, he can change where the payouts go. The orders keep coming in. The money stops reaching you.
- You want to change developer. The new one asks for access, and you have nothing to give him.
Who should own what?
| Asset | Must be in the name of | The developer gets | Red flag |
|---|---|---|---|
| Domain | You or your company | Access to edit DNS, if needed | "I registered it for you, don't worry" |
| Hosting | You, your email, your card | A user account | The renewal invoice goes to him |
| Code | A repository you own | Collaborator access | "The code is on my machine" |
| Payment accounts | You, payouts to your account | Test access only | He set up the payment account himself |
| Admin passwords | You | His own login, removed at the end | Passwords only he knows |
| App store accounts | Your business | A team member role | The app is published under his account |
Why this happens so often in Algeria 🇩🇿
Many sites here are built informally. A friend of a friend, a freelancer paid in cash, no written contract. To move fast, the developer buys the domain and the hosting himself and "adds it to the price". Everyone is happy until the first renewal, or the first disagreement.
A .dz domain adds a step, because it has its own registry and its own rules. That is one more reason the developer offers to handle it, and one more reason to make sure it ends up in your name.
The fix is not to distrust every developer. It is to put the ownership in writing. Since the carte d'auto-entrepreneur, a freelancer can sign a real contract and invoice legally, and I wrote about how that card works.
The handover checklist 🛠️
This is the list I put in my own contracts. Copy it into yours.
Before you sign
- The contract names the domain, the hosting, the code repository and the payment accounts, and says they are delivered in the client's name.
- You open the hosting account yourself, with your email and your payment method.
- You create the code repository yourself, or the developer transfers it to you at the end.
- The domain is registered with your name and your email as the registrant.
During the build
- The developer works with collaborator or user access, never as the owner.
- Payment accounts (Chargily, a bank account, Stripe for foreign cards) are opened in your name, with payouts to your account.
- Every third party service (email sending, maps, SMS, analytics, Meta Pixel) is on an account you control.
On delivery day
- You log into every account yourself, one by one: registrar, hosting, repository, payments, site admin.
- You change the passwords.
- You get a short document: how to deploy an update, where the backups are, and when each service renews.
- You remove the developer's owner rights, and keep collaborator access only if support continues.
Every year
- Check the renewal dates of the domain and the hosting. A forgotten renewal is the most common way a site disappears.
What if it is already too late?
Do not panic, and do not fight. Ask.
- Look up your domain on the ICANN lookup tool, or on NIC.dz for a
.dz. Write down who the registrant is. - Ask the developer to transfer the domain, the hosting and the repository to accounts you create. Most developers say yes when the request is calm and in writing.
- If he refuses or disappeared, contact the registrar with proof that the site is your business: invoices, messages, your trade register or your carte d'auto-entrepreneur.
- For the code, if you cannot get it back, a site can be rebuilt. It costs time. That is exactly the cost this checklist exists to avoid.
TL;DR 🧾
Your website = domain + hosting + code. Pay for all three, own all three.
Before the final payment, check that the domain is registered in your name, the hosting is on your account, and the code is in your repository. Put it in the contract, log in yourself on delivery day, and change the passwords. A good developer will not mind. The one who minds is the one you needed this checklist for.