Your CMS Hosting and Who Controls It

A Gulf Coast contractor called us in a panic. Their web developer had disappeared—no calls, no emails. Their website was still up, but they had no idea how to access the hosting account, update DNS, or even log into their domain registrar.

The website was built on the developer's hosting account. The domain was registered under the developer's name. When the developer vanished, the business owned nothing digital except a vague claim to a website they couldn't control.

This happens more than it should. Here's what you need to know.

The problem: who controls the account

Every hosting account has an owner. That owner controls:

• The servers and all data on them
• Who can access the control panel
• Billing for the account
• The ability to cancel or transfer the account
• DNS settings
• SSL certificates
• Email accounts associated with the domain

If you're not the account owner, you don't control any of this. You're dependent on whoever is.

Common scenarios that create problems

Developer registers hosting in their name. You pay for hosting, but the account is under the developer's email. When the relationship ends, the developer can hold your website hostage or simply let it expire.

Agency uses their master account. Digital agencies often host client sites under their own accounts. This is convenient for the agency. It's risky for you. If the agency closes, gets acquired, or you fire them, your site goes with them.

Freelancer's credit card pays the bill. If the freelancer paid for hosting with their own card and you reimbursed them, the account is legally theirs. You have no recourse if they disappear.

Domain registered by the designer. Most people don't realize domains can be registered under personal names. The person who registered your domain owns that domain legally. If they don't transfer it to you, you don't own it—even if you've been paying for it.

What can go wrong

Lost access when relationships end. Developer moves on. Agency relationship ends. Freelancer goes out of business. You're left with a website you can't update, DNS you can't change, and no way to prove you own any of it.

Surprise billing changes. If the account owner decides to raise prices, you're stuck. The hosting market might offer better rates, but switching means losing your setup and starting over.

Account suspension. If the account owner has a billing dispute with the host, or if they violate terms of service, your site goes down. You have no control over events that affect your business.

Data loss risk. If the account owner deletes resources, fails to renew, or loses access themselves, your data may be unrecoverable.

No direct support. You can't call the host directly about your issues. You're going through the account owner, who may or may not prioritize your problem.

How to know who controls your hosting

1. Check the hosting account directly. If you have access, log into your hosting control panel (cPanel, Plesk, or the provider's dashboard). Look at the account information. The registered email address tells you who the owner is.

2. Ask your developer or agency. Direct question: "Who owns the hosting account for my website? Can you transfer it to my name?" Their answer—and their willingness to help—tells you a lot.

3. Run a WHOIS lookup on your domain. Go to whois.com or icann.org and look up your domain. The registrant name tells you who legally owns the domain. If it's not your business or your name, that's a problem.

4. Check billing records. Look at your bank statements. If the hosting charge comes from "SiteGround" or "AWS" directly, you might be the owner. If it comes from "XYZ Digital Agency," you're not.

What you need to own

The hosting account. You need an account in your business name (or your personal name if you're a sole proprietor) with the hosting provider. Not your developer's account. Not your agency's master account.

The domain name. Registered in your name, not your developer's. The registration should show your business address and email.

The ability to add and remove users. You should be able to grant access to contractors and remove access when relationships end. If only one person can do this, you're dependent on them.

Access to backups. You should be able to download a full backup of your website at any time. If the only backup lives on a server you don't control, it's not really yours.

SSL certificate control. You need the ability to manage SSL certificates for your domain. If the account owner controls this, they control whether your site works.

How to fix it

For new projects:

1. Create the hosting account in YOUR name before work begins.
2. Add the developer as a user with appropriate permissions (not admin).
3. Register the domain in YOUR name.
4. Keep billing in YOUR name.
5. Maintain your own access to backups.

For existing projects:

1. Request a transfer of the hosting account to your name. Most hosts make this straightforward.
2. Request a domain transfer if it's in someone else's name. This requires an authorization code from the current registrar.
3. If the current owner won't cooperate, you're in a harder position—see "when to hire help" below.

Protections to put in place:

• Require all contractors to work within YOUR hosting account
• Register domains yourself before giving access to designers
• Maintain your own admin access even when working with agencies
• Download backups regularly and store them independently

Vendor questions (copy/paste)

For hosting providers:

• How do I transfer a hosting account to a different owner?
• Can I add a second owner or admin to an existing account?
• What's your process for recovering access if the current owner is unresponsive?

For domain registrars:

• How do I transfer a domain to a different registrar?
• What information do I need to initiate a transfer?
• Can I place a transfer lock to prevent unauthorized transfers?

For agencies and developers:

• Will the hosting account be in my name or yours?
• Can you register the domain in my name before starting work?
• Will I have full admin access to the hosting account?
• What happens to my hosting account and domain if our relationship ends?

Minimum viable implementation

1. Today: Run a WHOIS lookup on your domain. Find out who owns it.
2. Today: Check your hosting account owner. Log in and look at the account settings.
3. This week: If you're not the owner, request a transfer. Most hosts and registrars make this process straightforward.
4. This week: Add yourself as an admin user if you're not already. If you can't, that's a red flag.
5. Every month: Download a full backup of your website. Store it somewhere independent of your hosting.

When to hire help

• Your hosting account is in someone else's name and they won't respond to transfer requests.
• Your domain is registered to a person or company that's no longer in business.
• You're in a dispute with a developer or agency over control of your digital assets.
• You discovered your website exists but you have no access to the hosting account at all.
• You need to reconstruct a website from backups because you've lost all access.

The uncomfortable truth

If you didn't create the account, you may not own it. This is a business risk that most small businesses don't discover until a relationship goes bad. The fix is straightforward: make sure everything is in your name. The time to do it is before you need it.