Registrant Rights and Responsibilities Under the 2009 Registrar Accreditation Agreement（2009 年注册商委任协议规定之注册人权利与责任）
27 June 2011
Registrant Rights and Responsibilities Under the 2009 Registrar Accreditation Agreement
Background: One of the new provisions added to the 2009 RAA requires ICANN to develop in consultation with registrars a webpage that identifies available registrant rights and responsibilities. This published document is the result of initial input from a joint working group of the GNSO Council and the At-Large Advisory Committee and subsequent consultations with the registrars; and provides a "plain language" summary of registrant rights and responsibilities that currently exist under the 2009 RAA.
This document provides some "plain language" summarization of terms related to Registrant Rights and Responsibilities as set out in the Registrar Accreditation Agreement (RAA), for posting on Registrar websites. While some of the terms included here do not specifically refer to registrants, those terms are included because of the potential import to understanding registrar/registrant relations. This document also summarizes registrant rights and responsibilities that arise within ICANN Consensus Policies and specifications, as those policies and specifications are incorporated into the RAA.'
The summarization of terms within this document do not override or replace the terms set forth in the RAA or within those specifications or policy.
In order to register a domain name, a Registered Name Holder (also known as a Registrant) has to use the services of an ICANN-accredited Registrar. In order to become an ICANN-accredited Registrar, the Registrar must enter into a contract with ICANN, referred to as the Registrar Accreditation Agreement or the RAA. The RAA sets out various rights and responsibilities for Registrants, and Registrants have additional rights and responsibilities that are set forth in separate ICANN policies and specifications that the Registrars agree to follow.
The RAA and the related policies are drafted in very specific, often legal terminology. In order to help Registrants better understand the rights and responsibilities that come along with the registration of a domain name, these rights and responsibilities are being summarized and presented within a single document. The summaries provided here do not override or replace the actual terms as written in the RAA or the related policies and specifications.
RAA Terms of Interest
As the RAA is between ICANN and a Registrar, no one else – including a Registered Name Holder – may sue ICANN or the Registrar to claim a breach of the RAA.
Registrars may not make claims that they can provide registrants with superior access to any relevant TLD in comparison to other Registrars.
Some of the Registrar obligations are dependent upon Registered Name Holders fulfilling certain responsibilities, particularly as it relates to payment of registration fees, submission of required data points to the Registrars, and submission of accurate data and timely updates to that required data. Registrars also have specific items on which they must provide notice to Registered Name Holders, including notifications of the end of a registration term, use of Registered Name Holder’s Personal Data, and notices regarding escrowing of data for domain names registered through privacy or proxy registration services, as well as the posting of fees for the recovery of registered names.
Registrar Submission of Data to Registry Operators
For each relevant TLD, Registrars must submit certain data points relating to each Registered Name within a TLD:
The name of the Registered Name being registered (126.96.36.199);
The IP addresses of the primary nameserver and secondary nameserver(s) for the Registered Name (188.8.131.52);
The corresponding names of those nameservers (184.108.40.206);
Unless automatically generated by the registry system, the identity of the Registrar (220.127.116.11);
Unless automatically generated by the registry system, the expiration date of the registration (18.104.22.168); and
Any other data the Registry Operator requires be submitted to it (22.214.171.124).
Registered Name Holders are normally required to provide the Registrar with information relating to nameservers (126.96.36.199 – 3), and there may be additional data required under Section 188.8.131.52 that the Registered Name Holder must provide. If the Registered Name Holder provides an update on these data points, the Registrar has five (5) days to provide the update to the Registry Operator.
Registrars are required to have an interactive web page and port 43 Whois service that is available to the public to query free of charge. The RAA specifies certain data points that must be provided in response to a query:
The Registered Name (184.108.40.206);
The names of the primary nameserver and secondary nameserver(s) for the Registered Name (220.127.116.11);
The identity of Registrar (which may be provided through Registrar's website) (18.104.22.168);
The original creation date of the registration (22.214.171.124);
The expiration date of the registration (126.96.36.199);
The name and postal address of the Registered Name Holder (188.8.131.52)
The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name (184.108.40.206); and
The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name (220.127.116.11).
These data points are commonly referred to as Whois data. As discussed below, Registered Name Holders are required to provide a Registrar with timely updates to Whois data for a Registered Name. Upon receiving the update, a Registrar is to "promptly" update the Whois data. Registrars may contract out the maintenance of the public query function.
The RAA allows Registrars to provide bulk access to Whois data to third parties. When providing bulk access or access to the Whois data through the public query function, the Registrar is required to restrict access for high volume queries or other restrictions on uses of Whois data as specified in the RAA, including marketing activities and mass solicitations. If a Registrar contracts the public function query to an outside party, the Registrar must require any contractor providing the port 43 service to impose the same restrictions on access to and use of the Whois data.
Communications with Registered Name Holders
Registrars are required to maintain records of all communications with Registered Name Holders, as well as records of information provided to Registry Operators.
Escrow of Registered Name Holder Data
A Registrar is required to maintain a database of all Whois data for all Registered Names registered through the Registrar’s accreditation, as well as all data the Registrar submits to the Registry Operator. In addition, the Registrar must include in the database the name and (where available) postal address, e-mail address, voice telephone number, and fax number of the billing contact for each Registered Name.
In some instances, a registrant may choose to limit the amount of personal information that a Registrar makes available in a Whois query. To do so, the name may be registered through a privacy service (allowing a registrant to conceal personal identifying information and often replacing it with the information of the privacy service). Customers may also choose to register names through a proxy service, where the proxy service is the Registered Name Holder, and the proxy service licenses the use of the domain name to the customer. In that situation, the proxy service, as the Registered Name Holder, has its information listed for most or all required data points.
When a Registered Name is registered through a privacy or proxy registration service, that affects the information that is placed in the database, and a Registrar must do one of two things: The Registrar must either (1) include in the database the name and postal address, e-mail address, and voice telephone number provided by the customer in connection with each registration, even when a privacy or proxy registration is used; or (2) at the time that a customer elects to use a privacy or proxy registration service, display a notice that the customer’s data is not being escrowed. When a customer’s data is not being escrowed, only the contact information associated with the privacy or proxy registration service will be escrowed. If a customer’s data is not escrowed, and only the information of the proxy or privacy service is maintained in the database, in the event of Registrar or Registry failure future notices may only be sent to the contact information within the database.
Registrar Business Dealings with Registrants
The RAA imposes many requirements on a Registrar’s business dealings, including its dealings with Registered Name Holders.
A registrar may not activate a Registered Name until it receives reasonable assurance from the Registered Name Holder that the registration fee will be paid.
The RAA sets forth actions the Registrar may take at the conclusion of the registration period if a Registered Name Holder has not provided consent to renew the registration, including the Registrar cancelling the registration at the end of the current registration term. If the Registered Name Holder did not consent to renewal, the Registrar must make sure that a Registered Name is deleted from the Registry database within 45 days of the end of the registration term.
This right for the Registrar to cancel the registration and the obligation to the delete the domain name is not absolute. Section 18.104.22.168 of the RAA sets forth a list of potential "extenuating circumstances," that, if exist, allows the Registrar to renew the domain name even without the consent of the Registered Name Holder. These circumstances include the Registered Name being subject to a UDRP action, court order, bankruptcy proceeding, or billing dispute, among other items. The Registrar must keep a record of reasons why the Registrar renewed a registration without the consent of a Registered Name Holder.
Registrars have to provide each new registrant with notice of the Registrar’s deletion and auto-renewal policies. If the Registrar’s deletion policy changes during the time of the registration agreement, the Registrar has to make efforts to inform the registrants of those policy changes. Details of the deletion and auto-renewal policies have to be displayed on any website the Registrar operates for domain name registration and renewal, and the Registrar should also state on those sites any fee that will be charged for the recovery of a domain name during the Redemption Grace Period (the 30 day period of time during which the name is in "Pending Delete" status with the Registry).1
If a Registered Name is the subject of a UDRP dispute at the time of deletion or expiration of the registration, the UDRP complainant has the right to renew (or restore, in the case of a deletion) the domain name. If the complainant renews or restores the name, the Registrar must place the name in a HOLD or LOCK status,2 and must modify the Whois information to show that the name is subject to dispute. Section 22.214.171.124 of RAA also provides for a right for the original domain name registrant to recover or renew the name in the event the UDRP complaint is terminated without decision, or the UDRP complaint is decided in favor of the original domain name registrant.
The Registrar/Registered Name Holder Agreement
Registrars are required to enter into electronic or paper registration agreements with all Registered Name Holders. According to the RAA, the Registrar/Registered Name Holder Agreement must include – at minimum – the following items (as stated at Sections 126.96.36.199 – 12 of the RAA):
The Registered Name Holder must provide "accurate and reliable contact details" and must "promptly correct and update them" during the registration term. The details required are stated in Section 188.8.131.52.: "the full name, postal address, e-mail address, voice telephone number, and fax number if available of the Registered Name Holder; name of authorized person for contact purposes in the case of an Registered Name Holder that is an organization, association, or corporation; and the data elements listed in Subsections 184.108.40.206, 220.127.116.11 and 18.104.22.168."
If a Registered Name Holder intentionally provides inaccurate or unreliable information, intentionally fails to promptly update the information, or fails to respond over fifteen (15) days to Registrar inquiries about the accuracy of the contact details, the Registered Name Holder will be in material breach of the agreement and the registration may be cancelled.
Whoever is listed as the Registered Name Holder must provide full contact information, and is the Registered Name Holder of record. Sometimes a Registered Name Holder may register a domain name and then allow another person to use the domain name (such as a website designer registering a domain name for a client). If this happens, and the person actually using the name did not enter into the Registrar/Registered Name Holder Agreement (referred to as a "third party" in the RAA), the Registered Name Holder could be accountable for wrongful use of the domain name by the third party. This will happen if the Registered Name Holder is provided with "reasonable evidence of actionable harm" from the third party’s use of the domain name. In that situation the Registered Name Holder will "accept liability for harm caused by wrongful use of the Registered Name," unless the Registered Name Holder discloses the user’s identity and current contact information.
The Registrar must provide notice of how it intends to use data provided by the Registered Name Holder and who will received the Registered Name Holder’s data. The Registrar must also provide notice of how Registered Name Holders may access and update data. Additionally, the Registrar must identify which data points the Registered Name Holder must provide to the Registrar, and what information can be provided on a voluntary basis. The Registered Name Holder must consent to all of these data processing terms.
If a Registered Name Holder provides the Registrar with Personal Data on behalf of any person who did not enter into the Registrar/Registered Name Holder Agreement (the "third party" discussed above), the Registered Name Holder must confirm that it (1) provided those third-party individuals with the same data processing notices that the Registrar provides, and (2) received the same consents from the third party regarding the Registrar’s data processing terms.
A Registrar may only process the Registered Name Holder’s data as stated in the data processing notices described above.
A Registrar has to agree that it will take reasonable precautions to protect the Registered Name Holder’s data from "loss, misuse, unauthorized access or disclosure, alteration, or destruction."
Registered Name Holders must represent that: "to the best of the Registered Name Holder's knowledge and belief, neither the registration of the Registered Name nor the manner in which it is directly or indirectly used infringes the legal rights of any third party." This means that the Registered Name Holder must represent to the Registrar that the domain name is not being registered for use in a way that would violate the legal rights of others. An example of this "infringement" could be a registration of a domain name that violates a trademark or copyright held by someone that is not the Registered Name Holder.3
If there is a dispute in connection with the use of the registered name, the Registered Name Holder must agree to jurisdiction of the courts in at least one of two places: where the Registrar is located (often stated on the website or in the Registrar/Registered Name Holder Agreement) or the "Registered Name Holder's domicile." "Domicile" is a word with legally-specific meaning, but typically will be the location the Registered Name Holder provides to the Registrar in the required Personal Data. Agreeing to jurisdiction means that the Registered Name Holder agrees that the courts in those locations have the power to decide these types of cases.4
The Registered Name Holder must agree that its registration is subject to "suspension, cancellation, or transfer" for the reasons stated in Section 22.214.171.124. Those reasons include: if an ICANN adopted specification or policy requires it or if a registrar or registry procedure requires it "to correct mistakes by Registrar or the Registry Operator in registering the name or for the resolution of disputes concerning the Registered Name." For example, the UDRP is an ICANN adopted policy that specifies that an administrative panel hearing a domain name dispute could order that a domain name registration be suspended, transferred or cancelled, and the Registered Name Holder has to agree that this is a possibility.
The Registered Name Holder shall "indemnify and hold harmless the Registry Operator and its directors, officers, employees, and agents from and against any and all claims, damages, liabilities, costs, and expenses (including reasonable legal fees and expenses) arising out of or related to the Registered Name Holder's domain name registration." At its simplest, this means that if the Registry Operator (or its employees, etc.) for the registered name is sued because of the Registered Name Holder’s domain name registration, the Registered Name Holder will pay the Registry Operator for all fees and expenses in defending against the suit as well as pay for any judgments or liabilities awarded. This "indemnification" is not solely limited to court cases.
Verification of contact information
As described in more detail below, there are specifications and policies that may be created and that apply to the Registrars. Some of the specifications or policies may address a Registrar's obligation to verify the contact information supplied by the Registered Name Holder when the domain is first registered, as well as setting out requirements for periodic re-verification of contact information.
Registrars are also required to take "reasonable steps" to verify contact information in the event any person notifies the Registrar that contact information for a Registered Name is inaccurate. The Registrar also has obligations to act to correct inaccuracies in contact information that the Registrar becomes aware of, even if the inaccuracy was not reported by anyone.
The Registrar must also maintain proper contact information for itself, including a valid email and mailing address. This contact information should be posted on the Registrar’s website.
The RAA imposes obligations on Registrars working with third-party Resellers – persons or entities that the Registrar contracts with to provide Registrar Services. The RAA now requires Registrars to include specific items in the Registrar/Reseller Agreements, including: prohibiting the Reseller from making representations that it is accredited by ICANN; requiring that all Reseller registration agreements include all provisions that the Registrar is required to include in its Registrar/Registered Name Holder Agreement; requiring the posting of all links to all ICANN websites that the Registrar is obligated to post; and identification of the sponsoring registrar. The Reseller is also required to make sure that that if a customer is using a Reseller’s privacy or proxy registration service for a domain name registration, the Reseller does one of the following three things: (1) deposit the identity and contact information of the customer with the Registrar; (2) deposit the identity and contact information in escrow; or (3) posts a notice to the customer that their contact information is not being escrowed.
The RAA also requires the Registrar to take compliance and enforcement action against a Reseller violating any of the required provisions.
The Restored Names Accuracy Policy (http://www.icann.org/en/registrars/rnap.htm) requires that when a registrar restores a name (from the redemption grace period) that had been deleted on the basis of submission of false contact data or non-response to registrar inquiries, the name must be placed on Registrar Hold status until the registrant has provided updated and accurate Whois information.
In addition to the RAA requirement that a Registered Name Holder represent that to the best of its knowledge, the registration or use of the domain name does not infringe on the legal rights of others, the Uniform Domain Name Dispute Resolution Policy ("UDRP") requires that same representation to be made, as well as a representation that the domain name is not being registered for an unlawful purpose, and will not be used in violation of any applicable laws.
The UDRP also requires Registered Name Holders to submit to mandatory administrative proceedings to resolve disputes under the UDRP. These mandatory administrative proceedings, as described in the UDRP, are disputes that are filed before one of the ICANN approved UDRP dispute resolution providers (listed at http://www.icann.org/en/dndr/udrp/approved-providers.htm) and following the uniform Rules for UDRP administrative proceedings (set out at http://www.icann.org/en/dndr/udrp/uniform-rules.htm). The requirement for submission to mandatory administrative proceedings does not mean that Registered Name Holders cannot also have judicial proceedings filed against them for the same or similar conduct. Similar to the jurisdictional requirements set out in the RAA, the requirement to submit to a mandatory administrative proceeding means that the Registered Name Holder cannot dispute the UDRP provider’s ability to hear a dispute that is otherwise properly brought under the UDRP.
The Policy on Transfers of Registrations between Registrars provides that Registered Name Holders have the right to transfer domain name registrations among registrars. The transfer policy imposes time limits on when the Registrar must respond to a transfer request. The right to transfer is not absolute – there are ICANN and Registry policies that may set limits on the transfer right, including: limitations on when a domain name may be transferred (measured from dates of creation or earlier transfer); and the Registered Name Holder providing of required authorization and documentation for Registrar review. The Registrar of Record may only deny a transfer in the following instances:
Evidence of fraud
Court order by a court of competent jurisdiction
Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact
No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.
Express written objection to the transfer from the Transfer Contact. (e.g. - email, fax, paper document or other processes by which the Transfer Contact has expressly and voluntarily objected through opt-in means)
A domain name was already in "lock status" provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status.
The transfer was requested within 60 days of the creation date as shown in the registry Whois record for the domain name.
A domain name is within 60 days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs).
1 A graphic representation of the life cycle of a typical gTLD Registered Name is located at http://www.icann.org/en/registrars/gtld-lifecycle.htm. This diagram may be useful to refer to for more information on the post-expiration status of domain names.
2 There are formal technical names for domain name statuses, arising out of the community-based Internet draft Request for Comments. The statuses required here are set by the Registrar. When a registration is in one of these statuses, the domain cannot be deleted and the registration cannot be modified. The Registrar must alter the status in order for any modification to occur.
3 There are many other potential ways to "infringe the legal rights" of others, and potential Registered Name Holders are encouraged to seek independent advice if they are concerned that the registration or use of a domain name may violate someone else’s rights.
4 There could be other jurisdictions that are able to decide a dispute about the use of a registered name, but those additional jurisdictions are not specified in the RAA.
2011 年 6 月 27 日
背景：2009 年认证注册商协议 (RAA) 新增的一条规定是要求 ICANN 与注册商协商后开发一个网页，在上面标识出注册人享有的权利和责任。这份文件是在 GNSO 理事会和一般会员咨询委员会联合工作小组的初步建议下，与注册商商议之后发布的。该文件还以"简明语言"列举了注册人根据现行的 2009 年认证注册商协议 (RAA) 所享有的权利和责任。
本文为 注 册商委任协议 (RAA) 中关于注册人权利与责任的条款摘要，采用"平白语言"书写，用于在注册商网站上发布。虽然本文所含部分条款并非特别针对注册人，但由于其有利于理解注册商和注册人之间的关系，因此也予以纳入。由于注册商委任协议 (RAA) 中包含了 互联网名称与数字地址分配机构 (ICANN) 合意政策与规范，因此本文亦对该合意政策与规范中关于注册人权利与责任的规定进行了总结。
本文中的条款摘要并不能取代注册商委任协议 (RAA) 及上述政策与规范中规定的条款。
已注册名称持有人（也称为"注册人"）必须使用互联网名称与数字地址分配机构 (ICANN) 认可的注册商所提供的服务注册域名。注册商必须与互联网名称与数字地址分配机构 (ICANN) 签署注册商委任协议 (RAA) 方可成为互联网名称与数字地址分配机构 (ICANN) 认可的注册商。注册商委任协议 (RAA) 规定了注册人的各种权利与责任，互联网名称与数字地址分配机构 (ICANN) 各单项政策和规范也规定了注册人的其他权利与责任，注册人亦同意遵守。
注册商委任协议 (RAA) 及相关政策采用非常具体、常用的法律术语起草。为便于注册人更好地理解其与域名注册相关的权利与责任，本文对这些权利与责任进行了总结。本文所述摘要并不能取代注册商委任协议 (RAA) 中的实际书面条款或相关政策及规范。
注册商委任协议 (RAA) 利益条款
由于注册商委任协议 (RAA) 由互联网名称与数字地址分配机构 (ICANN) 和注册商双方签署，因此其他任何人（包括已注册名称持有人）均不得以违反注册商委任协议 (RAA) 为由向上述任何一方提起诉讼。
注册商不得声称其可向注册人提供比其他注册商更优先的任何相关顶级域名 (TLD) 访问权。
对于各相关顶级域名 (TLD)，注册商均必须在顶级域名 (TLD) 内提交与已注册名称的相关 特定 数据 点：
已注册名称的主名称服务器和辅名称服务器的 IP 地址 (126.96.36.199)；
已注册名称持有人通常必须向注册商提供名称服务器的相关信息 (188.8.131.52 – 3)，另有第 184.108.40.206 小节可能规定已注册名称持有人必须提供部分其他数据。如果已注册名称持有人提供了这些数据点的更新数据，则注册商需在五 (5) 天内将这些更新数据提交给注册运营商。
注册商需要提供一个交互式网页和端口 43 Whois 服务，以便公众免费查询。注册商委任协议 (RAA) 指定了必须提供以响应查询的特定数据点：
这些数据点通常称为 Whois 数据。如下所述，已注册名称持有人需要向注册商提供及时更新的已注册名称 Whois 数据。收到更新数据后，注册商需"立即"更新 Whois 数据。注册商可将公共查询功能的维护工作外包。
注册商委任协议 (RAA) 允许注册商向第三方提供 Whois 数据的批量访问权限。通过公共查询功能提供 Whois 数据的批量访问或访问权限时，注册商需对大量查询或注册商委任协议 (RAA) 中所限制使用的 Whois 数据（包括市场营销活动和大量推销活动） 进行限制访问。如果注册商将公共查询功能外包给外部机构，注册商必须要求所有承包商提供端口 43 服务，对访问和使用 Whois 数据实施同等限制。
注册商必须为通过注册商委任注册之所有已注册名称的全部 Whois 数据、以及注册商提交 给注册运营商的所有数据 建立一个数据库，并在该数据库内记录各个已注册名称的付费联系人的姓名和邮政地址 （如果有）、电子邮件地址、语音电话号码和传真号码。
在某些情况下，注册人可限制注册商在 Whois 查询中提供的个人信息数量。要实现此目的，注册人可通过隐私服务（允许注册人隐藏个人识别信息并经常用隐私服务信息替换的服务） 注册名称。客户还可通过代理服务注册名称，其中代理服务商为已注册名称持有人，且代理服务商准许客户使用其域名，在这种情况下，大部分或所有必要数据点列出的信息均为代理服务商（即已注册名称持有人）的信息。
当已注册名称通过隐私或代理注册服务注册后，会对数据库内的信息造成影响，因此注册商 必须执行以下任一一项操作：注册商必须 (1) 在数据库内记录注册客户提供的姓名和邮政 地址、电子邮件地址和语音电话号码（即便已使用隐私或代理注册服务也不例外）；或 (2) 在客户选择使用隐私或代理注册服务时，告知客户其数据未被托管。如果客户的数据未被托管，则仅托管与隐私或代理注册服务相关的联系信息。如果客户数据未被托管，且数据库中仅留有代理或隐私服务信息，一旦注册商或注册机构出现故障，则此后的通知将仅发送给数据库内记录的联系对象。
注册商委任协议 (RAA) 对注册商的业务（包括其 与已注册名称持有人之间的业务）作出了许多规定。
如果已注册名称持有人未声明同意续签注册（包括注册商在当前注册期满后取消注册）， 则注册商委任协议 (RAA) 规定了注册商可在 注册期满后采取的措施。如果已注册名称持有人不同意续签，注册商必须确保在注册期满后 45 天内将已注册名称从注册数据库内删除。
注册商取消注册的权利和删除域名的义务并非绝对。注册商委任协议 (RAA) 第 220.127.116.11 小节 列出了可能的"可以减轻处罚的情况"列表，即如果情况属实，则允许注册商在已注册名称持有人未同意的情况下续签域名。这些情况包括已注册名称处于 UDRP 诉讼、法院指令、破产程序或计费争议等的情况。表明注册商在已注册名称持有人未同意的情况下续签注册的，必须保留原因记录。
注册商必须向每一位新注册人提供 注册商删除和自动续签政策通知。如果注册商的删除政策在注册协议期内有所变更，则注册商必须尽量通知注册人。删除和自动续签政策的详细信息 必须公布于注册商运营域名注册和续签的所有网站，注册商还应于域名赎回宽限期（域名在注册机构内处于"删除未决"状态的 30 天）内在 对恢复域名收取任何费用的网站上予以公布 。1
如果已注册名称在删除时或注册到期时存在 UDRP 争议，则 UDRP 原告有权续签（如果是删除则为恢复）域名。如果原告续签或恢复了名称，注册商必须将该名称置于"保留"或"锁定"状态2 ，并修改 Whois 信息以显示该名称存在争议。注册商委任协议 (RAA) 第 18.104.22.168 小节还规定了一项权利，即一旦 UDRP 争议未经裁决被终止，或其裁决有利于原域名注册人，则原域名注册人有权恢复或续签该名称。
注册商必须与所有已注册名称持有人 签署一份电子或书面注册协议。根据注册商委任协议 (RAA) 的规定，《注册商/已注册名称持有人协议》必须（至少）包括以下条款（见注册商委任协议 (RAA) 第 22.214.171.124 – 12 小 节）：
已注册名称持有人必须提供"准确而可靠的详细联系信息"，并在注册期间及时更正和更新这些信息。所需的详细信息见第 126.96.36.199. 小节所述：已注册名称持有人的全名称、邮政地址、电子邮件地址和语音电话号码（可能还要包括传真号码）；若已注册名称持有人为组织、协会或公司，则应提供负责联系事宜的授权人员的姓名；以及第 188.8.131.52、184.108.40.206 和 220.127.116.11 小节中列出的数据元素。
如果已注册名称持有人有意提供不准确或不可靠的信息、有意不及时更新信息、或者未能在注册商就详细联系信息的准确性发出询问后十五 (15) 天内作出回应，则视为已注册名称持有人重大违约，可导致注册被取消。
凡被列为已注册名称持有人者均须提供完整的联系信息，并且为登记之已注册名称持有人。有时已注册名称持有人可能会注册域名后许可他人使用该域名（如网站设计师为客户注册域名），在这种情况下，如果实际使用域名的人员（在注册商委任协议 (RAA) 中称为"第三方"）尚未签署《注册商/已注册名称持有人协议》，则已注册名称持有人要对第三方不当使用域名的行为负责，即如果存在因第三方使用域名所产生的"可诉诸法律之损害的合理证据"，则已注册名称持有人就应承担责任。在这种情形下，除非已注册名称持有人披露用户的身份和当前联系信息，否则就要"对因不当使用已注册名称所引起的损害负责"。
如果已注册名称持有人代表任何并未签署《注册商/已注册名称持有人协议》 的人员（上文提述的"第三方"）向注册商提供个人数据，则已注册名称持有人必须确认其：(1) 已向相关第三方提供注册商所发出的同一份数据处理通知，以及 (2) 已收到第三方就注册商数据处理条款所作出的同等同意书。
已注册名称持有人必须同意，在第 18.104.22.168 小节所述的情形下，其注册可能会被"暂停、取消或转让"。这些情形包括：互联网名称与数字地址分配机构 (ICANN) 采纳的规范或政策要求，或者注册商或注册机构施行的程序要求已注册名称持有人"更正注册商或注册运营商在注册名称或解决已注册名称相关争议时犯下的错误"。例如，互联网名称与数字地址分配机构 (ICANN) 采纳的 统一域名争议解决政策 (UDRP)，该政策规定，参加域名争议听证会的行政专家组有权命令暂停、转让或取消域名注册，而已注册名称持有人必须同意这种可能发生的情况。
如果有任何人员向注册商提出已注册名称持有人的联系信息不准确，注册商还必须采取 "合理的措施" 验证联系信息。此外，即使无人报告联系信息有误，如果注册商知道联系信息不准确，也应予以更正。
注册商委任协议 (RAA) 规定了注册商与第三方分销商合作的义务，第三方分销商可以是与注册商合作提供注册商服务的个人或实体。注册商委任协议 (RAA) 要求注册商将特殊条款纳入《注册商/分销商协议》中，这些条款包括：分销商不得声称其获得了互联网名称与数字地址分配机构 (ICANN) 的委任、分销商应将要求纳入《注册商/已注册名称持有人协议》中的所有条款纳入所有的分销商注册协议、分销商必须发布注册商必须提供之互联网名称与数字地址分配机构 (ICANN) 的全部网站链接、分销商必须确定赞助注册商身份等条款。分销商还必须确保，如果客户正使用分销商的域名注册隐私服务或代理注册服务，则其必须采取以下任何一种措施：(1) 与注册商一同寄存客户的身份和联系信息；(2) 以托管方式寄存身份和联系信息；或 (3) 向客户发出其联系信息尚未托管的通知。
注册商委任协议 (RAA) 还要求注册商针对分销商违反任何相关条款的行为采取合规措施和强制措施。
按照 姓名重建准确原则 (http://www.icann.org/zh/registrars/rnap-zh.htm) 的规定，凡注册商（在域名赎回宽限期内）就因提供不实联系数据或无法成功响应注册商问询而被删除的域名进行续费的，则该域名必须置于注册商保留状态，直至注册人提供最新准确的 Whois 信息。
除注册商委任协议 (RAA) 要求已注册名称持有人作出尽其所知，域名的注册或使用均不会 侵犯他人合法权利的声明外，统一域名争议解决政策（"UDRP"）也要求作出相同声明，而且须额外声明，域名的注册并非出于非法目的，且其使用不会违反任何适用法律。
统一域名争议解决政策 (UDRP) 还要求已注册名称持有人遵循强制性行政处理程序，并按 照该政策的规定解决争议。这些强制性行政管理程序（见统一域名争议解决政策 (UDRP) 中所述）是由一位经互联网名称与数字地址分配机构 (ICANN) 批准的 统一域名争议解决政策 (UDRP) 争议解决方案提供商 之前提交的争议解决程序 （见 http://www.icann.org/zh/dndr/udrp/ap