Who Should Own Your Website Domain, Code, and Hosting?

Your website is not one asset. The domain registration, source code, content, design files, hosting, database, analytics, search accounts, forms, licenses, and business listings can all have different owners and administrators.

A business should be able to change developers or hosting providers without losing its name, content, customer inquiries, or search history. That requires clear contract terms and practical account control, not merely a promise that "the website is yours."

The business should be the domain registrant

A domain is maintained through a registrar under a registration agreement. ICANN explains that the registrant is the individual or entity that registers the name and has rights and responsibilities involving management, renewal, restoration, and transfer. Its information for domain registrants is a useful starting point.

The business's correct legal or organizational information should be used for the registrant. The web developer, marketing employee, former partner, or agency can receive authorized technical access without becoming the beneficial owner.

Keep the registrar name, account email, multifactor-authentication method, recovery contacts, renewal method, expiration date, transfer lock, and nameserver records in a controlled asset inventory.

Domain management is different from domain ownership

A provider may register, renew, configure, and monitor the domain as a managed service. That can be convenient for a business that does not want to handle DNS records and renewals.

The agreement should still state that the client remains the registrant or beneficial owner, describe the provider's administrative access, and explain transfer after cancellation. Ask how quickly the authorization code or account control will be supplied and what outstanding payment must be resolved.

Website code may be owned, licensed, or rented

A custom-coded website can transfer to the business after payment. A theme may combine client modifications with separately licensed template code. A hosted website builder may provide only the right to use its platform while the subscription continues.

Ask whether the business receives:

• The complete source repository.
• Project-specific interface and component code.
• Build and deployment instructions.
• Configuration and environment inventory.
• Database schema and export method where applicable.
• A license to any retained developer components.
• A list of third-party packages and licenses.

A static export or backup is not always equivalent to maintainable source code. Confirm that another qualified developer could build and deploy the site.

Content and design files need separate terms

Business-supplied text, logos, photography, video, and data should remain under the business's rights or valid licenses. Developer-created copy, illustrations, icons, layouts, prototypes, and design systems should be addressed in the agreement.

Stock imagery, fonts, themes, plugins, and other purchased assets may remain subject to vendor licenses. Determine whether the license belongs to the client, can be transferred, requires renewal, or only works under the provider's agency account.

For U.S. copyright transfers, the U.S. Copyright Office publishes the ownership and written-transfer provisions. Important agreements should be reviewed by qualified counsel.

Hosting is a service, not usually the website itself

Hosting supplies the infrastructure that serves the site. The business can own its code and content while paying a provider to operate the hosting. It can also rent a hosted platform that combines code, editing tools, infrastructure, and licenses.

Ask:

• Whose legal name and payment method control the hosting account?
• Can the business receive administrator and billing visibility?
• What backups exist, and can the business retrieve them?
• Which traffic, storage, email, and database limits apply?
• What security and maintenance work is included?
• How is the site moved to replacement hosting?
• What continues to work after the relationship ends?

Do not forget operational accounts

A website can become difficult to operate even when the domain and code are available. Inventory:

• Analytics and tag-management accounts.
• Search Console and business-profile access.
• Form, email-delivery, and spam-protection services.
• Scheduling, payment, ecommerce, and customer-management integrations.
• Consent and privacy tools.
• CDN, DNS, certificates, and monitoring.
• Image, font, theme, and plugin licenses.
• Repository, deployment, backup, and error-monitoring systems.

Create these accounts in the business's name when practical, then invite the provider with the minimum role needed.

Website builders require a portability check

Wix, Squarespace, WordPress, Shopify, Webflow, and custom code do not offer the same ownership and export model. A builder can be a sound choice, but the business should know what can move and what must be recreated.

Test whether pages, structured content, products, customers, orders, blog posts, media, form submissions, redirects, metadata, and design behavior can be exported in useful formats. Also compare subscriptions, transaction charges, plugin reliance, and the cost of leaving.

The platform guide, Wix, Squarespace, WordPress, or custom, compares the broader tradeoffs.

Ownership should transfer at a defined event

The agreement should identify whether project-specific rights transfer when created, at a milestone, on delivery, or after final payment. It should also say what the client receives if the project ends early.

Under Vertinus's terms, after final payment the client receives ownership of the completed project code, interface work, and project-specific deliverables. Third-party assets keep their separate licenses.

The website payment schedule guide explains how acceptance and handoff can be connected to the final balance.

How Vertinus Managed Website Care works

Managed Website Care is optional at $50 per month. Vertinus can manage hosting, one standard-priced domain, DNS, SSL and CDN configuration, uptime and contact-form monitoring, backups, deployments, and reasonable routine technical maintenance.

The client remains the legal registrant and beneficial owner of the managed domain. The client also owns the completed code after final payment. New content, pages, features, integrations, premium domains, paid third-party tools, business email, and unusually high usage are not included in the monthly care price.

On cancellation or written transfer request, the current terms describe a transfer process after outstanding invoices are paid. The client is responsible for accepting the transfer and arranging replacement hosting, DNS, and renewals.

Warning signs of website lock-in

• The provider registers the domain in its own name without client terms.
• The business cannot access registrar, hosting, analytics, or search accounts.
• The contract says "you own the site" but excludes the code needed to operate it.
• There is no usable content, data, or repository export.
• A proprietary platform or agency license is not disclosed.
• Moving the site causes unrelated content or customer data to disappear.
• Cancellation terms allow immediate shutdown without a transfer window.
• The business cannot identify recurring renewals or the payment method behind them.
• The provider promises transfer but has no documented process.

Use a website control checklist

Before final payment or launch, record the owner, administrator, billing contact, recovery method, renewal date, transfer process, and backup location for every important asset.

Test access. A spreadsheet saying the client owns the domain does not help if the recovery email belongs to a former developer.

Ownership should support an ordinary provider change

The goal is not to distrust the current developer. It is to make the business durable. Providers change focus, people leave, platforms close, and requirements grow.

A well-structured relationship lets the developer manage technical complexity while the business retains durable control of the name, customer path, data, code rights, and essential accounts.