31 July 2025

.亚马逊 New gTLD Application

31 July 2025

Click to view Chinese translation articles.

-----------------------------------

New gTLD Application Submitted to ICANN by: Amazon EU S.à r.l.

Application Downloaded On: 09 Aug 2019

String: 亚马逊

Application ID: 1-1318-5591

Applicant Information

Full legal name

Amazon EU S.à r.l.

Address of the principal place of business

38 Avenue John F. Kennedy - L-1855 Luxembourg

Phone number

+352 26733 300

Fax number

+352 26733 335

If applicable, website or URL

http://www.amazon.com/

Primary Contact

6(a). Name

Lorna Gradden

6(b). Title

Director & Co-Founder

6(c). Address

6(d). Phone Number

+442074218250

6(e). Fax Number

+448700118187

6(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

Secondary Contact

7(a). Name

Dana Northcott

7(b). Title

Vice President & Associate General Counsel, IP

7(c). Address

7(d). Phone Number

+1 2062667260

7(e). Fax Number

+1 2062667010

7(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

Proof of Legal Establishment

8(a). Legal form of the Applicant

Corporation (Société à responsabilité limitée)

8(b). State the specific national or other jurisdiction that defines the type of entity identified in 8(a).

Luxembourg

8(c). Attach evidence of the applicant's establishment.

Attachments are not displayed on this form.

9(a). If applying company is publicly traded, provide the exchange and symbol.

Amazon EU S.à.r.l. is not a publicly traded entity.

9(b). If the applying entity is a subsidiary, provide the parent company.

Amazon Europe Core S.à.r.l. (“AEC”) owns 100% of Amazon EU S.à.r.l. AEC is 100% owned by Amazon.com Int’l Sales, Inc., which is 100% owned by Amazon.com, Inc.

9(c). If the applying entity is a joint venture, list all joint venture partners.

Amazon EU S.à r.l. is not a joint venture.

Applicant Background

11(a). Name(s) and position(s) of all directors

Name

Position

Barbara Scarafia Manager

Eva Charlotte Gehlin Manager

Jorritt Adrian Van der Meulen Manager

Roy Luigi Perticucci Manager

Xavier René Barthélémy Garambois Manager

11(b). Name(s) and position(s) of all officers and partners

Name

Position

Barbara Scarafia Manager

Eva Charlotte Gehlin Manager

Jorritt Adrian Van der Meulen Manager

Roy Luigi Perticucci Manager

Xavier René Barthélémy Garambois Manager

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

Name

Position

Amazon Europe Core S.à.r.l. Not Applicable

11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility

Applied-for gTLD string

Provide the applied-for gTLD string. If an IDN, provide the U-label.

亚马逊

14A. If applying for an IDN, provide the A-label (beginning with "xn--").

xn--jlq480n2rg

14B. If an IDN, provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.

Amazon

14C1. If an IDN, provide the language of the label (in English).

Chinese

14C2. If an IDN, provide the language of the label (as referenced by ISO-639-1).

14D1. If an IDN, provide the script of the label (in English).

Han (Simplified variant)

14D2. If an IDN, provide the script of the label (as referenced by ISO 15924).

Hans

14E. If an IDN, list all code points contained in the U-label according to Unicode form.

U+4E9A U+9A6C U+900A

15A. If an IDN, upload IDN tables for the proposed registry. An IDN table must include:

the applied-for gTLD string relevant to the tables,

the script or language designator (as defined in BCP 47),

table version number,

effective date (DD Month YYYY), and

contact name, email address, and phone number.

Submission of IDN tables in a standards-based format is encouraged.

15B. Describe the process used for development of the IDN tables submitted, including consultations and sources used.

Wherever possible, well-established language tables that have been published in IANA Repository of IDN Practices are adopted. Published tables, especially from a ccTLD that primarily uses the given language or script, represent valuable research and deployment experience. In the interest of interoperability, we reuse these tables in our IDN implementation.

In some instances, multiple language tables for the same language may exist, with material differences in their content. In order to determine the best approach that fits our needs and specific target audience, we may conduct research and consult reference sources such as omniglot.com and evertype.com for clarity and understand the reason for the differences.

The Chinese IDN table is based on the .biz table found on in the IANA Repository. This table has been in use for nearly five years. When it was created in 2007, it was derived from the following sources:

IDN Character Table for CNNIC: http:⁄⁄www.iana.org⁄domains⁄idn-tables⁄tables⁄cn_zh-cn_4.0.html

IDN Character Table for TWNIC: http:⁄⁄www.iana.org⁄domains⁄idn-tables⁄tables⁄tw_zh-tw_4.0.1.html

When constructing the table, Neustar consulted with various experts including representatives at CNNIC and TWNIC.

15C. List any variants to the applied-for gTLD string according to the relevant IDN tables.

Variant 1

A-label: xn--jlq061n1kg

U-label: 亚马遜

Unicode: U+4E9A U+9A6C U+905C

Variant 2

A-label: xn--jlqz76b6y5b

U-label: 亚马愻

Unicode: U+4E9A U+9A6C U+613B

Variant 3

A-label: xn--jlq480nmbg

U-label: 亚馬逊

Unicode: U+4E9A U+99AC U+900A

Variant 4

A-label: xn--jlq061nl3f

U-label: 亚馬遜

Unicode: U+4E9A U+99AC U+905C

Variant 5

A-label: xn--jlqz76bqi5b

U-label: 亚馬愻

Unicode: U+4E9A U+99AC U+613B

Variant 6

A-label: xn--nlqw80n2rg

U-label: 亞马逊

Unicode: U+4E9E U+9A6C U+900A

Variant 7

A-label: xn--nlqs61n1kg

U-label: 亞马遜

Unicode: U+4E9E U+9A6C U+905C

Variant 8

A-label: xn--nlqr76b6y5b

U-label: 亞马愻

Unicode: U+4E9E U+9A6C U+613B

Variant 9

A-label: xn--nlqw80nmbg

U-label: 亞馬逊

Unicode: U+4E9E U+99AC U+900A

Variant 10

A-label: xn--nlqs61nl3f

U-label: 亞馬遜

Unicode: U+4E9E U+99AC U+905C

Variant 11

A-label: xn--nlqr76bqi5b

U-label: 亞馬愻

Unicode: U+4E9E U+99AC U+613B

Variant 12

A-label: xn--llq080n2rg

U-label: 亜马逊

Unicode: U+4E9C U+9A6C U+900A

Variant 13

A-label: xn--llqw61n1kg

U-label: 亜马遜

Unicode: U+4E9C U+9A6C U+905C

Variant 14

A-label: xn--llqv76b6y5b

U-label: 亜马愻

Unicode: U+4E9C U+9A6C U+613B

Variant 15

A-label: xn--llq080nmbg

U-label: 亜馬逊

Unicode: U+4E9C U+99AC U+900A

Variant 16

A-label: xn--llqw61nl3f

U-label: 亜馬遜

Unicode: U+4E9C U+99AC U+905C

Variant 17

A-label: xn--llqv76bqi5b

U-label: 亜馬愻

Unicode: U+4E9C U+99AC U+613B

Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.

Amazon EU S.à r.l. (AEU) foresees no known rendering issues in connection with the .亚马逊 TLD. This is based upon consultation with AEU’s backend provider, Neustar, which has successfully launched a number of new gTLDs over the last decade. In reaching this determination, the following data points were analyzed:

ICANN’s Security Stability Advisory Committee DSV009, Alternative TLD Name Systems and Roots: Conflict, Control & Consequences
IAB - RFC3696 Application Techniques for Checking & Transformation of Names
Known software issues which Neustar has encountered from launching new gTLDs
Character type and length
ICANN supplemental notes to Q16
ICANN presentation during its Costa Rica regional meeting on TLD Universal Acceptance;

The following sections discuss the potential operational or rendering problems that can arise, and how mitigated.

Compliance & Interoperability

The applied-for string conforms to all relevant RFCs, as well as the string requirements set forth in s2.2.1.3.2 Applicant Guidebook.

Mixing Scripts

A domain name label with characters from different scripts has a higher likelihood of encountering rendering issues. If the mixing of scripts occurs within the top-level label, any rendering issue would affect all domain names registered under it. If occurring within second level labels, its ill-effects are confined to the domain names with such labels.

All characters in the applied-for gTLD string are taken from a single script. The IDN policies are conservative and compliant with ICANN Guidelines for the Implementation of IDN V3.0. Specifically, mixed-script labels may not be registered at the 2nd level, except for languages with established orthographies and conventions that require the commingled use of multiple scripts, e.g. Japanese.

Interaction between Labels

Even with the above issue appropriately restricted, it is possible that a domain name composed of labels with different properties such as script and directionality may introduce unintended rendering behavior.

Only scripts and characters that would not pose a risk when combined with the top level label will be offered.

Immature Scripts

Scripts or characters added in Unicode versions newer than 3.2 (on which IDNA2003 was based) may encounter interoperability issues due to the lack of software support.

We have no current plans to offer registration of labels containing such scripts or characters.

Other Issues

We are not offering the registration of domains that includes combining characters or characters that require IDNA contextual rules handling.

The following may be construed as operational or rendering issues, but consider them out of the scope of this question. Nevertheless, we will take reasonable steps to protect registrants and Internet users by working with vendors and relevant language communities to mitigate such issues.

missing fonts causing string to fail to render correctly
universal acceptance of the TLD

OPTIONAL.

Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

N⁄A

18A. Describe the mission/purpose of your proposed gTLD.

Founded in 1994, Amazon opened on the World Wide Web in July 1995 and today offers Earth’s Biggest Selection. Amazon seeks to be Earth’s most customer-centric company, where customers can find and discover anything they might want to buy online, and endeavors to offer its customers the lowest possible prices. Amazon and other sellers offer millions of unique new, refurbished and used items in categories such as Books; Movies, Music & Games; Digital Downloads; Electronics & Computers; Home & Garden; Toys, Kids & Baby; Grocery; Apparel, Shoes & Jewelry; Health & Beauty; Sports & Outdoors; and Tools, Auto & Industrial. Amazon Web Services provides Amazon’s developer customers with access to in-the-cloud infrastructure services based on Amazon’s own back-end technology platform, which developers can use to enable virtually any type of business. The new latest generation Kindle is the lightest, most compact Kindle ever and features the same 6-inch, most advanced electronic ink display that reads like real paper even in bright sunlight. Kindle Touch is a new addition to the Kindle family with an easy-to-use touch screen that makes it easier than ever to turn pages, search, shop, and take notes – still with all the benefits of the most advanced electronic ink display. Kindle Touch 3G is the top of the line e-reader and offers the same new design and features of Kindle Touch, with the unparalleled added convenience of free 3G. Kindle Fire is the Kindle for movies, TV shows, music, books, magazines, apps, games and web browsing with all the content, free storage in the Amazon Cloud, Whispersync, Amazon Silk (Amazon’s new revolutionary cloud-accelerated web browser), vibrant color touch screen, and powerful dual-core processor.

18a

The mission of the .亚马逊 registry is:

To provide a unique and dedicated platform for Amazon while simultaneously protecting the integrity of its brand and reputation.

A .亚马逊 registry will:

Provide Amazon with additional controls over its technical architecture, offering a stable and secure foundation for online communication and interaction.
Provide Amazon a further platform for innovation.
Enable Amazon to protect its intellectual property rights.

18B. How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

The .亚马逊 registry will benefit registrants and internet users by offering a stable and secure foundation for online communication and interaction.

What is the goal of your proposed gTLD in terms of areas of specialty, service levels or reputation?

Amazon intends for its new .亚马逊 gTLD to provide a unique and dedicated platform for stable and secure online communication and interaction. The .亚马逊 registry will be run in line with current industry standards of good registry practice.

What do you anticipate your proposed gTLD will add to the current space in terms of competition, differentiation or innovation?

Amazon values the opportunity to be one of the first companies to own a gTLD. A .亚马逊 registry will:

Provide Amazon with additional controls over its technical architecture, offering a stable and secure foundation for online communication and interaction.
Provide Amazon a further platform for innovation.
Enable Amazon to protect its intellectual property rights.

What goals does your proposed gTLD have in terms of user experience?

Amazon intends for its new .亚马逊 gTLD to provide a unique and dedicated platform for stable and secure online communication and interaction.

Provide a complete description of the applicant’s intended registration policies in support of the goals above

Amazon’s Intellectual Property group will be responsible for the development, maintenance and enforcement of a Domain Management Policy. The Domain Management Policy will define (i) the rules associated with eligibility and domain name allocation, (ii) the license terms governing the use of a .亚马逊 domain name, and (iii) the dispute resolution policies for the .亚马逊 gTLD. Amazon will continually update the Domain Management Policy as needed to reflect Amazon’s business goals and, where appropriate, ICANN consensus policies.

Registration of a domain name in the .亚马逊 registry will be undertaken in four steps: (i) Eligibility Confirmation, (ii) Naming Convention Check, (iii) Acceptable Use Review, and (iv) Registration. All domains in the .亚马逊 registry will remain the property of Amazon.

For example, on the rules of eligibility, each applied for character string must conform to the .亚马逊 rules of eligibility. Each .亚马逊 name must:

be at least 3 characters and no more than 63 characters long
not contain a hyphen on the 3rd and 4th position (tagged domains)
contain only letters (a-z), numbers (0-9) and hyphens or a combination of these
start and end with an alphanumeric character, not a hyphen
not match any character strings reserved by ICANN
not match any protected country names or geographical terms

Additionally:

Internationalized domain names (IDN) may be supported in the .亚马逊 registry at the second level.
The .亚马逊 registry will respect third party intellectual property rights.
.亚马逊 domains may not be delegated or assigned to third party organizations, institutions, or individuals.
All .亚马逊 domains will carry accurate and up-to-date registration records.

Amazon’s Intellectual Property group reserves the right to revoke a license to use a .亚马逊 domain name, at any time, if any use of a .亚马逊 domain name violates the Domain Management Policy.

Will your proposed gTLD impose any measures for protecting the privacy of confidential information of registrants or users?

Yes. Amazon will implement appropriate privacy policies respecting requirements of local jurisdictions. For example, Amazon is a participant in the Safe Harbor program developed by the U.S. Department of Commerce and the European Union.

Describe whether and in what ways outreach and communications will help to achieve your projected benefits?

There is no foreseeable reason for Amazon to undertake public outreach or mass communication about its new gTLD registry because domains will be provisioned in line with Amazon’s business goals.

18C. What operating rules will you adopt to eliminate or minimize social costs (e.g., time or financial resource costs, as well as various types of consumer vulnerabilities)? What other steps will you take to minimize negative consequences/costs imposed upon consumers?

Amazon intends to initially provision a relatively small number of domains in the .亚马逊 registry to support the business goals of Amazon. These initiatives should not impose social costs of any type on consumers.

How will multiple applications for a particular domain be resolved, for example, by auction or on a first come first served basis?

Applications from Amazon and its subsidiaries for domains in the .亚马逊 registry will be considered by Amazon’s Intellectual Property group and allocated in line with Amazon’s business goals. The .亚马逊 registry will not be promoted by hundreds of registrars simultaneously, so there will not be multiple-applications for a particular domain.

Explain any cost benefits for registrants you intend to implement (e.g. advantageous pricing, introductory discounts, bulk registration discounts).

Domains in the .亚马逊 registry will be provisioned to support the business goals of Amazon. Accordingly, “cost benefits” may be explored depending on the business goals of Amazon. Amazon shares the goals of enhancing customer trust and choice.

The Registry Agreement requires that registrars be offered the option to obtain initial domain name registrations for periods of one to ten years at the discretion of the registrar, but no greater than 10 years. Additionally the Registry Agreement requires advance written notice of price increases. Do you intend to make contractual commitments to registrants regarding the magnitude of price escalation?

The Domain Management Policy will include the costs and benefits of Amazon’s unique and dedicated platform for stable and secure online communication and interaction.