Skip to main content
Resources

注册商委任：成为 ICANN 委任的注册商

成为 ICANN 委任的注册商的流程包括多个步骤。以下是这些步骤的摘要，旨在指导您完成此流程。

  1. 查看注册商委任政策说明中指明的资格标准。
  2. 查看对成为 ICANN 委任的注册商所规定的财务考虑因素
  3. 查看每个 ICANN 委任的注册商需遵守的管理协议和政策
  4. 申请注册商委任。要进行申请，您必须填写 ICANN 注册商委任申请表，然后将其发送给 ICANN，同时支付申请费 3,500 美元，该费用不可退还。为帮助我们尽快处理您的申请表，请确保您提交的回答非常具体、透彻，并提供所有必需的支持文档。处理申请表出现拖延情况的主要原因包括缺少支持文档，以及对申请表中问题的回答不完整或不明确。解决有关申请表问题的通信地址如下：accredit@icann.org
  5. ICANN 对您的申请表进行审核并进行所有必需的后续查询和搜索后，将通过电子邮件将其对您委任申请的决定通知给您。

如果您的委任申请获得批准，还必须完成以下附加步骤：

  1. 与 ICANN 签订注册商委任协议并支付委任费用。当前版本的协议是所有注册商与 ICANN 签订的标准文档。ICANN 委任目前的授权期限为 5 年。（ICANN 会制定与您的协议并发送给您，同时随附委任费用年固定部分的发票。）
  2. 与 ICANN 签订注册商数据托管协议，并在 ICANN 指定的托管代理 Iron Mountain 处进行注册（与 ICANN 和 Iron Mountain 的标准化协议），或者选择使用第三方提供商 (TPP) 的托管服务。如注册商委任协议 (RAA) 第 3.6 款所述，所有 ICANN 委任的注册商都必须寄存特定的通用顶级域名 (gTLD) 注册信息。ICANN 注册商委任流程的最后步骤是与 ICANN 签订注册商委任协议 (RAA) 和注册商数据托管 (RDE) 协议。
  3. 返回您签订好的注册商委任协议 (RAA) 和注册商数据托管 (RDE) 协议并支付委任费用后，ICANN 会将您的委任情况通知给相应的注册机构，并将您添加到以下地址的注册商列表中：http://www.icann.org/registrars/accredited-list.htmlhttp://www.internic.net/regist.html。您应与注册机构运营商一起解决合同、财务和技术上的细节问题。
  4. 为已注册名称持有人的注册协议做好准备。ICANN 注册商委任协议要求在此注册协议中包含某些特定条款。此外，ICANN 采用统一域名争议解决政策，所有委任的注册商都必须遵守该政策。您可能还希望实施隐私政策以符合您的委任协议的要求。
  5. 开创您的服务。完成上述步骤后，只要您通过了测试流程并可与授权的各个注册机构开展业务，即可开始向公众提供服务。
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."
https://www.icann.org/resources/pages/accreditation-2012-02-25-zh
www.icann.org
crawl=CC-MAIN-2018-43
103637
application/http; msgtype=response
sha1:BX5UVRH44TODZVN3VY6L4P2ETHZXYCGV
<urn:uuid:e75151a3-7672-4541-b400-7843fec3cbfb>
2018-10-23T00:13:11Z
192.0.32.7
text/html
sha1:PCC5SBK7L3HHATWJYNLXFPYIEHIYUVG2
<urn:uuid:70e9563c-2bec-4a0e-a979-96b296729157>
https://www.icann.org/resources/pages/accreditation-2012-02-25-zh
response
<urn:uuid:06604cb2-870f-4b8d-9f43-1f0c811c3e7d>
isPartOf: CC-MAIN-2018-43
publisher: Common Crawl
description: Wide crawl of the web for October 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-168-124-187.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/