How Domain Transfers Work: A Complete Guide

Whether you've just purchased a domain from a marketplace, acquired one through a private negotiation, or simply want to move your domain to a new registrar, understanding how domain transfers work is essential. The process involves multiple steps, technical requirements, and potential pitfalls that can delay or even derail your transfer if you're not prepared.

This guide covers everything you need to know about domain transfers, from the basics of authorization codes to registrar-specific tips and troubleshooting common issues.

What Is a Domain Transfer?

A domain transfer is the process of moving a domain name's registration from one registrar to another. When you buy a domain from someone who uses a different registrar than you, the domain needs to be transferred to your registrar account so you have full control over it.

It's important to distinguish between two types of domain moves:

• Registrar transfer (inter-registrar transfer): Moving a domain from one registrar to a completely different registrar (e.g., from GoDaddy to Namecheap). This is the standard ICANN-regulated transfer process.
• Account transfer (intra-registrar push): Moving a domain from one account to another account at the same registrar (e.g., from one GoDaddy account to another GoDaddy account). This is faster and simpler.

This guide primarily covers registrar transfers, as they are more complex and are what most buyers encounter when acquiring a domain from a seller. If you're buying a domain that's already taken, understanding this process is crucial.

Authorization Codes (EPP/Auth Codes)

An authorization code (also called an EPP code, auth code, transfer key, or domain secret) is a unique password assigned to your domain by the current registrar. This code is required to initiate a registrar transfer, and it serves as proof that the transfer is authorized by the domain's current registrant.

How to Get Your Auth Code

The process for obtaining an auth code varies by registrar, but generally follows one of these paths:

• Self-service: Most registrars let you generate or view the auth code from your domain management dashboard. Look for options labeled "Authorization Code," "EPP Code," "Transfer Key," or "Get Auth Code."
• Support request: Some registrars, particularly those with older interfaces or strict security policies, require you to contact support to receive the auth code via email.
• Automatic email: A few registrars automatically email the auth code to the registrant email address when a transfer is requested.

Auth Code Best Practices

Auth codes are time-sensitive. Most registrars generate codes that expire after 5-14 days, so don't request the code until you're ready to initiate the transfer. Treat the auth code like a password — anyone with the code can transfer the domain away. Never share it publicly, and only provide it through secure channels (such as an escrow service).

The Transfer Process Step-by-Step

Here's what happens during a standard inter-registrar domain transfer:

Step 1: Prepare the Domain at the Current Registrar

Before initiating the transfer, the current registrar (the "losing" registrar) must prepare the domain. This involves three actions:

• Unlock the domain: Remove any transfer lock (also called registrar lock or client transfer prohibited status)
• Disable WHOIS privacy: Some registrars require temporarily removing privacy protection for the transfer to proceed (though this requirement is becoming less common)
• Obtain the auth code: Generate or request the EPP authorization code

Step 2: Initiate the Transfer at the New Registrar

At the new registrar (the "gaining" registrar), you'll start the transfer by entering the domain name you want to transfer, providing the auth code, agreeing to the terms (including the transfer fee, which typically includes a one-year registration extension), and providing your contact and payment information.

Step 3: Confirmation Emails

After you initiate the transfer, both registrars send confirmation emails:

• The gaining registrar sends a confirmation to the domain's administrative contact asking them to approve the transfer
• The losing registrar sends a notification that a transfer has been requested, with an option to approve or reject

Approving the transfer at both ends speeds up the process significantly. If neither party takes action, the transfer will still proceed automatically after a waiting period (typically 5 days).

Step 4: The Waiting Period

ICANN requires a waiting period during which either party can cancel the transfer. This is a security measure to prevent unauthorized transfers. The waiting period is typically 5 calendar days, but it can be shorter if both parties actively approve the transfer.

Step 5: Transfer Completes

Once the waiting period ends (or both parties approve), the domain moves to the new registrar. The domain's registration is extended by one year from the current expiration date, and the new registrar becomes the registrar of record.

Understanding Transfer Locks

Transfer locks are a security feature that prevents unauthorized domain transfers. There are several types of locks you may encounter:

Registrar Lock (Client Transfer Prohibited)

This is the most common lock. Most registrars apply this lock by default to all domains. It must be removed before a transfer can be initiated. You can usually toggle this on or off from your registrar's domain management panel.

Registry Lock (Server Transfer Prohibited)

This is a higher-level lock applied at the registry level (not the registrar). It's typically used for high-value domains and provides an extra layer of security. Removing a registry lock usually requires manual verification with the registrar's security team, which can take additional time.

WHOIS Update Lock

Some registrars automatically apply a temporary transfer lock when WHOIS information is updated. This is separate from the ICANN 60-day lock and may have its own duration (often 60 days as well).

The ICANN 60-Day Lock Rule

One of the most important rules to understand is the ICANN 60-day transfer lock. This rule states that a domain cannot be transferred to a different registrar within 60 days of either initial registration (you just bought a brand-new domain) or a previous transfer (the domain was recently transferred to the current registrar).

Additionally, ICANN allows (but does not require) registrars to impose a 60-day lock after changes to the registrant's name, organization, or email address. Many registrars do enforce this, so updating your WHOIS information can trigger a transfer lock.

How This Affects Domain Purchases

If you're buying a domain that was recently registered or transferred, you may need to wait up to 60 days before you can transfer it to your registrar. In these cases, the seller can often do an account push instead (moving the domain to your account at the same registrar), which is not subject to the 60-day lock.

DNS Considerations During Transfer

One of the biggest concerns during a domain transfer is maintaining the website and email services associated with the domain. Here's what you need to know.

DNS Records Are Not Automatically Transferred

When a domain transfers to a new registrar, the DNS records do not automatically come with it. The nameservers will remain pointed at wherever they were before the transfer, but if the nameservers were provided by the old registrar, they may stop working after the transfer completes.

Best Practices for DNS During Transfer

To avoid downtime, follow these steps:

• Before the transfer: Document all existing DNS records (A, AAAA, CNAME, MX, TXT, etc.) by exporting them from the current registrar or DNS provider
• Use a third-party DNS provider: If possible, point the domain's nameservers to a third-party DNS service (like Cloudflare, Route 53, or similar) before the transfer. Since the nameservers are independent of the registrar, the transfer won't affect DNS resolution
• After the transfer: If you didn't use a third-party DNS, recreate all DNS records at the new registrar's DNS service and update the nameservers

Email Considerations

If MX records are disrupted during a transfer, email delivery will be affected. This is particularly critical for business domains. Make sure your MX records and any related TXT records (SPF, DKIM, DMARC) are properly recreated at the new registrar or DNS provider. If you need to understand more about domain privacy and its role during transfers, see our guide on what domain privacy protection is and why it matters.

Common Transfer Issues and How to Fix Them

Transfer Denied or Rejected

Common reasons for transfer denial include the following:

• Domain is locked: The transfer lock was not removed. Solution: Log in to the current registrar and disable the transfer lock.
• Invalid auth code: The authorization code is wrong or has expired. Solution: Generate a new auth code from the current registrar.
• 60-day lock: The domain was recently registered, transferred, or had WHOIS changes. Solution: Wait until the 60-day period expires.
• Domain expired: Expired domains often cannot be transferred. Solution: Renew the domain first, then initiate the transfer.
• Administrative contact rejection: The admin contact declined the transfer in the confirmation email. Solution: Ensure the seller approves the transfer when prompted.

Transfer Stuck in "Pending" Status

If a transfer has been pending for more than 7 days, check the email associated with the domain's admin contact for confirmation requests and make sure the domain is unlocked and the auth code is valid. Contact the gaining registrar's support team for status updates. In rare cases, contact the losing registrar to ensure they haven't blocked the transfer.

Lost Email or Website After Transfer

If your website or email stops working after a transfer, the most likely cause is a DNS issue. Check that nameservers are correctly pointing to your DNS provider and verify all DNS records (especially A records and MX records) are properly configured at the new location. DNS propagation can take up to 48 hours, so minor delays are normal.

Transfer Timeline

Here's a realistic timeline for a standard domain transfer:

• Preparation (unlock, get auth code): 15 minutes to 24 hours (depending on the registrar)
• Initiate transfer at new registrar: 5-10 minutes
• Confirmation emails: Sent within minutes to hours
• Waiting period: Up to 5 days (shorter if both parties approve quickly)
• Transfer completion: Usually within 1-2 hours after the waiting period
• Total time: 1-7 days for a smooth transfer

Some registrars are known for faster transfers than others. GoDaddy, Namecheap, and Cloudflare typically process transfers quickly, while some smaller or legacy registrars may take longer.

Registrar-Specific Tips

GoDaddy

GoDaddy provides the auth code in the domain management dashboard under "Transfer domain away from GoDaddy." They apply a 60-day lock after any WHOIS changes. For domains purchased on GoDaddy Auctions, there may be additional processing time before the domain is eligible for transfer.

Namecheap

Namecheap makes the transfer process straightforward. The auth code is available directly in the domain dashboard. They do not charge a fee for transferring domains away, and their support team is generally responsive if issues arise.

Cloudflare Registrar

Cloudflare Registrar charges at-cost pricing with no markup, making it an attractive destination for transfers. They only support a limited number of TLDs, so check compatibility before initiating a transfer to Cloudflare.

Google Domains (now Squarespace)

Google Domains was acquired by Squarespace in 2023. Domains previously registered with Google Domains are now managed through Squarespace's registrar interface. The transfer-out process may differ from the original Google Domains experience, so check Squarespace's current documentation for specific steps.

Push vs. Transfer: What's the Difference?

If both the buyer and seller use the same registrar, a domain push (also called an account change or internal transfer) is usually a better option than a full registrar transfer.

Advantages of a Push

• Speed: Pushes are typically instant or complete within hours
• No auth code needed: The process is handled entirely within the registrar's system
• No 60-day lock applies: The ICANN 60-day restriction only applies to inter-registrar transfers
• No transfer fee: Most registrars don't charge for account-to-account pushes
• DNS preserved: Since the domain stays at the same registrar, DNS records are usually preserved

When a Push Isn't Possible

A push requires both parties to have accounts at the same registrar. If the buyer and seller use different registrars, a standard transfer is the only option (unless one party is willing to create an account at the other's registrar).

Many domain escrow services and marketplaces facilitate pushes when possible, as they result in a smoother transaction for everyone involved.

Let DomainBuyer Handle Your Transfer