# Transferring domains
<a name="domain-transfer"></a>

You can transfer domain registration from another registrar to Amazon Route 53, from one AWS account to another, or from Route 53 to another registrar. There is no cost for transferring domains from one AWS account to another.

The topics in this section cover the following topics related to transferring domains:

1. [Choose your transfer type](domain-transfer-decision-guide.md)
   + Understand the difference between transferring domain registration to Route 53 versus using Route 53 for DNS hosting only.
   + Learn which option is right for your needs based on your goals for domain management and DNS hosting.

1. [Pre-transfer checklist](domain-transfer-checklist.md)
   + Complete essential preparation steps before transferring your domain to Route 53 to avoid common transfer failures.
   + Verify domain eligibility, obtain authorization codes, and prepare your DNS settings for a smooth transfer process.

1. [Transferring registration for a domain to Amazon Route 53](domain-transfer-to-route-53.md)
   + Learn the step-by-step procedure for transferring a domain from another registrar to Route 53, including prerequisites, authorization codes, and updating DNS settings. 
   + Understand how transferring a domain affects the expiration date and the considerations for different top-level domains (TLDs).

1. [Common transfer issues](domain-transfer-troubleshooting.md)
   + Prevent common transfer issues by understanding domain requirements, authorization processes, and timing considerations.
   + Learn how to resolve transfer problems and what to do if your transfer is delayed or rejected.

1. [Transferring a domain from Amazon Route 53 to another registrar](domain-transfer-from-route-53.md)
   + Understand the process of transferring a domain from Route 53 to another registrar, including obtaining the authorization code, updating DNS settings, and responding to confirmation emails. 
   + Be aware of the considerations when transferring DNS service to another provider and the potential impact on Route 53-specific features like alias records and routing policies.

1. [Transferring a domain to a different AWS account](domain-transfer-between-aws-accounts.md)
   + Find out how to transfer a domain from one AWS account to another, including the roles and permissions required for initiating and accepting the transfer.
   + Learn about the optional step of migrating the hosted zone to the new account after the domain transfer. 

1. [Transfer status](domain-transfer-to-route-53-status.md)
   + Discover how to view the status of a domain transfer request and the meaning of different status codes during the transfer process.

1. [How transferring a domain to Amazon Route 53 affects the expiration date for your domain registration](domain-transfer-to-route-53-expiration.md)
   + Find out how transferring a domain to Route 53 might affect the expiration date for the domain.

By following the information provided in the topics listed above, you can effectively transfer domains to and from Route 53, manage the transfer process, and ensure a smooth transition while maintaining proper DNS configuration and routing.

# Choose your Route 53 transfer type
<a name="domain-transfer-decision-guide"></a>

When you want to use Amazon Route 53 with your domain, you have two options. Understanding the difference will help you choose the right approach for your needs:

## Transfer domain registration to Route 53
<a name="domain-transfer-decision-guide-registration-transfer"></a>

With this option, Route 53 becomes your domain registrar. This means you'll manage your domain renewals, contact information, and DNS settings all through Route 53. 

**Choose this option if you want to:**
+ Consolidate domain management and DNS hosting in one place
+ Take advantage of Route 53 domain management features
+ Simplify billing by having domain renewals on your AWS bill

**What to expect:**
+ **Time to complete:** 5-7 days
+ **Prerequisites:** Authorization code from current registrar, unlock domain, verify registrant email
+ **Who you pay for renewals:** Route 53

**Next step:** Complete the [Pre-transfer checklist for domain transfers](domain-transfer-checklist.md) to prepare for the transfer.

## Use Route 53 for DNS hosting only
<a name="domain-transfer-decision-guide-dns-only"></a>

With this option, you keep your current domain registrar but use Route 53 as your DNS service. 

**Choose this option if you want to:**
+ Keep your existing registrar relationship
+ Use Route 53 advanced DNS features without changing registrars
+ Get started quickly with minimal prerequisites

**What to expect:**
+ **Time to complete:** Up to 2 days (depends on DNS propagation)
+ **Prerequisites:** None
+ **Who you pay for renewals:** Your current registrar

**Next step:** Go to [Configuring Amazon Route 53 as your DNS service](dns-configuring.md) to set up DNS hosting.

**Important**  
You don't have to transfer your domain registration to use Route 53 as your DNS service. You can keep your existing registrar and use Route 53 only for DNS hosting.

# Pre-transfer checklist for domain transfers
<a name="domain-transfer-checklist"></a>

Before you begin transferring your domain registration to Amazon Route 53, complete the following checks to avoid common transfer failures and ensure a smooth process.

## Decide what you want to transfer
<a name="domain-transfer-checklist-decision"></a>

Choose the option that matches your needs:

**Transfer domain registration to Route 53**  
Your registrar becomes Amazon Route 53. You pay Route 53 for domain renewals and manage domain settings through the Route 53 console.  
**Next step:** Continue with this checklist, then follow [Transferring registration for a domain to Amazon Route 53](domain-transfer-to-route-53.md).

**Use Route 53 for DNS hosting only**  
Keep your current registrar but use Route 53 name servers for DNS resolution. You continue paying your current registrar for renewals.  
**Next step:** Skip this checklist and follow [Configuring Amazon Route 53 as your DNS service](dns-configuring.md).

## Prerequisites checklist
<a name="domain-transfer-checklist-prerequisites"></a>

Complete all of the following before starting your domain transfer.<a name="domain-transfer-checklist-with-timing"></a>

**Pre-transfer checklist (Complete all items)**

1. **☐ Verify registrant email access** 

   Confirm that you can receive email at the registrant email address, as it will receive the domain transfer authorization email.
**Important**  
If you cannot access the current registrant email address, update the email address for the registrant contact with your current registrar and wait 60 days before transferring.

1. **☐ Unlock domain** 

   Access your current registrar domain settings and disable the "Domain Lock" or "Transfer Lock" protection, if enabled.
**Note**  
After disabling the lock, allow a few minutes for the change to take effect before starting your transfer.

1. **☐ Obtain authorization code** 

   Request an authorization code (auth code) from your current registrar and maintain its confidentiality. You'll enter this code in the Route 53 console later in the transfer process.

1. **☐ Verify domain age and eligibility**

   Confirm your domain meets ICANN transfer requirements:
   + The domain must be at least 60 days old since initial registration.
   + If the domain registration expired and was restored, it must have been restored at least 60 days ago.
**Tip**  
ICANN rules may temporarily block transfers if registrant contact details were updated recently (for example, changing your name or email). Some registrars let you opt out of this hold — check with your current registrar if you're unsure.

1. **☐ Prepare payment method** 

   Ensure your AWS account has a valid payment method. When you transfer a domain to Route 53, the transfer fee that we apply to your AWS account varies by top-level domain.

   For current pricing, see [Route 53 Pricing](https://aws.amazon.com/route53/pricing/).
**Note**  
You cannot use AWS credits to pay for domain transfers. Route 53 charges the transfer fee before starting the process and provides an immediate refund if the transfer fails.

1. **☐ Disable DNSSEC (if enabled)** 

   If DNSSEC is currently enabled with your current registrar, temporarily disable it before starting the transfer. This ensures the transfer can complete without DNS validation issues.

   **Why this matters:**

   When you transfer a domain, the DNSSEC keys (KSK/ZSK) and DS records stored at your current registrar are not automatically transferred to Route 53. If you re-enable DNSSEC without reconfiguring these keys in Route 53, your domain may fail DNS validation.

   **Safe approach (recommended):**

   1. Disable DNSSEC at your current registrar before initiating the transfer.

   1. Complete the domain transfer and create your Route 53 hosted zone (if not already created).

   1. Verify that all DNS records are resolving correctly without DNSSEC enabled.

   1. Configure DNSSEC in Route 53 using your hosted zone's new KSK/ZSK values.

   1. Re-enable DNSSEC by publishing the new DS record with your TLD registrar (now Route 53).
**Tip**  
If you are transferring your domain along with creating a new hosted zone in Route 53, disable DNSSEC before transferring, then wait until the hosted zone setup is verified and DNS resolution works correctly. Once confirmed, you can safely enable DNSSEC again from Route 53's console. Always verify your DNS configuration in Route 53 before re-enabling DNSSEC. For more information about DNSSEC with Route 53, see [Configuring DNSSEC for a domain](domain-configure-dnssec.md).

## Optional: Transfer DNS service first
<a name="domain-transfer-checklist-optional"></a>

Consider transferring your DNS service to Route 53 before transferring domain registration. This approach provides these benefits:
+ Reduces the risk of website or email downtime during the transfer
+ Allows you to test Route 53 DNS functionality before committing to the full transfer
+ Provides a fallback option if the domain transfer encounters issues

To transfer DNS service first, see [Configuring Amazon Route 53 as your DNS service](dns-configuring.md).

## Next steps
<a name="domain-transfer-checklist-next-steps"></a>

After completing this checklist:

1. Follow the step-by-step transfer process in [Transferring registration for a domain to Amazon Route 53](domain-transfer-to-route-53.md).

1. Monitor your email for authorization messages during the transfer process.

# Transferring registration for a domain to Amazon Route 53
<a name="domain-transfer-to-route-53"></a>

**Important**  
During the transfer of any country code top-level domains (ccTLDs) to Route 53, except for .cc and .tv, updates to the owner contact are ignored and the owner contact data from the registry is used. You can update the owner contact after the transfer is complete. For more information, see [Updating contact information and ownership for a domain](domain-update-contacts.md).

To transfer the registration for a domain to Amazon Route 53, follow the procedures in this topic. 

## Transfer process overview
<a name="domain-transfer-overview"></a>

Domain transfer involves these key steps:

1. **Complete pre-transfer checklist** 

   Verify prerequisites to avoid transfer failures. See [Pre-transfer checklist for domain transfers](domain-transfer-checklist.md).

1. **Request transfer in Route 53 console** 

   Enter domain name and authorization code. See [Step 5: Request the transfer](#domain-transfer-to-route-53-request-transfer).

1. **Authorize via email** (*Customer action required)*

   Click authorization link sent to registrant email within 5 days. See [Step 6: Click the link in the confirmation and authorization emails](#domain-transfer-to-route-53-authorize-transfer).

1. **Wait for completion** 

   Transfer completes automatically unless rejected by current registrar. Monitor status in console.

**Most common failure points**  
The following are solutions for common issues:
+ **Email not received**: Verify registrant email is accessible and check spam folder
+ **Domain locked**: Unlock at current registrar before starting transfer
+ **Invalid auth code**: Request new authorization code from current registrar
+ **60-day rule violation**: 60-day ICANN rule (eligibility window). Transfers are blocked within 60 days of initial registration or a registrant contact change. Some registrars allow an opt-out before the change—ask your current registrar if applicable.

**Important**  
If you skip a step, your domain might become unavailable on the internet.

Note the following:

**Contacting AWS Support**  
If you encounter issues while transferring a domain, you can contact AWS Support for free. For more information, see [Contacting AWS Support about domain registration issues](domain-contact-support.md).

**Expiration date**  
For information about how transferring your domain affects the current expiration date, see [How transferring a domain to Amazon Route 53 affects the expiration date for your domain registration](domain-transfer-to-route-53-expiration.md).

**Transfer fee**  
When you transfer a domain to Route 53, the transfer fee that we apply to your AWS account depends on the top-level domain, such as .com or .org. For more information, see [Route 53 Pricing](https://aws.amazon.com/route53/pricing/).   
You can't use AWS credits to pay the fee, if any, for transferring a domain to Route 53.  
Route 53 charges the fee for transferring your domain before we start the transfer process. If a transfer fails for some reason, we immediately credit your account for the cost of the transfer.

**Special and premium domain names**  
TLD registries have assigned special or premium prices to some domain names. You can't transfer a domain to Route 53 if the domain has a special or premium price.

**Domain quotas**  
The default maximum number of domains per AWS account is 20. You can [request a higher quota](https://us-east-1.console.aws.amazon.com/servicequotas/home/services/route53/quotas/L-F767CB15). For more information, see [Quotas on domains](DNSLimitations.md#limits-api-entities-domains).

**Name servers limit**  
The maximum number of name servers per domain in Route 53 is 6.

**Topics**
+ [Transfer process overview](#domain-transfer-overview)
+ [Transfer requirements for top-level domains](#domain-transfer-to-route-53-requirements)
+ [Step 1: Confirm that Amazon Route 53 supports the top-level domain](#domain-transfer-to-route-53-confirm-tld)
+ [Step 2 (Optional): Transfer your DNS service to Amazon Route 53 or another DNS service provider](#domain-transfer-to-route-53-transfer-dns)
+ [Step 3: Change settings with the current registrar](#domain-transfer-to-route-53-change-registrar-settings)
+ [Step 4: Get the names of your name servers](#domain-transfer-to-route-53-get-name-servers)
+ [Step 5: Request the transfer](#domain-transfer-to-route-53-request-transfer)
+ [Step 6: Click the link in the confirmation and authorization emails](#domain-transfer-to-route-53-authorize-transfer)
+ [Step 7: Update the domain configuration](#domain-transfer-to-route-53-change-configuration)

## Transfer requirements for top-level domains
<a name="domain-transfer-to-route-53-requirements"></a>

Most domain registrars enforce requirements on transferring a domain to another registrar. The primary purpose of these requirements is to prevent the owners of fraudulent domains from repeatedly transferring the domains to different registrars. Requirements vary, but the following requirements are typical: 
+ You must have either registered the domain with the current registrar or transferred registration for the domain to the current registrar at least 60 days ago.
+ If the registration for a domain name expired and had to be restored, it must have been restored at least 60 days ago.
+ The domain cannot have any of the following domain name status codes:
  + clientTransferProhibited
  + pendingDelete
  + pendingTransfer
  + redemptionPeriod
  + serverTransferProhibited
+ The registries for some top-level domains don't allow transfers until changes are complete, such as changes to the domain owner.

For a current list of domain name status codes and an explanation of what each code means, go to the [website for ICANN](https://www.icann.org/), and search for EPP status codes. (Search on the ICANN website; web searches sometimes return an old version of the document.)

**Note**  
ICANN is the organization that establishes policies governing registration and transfer of domain names.

You can also search for your domain name in [website for Whois](https://www.whois.com/whois/) to see status codes and other information for your domain.

## Step 1: Confirm that Amazon Route 53 supports the top-level domain
<a name="domain-transfer-to-route-53-confirm-tld"></a>

See [Domains that you can register with Amazon Route 53](registrar-tld-list.md). If the top-level domain for the domain that you want to transfer is on the list, you can transfer the domain to Amazon Route 53. 

If a TLD is not on the list, you can't currently transfer the domain registration to Route 53. We occasionally add more TLDs to the list, so check back to see if we've added support for your domain. 

## Step 2 (Optional): Transfer your DNS service to Amazon Route 53 or another DNS service provider
<a name="domain-transfer-to-route-53-transfer-dns"></a>

**Why transfer DNS first?**

Some registrars provide free DNS service that might be disabled as soon as they receive a request from Route 53 to transfer the domain's registration. If you'd like Route 53 to provide DNS service for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Step 3: Change settings with the current registrar
<a name="domain-transfer-to-route-53-change-registrar-settings"></a>

Using the method provided by your current registrar, do each of the following for each domain that you want to transfer.
+ [Confirm that the email for the registrant contact for your domain is up to date](#domain-transfer-to-route-53-change-registrar-settings-email)
+ [Unlock the domain so it can be transferred](#domain-transfer-to-route-53-change-registrar-settings-unlock)
+ [Confirm that the domain status allows you to transfer the domain](#domain-transfer-to-route-53-change-registrar-settings-status)
+ [Disable DNSSEC for the domain](#domain-transfer-to-route-53-change-registrar-settings-dnssec)
+ [Get an authorization code](#domain-transfer-to-route-53-change-registrar-settings-code)
+ [Renew your domain registration before you transfer the domain (selected geographic TLDs)](#domain-transfer-to-route-53-change-registrar-settings-renew)

**Confirm that the email for the registrant contact for your domain is up to date**  
We'll send email to that email address to request authorization for the transfer. You need to click a link in the email to authorize the transfer. If you don't click the link, we must cancel the transfer.  
The contact you list as the registrant will have certain rights as the Registered Name Holder of the domain name, under the [ICANN Transfer Policy](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en). Most domains will be deleted upon closure of your AWS account (for more information, see [My AWS account is closed or permanently closed, and my domain is registered with Route 53](troubleshooting-account-closed.md)), however if a domain remains in a closed account, the contact you listed as the registrant may have the ability to request a transfer of the domain name to an external registrar. Therefore, it is important that the registrant contact you list is either yourself or another person you trust to act responsibly.

**Unlock the domain so it can be transferred**  
ICANN, the governing body for domain registrations requires that you unlock your domain before you transfer it.

**Confirm that the domain status allows you to transfer the domain**  
For more information, see [Transfer requirements for top-level domains](#domain-transfer-to-route-53-requirements).

** Disable DNSSEC for the domain **  
If you use DNSSEC with a domain and you transfer the domain registration to Route 53, you must disable DNSSEC at the former registrar first. Then, after you transfer the domain registration, take steps to set up DNSSEC for the domain in Route 53. Route 53 supports DNSSEC for domain registration and for DNSSEC signing. For more information, see [Configuring DNSSEC signing in Amazon Route 53](dns-configuring-dnssec.md).  
If you transfer a domain registration to Route 53 while DNSSEC is configured, the DNSSEC public keys are transferred, too. If you transfer DNS service to a provider that doesn't support DNSSEC, DNS resolution fails intermittently until you delete the DNSSEC keys from the domain. For more information, see [Deleting public keys for a domain](domain-configure-dnssec.md#domain-configure-dnssec-deleting-keys).

**Get an authorization code**  
An authorization code from the current registrar authorizes us to request that registration for the domain be transferred to Route 53. You'll enter this code in the Route 53 console later in the process.  
Some top-level domains have additional requirements:    
**.co.za domains**  
You don't need to get an authorization code to transfer a .co.za domain to Route 53.  
**.uk, .co.uk, .me.uk, and .org.uk domains**  
If you're transferring a .uk, .co.uk, .me.uk, or .org.uk domain to Route 53, you don't need to get an authorization code. Instead, use the method provided by your current domain registrar to update the value of the IPS tag for the domain to **GANDI**, all uppercase. (An IPS tag is required by Nominet, the registry for .uk domain names.) If your registrar doesn't provide a way to change the value of the IPS tag, [contact Nominet](https://www.nominet.uk/domain-support/online-services).  
Note the following about changing the IPS tag:    
**You must request the transfer within five days**  
If you don't request the transfer within five days after you change the IPS tag, the tag changes back to the previous value. You must change the value of the IPS tag again, or the transfer request will fail.   
**Viewing the IPS tag in WHOIS queries**  
The change to the IPS tag doesn't appear in WHOIS queries until after the transfer to Route 53 has completed.   
**Email from Gandi**  
You might receive an email from our registrar associate, Gandi, about the transfer process. If you receive an email from Gandi (transfer-auth@gandi.net) about transferring your domain, ignore the instructions in the email because they aren't relevant to a .uk, .co.uk, .me.uk, or .org.uk domains. Follow the instructions in this topic instead.

**Renew your domain registration before you transfer the domain (selected geographic TLDs)**  
For most TLDs, when you transfer a domain, the registration is automatically extended by one year. However, for some geographic TLDs, registration is not extended when you transfer the domain. If you're transferring a domain to Route 53 that has one of these TLDs, we recommend that you renew the domain registration before you transfer the domain, especially if the expiration date is approaching.  
If you don't renew the domain before you transfer it, the registration could expire before the transfer is complete. If this happens, the domain becomes unavailable on the internet, and the domain name could become available for others to purchase.
Registration is not automatically extended when you transfer the following domains to another registrar:  
+ .ch (Switzerland)
+ .cl (Chile)
+ .co.uk (United Kingdom)
+ .co.za (South Africa)
+ .com.au (Australia)
+ .cz (Czech Republic)
+ .es (Spain)
+ .fi (Finland)
+ .im (Isle of Man)
+ .jp (Japan)
+ .me.uk (United Kingdom)
+ .net.au (Australia)
+ .org.uk (United Kingdom)
+ .se (Sweden)
+ .uk (United Kingdom)

## Step 4: Get the names of your name servers
<a name="domain-transfer-to-route-53-get-name-servers"></a>

If you're using Amazon Route 53 as your DNS service or you're continuing to use the existing DNS service, we'll get the names of the name servers for you automatically later in the process. Skip to [Step 5: Request the transfer](#domain-transfer-to-route-53-request-transfer).

If you want to change the DNS service to a provider other than Route 53 at the same time that you're transferring the domain to Route 53, use the procedure provided by the DNS service provider to get the names of the name servers for each domain that you want to transfer.

**Important**  
If the registrar for your domain is also the DNS service provider for the domain, transfer your DNS service to Route 53 or another DNS service provider *before* you continue with the process to transfer the domain registration.   
If you transfer DNS service at the same time that you transfer domain registration, your website, email, and the web applications associated with the domain might become unavailable. For more information, see [Step 2 (Optional): Transfer your DNS service to Amazon Route 53 or another DNS service provider](#domain-transfer-to-route-53-transfer-dns).

## Step 5: Request the transfer
<a name="domain-transfer-to-route-53-request-transfer"></a>

To transfer domain registration from the current registrar to Amazon Route 53, use the Route 53 console to request the transfer. Route 53 handles the communication with the current registrar for the domain.

You can use the console to transfer up to five domains.

The procedure that you use depends on whether you want to transfer a single domain or up to five domains:
+ [To transfer domain registration of a single domain to Route 53](#domain-transfer-to-route-53-single-procedure)
+ [To transfer domain registration to Route 53 for up to five domains](#domain-transfer-to-route-53-up-to-five-procedure)

Use the **Transfer domain to your account** process to transfer a single domain to your account.<a name="domain-transfer-to-route-53-single-procedure"></a>

**To transfer domain registration of a single domain to Route 53**

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Registered domains**.

1. On the **Registered Domains** page, choose **Single domain** from the **Transfer in** dropdown.

1. On the **Transfer domain to your account** page, in the **Check domain transferability** section, enter the name of the domain for which you want to transfer registration to Route 53, and choose **Check**.

1. If the domain registration is available for transfer, verify that you have completed the transfer requirements for top-level domains, and choose **Next**.

   If the domain registration is not available for transfer, the Route 53 console lists the reasons. Contact your registrar for information about how to resolve the issues that prevent you from transferring the registration.

1. On the **DNS service** page, review the information about name servers, and choose **Next**.

1. If prompted, enter the authorization code or IPS tag that you got from your current registrar in [Step 3: Change settings with the current registrar](#domain-transfer-to-route-53-change-registrar-settings).
**Note**  
You don't need to enter an authorization code to transfer a .co.za, .uk, .co.uk, .me.uk, or .org.uk domain to Route 53.

   Choose **Next**.

1. On the **Domain pricing options** page, choose the number of years that you want to register the domain you are transferring for and whether you want us to automatically renew your domain registration before the expiration date. 
**Note**  
Domain name registrations and renewals are not refundable. If you enable automatic domain renewal and you decide that you don't want the domain name after we renew the registration, you can't get a refund for the cost of the renewal.

   Choose **Next**.

1. On the **Contact information** page, enter contact information for the domain registrant, admin, technical, and billing contacts. The values that you enter here are applied to all of the domains that you're registering. For more information, see [Values that you specify when you register or transfer a domain](domain-register-values-specify.md).

   Note the following considerations:  
**First Name and Last Name**  
For **First Name** and **Last Name**, we recommend that you specify the name on your official ID. For some changes to domain settings, some domain registries require that you provide proof of identity. The name on your ID must match the name of the registrant contact for the domain.  
**Different contacts**  
By default, we use the same information for all three contacts. If you want to enter different information for one or more contacts, change the value of **Same as registrant contact** toggle switch to off position.  
For .it domains, the registrant and admin contacts must be the same.  
**Additional required information**  
For some top-level domains (TLDs), we're required to collect additional information. For these TLDs, enter the applicable values after the **Postal/Zip Code** field.  
**Privacy protection**  
Choose whether you want to hide your contact information from WHOIS queries.   
You must specify the same privacy setting for the admin, registrant, and technical contacts.
For more information, see the following topics:  
   + [Enabling or disabling privacy protection for contact information for a domain](domain-privacy-protection.md)
   + [Domains that you can register with Amazon Route 53](registrar-tld-list.md)
To enable privacy protection for .uk, .co.uk, .me.uk, and .org.uk domains, you must open a support case and request privacy protection. 

   Choose **Next**.

1. On the **Review** page, review the information that you entered, and optionally correct it. Read the terms of service, and select the check box to confirm that you've read the terms of service.

   Choose **Submit request**.

1. In the navigation pane, choose **Domains** and then **Requests**.

   On this page, you can view the status of domain and also if you need to respond to registrant contact verification email. You can also choose to resend the verification email.

   If you specified an email address for the registrant contact that has never been used to register a domain with Route 53, some TLD registries require you to verify that the address is valid.

   We send a verification email from one of the following email addresses:
   + **noreply@registrar.amazon** – for TLDs registered by Amazon Registrar.
   + **noreply@domainnameverification.net** or **noreply@emailverification.info** – for TLDs registered by our registrar associate, Gandi. To determine who the registrar is for your TLD, see [Finding your registrar](find-your-registrar.md).
**Important**  
The registrant contact must follow the instructions in the email to verify that the email was received, or we must suspend the domain as required by ICANN. When a domain is suspended, it's not accessible on the internet.

   1. When you receive the verification email, choose the link in the email that verifies that the email address is valid. If you don't receive the email immediately, check your junk email folder.

   1. Return to the **Requests** page. If the status doesn't automatically update to say **email-address is verified**, choose **Refresh status**.

1. When domain transfer is complete, your next step depends on whether you want to use Route 53 or another DNS service as the DNS service for the domain:
   + **Route 53** – In the hosted zone that Route 53 created when you registered the domain, create records to tell Route 53 how you want to route traffic for the domain and subdomains. 

     For example, when someone enters your domain name in a browser and that query is forwarded to Route 53, do you want Route 53 to respond to the query with the IP address of a web server in your data center or with the name of an Elastic Load Balancing load balancer?

     For more information, see [Working with records](rrsets-working-with.md).
**Important**  
If you create records in a hosted zone other than the one that Route 53 creates automatically, you must update the name servers for the domain to use the name servers for the new hosted zone.
   + **Another DNS service** – Configure your new domain to route DNS queries to the other DNS service. Perform the procedure [Updating name servers to use another registrar](domain-register-other-dns-service.md).

Use the following procedure to transfer up to five domains to your account.<a name="domain-transfer-to-route-53-up-to-five-procedure"></a>

**To transfer domain registration to Route 53 for up to five domains**

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Registered domains**.

1. On the **Registered domains** page, choose **Multiple domains** from the **Transfer in** dropdown.

1. On the **Transfer multiple domains to your account** page, enter up to five domains you want to transfer, and their authorization code, if required, per line, and choose **Check**.

1. If the domain registration is available for transfer, it is listed in the **Domain availability** list as available. Select the check-box next to each domain for which you want to transfer the registration, verify that you have completed the transfer requirements for top-level domains, and choose **Next**.

   If the domain registration is not available for transfer, the Route 53 console lists the reasons. Contact your registrar for information about how to resolve the issues that prevent you from transferring the registration.

1. On the **DNS service** page, review the information about name servers, and choose **Next**.
**Note**  
Domain name registrations and renewals are nonrefundable. If you enable automatic domain renewal and you decide that you don't want the domain name after we renew the registration, you can't get a refund for the cost of the renewal.

1. On the **Contact information** page, enter contact information for the domain registrant, admin, and tech contacts. The values that you enter here are applied to all the domains that you're transferring. 
**Important**  
We recommend that you specify the following values for the registrant contact (the domain owner):  
**First and last name**: We recommend that you specify the name that appears on your official ID. For some changes to domain settings, some domain registries require that you provide proof of identity. The name on your ID must match the name of the registrant contact for the domain.
**Contact details**: During the domain transfer, we recommend that you specify the same values as are specified with the current registrar. When you change contact details for the registrant contact, you change the domain owner, and some TLD registries don't allow you to change the domain owner during a domain transfer. If you change contact details for the registrant contact, the transfer might fail. You can change contact details for the registrant contact after you transfer the domain.

   By default, we use the same information for all three contacts. If you want to enter different information for one or more contacts, set the value of **Same as the registrant contact** to off position.
**Note**  
For .it domains, the registrant and admin contacts must be the same.

   For more information, see [Values that you specify when you register or transfer a domain](domain-register-values-specify.md).

1. For some TLDs, we're required to collect additional information. For these TLDs, enter the applicable values after the **Postal/Zip Code** field.

1. If the value of **Contact Type** is **Person**, choose whether you want to hide your contact information from WHOIS queries. For more information, see [Enabling or disabling privacy protection for contact information for a domain](domain-privacy-protection.md).

1. Choose **Submit**.

1. Review the information you entered, read the terms of service, and select the check box to confirm that you've read the terms of service. 

1. Choose **Submit request**. 

   We confirm that the domains are eligible for transfer, and we send an email to the registrant contacts for the domain to request authorization to transfer the domain. 

1. In the navigation pane, choose **Domains** and then **Requests**.

   On this page you can view the status of domain and also if you need to respond to registrant contact verification email. You can also choose to resend the verification email.

   If you specified an email address for the registrant contact that has never been used to register a domain with Route 53, some TLD registries require you to verify that the address is valid.

   We send a verification email from one of the following email addresses:
   + **noreply@registrar.amazon** – for TLDs registered by Amazon Registrar.
   + **noreply@domainnameverification.net** or **noreply@emailverification.info** – for TLDs registered by our registrar associate, Gandi. To determine who the registrar is for your TLD, see [Finding your registrar](find-your-registrar.md).
**Important**  
The registrant contact must follow the instructions in the email to verify that the email was received, or we must suspend the domain as required by ICANN. When a domain is suspended, it's not accessible on the internet.

   1. When you receive the verification email, choose the link in the email that verifies that the email address is valid. If you don't receive the email immediately, check your junk email folder.

   1. Return to the **Requests** page. If the status doesn't automatically update to say **email-address is verified**, choose **Refresh status**.

1. When domain transfer is complete, your next step depends on whether you want to use Route 53 or another DNS service as the DNS service for the domain:
   + **Route 53** – In the hosted zone that Route 53 created when you registered the domain, create records to tell Route 53 how you want to route traffic for the domain and subdomains. 

     For example, when someone enters your domain name in a browser and that query is forwarded to Route 53, do you want Route 53 to respond to the query with the IP address of a web server in your data center or with the name of an ELB load balancer?

     For more information, see [Working with records](rrsets-working-with.md).
**Important**  
If you create records in a hosted zone other than the one that Route 53 creates automatically, you must update the name servers for the domain to use the name servers for the new hosted zone.
   + **Another DNS service** – Configure your new domain to route DNS queries to the other DNS service. Perform the procedure [Updating name servers to use another registrar](domain-register-other-dns-service.md).

## Step 6: Click the link in the confirmation and authorization emails
<a name="domain-transfer-to-route-53-authorize-transfer"></a>

Soon after you request the transfer, we might send one or more emails to the registrant contact for the domain:

**Email to confirm that the registrant contact is reachable**  
If you've never registered a domain with Route 53 or transferred a domain to Route 53, we send you an email that asks you to confirm that the email address is valid. We retain this information so we don't have to send this confirmation email again.

**Email to get authorization to transfer the domain**  
For some TLDs, you need to respond to an email to authorize transfer of the domain.    
**Generic TLDs such as .com, .net, and .org**  
Authorization isn't required for domains that have a [generic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-generic), such as .com, .net, or .org.  
**Geographic TLDs such as .co.uk and .jp**  
For domains that have a [geographic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-geographic), we're required to get your authorization to transfer the domain. If you transfer 10 domains, we have to send you 10 emails, and you have to click the authorization link in each one.

The emails all go to the registrant contact for the domain:
+ If you're the registrant contact for the domain, follow the instructions in the email to authorize the transfer.
+ If someone else is the registrant contact, ask that person to follow the instructions in the email to authorize the transfer.

**Important**  
If you're transferring a domain that has a geographic TLD, we wait up to five days for the registrant contact to authorize the transfer. If the registrant contact doesn't respond within five days, we cancel the transfer operation and send an email to the registrant contact about the cancellation. 

**Topics**
+ [Authorization email for a new owner or email address](#domain-transfer-to-route-53-authorize-transfer-additional-email)
+ [Email addresses that authorization emails come from](#domain-transfer-to-route-53-authorize-transfer-email-addresses)
+ [Approval from the current registrar](#domain-transfer-to-route-53-authorize-transfer-registrar-approval)
+ [What happens next](#domain-transfer-to-route-53-authorize-transfer-what-next)

### Authorization email for a new owner or email address
<a name="domain-transfer-to-route-53-authorize-transfer-additional-email"></a>

If you changed the following values, we send you a separate email that asks for your authorization:

**Domain owner**  
If you change the owner of the domain, as described in [What triggers a domain ownership change?](domain-update-contacts.md#domain-update-contacts-who-is-domain-owner), we send email to the registrant contact for the domain.

**Email address for the registrant contact (only for some TLDs)**  
For some TLDs, if you change the email address for the registrant contact, we send an email to the old and the new email address for the registrant contact. Someone at both email addresses must follow the instructions in the email to authorize the change.

For changes to the domain owner or the email address for the registrant contact, if we don't receive authorization for the change within 3-15 days, depending on the top-level domain, we must cancel the request as required by ICANN.

### Email addresses that authorization emails come from
<a name="domain-transfer-to-route-53-authorize-transfer-email-addresses"></a>

All email comes from one of the following email addresses.


****  

| TLDs | Email address that authorization email comes from | 
| --- | --- | 
|  .com.au and .net.au  |  no-reply@ispapi.net The email contains a link to http://transfers.ispapi.net.  | 
|  .fr  |  nic@nic.fr, if you're changing the registrant contact for a .fr domain name at the same time that you're transferring the domain. (The email is sent both to the current registrant contact and the new registrant contact.)  | 
|  All others  |  One of the following email addresses: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.html)  | 

To determine who the registrar is for your TLD, see [Domains that you can register with Amazon Route 53](registrar-tld-list.md).

### Approval from the current registrar
<a name="domain-transfer-to-route-53-authorize-transfer-registrar-approval"></a>

If the registrant contact authorizes the transfer, we start to work with your current registrar to transfer your domain. This step might take up to ten days, depending on the TLD for your domain:
+ [Generic top-level domains](registrar-tld-list-generic.md) – take up to seven days
+ [Geographic top-level domains](registrar-tld-list-geographic.md) (also known as country code top-level domains) – take up to ten days

If your current registrar doesn't reply to our transfer request, which is common among registrars, the transfer happens automatically. If your current registrar rejects the transfer request, we send an email notification to the current registrant contact. The registrant needs to contact the current registrar and resolve the issues with the transfer.

### What happens next
<a name="domain-transfer-to-route-53-authorize-transfer-what-next"></a>

When your domain transfer has been approved, we send another email to the registrant contact. For more information about the process, see [Viewing the status of a domain transfer](domain-transfer-to-route-53-status.md).

We charge your AWS account for the domain transfer as soon as the transfer is complete. For a list of charges by TLD, see [Amazon Route 53 Pricing for Domain Registration](https://d32ze2gidvkk54.cloudfront.net/Amazon_Route_53_Domain_Registration_Pricing_20140731.pdf).

**Note**  
This is a one-time charge, so the charge doesn't appear in your CloudWatch billing metrics. For more information about CloudWatch metrics, see [Using Amazon CloudWatch metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/working_with_metrics.html) in the *Amazon CloudWatch User Guide*.

## Step 7: Update the domain configuration
<a name="domain-transfer-to-route-53-change-configuration"></a>

After the transfer is complete, you can optionally change the following settings:

**Transfer lock**  
To transfer the domain to Route 53, you had to disable the transfer lock. If you want to re-enable the lock to prevent unauthorized transfers, see [Locking a domain to prevent unauthorized transfer to another registrar](domain-lock.md).

**Automatic renewal**  
We configure the transferred domain to automatically renew as the expiration date approaches. For information about how to change this setting, see [Enabling or disabling automatic renewal for a domain](domain-enable-disable-auto-renewal.md).

**Extended registration period**  
By default, Route 53 renews the domain annually. If you want to register the domain for a longer period, see [Extending the registration period for a domain](domain-extend.md).

**DNSSEC**  
For information about configuring DNSSEC for the domain, see [Configuring DNSSEC for a domain](domain-configure-dnssec.md).

# Preventing common Route 53 transfer issues
<a name="domain-transfer-troubleshooting"></a>

If you encounter issues while your domain transfer is in progress, here are the most common problems and how to resolve them:

**Note**  
If your transfer has already failed, see [Transferring my domain to Amazon Route 53 failed](troubleshooting-domain-transfer-failed.md) for post-failure troubleshooting.

**You didn't receive the authorization email**  
If you don't receive the authorization email from Route 53, here are the most common causes and solutions:  
+ **Check your spam folder** - Authorization emails are sometimes filtered by email providers.
+ **Verify your email address** - Confirm that the registrant email address in your domain's contact information is current and accessible.
+ **Update your contact information** - If the email address is outdated, update it with your current registrar before starting the transfer.
+ **Resend the authorization email** - In the Route 53 console, click "Resend authorization email" for the domain in transfer status.

**You're getting an "invalid authorization code" error**  
If you receive an "invalid authorization code" error, try these solutions:  
+ **Double-check the code** - Authorization codes are case-sensitive. Copy and paste the code directly from your registrar's interface to avoid typing errors.
+ **Check if the code has expired** - Authorization codes can expire between 5-30 days depending on your current registrar. Request a new code if yours has expired.
+ **Remove extra spaces** - Make sure there are no leading or trailing spaces when you enter the code.
+ **Get a new authorization code** - If the code continues to fail, request a new authorization code from your current registrar.

**Your domain is locked at the current registrar**  
Domain transfers can fail when your current registrar has a transfer lock enabled (also known as "Domain Lock" or "Client Transfer Prohibited"). This is a common security setting that prevents unauthorized transfers.  
To resolve this issue:  
+ **Unlock your domain** - Log in to your current registrar's control panel and disable the domain transfer lock.
+ **Verify the lock is removed** - You can use any public WHOIS lookup tool to confirm that the domain status shows "OK" instead of "clientTransferProhibited."
+ **Get help from your registrar** - If you don't see an option to unlock your domain, contact your current registrar's support team. They can help you remove the lock.

**Your domain isn't eligible for transfer**  
If your domain transfer is rejected due to eligibility issues, check the following:  
+ **Verify domain age** - Your domain must be at least 60 days old since registration or last transfer.
+ **Check TLD support** - Confirm that Route 53 supports your domain's top-level domain (TLD). See [Domains that you can register with Amazon Route 53](registrar-tld-list.md) for supported TLDs.
+ **Review domain status** - Domains with certain status codes (such as "pendingTransfer" or "redemptionPeriod") cannot be transferred.
+ **Check expiration date** - Domains that are expired or within 15 days of expiration may not be transferable.
+ **Resolve billing issues** - Make sure all outstanding fees with your current registrar are paid.

**Your transfer is taking longer than expected**  
If your transfer seems to be delayed, here's what you should know:  
+ **Normal timeframe** - Most transfers complete within 5-7 days, but can take up to 10 days.
+ **Monitor transfer status** - Check your transfer progress in the Route 53 console. For more information, see [Viewing the status of a domain transfer](domain-transfer-to-route-53-status.md).
+ **Respond to emails quickly** - Both registrars may send confirmation emails that require your response to proceed.
+ **Contact your current registrar** - If the transfer is delayed, contact your current registrar to make sure they're not blocking the transfer.

**When to contact AWS Support**  
Contact AWS Support if you've tried the solutions above and still have issues, or if you encounter:  
+ Transfer failures after multiple attempts with correct information
+ Billing or payment issues during the transfer process
+ Technical errors in the Route 53 console that prevent you from starting a transfer
+ Transfers that remain in "pending" status for more than 10 days
When you contact support, include your domain name, transfer request ID (if available), and details about the specific error or issue you're experiencing.

# Transferring a domain from Amazon Route 53 to another registrar
<a name="domain-transfer-from-route-53"></a>

When you transfer a domain from Amazon Route 53 to another registrar, you get some information from Route 53 and provide it to the new registrar. The new registrar will do the rest.

**Important**  
If you're currently using Route 53 as your DNS service provider and you also want to transfer DNS service to another provider, be aware that the following Route 53 features don't have direct parallels with features provided by other DNS service providers. You'll need to work with the new DNS service provider to determine how to achieve comparable functionality:  
Alias records. For more information, see [Choosing between alias and non-alias records](resource-record-sets-choosing-alias-non-alias.md).
Routing policies other than the simple routing policy. For more information, see [Choosing a routing policy](routing-policy.md).
Health checks that are associated with records. For more information, see [Configuring DNS failover](dns-failover-configuring.md).

Most domain registrars enforce requirements on transferring a domain to another registrar. The primary purpose of these requirements is to prevent the owners of fraudulent domains from repeatedly transferring the domains to different registrars. Requirements vary, but the following requirements are typical: 
+  You must have registered the domain with the current registrar or transferred registration for the domain to the current registrar at least 14 days ago.
+ The domain cannot have any of the following domain name status codes:
  + pendingDelete
  + pendingTransfer
  + redemptionPeriod
  + clientTransferProhibited
  + serverTransferProhibited

For a current list of domain name status codes and an explanation of what each code means, go to the [ICANN website](https://www.icann.org/) and search for **epp status codes**. (Search on the ICANN website; web searches sometimes return an old version of the document.)

**Note**  
If you want to transfer your domain to another domain registrar but the AWS account that the domain is registered with is closed, suspended, or terminated, you can contact AWS Support for help. Domains cannot be transferred within the first 14 days of registration. For more information, see [Contacting AWS Support about domain registration issues](domain-contact-support.md).

**Note**  
If the new registrar requires a REG-ID code, you can contact AWS Support for help. For more information, see [Contacting AWS Support about domain registration issues](domain-contact-support.md).<a name="domain-transfer-from-route-53-procedure"></a>

**To transfer a domain from Route 53 to another registrar**

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Registered domains**.

1. Choose the name of the domain that you want to transfer to another registrar.

1. On the *domain name* page, check the value of **Domain name status code**. If it is one of the following values, you can't currently transfer the domain: 
   + pendingDelete
   + pendingTransfer
   + redemptionPeriod
   + clientTransferProhibited
   + serverTransferProhibited

   For a current list of domain name status codes and an explanation of what each code means, go to the [ICANN website](https://www.icann.org/) and search for **epp status codes**. (Search on the ICANN website; web searches sometimes return an old version of the document.)

   If the value of **Domain name status code** is **serverTransferProhibited**, you can contact AWS Support for free to learn what you must do so you can transfer the domain. For more information, see [Contacting AWS Support about domain registration issues](domain-contact-support.md).

1. If the value of **Transfer lock** is **On**, choose **Turn off transfer lock** from the **Actions** dropdown.

1. *All domains except .be, .co.za, .ru, .uk, .co.uk, .me.uk, and .org.uk domains* – On the *domain name* page, choose **Transfer to another registrar** from the **Transfer out** dropdown. 

    In the **Transfer to another registrar** dialog box, choose **Copy** to copy the authorization code for the domain transfer. You'll provide this value to your registrar later in this procedure.
**Note**  
For .eu domains, you can also generate the auth code by using the "My.eu" panel at the registry: [https://my.eurid.eu/](https://my.eurid.eu/).

   *.be, .co.za, .es, .ru, .uk, .co.uk, .me.uk, and .org.uk domains* – Do the following:  
**.be domains**  
Get the authorization code from the registry for .be domains at [DNS Belgium website](https://www.dnsbelgium.be/en/transfer-code).  
**.co.za domains**  
You don't need to get an authorization code to transfer a .co.za domain to another registrar.  
**.ru domains**  
Get the authorization code from the registry for .ru domains at [https://www.nic.ru/en/auth/recovery/](https://www.nic.ru/en/auth/recovery/):  

   1. Choose the option to recover credentials by domain name.

   1. Enter your domain name, and choose **Continue**.

   1. Follow the on-screen prompts to get access to the RU-CENTER admin page.

   1. In the **Manage your account** section, choose **Domain transfer**.

   1. Confirm the transfer with REGRU-RU.  
**.uk, .co.uk, .me.uk, and .org.uk domains**  
Change the IPS tag to the value for the new registrar:  

   1. Go to the [Find a Registrar](http://www.nominet.uk/registrar-list/) page on the Nominet website, and find the IPS tag for the new registrar. (Nominet is the registry for .uk, .co.uk, .me.uk, and .org.uk domains.)

   1. On the **Registered Domains >** *domain name* page, select the **Transfer out**, drop-down, then **Update IPS Tag**, and specify the value that you got in step 6a.

   1. Choose **Update**.
**Note**  
You can also update the IPS tag on the Nominet console. For instructions, see [Switch the registrar](https://theukdomain.uk/help-centre/can-i-switch-the-registrar-i-have-my-domain-registered-with/).

1. If you're not currently using Route 53 as the DNS service provider for your domain, skip to step 10.

   If you are currently using Route 53 as the DNS service provider for the domain, perform the following steps:

   1. Choose **Hosted Zones.**

   1. Choose the name of the hosted zone for your domain. The domain and the hosted zone have the same name.

   1. *If you want to continue using Route 53 as the DNS service provider for the domain:* Get the names of the four name servers that Route 53 assigned to your hosted zone. For more information, see [Getting the name servers for a public hosted zone](GetInfoAboutHostedZone.md).

      *If you do not want to continue using Route 53 as the DNS service provider for the domain:* Make note of the settings for all of your records except the NS and SOA records. For Route 53–specific features such as alias records, you'll need to work with your new DNS service provider to determine how to achieve comparable functionality.

1. If you're transferring DNS service to another provider, use the methods that are provided by the new DNS service to perform the following tasks:
   + Create a hosted zone
   + Create records that reproduce the functionality of your Route 53 records
   + Get the name servers that the new DNS service assigned to your hosted zone

1. Use the process that is provided by the new registrar to request a transfer of the domain.

   *All domains except .co.za, .uk, .co.uk, .me.uk, and .org.uk domains* – You'll be prompted to enter the authorization code that you got from the Route 53 console in step 6 of this procedure.

1. If you still want to use Route 53 as your DNS service provider, use the process that is provided by the new registrar to specify the names of the Route 53 name servers that you got in step 7. If you want to use another DNS service provider, specify the names of the name servers that the new provider gave you when you created a new hosted zone in step 8.

1. Act on the confirmation email:  
**All domains except .jp domains**  
Route 53 sends a confirmation email to the registrant contact for the domain:  
   + Depending on the TLD, the confirmation email includes a link from one of the following domains. Use this link to approve or reject the transfer.
     + registrar.amazon
     + approvemove.com
     + domainnameverification.net
     + emailverification.info
     + key-systems.net
   + If you don't take action, the transfer will proceed automatically on the specified date.  
**.jp domains**  
Route 53 sends a confirmation email to the registrant contact for the domain from address *noreply@domainnameverification.net* or *noreply@emailverification.info* with a link to confirm the transfer:  
   + Use this link to approve or reject the transfer. You will need to provide the domain authorization code that you obtained in step 7.
   + If you don't take action, the transfer will be canceled on the specified date.
In addition you might receive an email from WIXI.jp. You can ignore this email.

1. If the registrar that you're transferring the domain to reports that the transfer failed, contact that registrar for more information. When you transfer a domain to another registrar, all status updates go to the new registrar, so Route 53 has no information about why a transfer failed.

   If the new registrar reports that the transfer failed because the authorization code that you got from Route 53 isn't valid, open a case with AWS Support. (You don't need a support contract, and there's no fee.) For more information, see [Contacting AWS Support about domain registration issues](domain-contact-support.md).
**Note**  
Authorization codes generated by Gandi are valid for about 5 days. If your transfer attempt occurs after this period, it might fail due to an expired code.

1. If you transferred DNS service to another DNS service provider, you can delete the records in the hosted zone and delete the hosted zone after DNS resolvers stop responding to DNS queries with the names of Route 53 name servers. This typically takes two days, the amount of time that DNS resolvers commonly cache the names of name servers for a domain.
**Important**  
If you delete the hosted zone while DNS resolvers are still responding to DNS queries with the names of Route 53 name servers, your domain will become unavailable on the internet.

   After you delete the hosted zone, Route 53 will stop billing you the monthly charge for a hosted zone. For more information, see the following documentation:
   + [Deleting records](resource-record-sets-deleting.md)
   + [Deleting a public hosted zone](DeleteHostedZone.md)
   + [Route 53 Pricing](https://aws.amazon.com/route53/pricing)

# Transferring a domain to a different AWS account
<a name="domain-transfer-between-aws-accounts"></a>

If you registered a domain using one AWS account and you want to transfer the domain to another AWS account, you can easily transfer it by using the new console, or by using the AWS CLI or other programmatic methods.

**Topics**
+ [Step 1: Transfer a domain to a different AWS account](#domain-transfer-between-aws-accounts-domain)
+ [Step 2 (Optional): Migrate a hosted zone to a different AWS account](#domain-transfer-between-aws-accounts-hosted-zone)

## Step 1: Transfer a domain to a different AWS account
<a name="domain-transfer-between-aws-accounts-domain"></a>

Domains cannot be transferred within the first 14 days of registration.

When you initiate the domain transfer, you must sign in either by using the root account or by using a user that has been granted IAM permissions in one or more of the following ways:
+ The user is assigned the **AdministratorAccess** managed policy.
+ The user is assigned the **AmazonRoute53DomainsFullAccess** managed policy.
+ The user is assigned the **AmazonRoute53FullAccess** managed policy.
+ The user is assigned the **PowerUserAccess** managed policy.
+ The user has permission to perform all the following actions: `TransferDomains`, `DisableDomainTransferLock`, and `RetrieveDomainAuthCode`.

If you don't sign in either by using the root account or by using a user that has the required permissions, we can't perform the transfer. This requirement prevents unauthorized users from transferring domains to other AWS accounts.

The transfer process has two steps. First the originating account owner starts the transfer: in the [initiate a transfer to another AWS account](#domain-transfer-between-aws-accounts-procedure) procedure, and then the destination account owner accepts the transfer in the [accept a transfer from another AWS account](#domain-transfer-between-aws-accounts-accept-procedure) procedure.<a name="domain-transfer-between-aws-accounts-procedure"></a>

**To transfer a domain to a different AWS account**

1. Sign in to AWS by using the AWS account that the domain is currently registered to. 

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Registered domains**.

1. Choose the name of the domain that you want to transfer to another AWS account.

1. Above the **Details** section, in the **Transfer out** dropdown, choose **Transfer to another AWS account**.

1. On the **Transfer to another AWS account** dialog, enter the destination account ID. You can get this ID from the destination AWS account owner.

1. Choose **Confirm**.

1. On the **Generate password** dialog, copy the password, and forward it to the receiving AWS account owner.

   On the **Requests** page, the **Status** for the domain will display **In progress**, and the **Type** will display **Internal transfer out**.<a name="domain-transfer-between-aws-accounts-accept-procedure"></a>

**To accept a domain transfer from a different AWS account**

1. Sign into AWS by using the AWS account that is receiving the domain. 

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Requests**.

1. On the **Requests** page, select the radio button next to the domain name you are transferring from another AWS account. If the domain is ready to be transferred the **Status** is **Action required** and the **Type** is **Internal transfer of domain in**.

   You have three days to accept the request. If the transfer isn't accepted in three days, the transfer request is cancelled.

1. In the **Action** dropdown, choose **Accept**.

   You can also choose **Reject** to cancel the transfer process.

1. If you accepted, on the **Transfer domain to your account** page, in the **Password** section, enter the password you received from the originating account owner. 

   Accept the terms and conditions, and choose **Next**.

1. Navigate to the **Requests** page to monitor the transfer status and other steps to complete.

1. After the transfer completes, you can update the contact information. For more information, see [Updating contact information and ownership for a domain](domain-update-contacts.md).



**Transfer the domain programmatically**  
You can also transfer the domain programmatically by using the AWS CLI, one of the AWS SDKs, or the Route 53 API. For more information, see the following documentation:  
+ For an overview of the transfer process and documentation about the API actions that you use to transfer a domain using the Route 53 domain registration API, see [TransferDomainToAnotherAwsAccount](https://docs.aws.amazon.com/Route53/latest/APIReference/API_domains_TransferDomainToAnotherAwsAccount.html) in the *Amazon Route 53 API Reference*.
+ For documentation about other options for transferring domains programmatically, see "SDKs & Toolkits" in the [Guides and API References](https://docs.aws.amazon.com/#user_guides) section of the "AWS documentation" page.
+ The receiving account has three days to accept the transfer from the originating account, by using the [transfer-domain-to-another-aws-account](https://docs.aws.amazon.com/cli/latest/reference/route53domains/transfer-domain-to-another-aws-account.html) API. If the transfer isn't accepted in three days, the transfer request is cancelled.
**Important**  
When you transfer a domain to a different AWS account, the hosted zone for the domain isn't transferred. If you also want to transfer the hosted zone, wait until the domain has been transferred, and then see [Step 2 (Optional): Migrate a hosted zone to a different AWS account](#domain-transfer-between-aws-accounts-hosted-zone). 

## Step 2 (Optional): Migrate a hosted zone to a different AWS account
<a name="domain-transfer-between-aws-accounts-hosted-zone"></a>

If you're using Route 53 as the DNS service for the domain, Route 53 doesn't transfer the hosted zone when you transfer a domain to a different AWS account. If domain registration is associated with one account and the corresponding hosted zone is associated with another account, neither domain registration nor DNS functionality is affected. The only effect is that you'll need to sign into the Route 53 console using one account to see the domain, and sign in using the other account to see the hosted zone. 

If you own the account that you're transferring the domain from and the account that you're transferring the domain to, you can optionally migrate the hosted zone for the domain to a different account, but it's not required. Route 53 will continue to use the records in the existing hosted zone to route traffic for the domain.

**Important**  
If you don't own both the account that you're transferring the domain from and the account that you're transferring the domain to, you must either migrate the existing hosted zone to the AWS account that you're transferring the domain to, or create a new hosted zone in an AWS account that you own. If you don't own the account that created the hosted zone that routes traffic for the domain, you can't control how traffic is routed.

To migrate the existing hosted zone to the new account, see [Migrating a hosted zone to a different AWS account](hosted-zones-migrating.md).

To create a new hosted zone, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md). This topic is typically used when you're transferring domains from another registrar to Route 53, but the process is the same when you're transferring domains from one AWS account to another.

**Important**  
**White-label name servers:** If your domain uses white-label name servers (custom name server hostnames like ns1.example.com), additional steps are required:  
**When transferring domain registration:** Update glue records with your new registrar after transfer completion
**When migrating hosted zones:** Update glue records with your domain registrar after zone migration, as IP addresses change even though hostnames remain the same
For detailed instructions, see [Step 7: Create glue records and change the registrar's name servers](white-label-name-servers.md#white-label-name-servers-create-glue-records).

# Viewing the status of a domain transfer
<a name="domain-transfer-to-route-53-status"></a>

After you initiate the transfer of a domain from another domain registrar to Amazon Route 53, you can track the status on the **Requests** page (new console) or the **Pending requests** (old console) page of the Route 53 console. The **Status** column includes a brief description of the current step. The following list includes the text in the console and a more detailed description of each step.

**Note**  
When you submit a transfer request, the initial status is **Domain transfer request submitted**, which indicates that we've received your request.

**Determining whether the domain meets transfer requirements (step 1 of 14)**  
We're confirming that your domain's status is eligible for transfer. You must unlock your domain, and the domain can't have any of the following status codes when you submit the transfer request:   
+ clientTransferProhibited
+ pendingDelete
+ pendingTransfer
+ redemptionPeriod

**Geographic TLDs only – verifying WHOIS information (step 2 of 14)**  
If you're transferring a domain that has a [geographic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-geographic), we sent a WHOIS query for your domain to determine whether you've disabled the privacy protection for the domain. If privacy protection is still enabled with your current registrar, we won't be able to access the information we need to transfer the domain.  
Authorization isn't required for domains that have a [generic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-generic), such as .com, .net, or .org.

**Geographic TLDs only – Sent email to registrant contact to get transfer authorization (step 3 of 14)**  
If you're transferring a domain that has a [geographic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-geographic), we've sent an email to the registrant contact for the domain. The purpose of the email is confirm that the transfer was requested by an authorized contact of the domain.  
Authorization isn't required for domains that have a [generic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-generic), such as .com, .net, or .org.

**Verifying transfer with current registrar (step 4 of 14)**  
We've sent a request to the current registrar for the domain to initiate the transfer.

**Geographic TLDs only – Awaiting authorization from registrant contact (step 5 of 14)**  
We sent email to the registrant contact for the domain (see step 3 of 14), and we're waiting for the registrant contact to click a link in the email to authorize the transfer. If you're transferring a domain that has a [geographic TLD](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar-tld-list.html#registrar-tld-list-geographic) and you didn't receive the email for some reason, see [Resending authorization and confirmation emails](domain-click-email-link.md).

**Contacted current registrar to request transfer (step 6 of 14)**  
We're working with the current registrar for the domain to finalize the transfer.

**Waiting for the current registrar to complete the transfer (step 7 of 14)**  
Your current registrar is confirming that your domain meets the requirements for being transferred. This step might take up to ten days, depending on the TLD for your domain:  
+ [Generic top-level domains](registrar-tld-list-generic.md) – take up to seven days
+ [Geographic top-level domains](registrar-tld-list-geographic.md) (also known as country code top-level domains) – take up to ten days
**Note**  
If you have approved the confirmation email sent from Route 53 when transferring a .JP domain, but it has stopped for several days in STEP 7, contact [AWS Support Center](https://console.aws.amazon.com/support/cases#/create?issueType=customer-service&serviceCode=service-domains&categoryCode=transfers) for assistance.
For most registrars, the process is entirely automated and can't be accelerated. Some registrars send you an email that asks you to approve the transfer; if your registrar sends this confirmation email, the transfer process might be much faster than seven to ten days.  
For information about reasons that a registrar might reject the transfer, see [Transfer requirements for top-level domains](domain-transfer-to-route-53.md#domain-transfer-to-route-53-requirements).

**Confirming with the registrant contact that the contact initiated the transfer (step 8 of 14)**  
Some TLD registries send the registrant contact another email to confirm that the domain transfer was requested by an authorized user.

**Synchronizing name servers with the registry (step 9 of 14)**  
This step occurs only if the name servers that you provided as part of the transfer request are different from the name servers that are listed with the current registrar. We'll try to update your name servers to the new name servers that you provided.

**Synchronizing settings with the registry (step 10 of 14)**  
We're verifying that the transfer has completed successfully, and we're synchronizing your domain-related data with our registrar associate.

**Sending updated contact information to the registry (step 11 of 14)**  
If you changed the ownership of the domain when you requested the transfer, we're trying to make this change. However, most registries don't allow a transfer of ownership as part of the domain transfer process.

**Finalizing the transfer to Route 53 (step 12 of 14)**  
We're confirming that the transfer process was successful.

**Finalizing transfer (step 13 of 14)**  
We're setting up your domain in Route 53.

**Transfer Complete (step 14 of 14)**  
Your transfer has been successfully completed.

# How transferring a domain to Amazon Route 53 affects the expiration date for your domain registration
<a name="domain-transfer-to-route-53-expiration"></a>

When you transfer a domain between registrars, some TLD registries let you keep the same expiration date for your domain, some registries add a year to the expiration date, and some registries change the expiration date to one year after the transfer date.

**Note**  
For most TLDs, you can extend the registration period for a domain by up to ten years after you transfer it to Amazon Route 53. For more information, see [Extending the registration period for a domain](domain-extend.md).

## Generic TLDs
<a name="domain-transfer-to-route-53-expiration-generic"></a>

When you transfer a domain that has a generic TLD (for example, .com) to Route 53, the new expiration date for the domain is the expiration date with your previous registrar plus one year.

## Geographic TLDs
<a name="domain-transfer-to-route-53-expiration-geographic"></a>

When you transfer a domain that has a geographic TLD (for example, .co.uk) to Route 53, the new expiration date for the domain depends on the TLD. Find your TLD in the following table to determine how transferring your domain affects the expiration date.


****  

| Continent | Geographic TLDs and the effect of transferring a domain on the expiration date | 
| --- | --- | 
|  Africa  |  **.co.za** – The expiration date remains the same.  | 
|  Americas  |  **.cl, .com.ar, .com.br** – The expiration date remains the same. **.ca, .co, .mx, .us** – One year is added to the old expiration date.  | 
|  Asia/Oceania  |  **.com.au, .com.sg, .jp, .net.au, .sg** – The expiration date remains the same. **.co.nz, .in, .net.nz, .org.nz ** – One year is added to the old expiration date.  | 
|  Europe  |  **.ch, .co.uk, .es, .fi, .me.uk, .org.uk, .se** – The expiration date remains the same. **.berlin, .eu, .io, .me, .ruhr, .wien** – One year is added to the old expiration date. **.be, .de, .fr, .it, .nl** – The new expiration date is one year after the date of transfer.  |