Who owns your domain name, and why it matters

Updated September 26, 2026

Who owns your domain name if a web designer bought it for you? Check the registration and account arrangements rather than assuming the name on the invoice settles everything. You want your business to control the address customers use, even if someone else maintains the website behind it.

Understand the three roles

The registrant is the person or organization that registers the domain. The registrar is the company that manages that registration. Your web designer builds or maintains the website and may help administer the domain, but that is a separate role.

ICANN's information for domain registrants explains that registration creates an agreement with a registrar. In everyday business conversation, people call this owning the domain. The practical concern is who holds the registration rights and can manage them while keeping the registration renewed.

Your website hosting is another separate service. It stores or runs the website. Moving the site does not always require moving the domain registration, and moving registration does not automatically move the website.

The plain-English hosting guide explains that distinction. Keeping these roles separate makes it easier to understand a provider's proposal and avoid canceling the wrong service when you switch.

Check the records and access you actually have

Start with your own paperwork. Find the registration receipt, renewal notices, and any agreement with the person who set up the site. Identify the registrar and the account used to manage the domain.

Sign in through the registrar's known website, not a link in an unexpected email. Review the domain's contact details, registration status, renewal information, and account recovery settings. If the interface is unclear, ask the registrar's support team to explain the relevant fields.

Public lookup tools can help identify a registrar, but they may not reveal all registrant details. Privacy arrangements and redacted information can limit what appears publicly. ICANN explains those limits in its registration data guidance.

Do not treat a hidden name in a public lookup as proof of a problem. Confirm the underlying arrangement through your account and provider. Likewise, access to a website editor does not prove access to the domain registration.

Recognize arrangements that can leave you stuck

A common problem begins with convenience. A designer registers everything through a personal account, a former employee receives the renewal emails, or a relative sets up the domain with contact details nobody remembers. It may work until that person becomes unavailable.

Another problem is unclear renewal responsibility. You may assume a website payment covers the domain while the provider assumes you will renew it separately. Put the arrangement in writing and keep a record of who checks that renewal succeeded.

Business email can also depend on the same domain. If you lose access to the domain and the only recovery email uses it, recovering the account can become harder. Keep an independent recovery route you control where the provider supports one.

Warning signs deserve questions, not immediate accusations. Ask for the registrar name, registrant information, renewal arrangements, and how you would leave. A cooperative provider should be able to explain what they manage and what access your business retains.

Fix control problems before canceling anything

If the domain is registered under someone else's details, contact that person and the registrar to establish the correct process. Gather invoices, agreements, and business records that explain the arrangement. Do not change random settings in an effort to force control.

Ask for a clear handover that covers:

• Confirmation of the intended registrant details.
• An account or access arrangement controlled by your business.
• A recovery method and contact email you can maintain.
• The renewal date, payment arrangement, and responsibility.
• A record of where website and email settings are managed.

Changing the registrant and changing the registrar are different tasks. The registrar can explain the steps and whether a change affects a planned transfer. ICANN directs registrants to their registrar for registrant changes.

If the arrangement is disputed, preserve the records and ask a lawyer about the agreement. Avoid threats or assumptions that paying a website invoice automatically resolves a contested registration. Get the account situation clear before ending the working relationship.

Protect the website and email during a move

Before switching providers, list what uses the domain. That can include the public website, business email, booking links, subdomains, and verification records for other services. A domain move should account for those dependencies.

Ask the new provider which settings need to change and which should stay in place. Keep a copy of the existing DNS records, which direct traffic and email to their destinations. Do not delete records simply because their names look unfamiliar.

Plan the order of work before canceling the old service. Confirm that the replacement website and email arrangements are ready, then make the agreed changes and test them. Check incoming and outgoing email as well as the public pages.

The domain transfer guide covers the next stage. Ask the current registrar about eligibility and timing rather than assuming every domain can move immediately or that every website change requires a registrar transfer.

Make domain checks part of ordinary administration

Treat your domain like another business account that needs a responsible owner. Keep the registrar name, account recovery method, and renewal responsibility documented. Store credentials securely rather than in an unprotected note passed between contractors.

Use available account protections and maintain current contact information. ICANN's guide to protecting registration accounts discusses ways to reduce account misuse and administrative mistakes. Apply the protections your provider supports and make recovery practical for your business.

Check access when staff or providers change. A password should not remain your only defense after the person who knew it leaves. Review authorized users and payment details while the handover is still cooperative.

Set your own reminder to confirm renewal instead of relying entirely on a billing email. Automatic renewal is useful, but checking that the domain actually renewed is a separate step. A failed payment should not be discovered when a customer says your website has disappeared.

Frequently asked questions

Does paying the designer mean I own the domain?

Payment alone does not tell you how the domain was registered or what your agreement says. Check the registrant details, contract, and account control, and ask a lawyer if there is a dispute.

Is domain privacy a sign that someone else owns it?

No, public records may conceal contact information for privacy reasons. Confirm the underlying details through the registrar rather than drawing conclusions from a public lookup alone.

Can I keep the domain when I change websites?

That is generally the goal, but verify your account control and provider terms first. A website move and a registrar transfer are separate tasks that should be planned around your email and other services.

Should my designer have access to the domain?

They may need appropriate access to do agreed technical work. Keep business control and recovery arrangements clear so their assistance does not become your only route to the account.

The short version

Check who holds the domain registration, who controls the account, and who makes sure renewal succeeds. Resolve access questions while everything is working, then plan any move around both website and email needs. Front Step Sites registers the domain in your name and lets you leave any time with your domain, with no transfer fee.