How to Transfer a Domain Safely After a Sale

Once a domain sale is agreed and the payment is secured, the transfer itself is the part where small technical slips cause the biggest headaches: a site that goes offline for days, email that stops arriving, or a transfer that silently fails because of a lock nobody checked. None of it is complicated if both sides know the sequence in advance. Here is how a domain changes hands cleanly, and what each party should check along the way.

Two ways a domain can move

There are two different operations people call "transferring a domain," and it helps to know which one you're doing:

• Account change at the same registrar. If buyer and seller use the same registrar, the seller can usually move the domain directly into the buyer's account (often called a "push" or "account change"). It's typically fast and doesn't reset the registration.
• Registrar transfer. If the buyer wants the domain at a different registrar, it's moved between companies using an authorization code (also called an EPP or auth code). This takes longer — often several days — and usually includes a year of renewal paid at the new registrar.

An account change first, followed later by a registrar transfer if the buyer prefers another provider, is often the smoothest path.

Before the transfer starts

Seller's checklist:

• Confirm the payment is held in escrow before touching anything. On Alpha Account Market, the buyer pays first and the funds are locked until the deal completes, so the transfer never happens on trust alone.
• Check the expiry date. A domain close to expiry should be renewed (or the renewal agreed) so it doesn't lapse mid-transfer.
• Check for transfer locks. Many registrars block registrar transfers for up to 60 days after a new registration, a previous transfer, or certain changes to the registrant's contact details. If the domain is inside one of those windows, plan an account change instead, or agree the timing with the buyer up front.
• Disable the registrar lock (sometimes called "transfer lock" or "clientTransferProhibited") when you're ready to move it.
• Map what depends on the domain. Note the current DNS records — website, email (MX records), verification records for services — so nothing is lost by accident.

During the transfer

For a registrar transfer, the seller requests the authorization code and shares it with the buyer through the deal chat, not by email or a side channel. The buyer starts the transfer at their registrar using that code, and the seller approves the request if the current registrar asks for confirmation. For an account change, the seller initiates it from their registrar dashboard using the buyer's account identifier.

Keep the conversation inside the platform's chat. If anything goes wrong later, that record is what a dispute review relies on.

Avoiding downtime

The domain moving is not the same thing as the site moving. If the domain points to a live website or email that the buyer is acquiring too, the safest approach is to keep the existing DNS records in place until the buyer has set up their own hosting and mail, and then switch the records in one planned step. If the buyer is acquiring only the name, the seller should move their own site or email off it before handover, so nothing breaks unexpectedly on either side.

After the domain arrives

Buyer's checklist once the domain is in their account:

• Confirm it appears in your registrar account with you as the registrant.
• Update the registrant, admin and technical contact details to your own.
• Re-enable the registrar lock and turn on auto-renew.
• Review the DNS records and remove anything you don't recognize.
• Enable two-factor authentication on the registrar account.

The 7-day inspection window starts at handover, which gives you time to confirm everything matches the listing before the funds are released to the seller.

Selling a name of your own? Start with how to sell your domain name. Looking for one instead? Browse domains for sale.