Amazon Route 53 Developer Guide

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 333 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Amazon Route 53
Developer Guide
API Version 2013-04-01
Amazon Route 53: Developer Guide
Copyright © 2016 Amazon Web Services, Inc. and/or its affiliates. All rights reserved.
Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner
that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not
owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by
Amazon.
Amazon Route 53 Developer Guide
Table of Contents
What Is Amazon Route 53? ............................................................................................................. 1
Domain Registration .............................................................................................................. 1
DNS Service ........................................................................................................................ 1
Health Checking .................................................................................................................... 2
DNS Domain Name Format ..................................................................................................... 2
Formatting Domain Names for Domain Name Registration ................................................... 2
Formatting Domain Names for Hosted Zones and Resource Record Sets ................................ 3
Using an Asterisk (*) in the Names of Hosted Zones and Resource Record Sets ...................... 3
Formatting Internationalized Domain Names ...................................................................... 4
Supported DNS Resource Record Types ................................................................................... 4
A Format ..................................................................................................................... 5
AAAA Format ............................................................................................................... 5
CNAME Format ............................................................................................................ 5
MX Format ................................................................................................................... 6
NS Format ................................................................................................................... 6
PTR Format ................................................................................................................. 6
SOA Format ................................................................................................................. 7
SPF Format .................................................................................................................. 7
SRV Format ................................................................................................................. 7
TXT Format .................................................................................................................. 8
IP Address Ranges of Amazon Route 53 Servers ....................................................................... 8
DNS Constraints and Behaviors ............................................................................................... 8
Maximum Response Size ............................................................................................... 8
Authoritative Section Processing ...................................................................................... 8
Additional Section Processing .......................................................................................... 9
Amazon Route 53 Pricing ....................................................................................................... 9
AWS Identity and Access Management ..................................................................................... 9
Getting Started ............................................................................................................................ 10
The Amazon Route 53 Console .............................................................................................. 10
The Amazon Route 53 API .................................................................................................... 11
AWS SDKs that Support Amazon Route 53 .............................................................................. 11
AWS Command Line Interface Support for Amazon Route 53 ...................................................... 11
AWS Tools for Windows PowerShell Support for Amazon Route 53 ............................................... 12
Registering Domain Names Using Amazon Route 53 ......................................................................... 13
Registering and Updating Domains ......................................................................................... 14
Registering a New Domain ............................................................................................ 14
Values that You Specify When You Register a Domain or Edit Domain Settings ....................... 16
Values that Amazon Route 53 Returns When You Register or Update a Domain ..................... 19
Viewing the Status of a Domain Registration .................................................................... 20
Adding Resource Record Sets for a New Domain .............................................................. 20
Editing Contact Information and Other Settings for a Domain ............................................... 20
Adding or Changing Name Servers and Adding or Changing Glue Records ........................... 22
Privacy Protection for Contact Information ................................................................................ 22
Renewing Registration for a Domain ....................................................................................... 23
Renewing or Restoring an Expired Domain ...................................................................... 25
Extending the Registration Period for a Domain ......................................................................... 26
Transferring Domains ........................................................................................................... 27
Transferring Domain Registration to Amazon Route 53 ....................................................... 27
Viewing the Status of a Domain Transfer .......................................................................... 30
How Transferring a Domain to Amazon Route 53 Affects the Expiration Date .......................... 32
Transferring a Domain to a Different AWS Account ............................................................ 32
Transferring a Domain from Amazon Route 53 .................................................................. 33
Configuring DNSSEC for a Domain ......................................................................................... 35
Overview of How DNSSEC Protects Your Domain .............................................................. 36
Prerequisites and Limits for Configuring DNSSEC for a Domain ........................................... 37
API Version 2013-04-01
iii
Amazon Route 53 Developer Guide
Adding Public Keys for a Domain .................................................................................... 37
Deleting Public Keys for a Domain .................................................................................. 38
Getting a Domain Name Unsuspended .................................................................................... 39
Deleting a Domain Name Registration ..................................................................................... 40
Downloading a Domain Billing Report ...................................................................................... 40
Domains that You Can Register with Amazon Route 53 .............................................................. 41
Generic Top-Level Domains ........................................................................................... 41
Geographic Domains .................................................................................................. 122
Configuring Amazon Route 53 as Your DNS Service ........................................................................ 141
Migrating DNS Service for an Existing Domain to Amazon Route 53 ........................................... 141
Creating a Hosted Zone .............................................................................................. 142
Getting Your Current DNS Configuration from Your DNS Service Provider ............................ 142
Creating Resource Record Sets ................................................................................... 143
Checking the Status of Your Changes (API Only) ............................................................. 143
Updating Your Registrar's Name Servers ........................................................................ 143
Waiting for Your Changes to Take Effect ......................................................................... 144
Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent
Domain ............................................................................................................................ 145
Creating a Hosted Zone for the New Subdomain ............................................................. 145
Creating Resource Record Sets ................................................................................... 146
Checking the Status of Your Changes (API Only) ............................................................. 146
Updating Your DNS Service with Name Server Records for the Subdomain .......................... 146
Migrating DNS Service for a Subdomain to Amazon Route 53 without Migrating the Parent
Domain ............................................................................................................................ 147
Creating a Hosted Zone for the Subdomain .................................................................... 147
Getting Your Current DNS Configuration from Your DNS Service Provider ............................ 148
Creating Resource Record Sets ................................................................................... 148
Checking the Status of Your Changes (API Only) ............................................................. 148
Updating Your DNS Service with Name Server Records for the Subdomain .......................... 149
Routing Traffic to AWS Resources ................................................................................................. 151
Routing Traffic to an Amazon CloudFront Distribution (Public Hosted Zones Only) ......................... 151
Routing Traffic to an AWS Elastic Beanstalk Environment .......................................................... 152
Deploying an Application into an Elastic Beanstalk Environment ......................................... 153
Getting the Domain Name for Your Elastic Beanstalk Environment ...................................... 153
Creating an Amazon Route 53 Resource Record Set ....................................................... 153
Routing Traffic to an Elastic Load Balancing Load Balancer ....................................................... 155
Routing Traffic to an Amazon EC2 Instance ............................................................................ 156
Routing Traffic to a Website That Is Hosted in an Amazon S3 Bucket ........................................... 156
Opening Connections to an Amazon RDS Database Instance Using Your Domain Name ................ 157
Prerequisites ............................................................................................................. 157
Configuring Amazon Route 53 So You Can Use Your Domain Name to Open Connections ...... 157
Routing Traffic to Amazon WorkMail (Public Hosted Zones Only) ................................................ 159
Working with Public Hosted Zones ................................................................................................ 162
Creating a Public Hosted Zone ............................................................................................. 162
Getting the Name Servers for a Public Hosted Zone ................................................................. 163
Listing Public Hosted Zones ................................................................................................. 164
Deleting a Public Hosted Zone ............................................................................................. 164
Configuring White Label Name Servers .................................................................................. 165
NS and SOA Resource Record Sets that Amazon Route 53 Creates for a Public Hosted Zone ........ 169
The Name Server (NS) Resource Record Set ................................................................. 169
The Start of Authority (SOA) Resource Record Set .......................................................... 170
Working with Private Hosted Zones ............................................................................................... 171
Creating a Private Hosted Zone ............................................................................................ 172
Listing Private Hosted Zones ................................................................................................ 174
Associating More Amazon VPCs with a Private Hosted Zone ..................................................... 174
Associating Amazon VPCs and Private Hosted Zones That You Create with Different AWS
Accounts .......................................................................................................................... 175
Disassociating Amazon VPCs from a Private Hosted Zone ........................................................ 176
API Version 2013-04-01
iv
Amazon Route 53 Developer Guide
Deleting a Private Hosted Zone ............................................................................................ 177
Working with Resource Record Sets ............................................................................................. 178
Choosing a Routing Policy ................................................................................................... 179
Weighted Routing ...................................................................................................... 179
Latency-Based Routing ............................................................................................... 180
Geolocation Routing ................................................................................................... 181
Choosing Between Alias and Non-Alias Resource Record Sets .................................................. 182
Creating Resource Record Sets by Using the Amazon Route 53 Console .................................... 184
Values that You Specify When You Create or Edit Amazon Route 53 Resource Record Sets ............ 186
Values for Basic Resource Record Sets ......................................................................... 186
Values for Weighted Resource Record Sets .................................................................... 189
Values for Alias Resource Record Sets .......................................................................... 192
Values for Weighted Alias Resource Record Sets ............................................................ 196
Values for Latency Resource Record Sets ...................................................................... 202
Values for Latency Alias Resource Record Sets .............................................................. 206
Values for Failover Resource Record Sets ...................................................................... 212
Values for Failover Alias Resource Record Sets .............................................................. 215
Values for Geolocation Resource Record Sets ................................................................ 220
Values for Geolocation Alias Resource Record Sets ......................................................... 224
Creating Resource Record Sets By Importing a Zone File ......................................................... 230
Editing Resource Record Sets .............................................................................................. 232
Deleting Resource Record Sets ............................................................................................ 232
Listing Resource Record Sets .............................................................................................. 233
Using Traffic Flow to Route DNS Traffic .......................................................................................... 234
Creating and Managing Traffic Policies ................................................................................... 235
Creating a Traffic Policy ............................................................................................... 235
Values that You Specify When You Create a Traffic Policy .................................................. 236
Creating Additional Versions of a Traffic Policy ................................................................. 238
Creating a Traffic Policy by Importing a JSON Document ................................................... 239
Viewing Traffic Policy Versions and the Associated Policy Records ...................................... 240
Deleting Traffic Policy Versions and Traffic Policies ........................................................... 241
Creating and Managing Policy Records .................................................................................. 242
Creating Policy Records .............................................................................................. 242
Values that You Specify When You Create or Update a Policy Record .................................. 243
Updating Policy Records ............................................................................................. 243
Deleting Policy Records .............................................................................................. 244
Health Checks and DNS Failover .................................................................................................. 245
Creating, Updating, and Deleting Health Checks ..................................................................... 245
Creating and Updating Health Checks ........................................................................... 246
Deleting Health Checks ............................................................................................... 253
Updating or Deleting Health Checks when DNS Failover Is Configured ................................ 253
Configuring Router and Firewall Rules for Amazon Route 53 Health Checks ......................... 254
How Amazon Route 53 Determines Whether an Endpoint Is Healthy ................................... 254
Monitoring Health Check Status and Getting Notifications ......................................................... 255
Viewing Health Check Status and the Reason for Health Check Failures .............................. 255
Monitoring the Latency Between Health Checkers and Your Endpoint .................................. 256
Monitoring Health Checks Using CloudWatch ................................................................. 257
Configuring DNS Failover .................................................................................................... 261
How Health Checks Work in Simple Amazon Route 53 Configurations ................................. 262
How Health Checks Work in Complex Amazon Route 53 Configurations .............................. 264
Task List for Configuring DNS Failover ........................................................................... 269
Configuring Failover in a Private Hosted Zone ................................................................. 270
Options for Configuring Amazon Route 53 Active-Active and Active-Passive Failover ............. 271
How Amazon Route 53 Averts Failover Problems ............................................................. 274
Naming and Tagging Health Checks ...................................................................................... 275
Tag Restrictions ......................................................................................................... 275
Adding, Editing, and Deleting Tags for Health Checks ....................................................... 275
Using API Versions Before 2012-12-12 .................................................................................. 276
API Version 2013-04-01
v
Amazon Route 53 Developer Guide
Authentication and Access Control ................................................................................................ 277
Authentication ................................................................................................................... 277
Access Control .................................................................................................................. 278
Overview of Managing Access ............................................................................................. 279
ARNs for Amazon Route 53 Resources ......................................................................... 279
Understanding Resource Ownership ............................................................................. 280
Managing Access to Resources .................................................................................... 280
Specifying Policy Elements: Resources, Actions, Effects, and Principals .............................. 282
Specifying Conditions in a Policy ................................................................................... 282
Using IAM Policies for Amazon Route 53 ................................................................................ 283
Permissions Required to Use the Amazon Route 53 Console ............................................ 284
AWS Managed (Predefined) Policies for Amazon Route 53 ................................................ 286
Customer Managed Policy Examples ............................................................................. 286
Amazon Route 53 API Permissions Reference ........................................................................ 288
Required Permissions for Actions on Public Hosted Zones ................................................ 289
Required Permissions for Actions on Private Hosted Zones ............................................... 290
Required Permissions for Actions on Reusable Delegation Sets ......................................... 290
Required Permissions for Actions on Resource Record Sets .............................................. 291
Required Permissions for Actions on Traffic Policies ......................................................... 291
Required Permissions for Actions on Traffic Policy Instances .............................................. 292
Required Permissions for Actions on Health Checks ......................................................... 293
Required Permissions for Actions on Domain Registrations ............................................... 293
Required Permissions for Actions on Tags for Hosted Zones and Health Checks ................... 295
Required Permissions for Actions on Tags for Domains ..................................................... 295
Capturing API Requests with CloudTrail ......................................................................................... 296
Configuring CloudTrail for Amazon Route 53 ........................................................................... 296
Amazon Route 53 Information in CloudTrail Log Files ............................................................... 297
Understanding Amazon Route 53 Log File Entries ................................................................... 297
Tagging Amazon Route 53 Resources ........................................................................................... 302
Tutorials ................................................................................................................................... 303
Transitioning to Latency-Based Routing in Amazon Route 53 ..................................................... 303
Adding Another Region to Your Latency-Based Routing in Amazon Route 53 ................................ 305
Using Latency and Weighted Resource Record Sets in Amazon Route 53 to Route Traffic to Multiple
Amazon EC2 Instances in a Region ...................................................................................... 306
Managing Over 100 Weighted Resource Record Sets in Amazon Route 53 .................................. 307
Weighting Fault-Tolerant Multi-Record Answers in Amazon Route 53 .......................................... 307
Limits ....................................................................................................................................... 309
Limits on API Requests ....................................................................................................... 309
Limits on Entities ................................................................................................................ 310
Resources ................................................................................................................................ 311
AWS Resources ................................................................................................................ 311
Third-Party Tools and Libraries ............................................................................................. 312
Graphical User Interfaces .................................................................................................... 313
Document History ...................................................................................................................... 314
AWS Glossary ........................................................................................................................... 327
API Version 2013-04-01
vi
Amazon Route 53 Developer Guide
What Is Amazon Route 53?
Amazon Route 53 performs three main functions:
Domain registration – Amazon Route 53 lets you register domain names such as example.com.
Domain Name System (DNS) service – Amazon Route 53 translates friendly domains names like
www.example.com into IP addresses like 192.0.2.1. Amazon Route 53 responds to DNS queries using
a global network of authoritative DNS servers, which reduces latency.
Health checking – Amazon Route 53 sends automated requests over the Internet to your application
to verify that it's reachable, available, and functional.
You can use any combination of these functions. For example, you can use Amazon Route 53 as both
your registrar and your DNS service, or you can use Amazon Route 53 as the DNS service for a domain
that you registered with another domain registrar.
Domain Registration
If you want to create a website, you start by registering the name of your website, known as a domain
name.Your domain name is the name, such as example.com, that your users enter in a browser to display
your website. For more information, see Registering Domain Names Using Amazon Route 53 (p. 13).
If you already registered a domain name with another registrar, you can optionally transfer the domain
registration to Amazon Route 53.This isn't required to use Amazon Route 53 as your DNS service or to
configure health checking for your resources. For more information, see Transferring Registration for a
Domain to Amazon Route 53 (p. 27).
Amazon Route 53 supports domain registration for a wide variety of generic top-level domains (such as
.com or .org) and geographic top-level domains (such as .be or .us). For a complete list of supported
top-level domains, see Domains that You Can Register with Amazon Route 53 (p. 41).
DNS Service
Amazon Route 53 is an authoritative DNS service, meaning that it routes Internet traffic to your website
by translating friendly domain names like www.example.com into the numeric IP addresses like 192.0.2.1
that computers use to connect to each other. When someone enters your domain name in a browser or
sends you email, a DNS request is forwarded to the nearest Amazon Route 53 DNS server in a global
API Version 2013-04-01
1
Amazon Route 53 Developer Guide
Domain Registration
network of authoritative DNS servers. Amazon Route 53 responds with the IP address that you specified.
For a list of the locations of Amazon Route 53 DNS servers, see The Amazon Route 53 Global Network
section on the Amazon Route 53 Product Details page.
If you register a new domain name with Amazon Route 53, we automatically configure Amazon Route 53
as the DNS service for the domain, and we create a hosted zone for your domain.You add resource
record sets to the hosted zone, which define how you want Amazon Route 53 to respond to DNS queries
for your domain—for example, with the IP address for a web server, the IP address for the nearest
CloudFront edge location, or the IP address for an Elastic Load Balancing load balancer. For more
information, see Working with Resource Record Sets (p. 178).
If you registered your domain with another domain registrar, that registrar is likely providing the DNS
service for your domain.You can transfer DNS service to Amazon Route 53, either with or without
transferring registration for the domain. For information about transferring DNS service to Amazon
Route 53, see Configuring Amazon Route 53 as Your DNS Service (p. 141).
If you're using Amazon CloudFront, AWS Elastic Beanstalk, Elastic Load Balancing, or Amazon S3, you
can configure Amazon Route 53 to route Internet traffic to those resources.There's no charge for the
DNS queries that Amazon Route 53 routes to CloudFront, Elastic Beanstalk, Elastic Load Balancing, or
Amazon S3. For information about routing queries to a variety of AWS resources, including Amazon EC2
instances, Amazon RDS databases, and Amazon WorkMail, see Routing Traffic to AWS Resources (p.151).
Health Checking
Amazon Route 53 health checks monitor the health of your resources such as web servers and email
servers.You can configure CloudWatch alarms for your health checks, so that you receive notification
when a resource becomes unavailable.You can also configure Amazon Route 53 to route Internet traffic
away from resources that are unavailable. For more information about using Amazon Route 53 to monitor
the health of your resources, see Amazon Route 53 Health Checks and DNS Failover (p. 245).
DNS Domain Name Format
Domain names (including the names of domains, hosted zones, and resource record sets) consist of a
series of labels separated by dots. Each label can be up to 63 bytes long. The total length of a domain
name cannot exceed 255 bytes, including the dots. Amazon Route 53 supports any valid domain name.
Naming requirements depend on whether you're registering a domain name or you're specifying the name
of a hosted zone or a resource record set. See the applicable topic.
Topics
Formatting Domain Names for Domain Name Registration (p. 2)
Formatting Domain Names for Hosted Zones and Resource Record Sets (p. 3)
Using an Asterisk (*) in the Names of Hosted Zones and Resource Record Sets (p. 3)
Formatting Internationalized Domain Names (p. 4)
Formatting Domain Names for Domain Name
Registration
For domain name registration, a domain name can contain only the characters a-z, 0-9, and – (hyphen).
You can't specify a hyphen at the beginning or end of a label.
API Version 2013-04-01
2
Amazon Route 53 Developer Guide
Health Checking
For information about how to register an internationalized domain name (IDN), see Formatting
Internationalized Domain Names (p. 4).
Formatting Domain Names for Hosted Zones and
Resource Record Sets
For hosted zones and resource record sets, the domain name can include any of the following printable
ASCII characters (excluding spaces):
• a-z
• 0-9
- (hyphen)
! " # $ % & ' ( ) * + , - / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ .
Amazon Route 53 stores alphabetic characters as lowercase letters (a-z), regardless of how you specify
them: as uppercase letters, lowercase letters, or the corresponding letters in escape codes.
If your domain name contains any of the following characters, you must specify the characters by using
escape codes in the format \three-digit octal code:
Characters 000 to 040 octal (0 to 32 decimal, 0x00 to 0x20 hexadecimal)
Characters 177 to 377 octal (127 to 255 decimal, 0x7F to 0xFF hexadecimal)
. (period), character 056 octal (46 decimal, 0x2E hexadecimal), when used as a character in a domain
name. When using . as a delimiter between labels, you do not need to use an escape code.
For example, to create a hosted zone for exämple.com, you specify ex\344mple.com.
If the domain name includes any characters other than a to z, 0 to 9, - (hyphen), or _ (underscore), Amazon
Route 53 API actions return the characters as escape codes.This is true whether you specify the characters
as characters or as escape codes when you create the entity. The Amazon Route 53 console displays
the characters as characters, not as escape codes.
For a list of ASCII characters the corresponding octal codes, do an Internet search on "ascii table".
To specify an internationalized domain name (IDN), convert the name to Punycode. For more information,
see Formatting Internationalized Domain Names (p. 4).
Using an Asterisk (*) in the Names of Hosted Zones
and Resource Record Sets
You can create hosted zones that include * in the name. Note the following:
You can't include an * in the leftmost label in a domain name. For example, *.example.com is not
allowed.
If you include * in other positions, DNS treats it as an * character (ASCII 42), not as a wildcard.
You can also create resource record sets that include * in the name. DNS treats the * character either as
a wildcard or as the * character (ASCII 42), depending on where it appears in the name. Note the following
restrictions on using * as a wildcard in the name of resource record sets:
The * must replace the leftmost label in a domain name, for example, *.example.com. It can't replace
any of the middle labels, for example, marketing.*.example.com.
API Version 2013-04-01
3
Amazon Route 53 Developer Guide
Formatting Domain Names for Hosted Zones and
Resource Record Sets
The * must replace the entire label. For example, you can't specify *prod.example.com or
prod*.example.com.
You can't use the * as a wildcard for resource records sets that have a type of NS.
For resource record sets, if you include * in any position other than the leftmost label in a domain name,
DNS treats it as an * character (ASCII 42), not as a wildcard.
Formatting Internationalized Domain Names
When you register a new domain name or create hosted zones and resource record sets, you can specify
characters in other alphabets (for example, Cyrillic or Arabic) and characters in Chinese, Japanese, or
Korean. Amazon Route 53 stores these internationalized domain names (IDNs) in Punycode, which
represents Unicode characters as ASCII strings.
The following example shows the Punycode representation of the internationalized domain name .asia:
xn--fiqs8s.asia
When you enter an IDN in the address bar of a modern browser, the browser converts it to Punycode
before submitting a DNS query or making an HTTP request.
How you enter an IDN depends on what you're creating (domain names, hosted zones, or resource record
sets), and how you're creating it (API, SDK, or Amazon Route 53 console):
If you're using the Amazon Route 53 API or one of the AWS SDKs, you can programmatically convert
a Unicode value to Punycode. For example, if you're using Java, you can convert a Unicode value to
Punycode by using the toASCII method of the java.net.IDN library.
If you're using the Amazon Route 53 console to register a domain name, you can paste the name,
including Unicode characters, into the name field, and the console converts the value to Punycode
before saving it.
If you're using the Amazon Route 53 console to create hosted zones or resource record sets, you need
to convert the domain name to Punycode before you enter the name in the applicable Name field. For
information about online converters, perform an Internet search on "punycode converter".
If you're registering a domain name, note that not all top-level domains (TLDs) support IDNs. For a list
of TLDs supported by Amazon Route 53, see Domains that You Can Register with Amazon
Route 53 (p. 41). TLDs that don't support IDNs are noted.
Supported DNS Resource Record Types
Amazon Route 53 supports the DNS resource record types that are listed in this section. Each record
type also includes an example of how to format the Value element when you are accessing Amazon
Route 53 using the API.
Note
For resource record types that include a domain name, enter a fully qualified domain name, for
example, www.example.com. The trailing dot is optional; Amazon Route 53 assumes that the
domain name is fully qualified. This means that Amazon Route 53 treats www.example.com
(without a trailing dot) and www.example.com. (with a trailing dot) as identical.
Topics
A Format (p. 5)
AAAA Format (p. 5)
API Version 2013-04-01
4
Amazon Route 53 Developer Guide
Formatting Internationalized Domain Names
CNAME Format (p. 5)
MX Format (p. 6)
NS Format (p. 6)
PTR Format (p. 6)
SOA Format (p. 7)
SPF Format (p. 7)
SRV Format (p. 7)
TXT Format (p. 8)
A Format
The value for an A record is an IPv4 address in dotted decimal notation.
Example for the Amazon Route 53 console
192.0.2.1
Example for the Amazon Route 53 API
<Value>192.0.2.1</Value>
AAAA Format
The value for a AAAA record is an IPv6 address in colon-separated hexadecimal format.
Example for the Amazon Route 53 console
2001:0db8:85a3:0:0:8a2e:0370:7334
Example for the Amazon Route 53 API
<Value>2001:0db8:85a3:0:0:8a2e:0370:7334</Value>
CNAME Format
A CNAME Value element is the same format as a domain name.
Important
The DNS protocol does not allow you to create a CNAME record for the top node of a DNS
namespace, also known as the zone apex. For example, if you register the DNS name
example.com, the zone apex is example.com.You cannot create a CNAME record for
example.com, but you can create CNAME records for www.example.com,
newproduct.example.com, and so on.
In addition, if you create a CNAME record for a subdomain, you cannot create any other resource
record sets for that subdomain. For example, if you create a CNAME for www.example.com,
you cannot create any other resource record sets for which the value of the Name field is
www.example.com.
Amazon Route 53 also supports alias resource record sets, which allow you to route queries to a CloudFront
distribution, an Elastic Beanstalk environment, an ELB load balancer, an Amazon S3 bucket that is
configured as a static website, or another Amazon Route 53 resource record set. Aliases are similar in
API Version 2013-04-01
5
Amazon Route 53 Developer Guide
A Format
some ways to the CNAME resource record type; however, you can create an alias for the zone apex. For
more information, see Choosing Between Alias and Non-Alias Resource Record Sets (p. 182).
Example for the Amazon Route 53 console
hostname.example.com
Example for the Amazon Route 53 API
<Value>hostname.example.com</Value>
MX Format
The value for an MX record contains a decimal number that represents the priority of the MX record, and
the domain name of an email server.
Example for the Amazon Route 53 console
10 mail.example.com
Example for the Amazon Route 53 API
<Value>10 mail.example.com</Value>
NS Format
An NS record identifies the name servers for the hosted zone.The value for an NS record is the domain
name of a name server. For more information about NS records, see NS and SOA Resource Record
Sets that Amazon Route 53 Creates for a Public Hosted Zone (p. 169). For information about configuring
white label name servers, see Configuring White Label Name Servers (p. 165).
Example for the Amazon Route 53 console
ns-1.example.com
Example for the Amazon Route 53 API
<Value>ns-1.example.com</Value>
PTR Format
A PTR record Value element is the same format as a domain name.
Example for the Amazon Route 53 console
hostname.example.com
Example for the Amazon Route 53 API
API Version 2013-04-01
6
Amazon Route 53 Developer Guide
MX Format
<Value>hostname.example.com</Value>
SOA Format
A start of authority (SOA) record provides information about a domain and the corresponding Amazon
Route 53 hosted zone. For information about the fields in an SOA record, see NS and SOA Resource
Record Sets that Amazon Route 53 Creates for a Public Hosted Zone (p. 169).
Example for the Amazon Route 53 console
ns-2048.awsdns-64.net hostmaster.awsdns.com 1 1 1 1 60
Example for the Amazon Route 53 API
<Value>ns-2048.awsdns-64.net hostmaster.awsdns.com 1 1 1 1 60</Value>
SPF Format
SPF records were formerly used to verify the identity of the sender of email messages. However, we no
longer recommend that you create resource record sets for which the record type is SPF. RFC 7208,
Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, has been updated
to say, "...[I]ts existence and mechanism defined in [RFC4408] have led to some interoperability issues.
Accordingly, its use is no longer appropriate for SPF version 1; implementations are not to use it." In RFC
7208, see section 14.1, The SPF DNS Record Type.
Instead of an SPF record, we recommend that you create a TXT record that contains the applicable value.
For more information about valid values, see Sender Policy Framework, SPF Record Syntax.
Example for the Amazon Route 53 console
"v=spf1 ip4:192.168.0.1/16 -all"
Example for the Amazon Route 53 API
<Value>"v=spf1 ip4:192.168.0.1/16 -all"</Value>
SRV Format
An SRV record Value element consists of four space-separated values.The first three values are decimal
numbers representing priority, weight, and port.The fourth value is a domain name. For information about
SRV record format, refer to the applicable documentation.
Example for the Amazon Route 53 console
10 5 80 hostname.example.com
Example for the Amazon Route 53 API
<Value>10 5 80 hostname.example.com</Value>
API Version 2013-04-01
7
Amazon Route 53 Developer Guide
SOA Format
TXT Format
A TXT record contains a space-separated list of double-quoted strings. A single string include a maximum
of 255 characters. In addition to the characters that are permitted unescaped in domain names, space
is allowed in TXT strings. All other octet values must be quoted in octal form. Unlike domain names, case
is preserved in character strings, meaning that Ab is not the same as aB.You can include a literal quote
in a string by preceding it with a \ character.
Example for the Amazon Route 53 console
"This string includes \"quotation marks\"." "The last character in this string
is an accented e specified in octal format: \351"
Example for the Amazon Route 53 API
<Value>"This string includes \"quotation marks\"." "The last character in this
string is an accented e specified in octal format: \351"</Value>
IP Address Ranges of Amazon Route 53 Servers
Amazon Web Services (AWS) publishes its current IP address ranges in JSON format.To view the current
ranges, download ip-ranges.json. For more information, see AWS IP Address Ranges in the Amazon
Web Services General Reference.
To find the IP address ranges that are associated with Amazon Route 53 name servers, search
ip-ranges.json for the following string:
"service": "ROUTE53"
To find the IP address ranges that are associated with Amazon Route 53 health checkers, search
ip-ranges.json for the following string:
"service": "ROUTE53_HEALTHCHECKS"
DNS Constraints and Behaviors
DNS messaging is subject to factors that affect how you create and use hosted zones and resource
record sets.This section explains these factors.
Maximum Response Size
To comply with DNS standards, responses sent over UDP are limited to 512 bytes in size. Responses
exceeding 512 bytes are truncated and the resolver must re-issue the request over TCP. If the resolver
supports EDNS0 (as defined in RFC 2671), and advertises the EDNS0 option to Amazon Route 53,
Amazon Route 53 permits responses up to 4096 bytes over UDP, without truncation.
Authoritative Section Processing
For successful queries, Amazon Route 53 appends name server (NS) resource record sets for the relevant
hosted zone to the Authority section of the DNS response. For names that are not found (NXDOMAIN
API Version 2013-04-01
8
Amazon Route 53 Developer Guide
TXT Format
responses), Amazon Route 53 appends the start of authority (SOA) resource record set (as defined in
RFC 1035) for the relevant hosted zone to the Authority section of the DNS response.
Additional Section Processing
Amazon Route 53 appends resource record sets to the Additional section. If the records are known and
appropriate, the service appends A or AAAA resource record sets for any target of an MX, CNAME, NS,
or SRV record cited in the Answer section. For more information about these DNS record types, see
Supported DNS Resource Record Types (p. 4).
Amazon Route 53 Pricing
As with other AWS products, there are no contracts or minimum commitments for using Amazon
Route 53—you pay only for the hosted zones you configure and the number of queries that Amazon
Route 53 answers. For more information, see Amazon Route 53 Pricing.
AWS Identity and Access Management
Amazon Route 53 integrates with AWS Identity and Access Management (IAM), a service that lets your
organization do the following:
Create users and groups under your organization's AWS Account
Easily share your AWS Account resources between the users in the account
Assign unique security credentials to each user
Granularly control users access to services and resources
Get a single AWS bill for all users in the AWS Account
For example, you can use IAM with Amazon Route 53 to control which users in your AWS Account can
create a new hosted zone or change resource record sets.
For information about using Amazon Route 53 with IAM, see Authentication and Access Control for
Amazon Route 53 (p. 277).
For general information about IAM, go to:
Identity and Access Management (IAM)
IAM Getting Started Guide
IAM User Guide
API Version 2013-04-01
9
Amazon Route 53 Developer Guide
Additional Section Processing
Getting Started with Amazon
Route 53
Getting started with Amazon Route 53 is easy: create an AWS account if you don't already have one,
register a domain, and create some resource record sets, all in the Amazon Route 53 console. For a
detailed explanation of the process, see Registering a New Domain (p. 14).
Note
If you want to migrate an existing domain or subdomain to use Amazon Route 53 as the DNS
service, see Configuring Amazon Route 53 as Your DNS Service (p. 141).
You can access Amazon Route 53 using the Amazon Route 53 console, the Amazon Route 53 API, AWS
SDKs, or the AWS command-line interface. For more information, see the applicable topic.
Topics
The Amazon Route 53 Console (p. 10)
The Amazon Route 53 API (p. 11)
AWS SDKs that Support Amazon Route 53 (p. 11)
AWS Command Line Interface Support for Amazon Route 53 (p. 11)
AWS Tools for Windows PowerShell Support for Amazon Route 53 (p. 12)
The Amazon Route 53 Console
You can use the Amazon Route 53 console to create, delete, and list Amazon Route 53 hosted zones,
resource record sets, and health checks.
Note
Some ad-blocking plugins for web browsers interfere with Amazon Route 53 console operations,
which can cause the console to behave unpredictably. If you installed an ad-blocking plugin for
your browser, we recommend that you add the URL for the Amazon Route 53 console, https://
console.aws.amazon.com/route53/home, to the whitelist for the plugin.
To access the Amazon Route 53 console
Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
API Version 2013-04-01
10
Amazon Route 53 Developer Guide
The Amazon Route 53 Console
To display help for the Amazon Route 53 console
To display help for a field, move the cursor over the field name.
To display help for the current page in the console, click the help icon, in the upper right corner of
the Amazon Route 53 console.
The Amazon Route 53 API
The Amazon Route 53 API is a REST API that you can use to create, delete, and list Amazon Route 53
hosted zones and resource record sets. (When using the API, you change a resource record set by
deleting the existing one and creating a new one.) For information about the Amazon Route 53 API, see
the Amazon Route 53 API Reference. For information about how to use the API, including how to
authenticate REST requests, see Making API Requests in the Amazon Route 53 API Reference.
AWS SDKs that Support Amazon Route 53
The following AWS SDKs include a client for Amazon Route 53:
AWS SDK for Java version 1.2.13 and later. For more information, see AWS SDK for Java.
AWS SDK for .NET version 1.4.1 and later. For more information, see AWS SDK for .NET.
AWS SDK for PHP version 2.0.3 and later. For more information, see AWS SDK for PHP.
AWS SDK for Python version 2.0 and later. For more information, see boto on github.
AWS SDK for Ruby version 1.6.0 and later. For more information, see AWS SDK for Ruby.
AWS Command Line Interface Support for
Amazon Route 53
The AWS command line interface (AWS CLI) supports Amazon Route 53. For information about getting
set up to use the AWS CLI, see the AWS Command Line Interface User Guide. For information about
AWS CLI commands for Amazon Route 53, see route53 Available Commands in the AWS Command
Line Interface Reference.
API Version 2013-04-01
11
Amazon Route 53 Developer Guide
The Amazon Route 53 API
AWS Tools for Windows PowerShell Support for
Amazon Route 53
AWS Tools for Windows PowerShell supports Amazon Route 53. For more information, see AWS Tools
for Windows PowerShell Documentation.
API Version 2013-04-01
12
Amazon Route 53 Developer Guide
AWS Tools for Windows PowerShell Support for Amazon
Route 53
Registering Domain Names Using
Amazon Route 53
When you want to get a new domain name, such as the example.com part of the URL http://example.com,
you can register it with Amazon Route 53.You can also transfer the registration for existing domains from
other registrars to Amazon Route 53 or transfer the registration for domains that you register with Amazon
Route 53 to another registrar.
The procedures in this chapter explain how to register and transfer domains using the Amazon Route 53
console, and how to edit domain settings and view domain status. If you're only registering and managing
a few domains, using the console is the easiest way.
If you need to register and manage a lot of domains, you might prefer to use the Amazon Route 53 API
or one of the AWS SDKs. For more information about API actions for domain registration, see Actions
on Domain Registrations in the Amazon Route 53 API Reference. For a list of the AWS SDKs that support
Amazon Route 53 and for links to the corresponding SDK pages on the AWS website, see AWS SDKs
that Support Amazon Route 53 (p. 11).
Note
If you are using a language for which an AWS SDK exists, use the SDK rather than trying to
work your way through the APIs. The SDKs make authentication simpler, integrate easily with
your development environment, and provide easy access to Amazon Route 53 commands.
Domain name registration services are provided under our Domain Name Registration Agreement.
Topics
Registering and Updating Domains (p. 14)
Privacy Protection for Contact Information (p. 22)
Renewing Registration for a Domain (p. 23)
Extending the Registration Period for a Domain (p. 26)
Transferring Domains (p. 27)
Configuring DNSSEC for a Domain (p. 35)
Getting a Domain Name Unsuspended (p. 39)
Deleting a Domain Name Registration (p. 40)
Downloading a Domain Billing Report (p. 40)
Domains that You Can Register with Amazon Route 53 (p. 41)
API Version 2013-04-01
13
Amazon Route 53 Developer Guide
Registering and Updating Domains
For information about registering new domains and updating the settings in existing domains, see the
applicable topic.
Topics
Registering a New Domain (p. 14)
Values that You Specify When You Register a Domain or Edit Domain Settings (p. 16)
Values that Amazon Route 53 Returns When You Register or Update a Domain (p. 19)
Viewing the Status of a Domain Registration (p. 20)
Adding Resource Record Sets for a New Domain (p. 20)
Editing Contact Information and Other Settings for a Domain (p. 20)
Adding or Changing Name Servers and Adding or Changing Glue Records (p. 22)
Registering a New Domain
When you want to register a new domain using the Amazon Route 53 console, perform the following
procedure.
Important
When you register a domain with Amazon Route 53, we automatically create a hosted zone for
the domain to make it easier for you to use Amazon Route 53 as the DNS service provider for
your new domain. This hosted zone is where you store information about how to route traffic for
your domain, for example, to an Amazon EC2 instance or a CloudFront distribution. We charge
a small monthly fee for the hosted zone in addition to the annual charge for the domain
registration. If you don't want to use your domain right now, you can delete the hosted zone; if
you delete it within 12 hours of registering the domain, there won't be any charge for the hosted
zone on your AWS bill. We also charge a small fee for the DNS queries that we receive for your
domain. For more information, see Amazon Route 53 Pricing.
To register a new domain using Amazon Route 53
1. By default, you can register up to five domains. If you want to register more than five domains, open
a case with the Support Center, and request an increase in the number of domains that you can
register.
2. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
3. If you're new to Amazon Route 53, under Domain Registration, choose Get Started Now.
If you're already using Amazon Route 53, in the navigation pane, choose Registered Domains.
4. Choose Register Domain.
5. Enter the domain name that you want to register, and choose Check to find out whether the domain
name is available.
For information about how to specify characters other than a-z, 0-9, and - (hyphen) and how to specify
internationalized domain names, see DNS Domain Name Format (p. 2).
6. If the domain is available, choose Add to cart. The domain name appears in your shopping cart.
The Availability for popular TLDs list shows other domains that you might want to register instead
of your first choice (if it's not available) or in addition to your first choice. Choose Add to cart for
each additional domain that you want to register, up to a maximum of five domains.
7. In the shopping cart, choose the number of years that you want to register the domain for.
8. To register more domains, repeat steps 5 through 7.
API Version 2013-04-01
14
Amazon Route 53 Developer Guide
Registering and Updating Domains
9. Choose Continue.
10. On the Contact Details for Your nDomains page, enter contact information for the domain registrant,
administrator, and technical contacts.The values that you enter here are applied to all of the domains
that you're registering.
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 My Registrant, Administrative, and Technical
Contacts are all the same to No.
If you're registering more than one domain, we use the same contact information for all of the domains.
For more information, see Values that You Specify When You Register a Domain or Edit Domain
Settings (p. 16).
11. 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.
12. Choose whether you want to hide your contact information from WHOIS queries. For more information,
see the following topics:
Privacy Protection for Contact Information (p. 22)
Domains that You Can Register with Amazon Route 53 (p. 41)
13. Choose Continue.
14. Review the information that you entered, read the terms of service, and select the check box to
confirm that you've read the terms of service.
15. Choose Complete Purchase.
We send an email to the registrant for the domain to verify that the registrant contact can be reached
at the email address that you specified. (This is an ICANN requirement.) The email comes from one
of the following email addresses:
noreply@registrar.amazon.com – for TLDs registered by Amazon Registrar.
noreply@domainnameverification.net – for TLDs registered by our registrar associate, Gandi.
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
Important
The registrant contact must follow the instructions in the email to confirm 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.
You'll receive another email when your domain registration has been approved. To determine the
current status of your request, see Viewing the Status of a Domain Registration (p. 20).
16. When domain registration is complete, your next step depends on whether you want to use Amazon
Route 53 or another DNS service as the DNS service for the domain:
Amazon Route 53 – Create resource record sets to tell Amazon Route 53 how you want to route
traffic for the domain. For more information, see Adding Resource Record Sets for a New
Domain (p. 20).
Another DNS service – Configure your new domain to route DNS queries to the other DNS service.
Perform the procedure To update the name servers for your domain when you want to use another
DNS service (p. 16).
API Version 2013-04-01
15
Amazon Route 53 Developer Guide
Registering a New Domain
To update the name servers for your domain when you want to use another DNS service
1. Use the process that is provided by your DNS service to get the name servers for the domain.
2. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
3. In the navigation pane, choose Registered Domains.
4. Choose the name of the domain that you want to configure to use another DNS service.
5. Choose Add/Edit Name Servers.
6. Change the names of the name servers to the name servers that you got from your DNS service in
step 1.
7. Choose Update.
8. (Optional) Delete the hosted zone that Amazon Route 53 created automatically when you registered
your domain.This prevents you from being charged for a hosted zone that you aren't using.
a. In the navigation pane, choose Hosted Zones.
b. Select the radio button for the hosted zone that has the same name as your domain.
c. Choose Delete Hosted Zone.
d. Choose Confirm to confirm that you want to delete the hosted zone.
Values that You Specify When You Register a
Domain or Edit Domain Settings
When you register a domain, transfer domain registration to Amazon Route 53, or edit the settings for a
domain, you specify the values that are described in this topic.
If you change contact information for the domain, we send an email notification to the registrant contact
about the change.This email comes from route53-dev-admin@amazon.com. For most changes, the
registrant contact is not required to respond.
For changes to contact information that also constitute a change in ownership, we send the registrant
contact an additional email. ICANN requires that the registrant contact confirm receiving the email. For
more information, see First Name, Last Name and Organization later in this section.
If you're registering more than one domain, Amazon Route 53 uses the values that you specify for all of
the domains that are in your shopping cart.
My Registrant, Administrative, and Technical contacts are all the same
Specifies whether you want to use the same contact information for the registrant of the domain, the
administrative contact, and the technical contact.
Contact Type
Category for this contact. If you choose an option other than Person, you must enter an organization
name.
For some TLDs, the privacy protection available depends on the value that you choose for Contact
Type. For the privacy protection settings for your TLD, see Domains that You Can Register with
Amazon Route 53 (p. 41).
First Name, Last Name
The first and last names of the contact.
API Version 2013-04-01
16
Amazon Route 53 Developer Guide
Values that You Specify When You Register a Domain
or Edit Domain Settings
When the contact type is Person and you change the First Name and/or Last Name fields for the
registrant contact, you change the owner of the domain. ICANN requires that we email the registrant
contact to get approval. The email comes from one of the following email addresses:
Email address that approval email comes fromTLDs
noreply@registrar.amazon.comTLDs registered by
Amazon Registrar
domains@tppwholesale.com.au.com.au and .net.au
nic@nic.fr (The email is sent both to the current registrant contact and the
new registrant contact.)
.fr
noreply@domainnameverification.netAll others
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
Important
The registrant contact must follow the instructions in the email to confirm 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.
If you change the email address of the registrant contact, this email is sent to the former email address
and the new email address for the registrant contact.
Some TLD registrars charge a fee for changing the domain owner. When you change one of these
values, the Amazon Route 53 console displays a message that tells you whether there is a fee.
Organization
The organization that is associated with the contact, if any. For the registrant and administrative
contacts, this is typically the organization that is registering the domain. For the technical contact,
this might be the organization that manages the domain.
When the contact type is any value except Person and you change the Organization field for the
registrant contact, you change the owner of the domain. ICANN requires that we email the registrant
contact to get approval. The email comes from one of the following email addresses:
Email address that approval email comes fromTLDs
noreply@registrar.amazon.comTLDs registered by
Amazon Registrar
domains@tppwholesale.com.au.com.au and .net.au
nic@nic.fr (The email is sent both to the current registrant contact and the
new registrant contact.)
.fr
noreply@domainnameverification.netAll others
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
If you change the email address of the registrant contact, this email is sent to the former email address
and the new email address for the registrant contact.
API Version 2013-04-01
17
Amazon Route 53 Developer Guide
Values that You Specify When You Register a Domain
or Edit Domain Settings
Some TLD registrars charge a fee for changing the domain owner. When you change the value of
Organization, the Amazon Route 53 console displays a message that tells you whether there is a
fee.
Email
The email address for the contact.
If you change the email address for the registrant contact, we send a notification email to the former
email address and the new email address.This email comes from route53-dev-admin@amazon.com.
Phone
The phone number for the contact:
If you're entering a phone number for locations in the United States or Canada, enter 1 in the first
field and the 10-digit area code and phone number in the second field.
If you're entering a phone number for any other location, enter the country code in the first field,
and enter the rest of the phone number in the second field. See CountryCode.org for a list of phone
country codes, for example, 423 for Liechtenstein.
Address 1
The street address for the contact.
Address 2
Additional address information for the contact, for example, apartment number or mail stop.
Country
The country for the contact.
State
The state or province for the contact, if any.
CityThe city for the contact.
Postal/Zip code
The postal or zip code for the contact.
Fields for selected top-level domains
Some top-level domains require that you specify additional values.
Privacy Protection
Whether you want to conceal your contact information from WHOIS queries. If you select Hide
contact information, WHOIS ("who is") queries will return contact information for the registrar or
the value "Protected by policy."
If you select Don't hide contact information, you'll get more email spam at the email address that
you specified.
Anyone can send a WHOIS query for a domain and get back all of the contact information for that
domain. The WHOIS command is available in many operating systems, and it's also available as a
web application on many websites.
Important
Although there are legitimate users for the contact information associated with your domain,
the most common users are spammers, who target domain contacts with unwanted email
and bogus offers. In general, we recommend that you choose Hide contact information
for Privacy Protection.
For more information, see the following topics:
Privacy Protection for Contact Information (p. 22)
Domains that You Can Register with Amazon Route 53 (p. 41)
Auto Renew (Only available when editing domain settings)
Whether you want Amazon Route 53 to automatically renew the domain before it expires. The
registration fee is charged to your AWS account. For more information, see Renewing Registration
for a Domain (p. 23).
API Version 2013-04-01
18
Amazon Route 53 Developer Guide
Values that You Specify When You Register a Domain
or Edit Domain Settings
Caution
If you disable automatic renewal, registration for the domain will not be renewed when the
expiration date passes, and you might lose control of the domain name.
The period during which you can renew a domain name varies by top-level domain (TLD). For an
overview about renewing domains, see Renewing Registration for a Domain (p. 23). For information
about extending domain registration for a specified number of years, see Extending the Registration
Period for a Domain (p. 26).
Values that Amazon Route 53 Returns When You
Register or Update a Domain
When you register your domain with Amazon Route 53, Amazon Route 53 returns the following values
in addition to the values that you specified.
Registered on
The date on which the domain was originally registered with Amazon Route 53.
Expires on
The date and time on which the current registration period expires, in Greenwich Mean Time (GMT).
The registration period is typically one year, although the registries for some top-level domains (TLDs)
have longer registration periods. For the registration and renewal period for your TLD, see Domains
that You Can Register with Amazon Route 53 (p. 41).
For most TLDs, you can extend the registration period by up to ten years. For more information, see
Extending the Registration Period for a Domain (p. 26).
Domain name status code
The current status of the domain.
ICANN, the organization that maintains a central database of domain names, has developed a set
of domain name status codes (also known as EPP status codes) that tell you the status of a variety
of operations on a domain name, for example, registering a domain name, transferring a domain
name to another registrar, renewing the registration for a domain name, and so on. All registrars use
this same set of status codes.
For a current list of domain name status codes and an explanation of what each code means, go to
the ICANN website and search for epp status codes. (Search on the ICANN website; web searches
sometimes return an old version of the document.)
Transfer lock
Whether the domain is locked to reduce the possibility of someone transferring your domain to another
registrar without your permission. If the domain is locked, the value of Transfer Lock is Enabled. If
the domain is not locked, the value is Disabled.
Auto renew
Whether Amazon Route 53 will automatically renew the registration for this domain shortly before
the expiration date.
Authorization code
The code that is required if you want to transfer registration of this domain to another registrar. An
authorization code is only generated when you request it. For information about transferring a domain
to another registrar, see Transferring a Domain from Amazon Route 53 to Another Registrar (p. 33).
Name servers
The Amazon Route 53 servers that respond to DNS queries for this domain.We recommend that
you don't delete Amazon Route 53 name servers.
For information about adding, changing, or deleting name servers, see Editing Contact Information
and Other Settings for a Domain (p. 20).
API Version 2013-04-01
19
Amazon Route 53 Developer Guide
Values that Amazon Route 53 Returns When You
Register or Update a Domain
Viewing the Status of a Domain Registration
ICANN, the organization that maintains a central database of domain names, has developed a set of
domain name status codes (also known as EPP status codes) that tell you the status of a variety of
operations, for example, registering a domain name, transferring a domain name to another registrar,
renewing the registration for a domain name, and so on. All registrars use this same set of status codes.
To view the status code for your domains, perform the following procedure.
To view the status of a domain
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of your domain.
4. For the current status of your domain, see the value of the Domain name status field.
For a current list of domain name status codes and an explanation of what each code means, go to
the ICANN website and search for epp status codes. (Search on the ICANN website; web searches
sometimes return an old version of the document.)
Adding Resource Record Sets for a New Domain
As soon as you receive email confirmation that we successfully registered a domain for you, you can
start to create resource record sets for the domain. These resource record sets tell Amazon Route 53
how you want to route queries for your domain. For example, when someone enters your domain name
in a browser and that query makes its way to Amazon Route 53, do you want Amazon 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?
When you register your domain with Amazon Route 53, we automatically create a hosted zone for the
new domain.This hosted zone, which has the same name as your domain, is the container in which
Amazon Route 53 will store the resource record sets for your domain. For more information about how
to create resource record sets, see Working with Resource Record Sets (p. 178).
Editing Contact Information and Other Settings
for a Domain
When you want to edit settings for a domain that you registered using Amazon Route 53, perform the
following procedure.
Note
For most top-level domains (TLDs), you can change the expiration date for a domain. For more
information, see Extending the Registration Period for a Domain (p. 26).
To edit contact information and other settings for a domain
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of the domain that you want to edit settings for.
4. Edit the applicable values:
API Version 2013-04-01
20
Amazon Route 53 Developer Guide
Viewing the Status of a Domain Registration
Edit Contacts
To edit contact information, including the privacy-protection setting for a contact, choose Edit
Contacts. For more information, see Values that You Specify When You Register a Domain or
Edit Domain Settings (p. 16).
Transfer Lock
To change whether the domain is locked to prevent an unauthorized transfer to another registrar,
choose Enable (to lock the domain) or Disable (to unlock the domain).
Auto Renew
To change whether Amazon Route 53 automatically renews the registration for your domain
before the expiration date, choose Enable (to turn on automatic renewal) or Disable (to turn off
automatic renewal). We strongly recommend that you choose Enable to ensure that you retain
ownership of your domain.
Add/Edit Name Servers
To edit name servers, choose Add/Edit Name Servers and enter the applicable values. Then
choose Update. For more information about editing name servers, see Adding or Changing
Name Servers and Adding or Changing Glue Records (p. 22).
5. Choose Save.
When you change some values, you change the owner of the domain:
When the contact type is Person and you change the First Name and/or Last Name fields for the
registrant contact, you change the owner of the domain.
When the contact type is any other value and you change the Organization field for the registrant
contact, you change the owner of the domain.
ICANN requires that we email the registrant contact to get approval.The email comes from one of
the following email addresses:
Email address that approval email comes fromTLDs
noreply@registrar.amazon.comTLDs registered by
Amazon Registrar
domains@tppwholesale.com.au.com.au and .net.au
nic@nic.fr (The email is sent both to the current registrant contact and
the new registrant contact.)
.fr
noreply@domainnameverification.netAll others
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
Important
Within 15 days, the registrant contact must follow the instructions in the email to confirm
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.
API Version 2013-04-01
21
Amazon Route 53 Developer Guide
Editing Contact Information and Other Settings for a
Domain
Adding or Changing Name Servers and Adding or
Changing Glue Records
In general, you don't need to change the name servers that Amazon Route 53 assigned to your domain
and to the corresponding hosted zone when you registered the domain. If you do need to add or change
name servers, perform the following procedure.You can also use this procedure to specify glue records
(IP addresses) when you're configuring white label name servers—name servers that have the same
domain name as the hosted zone. For more information about configuring white label name servers (also
known as vanity name servers or private name servers), see Configuring White Label Name Servers (p. 165).
Caution
If you change name servers to the wrong values, specify the wrong IP addresses in glue records,
or delete one or more name servers without specifying new ones, your website or application
might become unavailable on the Internet.
To add or change name servers and glue records
1. .fi domains only – Order an authorization key from the Finnish Communications Regulatory Authority,
the registry for .fi domains.You use the authorization key later in this process. For more information,
see Ordering of authorization key on the Finnish Communications Regulatory Authority website.
Important
The Finnish Communications Regulatory Authority mails the authorization key to you, which
can take two weeks or more. Do not continue with this procedure until you have the key.
2. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
3. In the navigation pane, choose Registered Domains.
4. Choose the name of the domain for which you want to edit settings.
5. Choose Add/Edit Name Servers.
6. .fi domains only – In the Authorization Key field, type the authorization key that you got in step 1.
7. In the Edit Name Servers dialog box, you can do the following:
Add one or more name servers.
Replace the name of an existing name server.
Add glue records or change the IP addresses in glue records. If you add a name server or change
the name of a name server and specify a name that is a subdomain of the domain that you're
updating (for example, ns1.example.com in the domain example.com), Amazon Route 53 prompts
you to specify one or more IP addresses for the name server. These IP addresses are known as
glue records.
Delete a name server. Choose the x icon on the right side of the field for that name server.
8. Choose Update.
Privacy Protection for Contact Information
When you register a domain with Amazon Route 53, we enable privacy protection by default for all the
contacts for the domain. This typically hides most of your contact information from WHOIS ("Who is")
queries and reduces the amount of spam that you receive.Your contact information is replaced either
with contact information for the registrar or with the phrase "Protected by policy."
API Version 2013-04-01
22
Amazon Route 53 Developer Guide
Adding or Changing Name Servers and Adding or
Changing Glue Records
Important
You can hide contact information only when the domain is locked to prevent transfers. If you're
transferring the domain to or from Amazon Route 53, you must disable privacy protection, so
your contact information is visible in WHOIS queries.You can re-enable privacy protection when
the transfer is complete.
You can choose to disable privacy protection for some or all contacts for a domain. If you do, anyone can
send a WHOIS query for the domain and, for most top-level domains (TLDs), get all the contact information
that you provided when you registered the domain, including name, address, phone number, and email
address.The WHOIS command is widely available; it's included in many operating systems, and it's also
available as a web application on many websites.
The information that you can hide from WHOIS queries depends on two main factors:
The registry for the top level domain
Some TLD registries hide all contact information automatically, some allow you to choose to hide all
contact information, some allow you to hide only some information, and some do not allow you to
hide any information. For example, most registries allow you to hide your address, phone number,
and email address. Only a few also allow you to hide your name.
The registrar
When you register a domain with Amazon Route 53 or transfer a domain to Amazon Route 53, the
registrar for the domain is either Amazon Registrar or our registrar associate, Gandi. Amazon Registrar
and Gandi hide different information by default:
Amazon Registrar – By default, all of your contact information is hidden.
Gandi – By default, all of your contact information is hidden except first and last name, and
organization name. However, regulations for the TLD registry take precedence.
To find out what information is hidden for the TLD for your domain, see Domains that You Can Register
with Amazon Route 53 (p. 41). For information about how to change the privacy settings for the contacts
for a domain, see Editing Contact Information and Other Settings for a Domain (p. 20).
Renewing Registration for a Domain
When you register a domain with Amazon Route 53 or you transfer domain registration to Amazon
Route 53, we configure the domain to renew automatically.The automatic renewal period is typically one
year, although the registries for some top-level domains (TLDs) have longer renewal periods. For the
registration and renewal period for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
For most top-level domains (TLDs), you can change the expiration date for a domain. For more information,
see Extending the Registration Period for a Domain (p. 26).
Caution
If you turn off automatic renewal, be aware of the following effects on your domain:
Some TLD registries delete domains even before the expiration date if you don't renew early
enough. We strongly recommend that you leave automatic renewal enabled if you want to
keep a domain name.
We also strongly recommend that you not plan to re-register a domain after it has expired.
Some registrars allow others to register domains immediately after the domains expire, so
you might not be able to re-register before the domain is taken by someone else.
Some registries charge a large premium to restore expired domains.
On or near the expiration date, the domain becomes unavailable on the Internet.
API Version 2013-04-01
23
Amazon Route 53 Developer Guide
Renewing Registration for a Domain
To determine whether automatic renewal is enabled for your domain, see Editing Contact Information
and Other Settings for a Domain (p. 20).
If automatic renewal is enabled, here's what happens:
45 days before expiration
We send an email to the registrant contact that tells you that automatic renewal is currently enabled
and gives instructions about how to disable it. Keep your registrant contact email address current so
you don't miss this email.
35 or 30 days before expiration
For all domains except .com.ar, .com.br, and .jp domains, we renew domain registration 35 days
before the expiration date so we have time to resolve any issues with your renewal before the domain
name expires.
The registries for .com.ar, .com.br, and .jp domains require that we renew the domains no more than
30 days before expiration.You'll get a renewal email from Gandi, our registrar associate, 30 days
before expiration, which is the same day that we renew your domain if you have automatic renewal
enabled.
Note
When we renew your domain, we send you an email to let you know that we renewed it. If
the renewal failed, we send you an email to explain why it failed.
If automatic renewal is disabled, here's what happens as the expiration date for a domain name
approaches:
45 days before expiration
We send an email to the registrant contact for the domain that tells you that automatic renewal is
currently disabled and gives instructions about how to enable it. Keep your registrant contact email
address current so you don't miss this email.
30 days and 7 days before expiration
If automatic renewal is disabled for the domain, ICANN, the governing body for domain registration,
requires the registrar to send you an email. The email comes from one of the following email
addresses:
noreply@registrar.amazon.com – For domains for which the registrar is Amazon Registrar.
noreply@domainnameverification.net – For domains for which the registrar is our registrar
associate, Gandi.
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
If you enable automatic renewal less than 30 days before expiration, and the renewal period has not
passed, we renew the domain within 24 hours.
Caution
Some TLD registries stop allowing renewals as much as 25 days before the expiration date,
and many don't allow renewal after the expiration date. In addition, processing a renewal
can take up to a day. If you delay too long before enabling automatic renewal, the domain
might expire before renewal can be processed, and you might lose the domain. If the
expiration date is approaching, we recommend that you manually extend the expiration date
for the domain. For more information, see Extending the Registration Period for a
Domain (p. 26).
For more information about renewal periods, go to the "Renewal, restoration, and deletion times"
table on the Renewing a Domain Name page on the Gandi website.
After the expiration date
Most domains are held by the registrar for a brief time after expiration, so you might be able to renew
an expired domain after the expiration date, but we strongly recommend that you keep automatic
API Version 2013-04-01
24
Amazon Route 53 Developer Guide
Renewing Registration for a Domain
renewal enabled if you want to keep your domain. For information about trying to renew a domain
after the expiration date, see Renewing or Restoring an Expired Domain (p. 25).
Renewing or Restoring an Expired Domain
If you don't renew a domain before the expiration date, some registries for top-level domains (TLDs) allow
you to do one or both of the following:
Renew the expired domain during a late-renewal period
Restore the domain after the late-renewal period passes and before it becomes available for others to
register
To try to renew or restore domain registration for a domain that has expired
1. Determine whether the TLD registry for the domain supports renewing or restoring expired domains.
a. Go to the "Renewal, restoration, and deletion times" table on the Renewing a Domain Name
page on the Gandi website.
b. Find the TLD for your domain, and review the applicable values:
Determine whether the registry supports renewing or restoring an expired domain.
If renewal or restoration is supported, determine whether the domain is still within the renewal
or restoration period.
The list includes some TLDs that Amazon Route 53 doesn't support.
Important
We forward renewal and restoration requests to Gandi, which processes the requests during
business hours Monday through Friday. Gandi is based in Paris, where the time is UTC/GMT
+1 hour. As a result, depending on when you submit your request, in rare cases it can take
a week or more for a request to be processed.
2. Get the expiration date for the domain:
a. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
b. In the navigation pane, choose Registered Domains.
c. Choose the name of the domain that you want to view the expiration date for.
d. Check the value of Expires on.
3. Using the AWS account that the domain was registered to, sign in to the AWS Support Center.
4. Specify the following values:
Regarding
Accept the default value of Account and Billing Support.
Service
Accept the default value of Billing.
Category
Accept the default value of Domain name registration issue.
Subject
Type Renew an expired domain.
API Version 2013-04-01
25
Amazon Route 53 Developer Guide
Renewing or Restoring an Expired Domain
Description
Provide the following information:
The domain that you want to renew
The account ID of the AWS account that the domain was registered to
Contact method
Specify a contact method and, if you choose Phone, enter the applicable values.
5. Choose Submit.
6. When we learn whether we were able to renew or restore your expired domain, a customer support
representative will contact you. In addition, if we were able to renew or restore your domain, the
expiration date in the console will change to the new date.
Extending the Registration Period for a Domain
When you register a domain with Amazon Route 53 or you transfer domain registration to Amazon
Route 53, we configure the domain to renew automatically.The automatic renewal period is typically one
year, although the registries for some top-level domains (TLDs) have longer renewal periods.
All generic TLDs and many country-code TLDs let you extend domain registration for longer periods,
typically up to ten years in one-year increments.To determine whether you can extend the registration
period for your domain, see Domains that You Can Register with Amazon Route 53 (p. 41). If longer
registration periods are allowed, perform the following procedure.
Note
Some TLD registries have restrictions on when you can renew or extend a domain registration,
for example, the last two months before the domain expires. Even if the registry allows extending
the registration period for a domain, they might not allow it at the current number of days before
the domain expires.
To extend the registration period for your domain
1. Open the Amazon Route 53 console at https://console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of the domain for which you want to extend the registration period.
The Expires on field lists the current expiration date for the domain. If the registry for the TLD allows
extending the registration period, an extend link appears on the right side of the expiration date.
4. Choose extend.
5. In the Extend registration for list, choose the number of years that you want to extend the registration
for.
The list shows all the current options based on the current expiration date and the maximum
registration period allowed by the registry for this domain. The New expiration date field shows the
expiration date with that number of years applied.
6. Choose Extend domain registration.
When we receive confirmation from the registry that they've updated your expiration date, we send
you an email to confirm that we've changed the expiration date.
API Version 2013-04-01
26
Amazon Route 53 Developer Guide
Extending the Registration Period for a Domain
Transferring Domains
You can transfer domain registration from another registrar to Amazon Route 53, from one AWS account
to another, or from Amazon Route 53 to another registrar.
Topics
Transferring Registration for a Domain to Amazon Route 53 (p. 27)
Viewing the Status of a Domain Transfer (p. 30)
How Transferring a Domain to Amazon Route 53 Affects the Expiration Date for Your Domain
Registration (p. 32)
Transferring a Domain to a Different AWS Account (p. 32)
Transferring a Domain from Amazon Route 53 to Another Registrar (p. 33)
Transferring Registration for a Domain to Amazon
Route 53
When you transfer a domain name from another registrar to Amazon Route 53, you need to get some
information from your current registrar and enter it on the Amazon Route 53 console.
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 (p. 32). By default, Amazon Route 53 automatically renews registration for the domain. For
information about changing this setting, see Editing Contact Information and Other Settings for a
Domain (p. 20).
When you transfer a domain to Amazon Route 53, the transfer fee that we apply to your AWS account
depends on the top-level domain (TLD). For more information, see Amazon Route 53 Pricing.
Transfer Requirements for Top-Level Domains
Registries for top-level domains (such as .com) have requirements for transferring domains. Requirements
vary among TLDs, but the following requirements are typical:
You must have registered the domain with 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.
You must have transferred registration for the domain to the current registrar at least 60 days ago.
The domain cannot have any of the following domain name status codes:
• pendingDelete
• pendingTransfer
• redemptionPeriod
• clientTransferProhibited
Some registries block transfers until changes, such as ownership changes, are complete.
For a current list of domain name status codes and an explanation of what each code means, go to the
ICANN website and search for epp status codes. (Search on the ICANN website; web searches sometimes
return an old version of the document.)
API Version 2013-04-01
27
Amazon Route 53 Developer Guide
Transferring Domains
Transferring a Domain to Amazon Route 53
To transfer a domain to Amazon Route 53, perform the following procedure.
To transfer a domain to Amazon Route 53 from another registrar
1. Confirm that Amazon Route 53 supports the top-level domain (for example, .com or .org) for the
domain name that you want to transfer. For more information, see Domains that You Can Register
with Amazon Route 53 (p. 41). If your top-level domain isn't on the list, you can't currently transfer
the domain name to Amazon Route 53.
2. If the registrar for your domain is also the DNS service provider for the domain, we highly recommend
that you consider transferring your DNS service to Amazon Route 53 or another DNS service provider
before you transfer your registration. Some registrars provide free DNS service when you purchase
a domain registration. When you transfer the registration, the previous registrar will not renew your
domain registration and might disable DNS service for the domain as soon as they receive transfer
the request from Amazon Route 53. For more information, see Migrating DNS Service for an Existing
Domain to Amazon Route 53 (p. 141).
Caution
If the registrar for your domain is also the DNS service provider for the domain and you
don't transfer DNS service to another provider, your website, email, and the web applications
associated with the domain might become unavailable.
The Amazon Route 53 DNS service doesn't support DNSSEC. If DNSSEC is configured for the
domain, you must do one of the following:
Delete DNSSEC keys for the domain.
Use a DNS service provider that supports DNSSEC and that won't cancel your DNS service when
you transfer the domain to Amazon Route 53.
For more information, see Configuring DNSSEC for a Domain (p. 35).
3. Using the method provided by your current registrar, perform the following tasks for each domain
that you want to transfer:
Unlock the domain so it can be transferred.
Disable privacy protection for the domain.This makes your contact information visible to WHOIS
queries.
Confirm that the email for the registrant for your domain is up to date. That's the email address at
which we'll contact you with information about the progress of the transfer.
Confirm that the domain status allows you to transfer the domain. For more information, see
Transfer Requirements for Top-Level Domains (p. 27).
Get an authorization code, which authorizes us to request that registration for the domain be
transferred to Amazon Route 53.You'll enter this code in the Amazon Route 53 console later in
the process.
.co.uk, .me.uk, and .org.uk domains
If you're transferring a .co.uk, .me.uk, or .org.uk domain to Amazon Route 53, you don't need
to specify 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 will not change
the value of the IPS tag, contact Nominet.
.jp domains
If you're transferring a .jp domain to Amazon Route 53, you don't need to specify an
authorization code. Instead, use the method provided by your current domain registrar to
update the value of the AGNT code to AGNT-1744, all uppercase.
API Version 2013-04-01
28
Amazon Route 53 Developer Guide
Transferring Domain Registration to Amazon Route 53
.ru domains
If you're transferring a .ru domain to Amazon Route 53, you don't need to specify an
authorization code. Instead, use the method provided by RU-Center, the registry for .ru domains,
to update the Partner Handle for the domain to 5427/NIC-REG. For more information, see
the Registrar's or Registrant's Transfer page on the RU-Center website.
4. If you're already using Amazon Route 53 as the DNS service provider for the domains that you want
to transfer, get the names of the Amazon Route 53 name servers for each of the corresponding
hosted zones. For more information, see Getting the Name Servers for a Public Hosted Zone (p.163).
Then go to the next step.
If you want to continue using another DNS service provider for the domains that you're transferring,
use the method provided by your current DNS service provider to get the names of the name servers
for each domain that you want to transfer.
5. Open the Amazon Route 53 console at https://console.aws.amazon.com/route53/.
6. In the navigation pane, choose Registered Domains.
7. Choose Transfer Domain.
8. Enter the name of the domain for which you want to transfer registration to Amazon Route 53, and
choose Check.
9. If the domain is available for transfer, choose Add to cart.
If the domain is not available for transfer, the Amazon Route 53 console lists the reasons. Contact
your registrar for information about how to resolve the issues that prevent you from transferring your
domain.
10. If you want to transfer other domains, repeat steps 8 and 9.
11. When you've added all of the domains that you want to transfer, choose Continue.
12. For each domain name that you want to transfer, enter the applicable values:
Authorization Code
Enter the authorization code that you got from your current registrar in step 3 of this procedure.
Name Servers
Enter the names of the name servers that you got from the DNS service for the domain in step
4 of this procedure. If you're using Amazon Route 53 as your DNS service provider, enter all
four of the name servers that Amazon Route 53 assigned to the hosted zone for your domain.
13. On the Contact Details for Your nDomains page, enter contact information for the domain registrant,
administrator, and technical contact. The values that you enter here are applied to all of the domains
that you're transferring.
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 My Registrant, Administrative, and Technical
contacts are all the same to No.
For more information, see Values that You Specify When You Register a Domain or Edit Domain
Settings (p. 16).
14. 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.
15. If the value of Contact Type is Person, choose whether you want to hide your contact information
from WHOIS queries. For more information, see Privacy Protection for Contact Information (p. 22).
16. Choose Continue.
17. 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.
18. Choose Complete Purchase.
API Version 2013-04-01
29
Amazon Route 53 Developer Guide
Transferring Domain Registration to Amazon Route 53
We confirm that the domain is eligible for transfer, and we send the registrant for the domain an email
to confirm that the registrant requested the transfer.The email comes from one of the following email
addresses:
Email address that approval email comes fromTLDs
noreply@registrar.amazon.comTLDs registered by
Amazon Registrar
domains@tppwholesale.com.au.com.au and .net.au
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.)
.fr
noreply@domainnameverification.netAll others
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
19. If you're the registrant contact for the domain, follow the instructions in the email to confirm that the
email was received. If someone else is the registrant contact, ask that person to confirm that the
email was received.
We wait up to five days for the registrant to confirm the transfer. If the registrant doesn't confirm the
transfer within five days, we cancel the transfer operation and send an email to the registrant about
the cancellation.
If the registrant contact confirms the transfer, we start to work with your current registrar to transfer
your domain.This step might take up to seven days, depending on your current registrar. 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.The registrant needs to contact the current registrar and resolve
the issues with the transfer.
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 (p. 30).
We charge your AWS account for the domain transfer as soon as the transfer is complete.This is a
one-time charge, so the charge doesn't appear in your CloudWatch billing metrics. For a list of charges
by TLD, see Amazon Route 53 Pricing for Domain Registration.
Viewing the Status of a Domain Transfer
After you initiate the transfer of a domain from another domain registrar to Amazon Route 53, you can
track the status on the Registered Domains page of the Amazon 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
API Version 2013-04-01
30
Amazon Route 53 Developer Guide
Viewing the Status of a Domain Transfer
• pendingDelete
• pendingTransfer
• redemptionPeriod
Verifying WHOIS information (step 2 of 14)
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.
Sent email to registrant contact to get transfer authorization (step 3 of 14)
We've sent an email to the registrant contact for the domain to confirm that the transfer was requested
by an authorized contact of the domain.
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.
Awaiting authorization from registrant contact (step 5 of 14)
We're waiting for the registrant contact of the domain to authorize the transfer (see step 3). If the
registrant contact does not receive the email, confirm that the current registrar for the domain has
the correct email address for the registrant contact.
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.
Requirements vary among TLDs, but the following requirements are typical:
You must have registered the domain with 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.
You must have transferred registration for the domain to the current registrar at least 60 days ago.
The domain cannot have any of the following domain name status codes:
• clientTransferProhibited
• pendingDelete
• pendingTransfer
• redemptionPeriod
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 Amazon Route 53.
Transfer Complete (step 14 of 14)
Your transfer has been successfully completed.
API Version 2013-04-01
31
Amazon Route 53 Developer Guide
Viewing the Status of a Domain Transfer
How Transferring a Domain to Amazon Route 53
Affects the Expiration Date for Your Domain
Registration
When you transfer a domain to another registrar, 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 (p. 26).
Generic TLDs
When you transfer a domain that has a generic TLD (for example, .com) to Amazon Route 53, the new
expiration date for the domain is the expiration date with your previous registrar plus one year.
Geographic TLDs
When you transfer a domain that has a geographic TLD (for example, .co.uk) to Amazon 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.
Geographic TLDs and the Effect of Transferring a Domain on the Expir-
ation Date
Continent
.co.zaThe expiration date remains the same.Africa
.cl, .com.ar, .com.brThe expiration date remains the same.
.ca, .co, .mx, .us – One year is added to the old expiration date.
Americas
.co.nz, .com.au, .com.sg, .jp, .net.au, .net.nz, .org.nz, .ru, .sgThe expir-
ation date remains the same.
.in – One year is added to the old expiration date.
Asia/Oceania
.ch, .co.uk, .de, .es, .fi, .me.uk, .org.uk, .seThe expiration date remains
the same.
.berlin, .eu, .io, .me, .ruhr, .wien – One year is added to the old expiration
date.
.be, .fr, .it, .nlThe new expiration date is one year after the date of transfer.
Europe
Transferring a Domain to a Different AWS Account
If you registered a domain using one AWS account and you want to transfer the domain to another AWS
account, you can do so simply by contacting the AWS Support Center and requesting the transfer.
When you transfer domain registration between AWS accounts, Amazon Route 53 does not transfer the
hosted zone for your domain. 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
API Version 2013-04-01
32
Amazon Route 53 Developer Guide
How Transferring a Domain to Amazon Route 53 Affects
the Expiration Date
affected. The only effect is that you'll need to sign into the Amazon Route 53 console using one account
to see the domain, and sign in using the other account to see the hosted zone.
Important
If you want to transfer the hosted zone to another account, you must manually create the new
hosted zone, create resource record sets in the new hosted zone, and update your domain with
the name servers for the new hosted zone.
To transfer registration for a domain from one AWS account to another, perform the following procedure.
To transfer a domain to a different AWS account
1. Using the AWS account that the domain is currently registered to, sign in to the AWS Support Center.
Important
You must sign in by using the root account that the domain is currently registered to. If you
sign in by using an IAM user or any other account, we can't perform the transfer. This
requirement prevents unauthorized users from transferring domains to other AWS accounts.
2. Specify the following values:
Regarding
Accept the default value of Account and Billing Support.
Service
Accept the default value of Billing.
Category
Accept the default value of Domain name registration issue.
Subject
Specify Transfer a domain to another AWS account.
Description
Provide the following information:
Domain that you want to transfer
Account ID of the AWS account that the domain is currently registered to
Account ID of the AWS account that you want to transfer domain registration to
Contact method
Specify a contact method and, if you choose Phone, enter the applicable values.
3. Choose Submit.
Transferring a Domain from Amazon Route 53 to
Another Registrar
When you transfer a domain from Amazon Route 53 to another registrar, you get some information from
Amazon Route 53 and provide it to the new registrar. The new registrar will do the rest.
Important
If you're currently using Amazon Route 53 as your DNS service provider and you also want to
transfer DNS service to another provider, be aware that the following Amazon 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 resource record sets
Weighted resource record sets
Latency resource record sets
API Version 2013-04-01
33
Amazon Route 53 Developer Guide
Transferring a Domain from Amazon Route 53
Failover resource record sets
Geo resource record sets
Usually, you can transfer registration of a domain name to another registrar without much trouble.
Requirements vary among TLDs, but the following requirements are typical:
You must have registered the domain with 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.
You must have transferred registration for the domain to the current registrar at least 60 days ago.
The domain cannot have any of the following domain name status codes:
• pendingDelete
• pendingTransfer
• redemptionPeriod
• clientTransferProhibited
For a current list of domain name status codes and an explanation of what each code means, go to the
ICANN website and search for epp status codes. (Search on the ICANN website; web searches sometimes
return an old version of the document.)
To transfer a domain from Amazon Route 53 to another registrar
1. .fi domains only – If you're transferring a .fi domain to another registrar, order an authorization key
from the Finnish Communications Regulatory Authority, the registry for .fi domains.You use the
authorization key later in this process. For more information, see Ordering of authorization key on
the Finnish Communications Regulatory Authority website.
Important
The Finnish Communications Regulatory Authority mails the authorization key to you, which
can take two weeks or more. Do not continue with this procedure until you have the key.
2. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
3. In the navigation pane, choose Registered Domains.
4. Choose the name of the domain that you want to transfer to another registrar.
5. On the Your Domains > domain name page, check the value of Domain name status. If it is one
of the following values, you can't currently transfer the domain:
• pendingDelete
• pendingTransfer
• redemptionPeriod
• clientTransferProhibited
For a current list of domain name status codes and an explanation of what each code means, go to
the ICANN website and search for epp status codes. (Search on the ICANN website; web searches
sometimes return an old version of the document.)
6. If the value of Transfer lock is Enabled, choose Disable.
7. Choose Edit contacts.
8. On the Edit Contact Details for domain name page, for Privacy Protection, select Don't hide
contact information for all contacts.
In addition, update the contact information so the new registrar can contact you.
9. Choose Save.
API Version 2013-04-01
34
Amazon Route 53 Developer Guide
Transferring a Domain from Amazon Route 53
10. All domains except .co.uk, .me.uk, .org.uk, and .fi domains – On the Your Domains > domain name
page, at Authorization Code, choose Generate and make note of the authorization code.You'll
provide this value to your registrar later in this procedure.
.co.uk, .me.uk, and .org.uk domains – Change the IPS tag to the value for the new registrar:
a. Go to the Find a Registrar page on the Nominet website, and find the IPS tag for the new registrar.
(Nominet is the registry for .co.uk, .me.uk, and .org.uk domains.)
b. On the Your Domains > domain name page, at IPS Tag, choose Change IPS Tag, and specify
the value that you got in step a.
c. Choose Update.
.fi domains – Skip this step.
11. If you're not currently using Amazon Route 53 as the DNS service provider for your domain, skip to
step 13.
If you are currently using Amazon Route 53 as the DNS service provider for the domain, perform the
following steps:
a. Choose Hosted Zones.
b. Double-click the name of the hosted zone for your domain.The domain and the hosted zone
have the same name.
c. If you want to continue using Amazon Route 53 as the DNS service provider for the domain:
Find the NS record for the hosted zone, and make note of the names of the four name servers.
These names all begin with ns-.
If you do not want to continue using Amazon Route 53 as the DNS service provider for the
domain: Make note of the settings for all of your resource record sets except the NS and SOA
records. For Amazon Route 53–specific features such as alias resource record sets, you'll need
to work with your new DNS service provider to determine how to achieve comparable functionality.
12. If you're transferring DNS service to another provider, use the methods that are provided by the new
DNS service to create a hosted zone and resource record sets to reproduce the functionality of your
Amazon Route 53 resource record sets.
13. Using the process that is provided by the new registrar, request a transfer of the domain.
All domains except .co.uk, .me.uk, .org.uk, and .fi domainsYou'll be prompted to enter the
authorization code that you got from the Amazon Route 53 console in step 10 of this procedure.
If you still want to use Amazon Route 53 as your DNS service provider, specify the names of the
Amazon Route 53 name servers that you got in step 11. 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 12.
.fi domains – Go to the Finnish Communications Regulatory Authority website and request a transfer.
For more information, see the procedure "Domain name transfer made by domain name holder" on
the Transfer of domain name to new holder page.
Configuring DNSSEC for a Domain
Attackers sometimes hijack traffic to Internet endpoints such as web servers by intercepting DNS requests
and returning their own IP addresses to DNS resolvers in place of the actual IP addresses for those
endpoints. Users are then routed to the IP addresses provided by the attackers in the spoofed response,
for example, to fake websites.
API Version 2013-04-01
35
Amazon Route 53 Developer Guide
Configuring DNSSEC for a Domain
You can protect your domain from this type of attack, known as DNS spoofing or a man-in-the-middle
attack, by configuring Domain Name System Security Extensions (DNSSEC), a protocol for securing
DNS traffic.
Important
Amazon Route 53 supports DNSSEC for domain registration but does not support DNSSEC for
DNS service. If you want to configure DNSSEC for a domain that is registered with Amazon
Route 53, you must use another DNS service provider.
Topics
Overview of How DNSSEC Protects Your Domain (p. 36)
Prerequisites and Limits for Configuring DNSSEC for a Domain (p. 37)
Adding Public Keys for a Domain (p. 37)
Deleting Public Keys for a Domain (p. 38)
Overview of How DNSSEC Protects Your Domain
When you configure DNSSEC for your domain, a DNS resolver establishes a chain of trust for responses
from intermediate resolvers.The chain of trust begins with the TLD registry for the domain (your domain's
parent zone) and ends with the authoritative name servers at your DNS service provider. Not all DNS
resolvers support DNSSEC; resolvers that don't support DNSSEC don't perform any signature or
authenticity validation.
Here's how you configure DNSSEC for domains registered with Amazon Route 53 to protect your Internet
hosts from DNS spoofing, simplified for clarity:
1. Use the method provided by your DNS service provider to sign the resource record sets in your hosted
zone with the private key in an asymmetric key pair.
Important
Amazon Route 53 supports DNSSEC for domain registration but does not support DNSSEC
for DNS service. If you want to configure DNSSEC for a domain that is registered with Amazon
Route 53, you must use another DNS service provider.
2. Provide the public key from the key pair to your domain registrar, and specify the algorithm that was
used to generate the key pair. The domain registrar forwards the public key and the algorithm to the
registry for the top-level domain (TLD).
For information about how to perform this step for domains that you registered with Amazon Route 53,
see Adding Public Keys for a Domain (p. 37).
After you configure DNSSEC, here's how it protects your domain from DNS spoofing:
1. Submit a DNS request, for example, by browsing to a website or by sending an email message.
2. The request is routed to a DNS resolver. Resolvers are responsible for returning the appropriate value
to clients based on the request, for example, the IP address for the host that is running a web server
or an email server.
3. If the IP address is cached on the DNS resolver (because someone else has already submitted the
same DNS request, and the resolver already got the value), the resolver returns the IP address to the
client that submitted the request. The client then uses the IP address to access the host.
If the IP address isn't cached on the DNS resolver, the resolver sends a request to the parent zone
for your domain, at the TLD registry, which returns two values:
The Delegation Signer (DS) record, which is a public key that corresponds with the private key that
was used to sign the resource record set.
The IP addresses of the authoritative name servers for your domain.
API Version 2013-04-01
36
Amazon Route 53 Developer Guide
Overview of How DNSSEC Protects Your Domain
4. The DNS resolver sends the original request to another DNS resolver. If that resolver doesn't have
the IP address, it repeats the process until a resolver sends the request to a name server at your DNS
service provider. The name server returns two values:
The resource record set for the domain, such as example.com.Typically this contains the IP address
of a host.
The signature for the resource record set, which you created when you configured DNSSEC.
5. The DNS resolver uses the public key that you provided to the domain registrar (and the registrar
forwarded to the TLD registry) to do to things:
Establish a chain of trust.
Verify that the signed response from the DNS service provider is legitimate and hasn't been replaced
with a bad response from an attacker.
6. If the response is authentic, the resolver returns the value to the client that submitted the request.
If the response can't be verified, the resolver returns an error to the user.
If the TLD registry for the domain doesn't have the public key for the domain, the resolver responds
to the DNS request by using the response that it got from the DNS service provider.
Prerequisites and Limits for Configuring DNSSEC
for a Domain
To configure DNSSEC for a domain, your domain and DNS service provider must meet the following
prerequisites:
The registry for the TLD must support DNSSEC.To determine whether the registry for your TLD supports
DNSSEC, see Domains that You Can Register with Amazon Route 53 (p. 41).
The DNS service provider for the domain must support DNSSEC.
Important
Amazon Route 53 supports DNSSEC for domain registration but does not support DNSSEC
for DNS service. If you want to configure DNSSEC for a domain that is registered with Amazon
Route 53, you must use another DNS service provider.
You must configure DNSSEC with the DNS service provider for your domain before you add public
keys for the domain to Amazon Route 53.
The number of public keys that you can add to a domain depends on the TLD for the domain:
.com and .net domains – up to thirteen keys
All other domains – up to four keys
Adding Public Keys for a Domain
When you're rotating keys or you're enabling DNSSEC for a domain, perform the following procedure
after you configure DNSSEC with the DNS service provider for the domain.
To add public keys for a domain
1. If you haven't already configured DNSSEC with your DNS service provider, use the method provided
by your service provider to configure DNSSEC.
2. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
3. In the navigation pane, choose Registered domains.
4. Choose the name of the domain that you want to add keys for.
API Version 2013-04-01
37
Amazon Route 53 Developer Guide
Prerequisites and Limits for Configuring DNSSEC for a
Domain
5. At the DNSSEC status field, choose Manage keys.
6. Specify the following values:
Key type
Choose whether you want to upload a key-signing key (KSK) or a zone-signing key (ZSK).
Algorithm
Choose the algorithm that you used to sign the resource record sets for the hosted zone.
Public key
Specify the public key from the asymmetric key pair that you used to configure DNSSEC with
your DNS service provider.
7. Choose Add.
Note
You can only add one public key at a time. If you need to add more keys, wait until you
receive a confirmation email from Amazon Route 53.
8. When Amazon Route 53 receives a response from the registry, we send an email to the registrant
contact for the domain. The email either confirms that the public key has been added to the domain
at the registry or explains why the key couldn't be added.
Deleting Public Keys for a Domain
When you're rotating keys or you're disabling DNSSEC for the domain, delete public keys using the
following procedure before you disable DNSSEC with your DNS service provider. We recommend that
you wait for up to three days to delete public keys after you rotate keys or disable DNSSEC with your
DNS service provider. Note the following:
If you're rotating public keys, we recommend that you wait for up to three days after you add the new
public keys to delete the old public keys.
If you're disabling DNSSEC, delete public keys for the domain first. We recommend that you wait for
up to three days before you disable DNSSEC with the DNS service for the domain.
Caution
If DNSSEC is enabled for the domain and you disable DNSSEC with the DNS service, DNS
resolvers that support DNSSEC will return a SERVFAIL error to clients, and the clients won't be
able to access the endpoints that are associated with the domain.
To delete public keys for a domain
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered domains.
3. Choose the name of the domain that you want to delete keys from.
4. At the DNSSEC status field, choose Manage keys.
5. Find the key that you want to delete, and choose Delete.
Note
You can only delete one public key at a time. If you need to delete more keys, wait until you
receive a confirmation email from Amazon Route 53.
6. When Amazon Route 53 receives a response from the registry, we send an email to the registrant
contact for the domain. The email either confirms that the public key has been deleted from the
domain at the registry or explains why the key couldn't be deleted.
API Version 2013-04-01
38
Amazon Route 53 Developer Guide
Deleting Public Keys for a Domain
Getting a Domain Name Unsuspended
When you register a domain with Amazon Route 53 or transfer a domain from another registrar to Amazon
Route 53, we send you a confirmation email.This email includes instructions about how to verify that we
have a valid email address for the registrant contact. The email comes from one of the following email
addresses:
Email Address that Approval Email Comes fromTLDs
noreply@registrar.amazon.comTLDs registered by
Amazon Registrar
domains@tppwholesale.com.au (only if you're transferring the domain to
Amazon Route 53)
.com.au and .net.au
nic@nic.fr (only if you're transferring the domain and you're changing the re-
gistrant contact at the same time.The email is sent both to the current regis-
trant contact and the new registrant contact.)
.fr
noreply@domainnameverification.netAll others
To determine who the registrar is for your TLD, see Domains that You Can Register with Amazon
Route 53 (p. 41).
If you don't respond to the email within 15 days—for example, because the email ended up in your junk
email folder—ICANN requires us to suspend the domain, meaning that it's no longer available on the
Internet. To get the domain unsuspended, perform the following procedure to request another copy of
the email, and follow the instructions in the email.
To get a domain unsuspended
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of the domain that you want to get unsuspended.
4. On the Registered Domains > domain-name page, confirm that the email address for the registrant
contact is valid and an address that you're able to receive email at.
If you need to correct the email address, choose Edit Contacts and change the value of Email for
the registrant contact.
5. On the Registered Domains > domain-name page, choose Send Email Again.
Important
If the domain was suspended for abuse, the Send Email Again button isn't available.You
must open a case with the AWS Support Center. Accept the default values for Regarding,
Service, and Category, and enter the applicable information for Subject, Description, and
Contact Method.
6. Follow the instructions in the email.
Typically, after you respond to the email, the domain is unsuspended in less than 30 minutes, but it
can take up to two hours.
API Version 2013-04-01
39
Amazon Route 53 Developer Guide
Getting a Domain Name Unsuspended
Deleting a Domain Name Registration
For most top-level domains (TLDs), you can delete the registration if you no longer want it. Registries for
some TLDs don't allow you to delete a domain name registration; instead, you must wait for it to expire.
To determine whether you can delete the registration for your domain, see Domains that You Can Register
with Amazon Route 53 (p. 41).
If the registry allows you to delete the registration, perform the procedure in this topic. If the registry
doesn't allow you to delete a domain name registration, disable automatic renewal of domain registration
for this domain. When the Expires on date passes, Amazon Route 53 will automatically delete the
registration for the domain. For information about how to change the automatic renewal setting, see
Editing Contact Information and Other Settings for a Domain (p. 20).
Important
If you delete a domain name registration before the registration was scheduled to expire, we will
not refund the registration fee.
To delete a domain name registration
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
2. In the navigation pane, choose Registered Domains.
3. Choose the name of your domain.
4. Choose Delete Domain.
5. If the registry for your TLD allows deleting a domain name registration, choose Delete Domain.
Downloading a Domain Billing Report
AWS invoices don't include the domain name for domain registration charges. If you manage multiple
domains and you want to view charges by domain for a specified time period, you can download a domain
billing report. This report includes all charges that apply to domain registration, including the following:
Registering a domain
Renewing registration for a domain
Transferring a domain to Amazon Route 53
Changing the owner of a domain (for some TLDs, this operation is free)
The billing report, in CSV format, includes the following values:
The AWS invoice ID that the charge appears on.
The operation (REGISTER_DOMAIN, RENEW_DOMAIN, TRANSFER_IN_DOMAIN, or
CHANGE_DOMAIN_OWNER).
The name of the domain.
The charge for the operation in US dollars.
The date and time in ISO 8601 format, for example, 2016-03-03T19:20:25.177Z. For more information
about ISO 8601 format, see the Wikipedia article ISO 8601.
To download a domain billing report
1. Sign in to the AWS Management Console and open the Amazon Route 53 console at https://
console.aws.amazon.com/route53/.
API Version 2013-04-01
40
Amazon Route 53 Developer Guide
Deleting a Domain Name Registration
2. In the navigation pane, choose Registered Domains.
3. Choose Domain billing report.
4. Choose the date range for the report, and then choose Download domain report.
5. Follow the prompts to open the report or to save it.
Domains that You Can Register with Amazon
Route 53
The following lists show the top-level domains (TLDs) for which you can register domains with Amazon
Route 53.
Topics
Generic Top-Level Domains (p. 41)
Geographic Domains (p. 122)
Generic Top-Level Domains
Generic top-level domains (gTLDs) are global extensions that are used and recognized around the world,
such as .com, .net, and .org.They also include specialty domains such as .bike, .condos, and .marketing.
Not all gTLDs support internationalized domain names (IDNs). The following list indicates whether each
gTLD supports IDNs. For more information about internationalized domain names, see DNS Domain
Name Format (p. 2).
A | B | C | D | E | F | G | H | I,J | K | L | M | N | O | P | Q | R | S | T | U | V | W,X,Y,Z
A
.academy, .accountants, .adult, .agency, .apartments, .associates, .auction, .audio
.academy
Used by educational institutions such as schools and universities. Also used by recruiters, advisors,
advertisers, students, teachers, and administrators who are affiliated with educational institutions.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.accountants
Used by businesses, groups, and individuals affiliated with the accounting profession.
Registration and renewal period
One to ten years.
API Version 2013-04-01
41
Amazon Route 53 Developer Guide
Domains that You Can Register with Amazon Route 53
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.adult
Used for websites that host adults-only content.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Not supported.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.agency
Used by any businesses or groups that identify as agencies.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.apartments
Used by real estate agents, landlords, and renters.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
42
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.associates
Used by businesses and firms that include the term "associates" in their titles. Also used by any
groups or agencies that want to indicate the professional nature of their organizations.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.auction
Used for events related to auctions and auction-based buying and selling.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Spanish, and Latin.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.audio
Used by the audiovisual industry and anyone interested in broadcasting, sound equipment, audio
production, and audio streaming.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for Cyrillic (primarily Russian), French, German, Italian, Portuguese, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
43
Amazon Route 53 Developer Guide
Generic Top-Level Domains
B
.band, .bargains, .bike, .bingo, .biz, .black, .blue, .boutique, .builders, .business, .buzz
.band
Used for sharing information about musical bands and band events. Also used by musicians to
connect with their fan base and sell band-related merchandise.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Spanish, and Latin.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.bargains
Used for information about sales and promotions.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.bike
Used by businesses or groups that cater to cyclists, such as bike stores, motorcycle dealerships,
and repair shops.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
44
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.bingo
Used for online gaming websites or for sharing information about the game of bingo.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.biz Used for business or commercial use.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Not supported.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.black
Used by those who like the color black or those who want to associate the color black with their
business or brand.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Not supported.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.blue
Used by those who like the color blue or those who want to associate the color blue with their business
or brand.
Registration and renewal period
One to ten years.
API Version 2013-04-01
45
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Not supported.
DNSSEC
Not supported.
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.boutique
Used for information about boutiques and small specialty shops.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.builders
Used by companies and individuals affiliated with the construction industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.business
Used by any kind of business. Can be used as an alternative to the .biz extension.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
46
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.buzz
Used for information about the latest news and events.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Spanish.
DNSSEC
Not supported.
Registrar
The registrar for this TLD is our registrar associate, Gandi.
C
.cab, .cafe, .camera, .camp, .capital, .cards, .care, .careers, .cash, .casino, .catering, .center, .ceo, .chat,
.cheap, .church, .city, .claims, .cleaning, .click, .clinic, .clothing, .cloud, .club, .coach, .codes, .coffee,
.college, .com, .community, .company, .computer, .condos, .construction, .consulting, .contractors, .cool,
.coupons, .credit, .creditcard, .cruises
.cabUsed by companies and individuals affiliated with the taxicab industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cafe
Used by cafe businesses and those who have an interest in cafe culture.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
API Version 2013-04-01
47
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Internationalized domain names
Supported for Chinese, French, German, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.camera
Used by photography enthusiasts and anyone who wants to share photos.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.camp
Used by parks and recreation departments, summer camps, writers' workshops, fitness camps, and
camping enthusiasts.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.capital
Used as a general category that describes any kind of capital, such as financial capital or the capital
of a city.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
48
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cards
Used by businesses that specialize in cards such as ecards, printed greeting cards, business cards,
and playing cards. Also ideal for gamers who want to discuss the rules and strategies of card games.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.care
Used by businesses or agencies in the care-giving field. Also used by charitable organizations.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.careers
Used for information about job recruitment.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
49
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.cash
Used by any organization, group, or individual engaged in money-related activities.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.casino
Used by the gambling industry or by gamers who want to share information about gambling and
casino games.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.catering
Used by catering businesses or those who share information about food-related events.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.center
Used as a generic extension for everything from research organizations to community centers.
Registration and renewal period
One to ten years.
API Version 2013-04-01
50
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.ceoUsed for information about CEOs and their equals.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for German.
DNSSEC
Not supported.
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.chat
Used by any kind of online chat website.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cheap
Used by e-commerce websites to promote and sell inexpensive products.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
API Version 2013-04-01
51
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.church
Used by churches of any size or denomination to connect with their congregations and to publish
information about church-related events and activities.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cityUsed to provide information about specific cities, such as points of interest, top local spots to visit,
or neighborhood activities.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.claims
Used by companies that handle insurance claims or provide legal services.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cleaning
Used by businesses or individuals that provide cleaning services.
API Version 2013-04-01
52
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.click
Used by businesses that want to associate the action of clicking with their websites, for example,
clicking products on a website to purchase them.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for Cyrillic (primarily Russian), French, German, Italian, Portuguese, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.clinic
Used by the health care industry and by medical professionals.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.clothing
Used by those in the fashion industry, including retailers, department stores, designers, tailors, and
outlets.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
API Version 2013-04-01
53
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cloud
Used as a general extension, but ideal for companies that provide cloud computing technologies and
services.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Not supported.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.club
Used by any type of club or organization.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Spanish and Japanese.
DNSSEC
Not supported.
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.coach
Used by anyone with an interest in coaching, such as sports professionals, lifestyle coaches, or
corporate trainers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
54
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.codes
Used as a generic extension for all kinds of code, such as codes of conduct, building codes, or
programming code.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.coffee
Used by those in the coffee industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.college
Used by educational institutions such as schools and universities. Also used by recruiters, advisors,
advertisers, students, teachers, and administrators who are affiliated with educational institutions.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for Arabic, simplified and traditional Chinese, Cyrillic, Greek, Hebrew, Japanese, and
Thai.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.com
Used for commercial websites. It is the most popular extension on the Internet.
Registration and renewal period
One to ten years.
Privacy protection
All information is hidden.
API Version 2013-04-01
55
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Internationalized domain names
Supported.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is Amazon Registrar, Inc.
.community
Used by any type of community, club, organization, or special interest group.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.company
Used as a generic extension for companies of all kinds.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.computer
Used as a generic extension for information about computers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
API Version 2013-04-01
56
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.condos
Used by individuals and businesses associated with condominiums.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.construction
Used by those in the construction industry, such as builders and contractors.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.consulting
Used by consultants and others who are affiliated with the consulting industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Latin, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.contractors
Used by contractors, such as contractors in the construction industry.
Registration and renewal period
One to ten years.
API Version 2013-04-01
57
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cool
Used by organizations and groups who want to associate their brand with the latest trends.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.coupons
Used by retailers and manufacturers that provide online coupons and coupon codes.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.credit
Used by the credit industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
58
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.creditcard
Used by companies or banks that issue credit cards.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.cruises
Used by the voyage industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
D
.dance, .dating, .deals, .delivery, .democrat, .dental, .diamonds, .diet, .digital, .direct, .directory, .discount,
.dog, .domains
.dance
Used by dancers, dance instructors, and dance schools.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Latin, and Spanish.
DNSSEC
Not supported.
API Version 2013-04-01
59
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.dating
Used for dating websites.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.deals
Used to provide information about online bargains and sales.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.delivery
Used by companies that deliver any kind of merchandise or service.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.democrat
Used for information about the Democratic Party. Also used by officials running for elected office,
elected officials, political enthusiasts, consultants, and advisors.
API Version 2013-04-01
60
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Latin, and Spanish.
DNSSEC
Not supported.
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.dental
Used by dental professionals and dental suppliers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.diamonds
Used by diamond enthusiasts and those in the diamond industry, including sellers, resellers, and
merchandisers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.dietUsed by health and fitness professionals.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for Cyrillic (primarily Russian), French, German, Italian, Portuguese, and Spanish.
API Version 2013-04-01
61
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.digital
Used for anything and everything digital, but ideal for technology businesses.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.direct
Used as a general extension, but ideal for those who sell products directly to customers through an
e-commerce website.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.directory
Used by the media sector.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
62
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.discount
Used for discount websites and businesses that slash prices.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.dogUsed by dog lovers and those who provide canine services and products.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.domains
Used for information about domain names.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
E
.education, .email, .energy, .engineering, .enterprises, .equipment, .estate, .events, .exchange, .expert,
.exposed, .express
API Version 2013-04-01
63
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.education
Used for information about education.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.email
Used for information about promoting email.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.energy
Used as a general extension, but ideal for those in the energy or energy conservation fields.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.engineering
Used by engineering firms and professionals.
Registration and renewal period
One to ten years.
API Version 2013-04-01
64
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.enterprises
Used for information about enterprises and businesses.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.equipment
Used for information about equipment, equipment retailers or manufacturers, and rental shops.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.estate
Used for information about housing and the housing sector.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
65
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.events
Used for information about events of all kinds.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.exchange
Used for any type of exchange: the stock exchange, the exchange of goods, or even the simple
exchange of information.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.expert
Used by those who have specialized knowledge in a variety of fields.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
66
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.exposed
Used as a generic extension for a variety of subjects, including photography, tabloids, and investigative
journalism.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.express
Used as a general extension, but ideal for those who want to emphasize the speedy delivery of good
or services.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
F
.fail, .farm, .finance, .financial, .fish, .fitness, .flights, .florist, .flowers, .football, .forsale, .foundation, .fund,
.furniture, .futbol, .fyi
.fail Used by anyone who has made mistakes, but ideal for publishing humorous "fail" blunders and
bloopers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
API Version 2013-04-01
67
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.farm
Used by those in the farming industry, such as farmers and agricultural engineers.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.finance
Used by the financial sector.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.financial
Used by the financial sector.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
API Version 2013-04-01
68
Amazon Route 53 Developer Guide
Generic Top-Level Domains
.fishUsed as a general extension, but ideal for websites related to fish and fishing.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.fitness
Used to promote fitness and fitness services.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.flights
Used by travel agents, airlines, and anyone affiliated with the travel industry.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.florist
Used by florists.
Registration and renewal period
One to ten years.
API Version 2013-04-01
69
Amazon Route 53 Developer Guide
Generic Top-Level Domains
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.flowers
Used for anything related to flowers, such as online flower sales or information about flower growing
and breeding.
Registration and renewal period
One to ten years.
Privacy protection
Not supported.
Internationalized domain names
Supported for Cyrillic (primarily Russian), French, German, Italian, Portuguese, and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.football
Used by anyone involved in the sport of football.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.forsale
Used for selling goods and services.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for Chinese, French, German, Latin, and Spanish.
API Version 2013-04-01
70
Amazon Route 53 Developer Guide
Generic Top-Level Domains
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.foundation
Used by non-profit organizations, charities, and other kinds of foundations.
Registration and renewal period
One to ten years.
Privacy protection (applies to all contact types: person, company, association, and public
body)
Hidden – address, phone number, fax number, and email address
Not hidden – contact name and organization name
Internationalized domain names
Supported for French and Spanish.
DNSSEC
Supported for domain registration. For more information, see Configuring DNSSEC for a
Domain (p. 35).
Registrar
The registrar for this TLD is our registrar associate, Gandi.
.fund
Used as a general extensio