“Who owns the website?” sounds like a simple question. In practice, several different assets and accounts may be involved, and each can have a different answer. The domain registration, registrar account, DNS records, hosting, website code, written content, images, and third-party services are connected, but they are not the same thing. Understanding those differences before hiring someone can prevent confusion later.
A domain is a renewable registration right
People commonly say they “bought” a domain. More precisely, a registrant holds renewable rights to use and manage that domain for a registration period. ICANN identifies the registrant, or Registered Name Holder, as the person or entity holding those rights. It also warns that a developer who registered a domain using the developer’s own information may appear as the official registrant even when the client paid for it. Read ICANN’s domain-holder explanation.
Domain registration must continue to be renewed. It is not permanent ownership in the same way someone owns physical property. That is why the registered holder, renewal process, and account-recovery structure matter.
The connected pieces are different
Domain registration
The renewable right associated with the business’s web address. The registration record identifies a holder and is maintained through a registrar.
Registrar account and DNS
The registrar account may contain registrant details, renewal settings, transfer controls, and recovery information. DNS records tell internet services where the website, email, and other approved services are located. DNS can be managed at the registrar or through another provider.
Hosting
Hosting is the service or platform that makes the website available online. A business can sometimes change hosting without changing registrars. Paying for hosting does not by itself determine who holds the domain registration.
Website code, files, and content
Templates, components, configuration, images, and other assets produce the website. Ownership or licensing can depend on the agreement and technology used. The business may own its approved text, logo, and original materials while fonts, photographs, themes, plugins, or other elements remain subject to third-party licenses.
Third-party services
Forms, analytics, scheduling tools, email platforms, maps, payment services, and other integrations can each have separate owner and administrator roles, billing, and terms. Access to one item does not automatically provide control over the others.
Why account structure matters
A developer may administer technical systems for a legitimate reason. The problem begins when the client’s rights are unclear, recovery details belong only to the developer, or no one has documented what happens after the relationship ends. If every connected account uses an agency-controlled email address, the owner may not receive security, expiration, or billing notices.
If the agreement says nothing about website files or licenses, both sides may have different expectations. Good administration should make the business easier to support without making the business identity dependent on one provider’s continued cooperation.
Questions to ask before hiring anyone
- Who will be listed as the domain’s registrant?
- Which email receives renewal and security notices?
- Who controls account recovery and multifactor authentication?
- Who pays the registrar, hosting provider, and third-party services?
- Which accounts will the client own directly, and which will the developer administer?
- What files, exports, or backups are available at handoff?
- Are any themes, fonts, photographs, plugins, or tools licensed rather than owned?
- What recurring charges should the client expect?
- What steps apply if either party ends service?
Red flags worth slowing down for
- The provider refuses to identify the registrar or hosting provider.
- No one will explain who is listed as the domain holder.
- Recurring charges are unclear or undocumented.
- Reasonable access is withheld without a documented security or service reason.
- There is no written offboarding process.
- The provider threatens to disable or redirect a domain during an ordinary disagreement.
- The provider cannot explain which files, licenses, or accounts can be transferred.
- Someone requests account passwords through an unsecured public inquiry form.
A business should never send registrar, hosting, email, or social-media passwords through a public website inquiry form. An initial inquiry should contain project information, not credentials. Necessary access can be arranged later through an appropriate secure process.
Magnitude’s approach
With Magnitude, the client is the beneficial owner of the domain. Magnitude may administer technical settings during an active service so the website, DNS, email, and approved connected services continue to work together. If service ends, the domain remains client-owned and an orderly handoff is available. Managed administration supports the client’s business; it does not give Magnitude ownership of the client’s business identity. Review Magnitude’s ownership and handoff approach for managed service.
A cooperative transfer can still take time
A delay does not always mean someone is withholding a domain. ICANN explains that transfers may be delayed by lock status, a new registration, certain changes to registrant information, or a recent transfer. Some situations involve a 60-day restriction. A business may still be able to change hosting or update nameservers without transferring to another registrar. Read ICANN’s transfer FAQ.
A good handoff should identify those constraints honestly, protect access during the transition, and complete the available steps in the correct order.
A practical ownership checklist
- Domain name, registrar, expiration date, registrant, and renewal method
- Recovery email, recovery phone, and multifactor-authentication method
- DNS and hosting providers
- Website administrator accounts
- Form destination email
- Analytics and search accounts
- Third-party services and billing owners
- Current written agreement
- Latest available backup or export
- Handoff contact and procedure