Most business owners find out who controls their website on a bad day. The site is down, the developer who built it stopped answering email, and the login you thought you had opens a dashboard with no admin menu. Or the domain renewal notice went to an address that left the company two years ago.
This doesn't mean anyone did anything shady. Freelancers move on, small agencies close, and the person who set things up sometimes registered the accounts under their own name because it was faster at the time. Paying for a site doesn't mean the accounts behind it are in your name.
This post walks through the four things that decide who controls a website or web app: the domain, the accounts behind hosting and DNS, the code, and the contract. You can check most of it in an afternoon without touching any code.
Start With the Domain Name
Your domain is the address everything else hangs on. Email, the website and many logins depend on it. If someone else controls the domain, they control where all of that points.
Look Up Who the Registrar Is
ICANN, the organization that coordinates domain names, runs a free tool at lookup.icann.org. Type in your domain and the "Registrar" field tells you which company it's registered through. That's the company you'll be dealing with for renewals and transfers.
Next, log in to that registrar. If your company doesn't have a login, that's your first finding. The registrant, meaning the legal holder of the domain, should be your business, with a contact email that your business controls. A shared office or admin mailbox is a good choice for that contact.
Know What ICANN Expects From You
ICANN's Registrants' Benefits and Responsibilities page puts some of the work on the domain holder. You're expected to keep your contact details accurate, respond to inquiries from your registrar within 15 days, and keep payment information current if the domain renews automatically. If the card on file expires and the renewal fails, the domain can lapse.
Understand Transfers and the 60-Day Lock
To move a domain to a different registrar you need an authorization code, sometimes called an Auth-Code or transfer code. ICANN's FAQ for registrants says your registrar must provide that code within five calendar days of your request.
The same FAQ says you can't transfer a domain to a different registrar within 60 days of changing the registrant name, organization or email address. Some registrars let you opt out of that lock, and they aren't required to. If you're cleaning up ownership and planning a move, update the registrant details first and expect to wait.
Hosting, DNS and the Accounts Behind Them
After the domain, make a list of every service the site depends on. For a typical small business site that's the hosting account, the DNS provider (often the registrar, sometimes a separate service like Cloudflare), the site's own admin login, and the email or form service that sends contact form messages. Web apps add a few more: a cloud account, a database, a payment processor and any third-party APIs.
For each one, write down three things:
- Whose name and email the account is under
- Whose card pays for it
- Who on your side can log in with full admin rights
The answer you want for the first two is "the business." The answer you want for the third is at least two people. One of them can be your developer or IT provider, as long as someone at your business also has access.
Check the Site's Admin Role
If your site runs on WordPress, open the Users screen and look at the roles. WordPress describes an Administrator as "somebody who has access to all the administration features within a single site." Other roles, such as Editor, have fewer permissions. Confirm that at least one login your business controls has the Administrator role.
While you're there, look for admin accounts that belong to people who no longer work with you. Remove them, or ask your current provider to.
Keep Credentials in One Place
Collect the logins in a password manager the business owns, with shared access for the people who need it.
The Code and Where It Lives
A simple brochure site built in a page builder may not have much custom code. A web app, a customer portal or a heavily customized site does. That code needs a home you control.
Find the Repository
Developers keep code in a repository, usually on a service like GitHub, GitLab or Bitbucket. Ask your developer where yours lives and whose account owns it. Sometimes it sits in a freelancer's personal account. That's easiest to fix while everyone is still on good terms.
On GitHub, the clean setup is an organization owned by your business, with the repository inside it. GitHub's documentation on transferring a repository explains that issues, pull requests, the wiki, stars and watchers move with it, and links to the old location redirect to the new one. The person transferring needs admin access to the repository.
GitHub also gives advice about the organization itself. Its roles documentation says organization owners have complete administrative access and that the owner role "should be limited, but to no less than two people." The same rule applies here as with hosting: two owners, and one of them is someone at your business.
Ask for the Documentation That Lets Someone Else Take Over
Code alone doesn't get a new developer very far. At a minimum you want a short README that explains how to run the project, a list of the services and environment settings it needs (with the secret values stored in your password manager, never in the document itself), and notes on how it gets deployed. Ask for it now, while the project is fresh in your developer's mind.
What Your Contract Says About Ownership
This is the part people assume is settled because they paid the invoice. Under U.S. copyright law, paying for a work and owning its copyright are separate questions.
Work Made for Hire Has a Narrow Definition
The U.S. Copyright Office's Circular 30, Works Made for Hire, describes two situations where the business that pays for a work is treated as its author. The first is work an employee creates as part of their regular duties. The second is a specially commissioned work that falls into one of nine listed categories, such as a contribution to a collective work, a compilation or an instructional text, with a written agreement signed by both parties.
The circular is direct about what happens otherwise: if a work fails any of the requirements, "it is not a work made for hire." Custom software and websites built by an outside contractor don't fit cleanly into that list of nine. That's why many development contracts use a written assignment of copyright instead of relying on a "work for hire" label alone.
What to Look For in Your Agreement
Pull out your contract or statement of work and look for language on these points:
- Who owns the code and design files once you've paid in full
- Whether copyright is assigned to you in writing
- Which parts the developer keeps, such as their own reusable tools, and what license you get to use them
- Whether third-party themes, plugins and libraries are licensed to your business or to the developer
- What the developer hands over when the engagement ends
We're not lawyers, and this isn't legal advice. If the contract is silent or unclear on ownership, have a business attorney read it. Ask whether a short signed assignment would close the gap.
If Your Developer Has Already Stopped Responding
Sometimes you're reading a post like this after the problem has started. Here's the order we'd work in.
- Secure the domain first. Find the registrar with ICANN Lookup. If the domain is in your business's name, contact the registrar's support to regain access to the account. If it's in someone else's name, start that conversation now, since registrant changes trigger the 60-day transfer lock.
- Get into the hosting account. If your business pays the hosting bill, contact the host's support about recovering access. Expect them to ask you to verify the account. If the developer pays it, you'll need their cooperation or a fresh hosting account and a copy of the site.
- Take a full backup. Once you have any working admin access, download a copy of the site files and database before changing anything else.
- Remove old access. Change passwords on every account you've recovered, turn on multi-factor authentication, and remove users you don't recognize.
- Ask for the repository and documentation in writing. Send a polite, specific email that lists what you need. It also gives you a record of the request.
How Canyon Handles Ownership and Handoffs
Our software development work covers web apps, mobile apps, APIs and cloud infrastructure, from the first build to support after launch. You own the code, the accounts and the documentation, and you can take them anywhere.
For the computers, accounts and support around your site, our managed IT services cover endpoint management, helpdesk, patching, and proactive monitoring.
Here's the short version to take with you:
- Look up your registrar at lookup.icann.org and confirm the domain is registered to your business
- List every account the site depends on and check whose name, email and card are on each one
- Make sure at least two people, one of them at your business, have full admin access everywhere
- Move the code repository into an account your business owns
- Read your contract for a written assignment of copyright, and ask an attorney if it's unclear
If you're not sure who controls your site today, tell us what you're dealing with. A person reads every message and writes back.
Sources & References
- [1] https://lookup.icann.org/
- [2] https://www.icann.org/resources/pages/benefits-2013-09-16-en
- [3] https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en
- [4] https://wordpress.org/documentation/article/roles-and-capabilities/
- [5] https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
- [6] https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
- [7] https://www.copyright.gov/circs/circ30.pdf
