Route 53 Domain Transfer: Move Your Domain In or Out (2026)

Transferring your domain name between registrars is a surprisingly manual process, often involving more clicks and confirmations than you’d expect for something so automated.

Let’s walk through transferring a domain into AWS Route 53 from another registrar. Imagine we have a domain, example.com, currently registered with GoDaddy.

First, we need to initiate the transfer from Route 53’s side.

1. Unlock the Domain at the Current Registrar: Log into your GoDaddy account. Find example.com. You’ll need to disable "domain lock" or "transfer protection." This is a security feature to prevent unauthorized transfers. Without this, Route 53 won’t even be able to start the process.

   • Why it works: This flag at the registrar level tells the registry (like Verisign for .com domains) that the domain is permitted to be moved.

2. Obtain the Authorization Code (EPP Code): While still in your GoDaddy account, you’ll need to request an authorization code, often called an EPP code or transfer code. This is a unique password for your domain. GoDaddy will usually email this to the administrative contact listed for the domain.

   • Why it works: This code proves you have legitimate control over the domain and are authorized to initiate the transfer. It’s like a digital key.

3. Initiate the Transfer in Route 53: Go to the Route 53 console in AWS. Navigate to "Registered domains" and click "Transfer domain." Enter example.com and click "Check availability." Route 53 will verify the domain is eligible for transfer (not within 60 days of registration or a previous transfer, for example). You’ll then be prompted to enter the authorization code you got from GoDaddy.

   • Why it works: Route 53 uses this code to authenticate your request with the domain registry, saying, "I have the owner’s permission to take this domain."

4. Confirm Contact Information: Route 53 will pull the current contact details for example.com. You’ll need to confirm these are correct, especially the administrative contact email. This is crucial because the registry will send confirmation emails to this address.

   • Why it works: This ensures that the domain’s ownership records are updated accurately with the new registrar.

5. Approve the Transfer at the Current Registrar (Often): Many registrars, including GoDaddy, will send an email to the administrative contact asking you to confirm the transfer request. This is another security step. You’ll typically click a link in this email to approve the transfer.

   • Why it works: This provides a final confirmation from the domain owner to the current registrar, signaling that the transfer is indeed intended.

6. Wait for the Transfer to Complete: Domain transfers can take anywhere from a few hours to several days (typically 5-7 days). Route 53 will show the status of the transfer. You’ll receive emails from both AWS and your old registrar as the process progresses.

   • Why it works: The actual DNS records are updated at the registry level to point to the new registrar’s management system. This takes time to propagate and for all parties to acknowledge.

Transferring Out of Route 53:

The process is similar but reversed.

1. Initiate Transfer Out in Route 53: In the Route 53 console, go to "Registered domains," select example.com, and click "Transfer domain to another registrar." Route 53 will ask you to confirm. It will then disable the transfer lock and generate an authorization code. You’ll find this code in the domain’s details page under "Transfer authorization code."

   • Why it works: Route 53 is removing its lock and providing the key (EPP code) needed by the new registrar to claim the domain.

2. Provide Auth Code to New Registrar: Log into your new registrar (e.g., Namecheap). Find their domain transfer section and initiate a transfer for example.com. You’ll need to provide the authorization code obtained from Route 53.

   • Why it works: The new registrar uses this code to prove to the registry that you’ve authorized them to take over management.

3. Approve Transfer (Email Confirmation): You’ll receive an email from Route 53 (to the administrative contact) asking you to confirm the transfer out. You must click the link in this email to approve.

   • Why it works: This is Route 53’s final check to ensure you, the owner, are intentionally moving the domain away.

4. Wait: Similar to transferring in, the process takes 5-7 days. The new registrar will update you on the status.

   • Why it works: The registry updates its records to reflect the new registrar.

A common pitfall is forgetting to disable the transfer lock at the current registrar before initiating the transfer at the new one. If you’ve started the transfer and it stalls, this is almost always the first thing to check.

Once a domain transfer completes, you might find that your DNS records (A, CNAME, MX records, etc.) are not automatically copied over. You’ll need to manually recreate them in the new registrar’s DNS management interface, or configure Route 53 to host your DNS if you’re transferring out of Route 53.