The Day You Discover Your Website Was Never Really Yours

Four things can be owned separately — the domain, the hosting, the site’s admin access, and the design files — and paying for a website often gets you none of the first three. Recover them in that order, because the domain is worth more than the other three combined.

The moment it happens

The day you discover your website was never really yours arrives with a small request. You want a phone number changed, or you’ve decided to work with someone else, or you simply want the login. And the answer is a version of “don’t worry, we handle all that.”

Then you ask directly and find the domain is registered to them, the hosting account is theirs, and there is no login in your name anywhere. You paid for a website. You have access to nothing.

Complaint records document both halves of this — buyers unable to move sites held in a developer’s account, and at least one case of a live site taken offline during a payment dispute.

The four kinds of ownership

What Who probably holds it Why it matters
The domain Frequently the developer Decides whether you can move anywhere. The most valuable item
The hosting account Frequently the developer Where the site lives; needed to copy it
Site admin access Often nobody gave it to you Needed to edit content
Design source files The developer Nice to have; you can usually work without them

Most buyers assume paying for a website means holding all four. In practice, on a low-cost build, you may hold none — not usually through bad faith, but because managing many client domains in one account is administratively cheaper.

Why the domain matters most

Because it’s the one thing that can’t be recreated.

Hosting can be replaced — buy your own, upload a copy of the site. Admin access can be reset if you control the hosting. Design files can be worked around; a new developer can rebuild from the live site.

The domain is your business’s name. Lose control of it and you lose your address, your business email, and every link, card and listing pointing at you. That’s why it sits at the top of the recovery order, and why registering it yourself before hiring anyone is the single best decision available to you.

The ten-minute check

Do this today, whatever state your site is in:

  1. Search “whois” plus your domain. Look at the registrant email and the expiry date. If the email isn’t yours, the domain isn’t practically yours.
  2. Try logging in to your hosting. No login means no access to your own site’s files.
  3. Try logging in to your site’s admin — usually your address followed by /wp-admin for WordPress.
  4. Check your email for a registrar welcome message. If one exists in your inbox, the account may already be yours and just needs a password reset.

That fourth step resolves more cases than people expect.

What you can genuinely demand

Being precise, because “everything” isn’t accurate:

Clearly yours: the domain if registered in your name, your content and photographs, your business’s data — enquiries, orders, customer records — and a copy of the live site you paid for.

Usually yours in practice: the hosting account if the plan was bought in your name, and admin access to the site itself.

Contested without a contract: design source files, custom code, and template licences the developer purchased. Most small projects have no written agreement, which is exactly why these become arguments. If you have anything in writing, read it now.

Not yours: their internal tools, and template or plugin licences bought under their own account for use across many clients.

Knowing the difference stops you spending three weeks fighting for a design file you don’t need.

The recovery order

1. The domain. If it’s in your name, reset the password through your own email. If it’s in theirs, request a transfer as routine housekeeping — framed as records-keeping, not as a departure. Where that fails, registrars have ownership-claim processes and will weigh evidence: GST registration, invoices, payment records, trademark.

2. Hosting. Contact the hosting company directly as the account owner. Where the plan sits inside a reseller account belonging to the developer, ask the host what recovery requires.

3. A backup. Once you have hosting, generate and download a full backup — files and database. Keep your own copy off the server.

4. Admin access. Recoverable through hosting, without the developer.

Notice that steps two to four collapse into one if you can reach the hosting account. Hosting access gives you almost everything except the domain.

How to ask

One civil message, no grievance:

Hi [name]. For my records, could you please confirm the domain registrar login, the hosting login and the website admin login, and send a full backup of the site as a zip? Also, please tell me whether anything — Google Business Profile, analytics, business email, payment gateway — is registered under your account for my business. Happy to settle anything pending.

The last question is the one most people forget, and it’s often where the real dependency is hiding.

What to do this week

  1. Run the WHOIS check and read the registrant email.
  2. Attempt to log in to hosting and site admin.
  3. Search your inbox for a registrar welcome email.
  4. Send the one civil message asking for all four items plus any registrations in their name.
  5. If you’re planning a new site, register the domain yourself first.

If you want it done the certain way

Tell us what access you hold and we’ll tell you what’s recoverable without the old developer, and what a clean rebuild would cost using your existing content. Either way the domain, hosting and logins end up in your name, with the handover written down. WhatsApp us; we reply in about five minutes between 9am and 7pm.

Related reading

FAQ

Who owns my website — me or my developer?
Four things are owned separately: the domain, the hosting account, site admin access, and design files. Paying for a website often gets you none of the first three, since vendors commonly register them under their own accounts.

How do I check whether my website is really mine?
Run a WHOIS lookup on your domain and check whether the registrant email is yours, then try logging in to your hosting and your site’s admin. Also search your inbox for a registrar welcome email — the account may already be yours.

Can I demand the design files for my website?
Without a written contract this is genuinely contested. You clearly own your content and the live site you paid for; source files and custom code depend on the agreement. A new developer can usually work from the live site without them.

What do you think?

What to read next