Who Should Own Your Domain, Hosting and Website? A Checklist Before You Sign With a Developer

Short answer: You should be the registered owner of your domain, hold (or have full admin access to) your hosting account and your website's admin login, and have the rights to your content and design in writing. If a developer registers or hosts those things under their own name, your site depends on that relationship — which is the usual root of the “I can't get my website back” stories.

When a website project starts, almost nobody asks who will own what at the end. It only comes up later, when the developer is unreachable, the relationship ends badly, or a renewal quietly lapses. A short checklist before you sign avoids most of it.

The four things to know apart

• Domain name — your address (yourbusiness.com), registered through a registrar. The registered owner is the one who controls it.
• Hosting — the server where the site's files and database run.
• The website itself — the pages, design, content and the login that manages them.
• Connected accounts — Google Analytics, Search Console, tag managers, email, and anything else tied to the site.

These can all sit with different people, and a problem with any one of them can cut you off from the rest. For the basics of what a site is made of, see what web development actually involves.

The ownership checklist

1. The domain is registered in your name and your email. You should be able to log in to the registrar account yourself. If the developer registered it for you, ask for it to be registered under your own account.
2. Auto-renewal is on, with a payment method you control. Expired domains are one of the most avoidable ways to lose a site.
3. You know where the site is hosted and who pays. Either the hosting account is yours, or you have documented admin access and a clear way to export the site.
4. You have your own administrator login to the website. Not a shared login, and not one that only the developer can reset.
5. You receive a full backup. Files and database, delivered to you, at launch and on a schedule that is agreed.
6. Third-party accounts are in your name. Analytics, Search Console, the Google Business Profile, social accounts — you should be the owner and the developer a user, not the other way round.
7. You know which paid tools the site depends on. Some themes and plugins are licensed to the buyer. Ask which are paid, who holds the licence and who pays to renew it.
8. The rights to your content, design and code are written down. What you own, what the developer reuses, and what happens to custom work if you leave.
9. There is a handover. A short document with the logins, the services used and what to do if something breaks.

Red flags

• “We handle all of that for you” with no access offered to you.
• The developer's personal email is the contact on the domain or hosting.
• Reluctance to put ownership or handover terms in writing.
• You cannot say where your site is hosted or who is paying for it.

It is perfectly normal for a developer to host and maintain a site for you. The point is not who runs it day to day; it is whether you can leave with your domain, your content and your data if you need to.

If you are already in the situation

Ask your developer for the registrar details and request a transfer of the domain into your own account. Domain transfers often have waiting periods after a registration or a change of owner, so start early and ask the registrar what applies to your domain extension. Then take a full backup and store it somewhere you control. Related housekeeping is covered in how WordPress sites actually get hacked, and cost expectations are in how much a website costs in the Philippines.