How to Transfer a Domain to a New Owner

Handing a domain to a new owner is not a single process. It depends on whether both parties use the same registrar, and whether ownership is moving between accounts or between completely different registrars. Both paths are also distinct from editing the registrant contact in WHOIS. This guide covers all three.

Two ways to transfer a domain to someone else

Account push (same registrar)

If both the current owner and the new owner have accounts at the same registrar, a domain push is the quickest option. The current owner initiates the push from their control panel and specifies the recipient's account. The recipient accepts, and the domain moves over — usually instantly, with no auth code, no transfer fee, and no waiting period. Not every registrar calls this a "push"; look for options like "Transfer to another account" or "Internal transfer."

Full registrar transfer (different registrar)

If the new owner prefers a different registrar, a standard outgoing domain transfer is required. This involves unlocking the domain, obtaining an authorization (EPP/auth) code, and the recipient initiating the transfer at their chosen registrar. The process takes up to 5–7 days and includes a transfer fee, which typically covers one additional year of registration. For the complete step-by-step on this path, see our guide to transferring a domain between registrars.

Before you start: what you need

Step-by-step: push at the same registrar

1

Confirm both accounts exist at the same registrar

The new owner needs an active account at the same registrar. If they do not have one, they can create a free account without purchasing anything.

2

Initiate the push from your account

In your registrar's control panel, open the domain's settings and look for an option such as "Push domain," "Transfer to another account," or "Internal transfer." Enter the new owner's account email or username exactly as registered.

3

New owner accepts the incoming domain

The new owner receives a notification — either in their account dashboard or by email — and accepts the domain. Once accepted, the domain is in their account. Update the registrant contact details afterwards to reflect the new owner.

Step-by-step: full transfer to a different registrar

This is a summary of the key steps. For the full walkthrough including WHOIS privacy, DNS verification, and common failure points, read our complete domain transfer guide.

1

Unlock the domain

Disable the transfer lock (also called registrar lock) in your control panel. This signals to the registry that you authorize an outgoing transfer.

2

Obtain the auth/EPP code

Request an authorization code from your current registrar. This is a security code that proves you are the domain owner. It is usually sent to the registrant email address within minutes to a few hours.

3

Share the code with the new owner

Send the auth code to the new owner securely. They will need it to initiate the transfer at their chosen registrar. Auth codes can be time-sensitive — some registrars issue codes that expire within 24–72 hours, so coordinate timing in advance.

4

New owner initiates the transfer

The new owner goes to their registrar and starts a domain transfer, entering the domain name and the auth code. They pay the transfer fee, which typically includes one additional year of registration added to the existing expiry date.

5

Approve the transfer

You will receive an email at the registrant address asking you to approve or cancel. Approve it to speed up the process. If you do not respond, most transfers complete automatically after 5 days for generic TLDs like .com.

6

Wait for completion and verify

The transfer typically completes within 2–7 days. DNS resolution is unaffected throughout. Once complete, the new owner should verify DNS settings and re-enable WHOIS privacy if it was disabled.

Changing the registrant contact (and what it means for transfers)

Changing the name, organization, or email listed as the registrant in WHOIS is a separate action from moving a domain between accounts. For generic TLDs like .com and .net, registrars are required under ICANN's inter-registrar transfer policy to send a Form of Authorization (FOA) to both the old and new registrant contact when a material change to the registrant is made — for example, changing from one legal entity to another.

Some registrars also apply a 60-day transfer lock after such a change, preventing the domain from being moved to a different registrar during that window. This is a registrar-level policy in response to ICANN guidance, not a universal rule that applies identically to all registrant edits or all registrars. Changing only an email address, for instance, may or may not trigger this depending on your registrar's specific implementation. Check with your registrar before making changes.

If your goal is both to transfer ownership and to switch registrars, completing the registrar transfer first and then updating the registrant contact at the new registrar is the simpler workflow.

Common blockers and mistakes

The domain push failed — why?

Most push failures are account-related: the recipient's account does not exist at that registrar, or the email address you entered is slightly incorrect. Some registrars also require the domain to be free of any locks before a push can proceed. Confirm the recipient's account details directly and contact your registrar's support if the issue persists.

The auth code was rejected at the new registrar

Auth codes can expire (some registrars issue codes valid for only 24–72 hours) and are case-sensitive. If the code is rejected, request a fresh one from your current registrar and submit it at the new registrar promptly. Do not copy-paste with extra spaces.

Do I need to update the registrant contact when transferring to a new owner?

For an account push, the registrant contact in WHOIS does not automatically update. It is good practice to update it after the push so the record reflects the actual new owner. For a full registrar transfer, the registrant contact can be updated once the transfer is complete at the new registrar.

Will there be any downtime?

Neither a push nor a registrar transfer should affect DNS resolution or cause website downtime. The domain continues to resolve normally throughout. Avoid changing nameservers until after the transfer is complete and confirmed.

Need to evaluate a domain name before registering?

Try the Domain Evaluator →

Related guides

How to transfer a domain between registrars →

How to transfer a locked domain →

Compare domain registrars →

How to buy a domain name →