How to Transfer Domain Ownership to Another Person or Company?

Selling a domain, handing a client their website, moving a domain from a founder's personal account into the company, or splitting assets after a business sale all have one thing in common: the domain needs a new legal owner. That is a different job from moving a domain to a new registrar, and mixing the two up is how domains end up half-transferred, locked, or still legally belonging to the wrong person. This guide explains what "ownership" of a domain actually means, the three ways to hand a domain over, the step-by-step process for each, how to do it safely when money is involved, and how to verify the result. If you are unsure who currently owns a domain, read registrant vs. admin vs. technical contact first.

What Does Owning a Domain Actually Mean?

Strictly speaking, nobody "owns" a domain the way they own a car. You hold a registration: a right to use the name for the registration term, under the registrar's terms and the registry's policies. The person or organization holding that right is the registrant, and the registrant record is what counts.

In practice, control of a domain has two separate parts:

1. The registrant record: the name, organization, and email stored with the registrar and registry. This is the legal holder.
2. The registrar account: the login that can change name servers, unlock the domain, and get the authorization code. This is practical control.

A clean ownership transfer changes both. If you only move the domain into the buyer's account but leave your name as registrant, you are still the legal holder. If you only change the registrant name but the domain stays in your account, you still have practical control. Either situation causes problems later, for example during a dispute or when the new owner tries to recover a domain registered under someone else's name.

Ownership Transfer vs. Registrar Transfer

Question	Ownership transfer	Registrar transfer
What changes?	Who the registrant is	Which company manages the registration
Uses an auth code?	Not necessarily	Yes
Adds a year to registration?	No	Usually yes for gTLDs
Can trigger a 60-day lock?	Yes, a change of registrant can	Yes, after the transfer completes
Typical use	Sale, gift, business restructure	Better pricing, features, consolidation

You can do one, the other, or both. The registrar-move side is covered in how to transfer a domain to another registrar.

The Three Ways to Hand Over a Domain

Option 1: Account-to-Account Push (Same Registrar)

If the new owner has, or creates, an account at the same registrar, the current owner can push the domain into it. Registrars call this an internal transfer, a domain push, a change of account, or moving a domain between accounts.

Pros: fast, often free, no auth code needed, no registrar transfer restrictions, DNS usually keeps working untouched.

Cons: the new owner is tied to that registrar until they move it, and the registrant details still need updating after the push.

Option 2: Change the Registrant, Then Hand Over the Account

For small businesses, the simplest path is sometimes to update the registrant details to the new owner and give them control of the registrar account. This only makes sense when the account contains nothing else, such as a dedicated account created for one client.

Pros: no movement of the domain at all.

Cons: account sharing is messy. Billing, 2FA devices, recovery emails, and history all belong to the old owner until changed. Generally prefer Option 1 or 3.

Option 3: Registrar Transfer to the New Owner's Registrar

The current owner unlocks the domain and gives the new owner the authorization code. The new owner starts a transfer at their own registrar and enters their own contact details there.

Pros: the new owner ends up at their preferred registrar with their own account.

Cons: slower (usually up to about five days for gTLDs), blocked if the domain is within a 60-day restriction window, and requires the domain to be unlocked. See what an EPP authorization code is for how auth codes work.

Step-by-Step: Transferring Ownership

These steps apply to most gTLDs. Registrar screens differ, but the sequence is the same.

Step 1: Agree and Document

Even for transfers within a family or between related companies, write down:

• The domain name or names.
• Who the current registrant is and who the new registrant will be.
• The price, if any, and when payment happens relative to the transfer.
• What else is included: website content, email, social accounts, trademarks.
• The date of handover.

For a business transfer or a sale of meaningful value, a short written agreement signed by both parties is worth having. If the domain is part of a larger acquisition, list it explicitly in the purchase documents.

Step 2: Check the Domain's Health

Before anything changes hands, both parties should know the domain's status:

whois example.com | grep -iE "registrar:|creation date|expiry|domain status"

Or with RDAP:

curl -sL https://rdap.org/domain/example.com \
  | jq '{registrar: (.entities[] | select(.roles | index("registrar")) | .vcardArray[1][] | select(.[0]=="fn") | .[3]), status: .status, events: [.events[] | {(.eventAction): .eventDate}] | add}'

Look for:

• Expiry date: renew first if it is close, so the domain does not lapse mid-handover. See what a domain grace period and redemption period are.
• Hold statuses such as clientHold, which indicate a problem that must be resolved first.
• Recent creation or transfer dates, which may block a registrar transfer for a while.

A buyer of a domain with any history should also look into its past. See how to check a domain's history before buying it.

Step 3: Use Escrow When Money Is Involved

If the domain is being sold, do not let either side go first on trust. A domain escrow service holds the buyer's payment, waits for the seller to transfer the domain, lets the buyer confirm they have control, and then releases the money. The full flow is explained in how to use a domain escrow service. Many marketplaces build escrow into their checkout.

Step 4: Move the Domain

Pick the method that suits you:

For an account push:

1. The new owner creates an account at the same registrar and shares their account ID or email.
2. The current owner selects the domain and chooses the push, move, or change account option.
3. The new owner accepts the incoming domain if the registrar requires it.

For a registrar transfer:

1. The current owner disables registrar lock.
2. The current owner retrieves the authorization code and shares it securely, not in a public channel.
3. The new owner initiates the transfer at their registrar and pays the transfer fee.
4. The current owner approves the transfer if their registrar sends a confirmation, or simply waits for the automatic approval.

Step 5: Update the Registrant Details

This is the step that makes the new owner the legal holder. The new owner should update the registrant contact to their own:

• Name of the person, or the legal entity name for a company
• Organization field, if it is a business
• Email address that the new owner controls long term
• Postal address and phone

For a company, list the company as the registrant organization, not an individual employee. Employees leave; companies do not.

Step 6: Handle the Change of Registrant Confirmation

For gTLDs, a material change to the registrant name, organization, or email is a Change of Registrant under ICANN's Transfer Policy. Under the long-standing rules:

• The registrar must obtain confirmation from both the prior registrant and the new registrant, typically via emailed links. Some registrars handle this through a Designated Agent authorization you accept in their terms.
• After the change, the registrar applies a 60-day lock on moving the domain to another registrar, unless the prior registrant opted out before the change.

If the new owner plans to move the domain to a different registrar soon, the previous owner should look for the opt-out option when the change is made. ICANN has been revising this part of the Transfer Policy, so the exact process may differ depending on your registrar's implementation. The details are in what the 60-day domain transfer lock is.

Step 7: Secure the Domain Under the New Owner

The new owner should immediately:

1. Turn registrar lock back on.
2. Enable two-factor authentication on their registrar account. See how to secure your domain registrar account with 2FA.
3. Turn on auto-renewal with a valid payment method.
4. Decide whether to use WHOIS privacy for the new contact details.
5. Rotate credentials for anything tied to the domain, such as DNS provider logins, email admin accounts, and hosting control panels.

Step 8: Sort Out DNS, Email, and Services

A domain transfer does not move the website or email. Before and after handover, agree on:

• Whether the DNS stays at the same provider or moves to the new owner's provider. If the zone moves, export the records first. See how to transfer DNS management to another provider.
• Whether the old owner's mailboxes on the domain need to be shut down or migrated.
• Any domain verification records for services such as Google Search Console, email providers, or SaaS tools. The new owner should verify their own accounts and remove the old owner's TXT records.
• SSL certificates, which will reissue automatically if the new owner's hosting uses ACME, but may need attention otherwise.

Verifying the Transfer

Public registration data is often redacted, so you may not see the new registrant's name in WHOIS. You can still verify the parts that are public:

# Registrar of record and status
whois example.com | grep -iE "registrar:|domain status"

# Name servers currently delegated
dig +short NS example.com

The new owner's registrar dashboard is the authoritative view of the registrant details. They should check that their name, organization, and email appear there, and the old owner should confirm the domain has disappeared from their account. More on running these lookups in how to use the dig command.

Special Situations

Moving a Domain From a Founder or Employee to the Company

This is one of the most common and most important ownership transfers. Domains registered years ago by a founder, developer, or agency in their own name are a serious business risk. Use a push into a company-controlled account, update the registrant organization to the company's legal name, and use a role email address. If the original registrant cannot be reached, see how to recover a domain registered under someone else's name.

Agencies Handing Domains to Clients

Agencies often register domains on behalf of clients. At the end of a project, push the domain to the client's own account and make sure the registrant is the client, not the agency. Doing this proactively avoids disputes later.

Deceased Registrants

Registrars usually have a documented process for transferring a domain after the registrant's death, typically requiring a death certificate and proof of the claimant's right to the estate. Contact the registrar's support team directly.

Country-Code TLDs

ccTLD registries set their own ownership transfer rules. Some require a formal registrant transfer form, identity checks, or a fee to the registry, and some require the new owner to meet local presence requirements. Check with the registrar or the registry for the specific TLD before promising a buyer a quick handover.

---

Domain Ownership Transfer FAQ

Conclusion

Transferring domain ownership comes down to changing two things: the registrant record, which defines the legal holder, and the account that controls the domain day to day. Choose between an account push at the same registrar, a registrant change, or a registrar transfer depending on where the new owner wants the domain to live, and use escrow whenever money changes hands.

Then finish the job. Update the registrant details to the correct person or company, handle the change-of-registrant confirmation and its transfer lock, re-enable locks and 2FA, turn on auto-renewal, and make sure DNS, email, and verification records belong to the new owner. A domain that is transferred properly today is one nobody has to fight over later.

Here are some useful references for going deeper on domain ownership transfers:

1. ICANN: Transfer Policy — the rules for inter-registrar transfers and the Change of Registrant process for gTLDs.
2. ICANN GNSO: Transfer Policy Review PDP — the policy work revising transfer and change of registrant rules.
3. ICANN: Registrants' Benefits and Responsibilities — what registrants are entitled to and responsible for under ICANN policy.
4. RFC 5731: EPP Domain Name Mapping — defines the domain object, contacts, and authorization information used in transfers.