{"id":122,"date":"2016-07-18T11:58:41","date_gmt":"2016-07-18T10:58:41","guid":{"rendered":"http:\/\/www.nameshield.com\/?page_id=122"},"modified":"2016-07-18T11:58:41","modified_gmt":"2016-07-18T10:58:41","slug":"registrars-accreditation-agreement","status":"publish","type":"page","link":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/","title":{"rendered":"Registrar\u2019s Accreditation Agreement"},"content":{"rendered":"<p>Back\u00adground: One of the new pro\u00advi\u00adsions added to the 2009 RAA requires ICANN to devel\u00adop in con\u00adsul\u00adta\u00adtion with reg\u00adis\u00adtrars a web\u00adpage that iden\u00adti\u00adfies avail\u00adable <a href=\"http:\/\/www.icann.org\/en\/registrars\/registrant-rights-responsibilities-en.htm\" target=\"_blank\" rel=\"noopener\">reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties<\/a>. This pub\u00adlished doc\u00adu\u00adment is the result of ini\u00adtial input from a joint work\u00ading group of the GNSO Coun\u00adcil and the At-Large Advi\u00adso\u00adry Com\u00admit\u00adtee and sub\u00adse\u00adquent con\u00adsul\u00adta\u00adtions with the reg\u00adis\u00adtrars; and pro\u00advides a \u201cplain lan\u00adguage\u201d sum\u00adma\u00adry of <a href=\"http:\/\/www.icann.org\/en\/registrars\/registrant-rights-responsibilities-en.htm\" target=\"_blank\" rel=\"noopener\">reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties<\/a> that cur\u00adrent\u00adly exist under the 2009 RAA.<\/p>\n<div class=\"surlignable\">\n<div class=\"texte entry-content\">\n<div class=\"surlignable\">\n<div class=\"texte entry-content\">\n<div class=\"surlignable\">\n<div class=\"texte entry-content\">\n<h3 class=\"spip\">Introduction<\/h3>\n<p>This doc\u00adu\u00adment pro\u00advides some \u201cplain lan\u00adguage\u201d sum\u00adma\u00adriza\u00adtion of terms relat\u00aded to <a href=\"http:\/\/www.icann.org\/en\/registrars\/registrant-rights-responsibilities-en.htm\" target=\"_blank\" rel=\"noopener\">reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties<\/a> as set out in the <a href=\"https:\/\/www.icann.org\/resources\/pages\/approved-with-specs-2013-09-17-en\" target=\"_blank\" rel=\"noopener\">reg\u00adis\u00adtrar Accred\u00adi\u00adta\u00adtion Agree\u00adment<\/a> (RAA), for post\u00ading on Reg\u00adis\u00adtrar web\u00adsites. While some of the terms includ\u00aded here do not specif\u00adi\u00adcal\u00adly refer to reg\u00adis\u00adtrants, those terms are includ\u00aded because of the poten\u00adtial import to under\u00adstand\u00ading registrar\/registrant rela\u00adtions. This doc\u00adu\u00adment also sum\u00adma\u00adrizes <a href=\"http:\/\/www.icann.org\/en\/registrars\/registrant-rights-responsibilities-en.htm\" target=\"_blank\" rel=\"noopener\">reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties<\/a> that arise with\u00adin <a href=\"http:\/\/www.icann.org\" target=\"_blank\" rel=\"noopener\">ICANN<\/a> Con\u00adsen\u00adsus Poli\u00adcies and spec\u00adi\u00adfi\u00adca\u00adtions, as those poli\u00adcies and spec\u00adi\u00adfi\u00adca\u00adtions are incor\u00adpo\u00adrat\u00aded into the RAA.\u2019<\/p>\n<p>The sum\u00adma\u00adriza\u00adtion of terms with\u00adin this doc\u00adu\u00adment do not over\u00adride or replace the terms set forth in the RAA or with\u00adin those spec\u00adi\u00adfi\u00adca\u00adtions or pol\u00adi\u00adcy.<\/p>\n<h3 class=\"spip\">Preamble<\/h3>\n<p>In order to reg\u00adis\u00adter a domain name, a Reg\u00adis\u00adtered Name Hold\u00ader (also known as a Reg\u00adis\u00adtrant) has to use the ser\u00advices of an ICANN-accred\u00adit\u00aded Reg\u00adis\u00adtrar. In order to become an ICANN-accred\u00adit\u00aded Reg\u00adis\u00adtrar, the Reg\u00adis\u00adtrar must enter into a con\u00adtract with ICANN, referred to as the Reg\u00adis\u00adtrar Accred\u00adi\u00adta\u00adtion Agree\u00adment or the RAA. The RAA sets out var\u00adi\u00adous rights and respon\u00adsi\u00adbil\u00adi\u00adties for Reg\u00adis\u00adtrants, and Reg\u00adis\u00adtrants have addi\u00adtion\u00adal rights and respon\u00adsi\u00adbil\u00adi\u00adties that are set forth in sep\u00ada\u00adrate ICANN poli\u00adcies and spec\u00adi\u00adfi\u00adca\u00adtions that the Reg\u00adis\u00adtrars agree to fol\u00adlow.<\/p>\n<p>The RAA and the relat\u00aded poli\u00adcies are draft\u00aded in very spe\u00adcif\u00adic, often legal ter\u00admi\u00adnol\u00ado\u00adgy. In order to help Reg\u00adis\u00adtrants bet\u00adter under\u00adstand the rights and respon\u00adsi\u00adbil\u00adi\u00adties that come along with the reg\u00adis\u00adtra\u00adtion of a domain name, these rights and respon\u00adsi\u00adbil\u00adi\u00adties are being sum\u00adma\u00adrized and pre\u00adsent\u00aded with\u00adin a sin\u00adgle doc\u00adu\u00adment. The sum\u00admaries pro\u00advid\u00aded here do not over\u00adride or replace the actu\u00adal terms as writ\u00adten in the RAA or the relat\u00aded poli\u00adcies and spec\u00adi\u00adfi\u00adca\u00adtions.<\/p>\n<h3 class=\"spip\">RAA Terms of Interest<\/h3>\n<p>As the RAA is between ICANN and a Reg\u00adis\u00adtrar, no one else \u2014 includ\u00ading a Reg\u00adis\u00adtered Name Hold\u00ader \u2014 may sue ICANN or the Reg\u00adis\u00adtrar to claim a breach of the RAA.<\/p>\n<p>Reg\u00adis\u00adtrars may not make claims that they can pro\u00advide reg\u00adis\u00adtrants with supe\u00adri\u00ador access to any rel\u00ade\u00advant TLD in com\u00adpar\u00adi\u00adson to oth\u00ader Reg\u00adis\u00adtrars.<\/p>\n<p>Some of the Reg\u00adis\u00adtrar oblig\u00ada\u00adtions are depen\u00addent upon Reg\u00adis\u00adtered Name Hold\u00aders ful\u00adfill\u00ading cer\u00adtain respon\u00adsi\u00adbil\u00adi\u00adties, par\u00adtic\u00adu\u00adlar\u00adly as it relates to pay\u00adment of reg\u00adis\u00adtra\u00adtion fees, sub\u00admis\u00adsion of required data points to the Reg\u00adis\u00adtrars, and sub\u00admis\u00adsion of accu\u00adrate data and time\u00adly updates to that required data. Reg\u00adis\u00adtrars also have spe\u00adcif\u00adic items on which they must pro\u00advide notice to Reg\u00adis\u00adtered Name Hold\u00aders, includ\u00ading noti\u00adfi\u00adca\u00adtions of the end of a reg\u00adis\u00adtra\u00adtion term, use of Reg\u00adis\u00adtered Name Holder\u2019s Per\u00adson\u00adal Data, and notices regard\u00ading escrow\u00ading of data for domain names reg\u00adis\u00adtered through pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion ser\u00advices, as well as the post\u00ading of fees for the recov\u00adery of reg\u00adis\u00adtered names.<\/p>\n<p><strong>Reg\u00adis\u00adtrar Sub\u00admis\u00adsion of Data to Reg\u00adistry Oper\u00ada\u00adtors<\/strong><\/p>\n<p>For each rel\u00ade\u00advant TLD, Reg\u00adis\u00adtrars must sub\u00admit <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3\" target=\"_blank\" rel=\"noopener\">cer\u00adtain data<\/a> points relat\u00ading to each Reg\u00adis\u00adtered Name with\u00adin a TLD:<\/p>\n<ul>\n<li>The name of the Reg\u00adis\u00adtered Name being reg\u00adis\u00adtered (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.1\" target=\"_blank\" rel=\"noopener\">3.2.1.1<\/a>);<\/li>\n<li>The IP address\u00ades of the pri\u00adma\u00adry name\u00adserv\u00ader and sec\u00adondary nameserver(s) for the Reg\u00adis\u00adtered Name (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.2\" target=\"_blank\" rel=\"noopener\">3.2.1.2<\/a>);<\/li>\n<li>The cor\u00adre\u00adspond\u00ading names of those name\u00adservers (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.3\" target=\"_blank\" rel=\"noopener\">3.2.1.3<\/a>);<\/li>\n<li>Unless auto\u00admat\u00adi\u00adcal\u00adly gen\u00ader\u00adat\u00aded by the reg\u00adistry sys\u00adtem, the iden\u00adti\u00adty of the Reg\u00adis\u00adtrar (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.4\" target=\"_blank\" rel=\"noopener\">3.2.1.4<\/a>);<\/li>\n<li>Unless auto\u00admat\u00adi\u00adcal\u00adly gen\u00ader\u00adat\u00aded by the reg\u00adistry sys\u00adtem, the expi\u00adra\u00adtion date of the reg\u00adis\u00adtra\u00adtion (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.5\" target=\"_blank\" rel=\"noopener\">3.2.1.5<\/a>); and<\/li>\n<li>Any oth\u00ader data the Reg\u00adistry Oper\u00ada\u00adtor requires be sub\u00admit\u00adted to it (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.6\" target=\"_blank\" rel=\"noopener\">3.2.1.6<\/a>).<\/li>\n<\/ul>\n<p>Reg\u00adis\u00adtered Name Hold\u00aders are nor\u00admal\u00adly required to pro\u00advide the Reg\u00adis\u00adtrar with infor\u00adma\u00adtion relat\u00ading to name\u00adservers (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.2.1.2\" target=\"_blank\" rel=\"noopener\">3.2.1.2 \u2014 3<\/a>), and there may be addi\u00adtion\u00adal data required under Sec\u00adtion 3.2.1.6 that the Reg\u00adis\u00adtered Name Hold\u00ader must pro\u00advide. If the Reg\u00adis\u00adtered Name Hold\u00ader pro\u00advides an update on these data points, the Reg\u00adis\u00adtrar has five (5) days to pro\u00advide the update to the Reg\u00adistry Oper\u00ada\u00adtor.<\/p>\n<p><strong>Whois Data<\/strong><\/p>\n<p>Reg\u00adis\u00adtrars are required to have an inter\u00adac\u00adtive web page and port 43 Whois ser\u00advice that is avail\u00adable to the pub\u00adlic to query free of charge. The RAA spec\u00adi\u00adfies cer\u00adtain data points that must be pro\u00advid\u00aded in response to a query:<\/p>\n<ul>\n<li>The Reg\u00adis\u00adtered Name (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.1\" target=\"_blank\" rel=\"noopener\">3.3.1.1<\/a>);<\/li>\n<li>The names of the pri\u00adma\u00adry name\u00adserv\u00ader and sec\u00adondary nameserver(s) for the Reg\u00adis\u00adtered Name (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.2\" target=\"_blank\" rel=\"noopener\">3.3.1.2<\/a>);<\/li>\n<li>The iden\u00adti\u00adty of Reg\u00adis\u00adtrar (which may be pro\u00advid\u00aded through Registrar\u2019s web\u00adsite) (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.3\" target=\"_blank\" rel=\"noopener\">3.3.1.3<\/a>);<\/li>\n<li>The orig\u00adi\u00adnal cre\u00adation date of the reg\u00adis\u00adtra\u00adtion (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.4\" target=\"_blank\" rel=\"noopener\">3.3.1.4<\/a>);<\/li>\n<li>The expi\u00adra\u00adtion date of the reg\u00adis\u00adtra\u00adtion (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.5\" target=\"_blank\" rel=\"noopener\">3.3.1.5<\/a>);<\/li>\n<li>The name and postal address of the Reg\u00adis\u00adtered Name Hold\u00ader (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.6\" target=\"_blank\" rel=\"noopener\">3.3.1.6<\/a>)<\/li>\n<li>The name, postal address, e\u2011mail address, voice tele\u00adphone num\u00adber, and (where avail\u00adable) fax num\u00adber of the tech\u00adni\u00adcal con\u00adtact for the Reg\u00adis\u00adtered Name (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.7\" target=\"_blank\" rel=\"noopener\">3.3.1.7<\/a>); and<\/li>\n<li>The name, postal address, e\u2011mail address, voice tele\u00adphone num\u00adber, and (where avail\u00adable) fax num\u00adber of the admin\u00adis\u00adtra\u00adtive con\u00adtact for the Reg\u00adis\u00adtered Name (<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.1.8\" target=\"_blank\" rel=\"noopener\">3.3.1.8<\/a>).<\/li>\n<\/ul>\n<p>These data points are com\u00admon\u00adly referred to as Whois data. As dis\u00adcussed below, Reg\u00adis\u00adtered Name Hold\u00aders are required to pro\u00advide a Reg\u00adis\u00adtrar with time\u00adly updates to Whois data for a Reg\u00adis\u00adtered Name. Upon receiv\u00ading the update, a Reg\u00adis\u00adtrar is to \u201cprompt\u00adly\u201d update the Whois data. Reg\u00adis\u00adtrars may con\u00adtract out the main\u00adte\u00adnance of the pub\u00adlic query func\u00adtion.<\/p>\n<p>The RAA allows Reg\u00adis\u00adtrars to pro\u00advide bulk access to Whois data to third par\u00adties. When pro\u00advid\u00ading bulk access or access to the Whois data through the pub\u00adlic query func\u00adtion, the Reg\u00adis\u00adtrar is <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.3.6\" target=\"_blank\" rel=\"noopener\">required to restrict access<\/a> for high vol\u00adume queries or oth\u00ader restric\u00adtions on uses of Whois data as spec\u00adi\u00adfied in the RAA, includ\u00ading mar\u00adket\u00ading activ\u00adi\u00adties and mass solic\u00adi\u00adta\u00adtions. If a Reg\u00adis\u00adtrar con\u00adtracts the pub\u00adlic func\u00adtion query to an out\u00adside par\u00adty, the Reg\u00adis\u00adtrar must require any con\u00adtrac\u00adtor pro\u00advid\u00ading the port 43 ser\u00advice to impose the same restric\u00adtions on access to and use of the Whois data.<\/p>\n<p><strong>Com\u00admu\u00adni\u00adca\u00adtions with Reg\u00adis\u00adtered Name Hold\u00aders<\/strong><\/p>\n<p>Reg\u00adis\u00adtrars are <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.4.2\" target=\"_blank\" rel=\"noopener\">required to main\u00adtain records of all com\u00admu\u00adni\u00adca\u00adtions<\/a> with Reg\u00adis\u00adtered Name Hold\u00aders, as well as records of infor\u00adma\u00adtion pro\u00advid\u00aded to Reg\u00adistry Oper\u00ada\u00adtors.<\/p>\n<p><strong>Escrow of Reg\u00adis\u00adtered Name Hold\u00ader Data<\/strong><\/p>\n<p>A Reg\u00adis\u00adtrar is required to <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.4.1\" target=\"_blank\" rel=\"noopener\">main\u00adtain a data\u00adbase<\/a> of all Whois data for all Reg\u00adis\u00adtered Names reg\u00adis\u00adtered through the Registrar\u2019s accred\u00adi\u00adta\u00adtion, as well as all data the Reg\u00adis\u00adtrar sub\u00admits to the Reg\u00adistry Oper\u00ada\u00adtor. In addi\u00adtion, the Reg\u00adis\u00adtrar must include in the data\u00adbase the name and (where avail\u00adable) postal address, e\u2011mail address, voice tele\u00adphone num\u00adber, and fax num\u00adber of the billing con\u00adtact for each Reg\u00adis\u00adtered Name.<\/p>\n<p>In some instances, a reg\u00adis\u00adtrant may choose to lim\u00adit the amount of per\u00adson\u00adal infor\u00adma\u00adtion that a Reg\u00adis\u00adtrar makes avail\u00adable in a Whois query. To do so, the name may be reg\u00adis\u00adtered through a pri\u00adva\u00adcy ser\u00advice (allow\u00ading a reg\u00adis\u00adtrant to con\u00adceal per\u00adson\u00adal iden\u00adti\u00adfy\u00ading infor\u00adma\u00adtion and often replac\u00ading it with the infor\u00adma\u00adtion of the pri\u00adva\u00adcy ser\u00advice). Cus\u00adtomers may also choose to reg\u00adis\u00adter names through a proxy ser\u00advice, where the proxy ser\u00advice is the Reg\u00adis\u00adtered Name Hold\u00ader, and the proxy ser\u00advice licens\u00ades the use of the domain name to the cus\u00adtomer. In that sit\u00adu\u00ada\u00adtion, the proxy ser\u00advice, as the Reg\u00adis\u00adtered Name Hold\u00ader, has its infor\u00adma\u00adtion list\u00aded for most or all required data points.<\/p>\n<p>When a Reg\u00adis\u00adtered Name is reg\u00adis\u00adtered through a pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion ser\u00advice, that affects the infor\u00adma\u00adtion that is placed in the data\u00adbase, and a Reg\u00adis\u00adtrar <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.4.1\" target=\"_blank\" rel=\"noopener\">must do one of two things<\/a>: The Reg\u00adis\u00adtrar must either (1) include in the data\u00adbase the name and postal address, e\u2011mail address, and voice tele\u00adphone num\u00adber pro\u00advid\u00aded by the cus\u00adtomer in con\u00adnec\u00adtion with each reg\u00adis\u00adtra\u00adtion, even when a pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion is used; or (2) at the time that a cus\u00adtomer elects to use a pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion ser\u00advice, dis\u00adplay a notice that the customer\u2019s data is not being escrowed. When a customer\u2019s data is not being escrowed, only the con\u00adtact infor\u00adma\u00adtion asso\u00adci\u00adat\u00aded with the pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion ser\u00advice will be escrowed. If a customer\u2019s data is not escrowed, and only the infor\u00adma\u00adtion of the proxy or pri\u00adva\u00adcy ser\u00advice is main\u00adtained in the data\u00adbase, in the event of Reg\u00adis\u00adtrar or Reg\u00adistry fail\u00adure future notices may only be sent to the con\u00adtact infor\u00adma\u00adtion with\u00adin the data\u00adbase.<\/p>\n<p><strong>Reg\u00adis\u00adtrar Busi\u00adness Deal\u00adings with Reg\u00adis\u00adtrants<\/strong><\/p>\n<p>The RAA impos\u00ades many require\u00adments on a Registrar\u2019s busi\u00adness deal\u00adings, includ\u00ading its <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7\" target=\"_blank\" rel=\"noopener\">deal\u00adings with Reg\u00adis\u00adtered Name Hold\u00aders<\/a>.<\/p>\n<p>A reg\u00adis\u00adtrar <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.4\" target=\"_blank\" rel=\"noopener\">may not acti\u00advate<\/a> a Reg\u00adis\u00adtered Name until it receives rea\u00adson\u00adable assur\u00adance from the Reg\u00adis\u00adtered Name Hold\u00ader that the reg\u00adis\u00adtra\u00adtion fee will be paid.<\/p>\n<p>The RAA sets forth actions the Reg\u00adis\u00adtrar may take at the <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5\" target=\"_blank\" rel=\"noopener\">con\u00adclu\u00adsion of the reg\u00adis\u00adtra\u00adtion peri\u00adod<\/a> if a Reg\u00adis\u00adtered Name Hold\u00ader has not pro\u00advid\u00aded con\u00adsent to renew the reg\u00adis\u00adtra\u00adtion, includ\u00ading the Reg\u00adis\u00adtrar can\u00adcelling the reg\u00adis\u00adtra\u00adtion at the end of the cur\u00adrent reg\u00adis\u00adtra\u00adtion term. If the Reg\u00adis\u00adtered Name Hold\u00ader did not con\u00adsent to renew\u00adal, the Reg\u00adis\u00adtrar must make sure that a Reg\u00adis\u00adtered Name is delet\u00aded from the Reg\u00adistry data\u00adbase with\u00adin 45 days of the end of the reg\u00adis\u00adtra\u00adtion term.<\/p>\n<p>This right for the Reg\u00adis\u00adtrar to can\u00adcel the reg\u00adis\u00adtra\u00adtion and the oblig\u00ada\u00adtion to the delete the domain name is not absolute. <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5.1\" target=\"_blank\" rel=\"noopener\">Sec\u00adtion 3.7.5.1<\/a> of the RAA sets forth a list of poten\u00adtial \u201cexten\u00adu\u00adat\u00ading cir\u00adcum\u00adstances,\u201d that, if exist, allows the Reg\u00adis\u00adtrar to renew the domain name even with\u00adout the con\u00adsent of the Reg\u00adis\u00adtered Name Hold\u00ader. These cir\u00adcum\u00adstances include the Reg\u00adis\u00adtered Name being sub\u00adject to a UDRP action, court order, bank\u00adrupt\u00adcy pro\u00adceed\u00ading, or billing dis\u00adpute, among oth\u00ader items. The Reg\u00adis\u00adtrar must keep a record of rea\u00adsons why the Reg\u00adis\u00adtrar renewed a reg\u00adis\u00adtra\u00adtion with\u00adout the con\u00adsent of a Reg\u00adis\u00adtered Name Hold\u00ader.<\/p>\n<p>Reg\u00adis\u00adtrars have to pro\u00advide each new reg\u00adis\u00adtrant with <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5.4\" target=\"_blank\" rel=\"noopener\">notice of the Registrar\u2019s dele\u00adtion and auto-renew\u00adal poli\u00adcies<\/a>. If the Registrar\u2019s dele\u00adtion pol\u00adi\u00adcy changes dur\u00ading the time of the reg\u00adis\u00adtra\u00adtion agree\u00adment, the Reg\u00adis\u00adtrar has to make efforts to inform the reg\u00adis\u00adtrants of those pol\u00adi\u00adcy changes. Details of the dele\u00adtion and auto-renew\u00adal poli\u00adcies <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5.5\" target=\"_blank\" rel=\"noopener\">have to be dis\u00adplayed<\/a> on any web\u00adsite the Reg\u00adis\u00adtrar oper\u00adates for domain name reg\u00adis\u00adtra\u00adtion and renew\u00adal, and the Reg\u00adis\u00adtrar should also <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5.6\" target=\"_blank\" rel=\"noopener\">state on those sites any fee that will be charged for the recov\u00adery of a domain name<\/a> dur\u00ading the Redemp\u00adtion Grace Peri\u00adod (the 30 day peri\u00adod of time dur\u00ading which the name is in \u201cPend\u00ading Delete\u201d sta\u00adtus with the Reg\u00adistry).<sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#foot1\">1<\/a><\/sup><\/p>\n<p>If a Reg\u00adis\u00adtered Name is the sub\u00adject of a <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/policy.htm\" target=\"_blank\" rel=\"noopener\">UDRP dis\u00adpute<\/a> at the time of dele\u00adtion or expi\u00adra\u00adtion of the reg\u00adis\u00adtra\u00adtion, the UDRP com\u00adplainant has the right to renew (or restore, in the case of a dele\u00adtion) the domain name. If the com\u00adplainant renews or restores the name, the Reg\u00adis\u00adtrar must place the name in a HOLD or LOCK sta\u00adtus,<sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#foot2\">2<\/a><\/sup> and must mod\u00adi\u00adfy the Whois infor\u00adma\u00adtion to show that the name is sub\u00adject to dis\u00adpute. <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.5.7\" target=\"_blank\" rel=\"noopener\">Sec\u00adtion 3.7.5.7<\/a> of RAA also pro\u00advides for a right for the orig\u00adi\u00adnal domain name reg\u00adis\u00adtrant to recov\u00ader or renew the name in the event the UDRP com\u00adplaint is ter\u00admi\u00adnat\u00aded with\u00adout deci\u00adsion, or the UDRP com\u00adplaint is decid\u00aded in favor of the orig\u00adi\u00adnal domain name reg\u00adis\u00adtrant.<\/p>\n<p><em>The Registrar\/Registered Name Hold\u00ader Agree\u00adment<\/em><\/p>\n<p>Reg\u00adis\u00adtrars are <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.7\" target=\"_blank\" rel=\"noopener\">required to enter into elec\u00adtron\u00adic or paper reg\u00adis\u00adtra\u00adtion agree\u00adments<\/a> with all Reg\u00adis\u00adtered Name Hold\u00aders. Accord\u00ading to the RAA, the Registrar\/Registered Name Hold\u00ader Agree\u00adment must include \u2014 at min\u00adi\u00admum \u2014 the fol\u00adlow\u00ading items (as stat\u00aded at Sec\u00adtions <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.7.1\" target=\"_blank\" rel=\"noopener\">3.7.7.1 \u2014 12<\/a> of the RAA):<\/p>\n<ul>\n<li>The Reg\u00adis\u00adtered Name Hold\u00ader must pro\u00advide \u201caccu\u00adrate and reli\u00adable con\u00adtact details\u201d <em>and<\/em> must \u201cprompt\u00adly cor\u00adrect and update them\u201d dur\u00ading the reg\u00adis\u00adtra\u00adtion term. The details required are stat\u00aded in Sec\u00adtion 3.7.7.1.: \u201cthe full name, postal address, e\u2011mail address, voice tele\u00adphone num\u00adber, and fax num\u00adber if avail\u00adable of the Reg\u00adis\u00adtered Name Hold\u00ader; name of autho\u00adrized per\u00adson for con\u00adtact pur\u00adpos\u00ades in the case of an Reg\u00adis\u00adtered Name Hold\u00ader that is an orga\u00adni\u00adza\u00adtion, asso\u00adci\u00ada\u00adtion, or cor\u00adpo\u00adra\u00adtion; and the data ele\u00adments list\u00aded in Sub\u00adsec\u00adtions 3.3.1.2, 3.3.1.7 and 3.3.1.8.\u201d<\/li>\n<li>If a Reg\u00adis\u00adtered Name Hold\u00ader inten\u00adtion\u00adal\u00adly pro\u00advides inac\u00adcu\u00adrate or unre\u00adli\u00adable infor\u00adma\u00adtion, inten\u00adtion\u00adal\u00adly fails to prompt\u00adly update the infor\u00adma\u00adtion, or fails to respond over fif\u00adteen (15) days to Reg\u00adis\u00adtrar inquiries about the accu\u00adra\u00adcy of the con\u00adtact details, the Reg\u00adis\u00adtered Name Hold\u00ader will be in mate\u00adr\u00adi\u00adal breach of the agree\u00adment and the reg\u00adis\u00adtra\u00adtion may be can\u00adcelled.<\/li>\n<li>Who\u00adev\u00ader is list\u00aded as the Reg\u00adis\u00adtered Name Hold\u00ader must pro\u00advide full con\u00adtact infor\u00adma\u00adtion, and is the Reg\u00adis\u00adtered Name Hold\u00ader of record. Some\u00adtimes a Reg\u00adis\u00adtered Name Hold\u00ader may reg\u00adis\u00adter a domain name and then allow anoth\u00ader per\u00adson to use the domain name (such as a web\u00adsite design\u00ader reg\u00adis\u00adter\u00ading a domain name for a client). If this hap\u00adpens, and the per\u00adson actu\u00adal\u00adly using the name did not enter into the Registrar\/Registered Name Hold\u00ader Agree\u00adment (referred to as a \u201cthird par\u00adty\u201d in the RAA), the Reg\u00adis\u00adtered Name Hold\u00ader could be account\u00adable for wrong\u00adful use of the domain name by the third par\u00adty. This will hap\u00adpen if the Reg\u00adis\u00adtered Name Hold\u00ader is pro\u00advid\u00aded with \u201crea\u00adson\u00adable evi\u00addence of action\u00adable harm\u201d from the third party\u2019s use of the domain name. In that sit\u00adu\u00ada\u00adtion the Reg\u00adis\u00adtered Name Hold\u00ader will \u201caccept lia\u00adbil\u00adi\u00adty for harm caused by wrong\u00adful use of the Reg\u00adis\u00adtered Name,\u201d unless the Reg\u00adis\u00adtered Name Hold\u00ader dis\u00adclos\u00ades the user\u2019s iden\u00adti\u00adty and cur\u00adrent con\u00adtact infor\u00adma\u00adtion.<\/li>\n<li>The Reg\u00adis\u00adtrar must pro\u00advide notice of how it intends to use data pro\u00advid\u00aded by the Reg\u00adis\u00adtered Name Hold\u00ader and who will received the Reg\u00adis\u00adtered Name Holder\u2019s data. The Reg\u00adis\u00adtrar must also pro\u00advide notice of how Reg\u00adis\u00adtered Name Hold\u00aders may access and update data. Addi\u00adtion\u00adal\u00adly, the Reg\u00adis\u00adtrar must iden\u00adti\u00adfy which data points the Reg\u00adis\u00adtered Name Hold\u00ader must pro\u00advide to the Reg\u00adis\u00adtrar, and what infor\u00adma\u00adtion can be pro\u00advid\u00aded on a vol\u00adun\u00adtary basis. The Reg\u00adis\u00adtered Name Hold\u00ader must con\u00adsent to all of these data pro\u00adcess\u00ading terms.<\/li>\n<li>If a Reg\u00adis\u00adtered Name Hold\u00ader pro\u00advides the Reg\u00adis\u00adtrar with Per\u00adson\u00adal Data on behalf of any per\u00adson who did not enter into the Registrar\/Registered Name Hold\u00ader Agree\u00adment (the \u201cthird par\u00adty\u201d dis\u00adcussed above), the Reg\u00adis\u00adtered Name Hold\u00ader must con\u00adfirm that it (1) pro\u00advid\u00aded those third-par\u00adty indi\u00advid\u00adu\u00adals with the same data pro\u00adcess\u00ading notices that the Reg\u00adis\u00adtrar pro\u00advides, and (2) received the same con\u00adsents from the third par\u00adty regard\u00ading the Registrar\u2019s data pro\u00adcess\u00ading terms.<\/li>\n<li>A Reg\u00adis\u00adtrar may only process the Reg\u00adis\u00adtered Name Holder\u2019s data as stat\u00aded in the data pro\u00adcess\u00ading notices described above.<\/li>\n<li>A Reg\u00adis\u00adtrar has to agree that it will take rea\u00adson\u00adable pre\u00adcau\u00adtions to pro\u00adtect the Reg\u00adis\u00adtered Name Holder\u2019s data from \u201closs, mis\u00aduse, unau\u00adtho\u00adrized access or dis\u00adclo\u00adsure, alter\u00adation, or destruc\u00adtion.\u201d<\/li>\n<li>Reg\u00adis\u00adtered Name Hold\u00aders must rep\u00adre\u00adsent that: \u201cto the best of the Reg\u00adis\u00adtered Name Holder\u2019s knowl\u00adedge and belief, nei\u00adther the reg\u00adis\u00adtra\u00adtion of the Reg\u00adis\u00adtered Name nor the man\u00adner in which it is direct\u00adly or indi\u00adrect\u00adly used infringes the legal rights of any third par\u00adty.\u201d This means that the Reg\u00adis\u00adtered Name Hold\u00ader must rep\u00adre\u00adsent to the Reg\u00adis\u00adtrar that the domain name is not being reg\u00adis\u00adtered for use in a way that would vio\u00adlate the legal rights of oth\u00aders. An exam\u00adple of this \u201cinfringe\u00adment\u201d could be a reg\u00adis\u00adtra\u00adtion of a domain name that vio\u00adlates a trade\u00admark or copy\u00adright held by some\u00adone that is not the Reg\u00adis\u00adtered Name Hold\u00ader.<sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#foot3\">3<\/a><\/sup><\/li>\n<li>If there is a dis\u00adpute in con\u00adnec\u00adtion with the use of the reg\u00adis\u00adtered name, the Reg\u00adis\u00adtered Name Hold\u00ader must agree to juris\u00addic\u00adtion of the courts in at least one of two places: where the Reg\u00adis\u00adtrar is locat\u00aded (often stat\u00aded on the web\u00adsite or in the Registrar\/Registered Name Hold\u00ader Agree\u00adment) or the \u201cReg\u00adis\u00adtered Name Holder\u2019s domi\u00adcile.\u201d \u201cDomi\u00adcile\u201d is a word with legal\u00adly-spe\u00adcif\u00adic mean\u00ading, but typ\u00adi\u00adcal\u00adly will be the loca\u00adtion the Reg\u00adis\u00adtered Name Hold\u00ader pro\u00advides to the Reg\u00adis\u00adtrar in the required Per\u00adson\u00adal Data. Agree\u00ading to juris\u00addic\u00adtion means that the Reg\u00adis\u00adtered Name Hold\u00ader agrees that the courts in those loca\u00adtions have the pow\u00ader to decide these types of cas\u00ades.<sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#foot4\">4<\/a><\/sup><\/li>\n<li>The Reg\u00adis\u00adtered Name Hold\u00ader must agree that its reg\u00adis\u00adtra\u00adtion is sub\u00adject to \u201csus\u00adpen\u00adsion, can\u00adcel\u00adla\u00adtion, or trans\u00adfer\u201d for the rea\u00adsons stat\u00aded in Sec\u00adtion 3.7.7.11. Those rea\u00adsons include: if an ICANN adopt\u00aded spec\u00adi\u00adfi\u00adca\u00adtion or pol\u00adi\u00adcy requires it or if a reg\u00adis\u00adtrar or reg\u00adistry pro\u00adce\u00addure requires it \u201cto cor\u00adrect mis\u00adtakes by Reg\u00adis\u00adtrar or the Reg\u00adistry Oper\u00ada\u00adtor in reg\u00adis\u00adter\u00ading the name or for the res\u00ado\u00adlu\u00adtion of dis\u00adputes con\u00adcern\u00ading the Reg\u00adis\u00adtered Name.\u201d For exam\u00adple, the <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/policy.htm\" target=\"_blank\" rel=\"noopener\">UDRP<\/a> is an ICANN adopt\u00aded pol\u00adi\u00adcy that spec\u00adi\u00adfies that an admin\u00adis\u00adtra\u00adtive pan\u00adel hear\u00ading a domain name dis\u00adpute could order that a domain name reg\u00adis\u00adtra\u00adtion be sus\u00adpend\u00aded, trans\u00adferred or can\u00adcelled, and the Reg\u00adis\u00adtered Name Hold\u00ader has to agree that this is a pos\u00adsi\u00adbil\u00adi\u00adty.<\/li>\n<li>The Reg\u00adis\u00adtered Name Hold\u00ader shall \u201cindem\u00adni\u00adfy and hold harm\u00adless the Reg\u00adistry Oper\u00ada\u00adtor and its direc\u00adtors, offi\u00adcers, employ\u00adees, and agents from and against any and all claims, dam\u00adages, lia\u00adbil\u00adi\u00adties, costs, and expens\u00ades (includ\u00ading rea\u00adson\u00adable legal fees and expens\u00ades) aris\u00ading out of or relat\u00aded to the Reg\u00adis\u00adtered Name Holder\u2019s domain name reg\u00adis\u00adtra\u00adtion.\u201d At its sim\u00adplest, this means that if the Reg\u00adistry Oper\u00ada\u00adtor (or its employ\u00adees, etc.) for the reg\u00adis\u00adtered name is sued because of the Reg\u00adis\u00adtered Name Holder\u2019s domain name reg\u00adis\u00adtra\u00adtion, the Reg\u00adis\u00adtered Name Hold\u00ader will pay the Reg\u00adistry Oper\u00ada\u00adtor for all fees and expens\u00ades in defend\u00ading against the suit as well as pay for any judg\u00adments or lia\u00adbil\u00adi\u00adties award\u00aded. This \u201cindem\u00adni\u00adfi\u00adca\u00adtion\u201d is not sole\u00adly lim\u00adit\u00aded to court cas\u00ades.<\/li>\n<\/ul>\n<p><em>Ver\u00adi\u00adfi\u00adca\u00adtion of con\u00adtact infor\u00adma\u00adtion<\/em><\/p>\n<p>As described in more detail below, there are spec\u00adi\u00adfi\u00adca\u00adtions and poli\u00adcies that may be cre\u00adat\u00aded and that apply to the Reg\u00adis\u00adtrars. Some of the spec\u00adi\u00adfi\u00adca\u00adtions or poli\u00adcies may address a Registrar\u2019s oblig\u00ada\u00adtion to ver\u00adi\u00adfy the con\u00adtact infor\u00adma\u00adtion sup\u00adplied by the Reg\u00adis\u00adtered Name Hold\u00ader when the domain is first reg\u00adis\u00adtered, as well as set\u00adting out <a href=\"http:\/\/www.icann.org\/en\/registrars\/wdrp.htm\" target=\"_blank\" rel=\"noopener\">require\u00adments for peri\u00adod\u00adic re-ver\u00adi\u00adfi\u00adca\u00adtion of con\u00adtact infor\u00adma\u00adtion<\/a>.<\/p>\n<p>Reg\u00adis\u00adtrars are also required to take \u201c<a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.7.8\" target=\"_blank\" rel=\"noopener\">rea\u00adson\u00adable steps<\/a>\u201d to ver\u00adi\u00adfy con\u00adtact infor\u00adma\u00adtion in the event <em>any <\/em>per\u00adson noti\u00adfies the Reg\u00adis\u00adtrar that con\u00adtact infor\u00adma\u00adtion for a Reg\u00adis\u00adtered Name is inac\u00adcu\u00adrate. The Reg\u00adis\u00adtrar also has oblig\u00ada\u00adtions to act to cor\u00adrect inac\u00adcu\u00adra\u00adcies in con\u00adtact infor\u00adma\u00adtion that the Reg\u00adis\u00adtrar becomes aware of, even if the inac\u00adcu\u00adra\u00adcy was not report\u00aded by any\u00adone.<\/p>\n<p>The Reg\u00adis\u00adtrar must also <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.16\" target=\"_blank\" rel=\"noopener\">main\u00adtain prop\u00ader con\u00adtact infor\u00adma\u00adtion<\/a> for itself, includ\u00ading a valid email and mail\u00ading address. This con\u00adtact infor\u00adma\u00adtion should be post\u00aded on the Registrar\u2019s web\u00adsite.<\/p>\n<p><em>Reseller arrange\u00adments<\/em><\/p>\n<p>The RAA <a href=\"http:\/\/www.icann.org\/en\/registrars\/ra-agreement-21may09-en.htm#3.12\" target=\"_blank\" rel=\"noopener\">impos\u00ades oblig\u00ada\u00adtions on Reg\u00adis\u00adtrars work\u00ading with third-par\u00adty Resellers<\/a> \u2014 per\u00adsons or enti\u00adties that the Reg\u00adis\u00adtrar con\u00adtracts with to pro\u00advide Reg\u00adis\u00adtrar Ser\u00advices. The RAA now requires Reg\u00adis\u00adtrars to include spe\u00adcif\u00adic items in the Registrar\/Reseller Agree\u00adments, includ\u00ading: pro\u00adhibit\u00ading the Reseller from mak\u00ading rep\u00adre\u00adsen\u00adta\u00adtions that it is accred\u00adit\u00aded by ICANN; requir\u00ading that all Reseller reg\u00adis\u00adtra\u00adtion agree\u00adments include all pro\u00advi\u00adsions that the Reg\u00adis\u00adtrar is required to include in its Registrar\/Registered Name Hold\u00ader Agree\u00adment; requir\u00ading the post\u00ading of all links to all ICANN web\u00adsites that the Reg\u00adis\u00adtrar is oblig\u00adat\u00aded to post; and iden\u00adti\u00adfi\u00adca\u00adtion of the spon\u00adsor\u00ading reg\u00adis\u00adtrar. The Reseller is also required to make sure that that if a cus\u00adtomer is using a Reseller\u2019s pri\u00adva\u00adcy or proxy reg\u00adis\u00adtra\u00adtion ser\u00advice for a domain name reg\u00adis\u00adtra\u00adtion, the Reseller does one of the fol\u00adlow\u00ading three things: (1) deposit the iden\u00adti\u00adty and con\u00adtact infor\u00adma\u00adtion of the cus\u00adtomer with the Reg\u00adis\u00adtrar; (2) deposit the iden\u00adti\u00adty and con\u00adtact infor\u00adma\u00adtion in escrow; or (3) posts a notice to the cus\u00adtomer that their con\u00adtact infor\u00adma\u00adtion is not being escrowed.<\/p>\n<p>The RAA also requires the Reg\u00adis\u00adtrar to take com\u00adpli\u00adance and enforce\u00adment action against a Reseller vio\u00adlat\u00ading any of the required pro\u00advi\u00adsions.<\/p>\n<\/div>\n<h3>Other Policies\/Specifications<\/h3>\n<p>The <a href=\"http:\/\/www.icann.org\/en\/registrars\/rnap.htm\" target=\"_blank\" rel=\"noopener\">Restored Names Accu\u00adra\u00adcy Pol\u00adi\u00adcy<\/a> (<a href=\"http:\/\/www.icann.org\/en\/registrars\/rnap.htm\" target=\"_blank\" rel=\"noopener\">http:\/\/www.icann.org\/en\/registrars\/rnap.htm<\/a>) requires that when a reg\u00adis\u00adtrar restores a name (from the redemp\u00adtion grace peri\u00adod) that had been delet\u00aded on the basis of sub\u00admis\u00adsion of false con\u00adtact data or non-response to reg\u00adis\u00adtrar inquiries, the name must be placed on Reg\u00adis\u00adtrar Hold sta\u00adtus until the reg\u00adis\u00adtrant has pro\u00advid\u00aded updat\u00aded and accu\u00adrate Whois infor\u00adma\u00adtion.<\/p>\n<p>In addi\u00adtion to the RAA require\u00adment that a Reg\u00adis\u00adtered Name Hold\u00ader rep\u00adre\u00adsent that to the best of its knowl\u00adedge, the reg\u00adis\u00adtra\u00adtion or use of the domain name does not infringe on the legal rights of oth\u00aders, the Uni\u00adform Domain Name Dis\u00adpute Res\u00ado\u00adlu\u00adtion Pol\u00adi\u00adcy (\u201c<a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/policy.htm\" target=\"_blank\" rel=\"noopener\">UDRP<\/a>\u201d) requires that same rep\u00adre\u00adsen\u00adta\u00adtion to be made, as well as a rep\u00adre\u00adsen\u00adta\u00adtion that the domain name is not being reg\u00adis\u00adtered for an unlaw\u00adful pur\u00adpose, and will not be used in vio\u00adla\u00adtion of any applic\u00ada\u00adble laws.<\/p>\n<p>The UDRP also requires Reg\u00adis\u00adtered Name Hold\u00aders to sub\u00admit to manda\u00adto\u00adry admin\u00adis\u00adtra\u00adtive pro\u00adceed\u00adings to resolve dis\u00adputes under the UDRP. These manda\u00adto\u00adry admin\u00adis\u00adtra\u00adtive pro\u00adceed\u00adings, as described in the UDRP, are dis\u00adputes that are filed before one of the ICANN approved <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/approved-providers.htm\" target=\"_blank\" rel=\"noopener\">UDRP dis\u00adpute res\u00ado\u00adlu\u00adtion providers<\/a> (list\u00aded at <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/approved-providers.htm\" target=\"_blank\" rel=\"noopener\">http:\/\/www.icann.org\/en\/dndr\/udrp\/approved-providers.htm<\/a>) and fol\u00adlow\u00ading the <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/uniform-rules.htm\" target=\"_blank\" rel=\"noopener\">uni\u00adform Rules for UDRP admin\u00adis\u00adtra\u00adtive pro\u00adceed\u00adings<\/a> (set out at <a href=\"http:\/\/www.icann.org\/en\/dndr\/udrp\/uniform-rules.htm\" target=\"_blank\" rel=\"noopener\">http:\/\/www.icann.org\/en\/dndr\/udrp\/uniform-rules.htm<\/a>). The require\u00adment for sub\u00admis\u00adsion to manda\u00adto\u00adry admin\u00adis\u00adtra\u00adtive pro\u00adceed\u00adings does not mean that Reg\u00adis\u00adtered Name Hold\u00aders can\u00adnot also have judi\u00adcial pro\u00adceed\u00adings filed against them for the same or sim\u00adi\u00adlar con\u00adduct. Sim\u00adi\u00adlar to the juris\u00addic\u00adtion\u00adal require\u00adments set out in the RAA, the require\u00adment to sub\u00admit to a manda\u00adto\u00adry admin\u00adis\u00adtra\u00adtive pro\u00adceed\u00ading means that the Reg\u00adis\u00adtered Name Hold\u00ader can\u00adnot dis\u00adpute the UDRP provider\u2019s abil\u00adi\u00adty to hear a dis\u00adpute that is oth\u00ader\u00adwise prop\u00ader\u00adly brought under the UDRP.<\/p>\n<p>The <a href=\"http:\/\/www.icann.org\/en\/transfers\/policy-en.htm\" target=\"_blank\" rel=\"noopener\">Pol\u00adi\u00adcy on Trans\u00adfers of Reg\u00adis\u00adtra\u00adtions between Reg\u00adis\u00adtrars<\/a> pro\u00advides that Reg\u00adis\u00adtered Name Hold\u00aders have the right to trans\u00adfer domain name reg\u00adis\u00adtra\u00adtions among reg\u00adis\u00adtrars. The trans\u00adfer pol\u00adi\u00adcy impos\u00ades time lim\u00adits on when the Reg\u00adis\u00adtrar must respond to a trans\u00adfer request. The right to trans\u00adfer is not absolute \u2014 there are ICANN and Reg\u00adistry poli\u00adcies that may set lim\u00adits on the trans\u00adfer right, includ\u00ading: lim\u00adi\u00adta\u00adtions on when a domain name may be trans\u00adferred (mea\u00adsured from dates of cre\u00adation or ear\u00adli\u00ader trans\u00adfer); and the Reg\u00adis\u00adtered Name Hold\u00ader pro\u00advid\u00ading of required autho\u00adriza\u00adtion and doc\u00adu\u00admen\u00adta\u00adtion for Reg\u00adis\u00adtrar review. The Reg\u00adis\u00adtrar of Record may only deny a trans\u00adfer in the fol\u00adlow\u00ading instances:<\/p>\n<ul>\n<li>Evi\u00addence of fraud<\/li>\n<li>UDRP action<\/li>\n<li>Court order by a court of com\u00adpe\u00adtent juris\u00addic\u00adtion<\/li>\n<li>Rea\u00adson\u00adable dis\u00adpute over the iden\u00adti\u00adty of the Reg\u00adis\u00adtered Name Hold\u00ader or Admin\u00adis\u00adtra\u00adtive Con\u00adtact<\/li>\n<li>No pay\u00adment for pre\u00advi\u00adous reg\u00adis\u00adtra\u00adtion peri\u00adod (includ\u00ading cred\u00adit card charge-backs) if the domain name is past its expi\u00adra\u00adtion date or for pre\u00advi\u00adous or cur\u00adrent reg\u00adis\u00adtra\u00adtion peri\u00adods if the domain name has not yet expired. In all such cas\u00ades, how\u00adev\u00ader, the domain name must be put into \u201cReg\u00adis\u00adtrar Hold\u201d sta\u00adtus by the Reg\u00adis\u00adtrar of Record pri\u00ador to the denial of trans\u00adfer.<\/li>\n<li>Express writ\u00adten objec\u00adtion to the trans\u00adfer from the Trans\u00adfer Con\u00adtact. (e.g. \u2014 email, fax, paper doc\u00adu\u00adment or oth\u00ader process\u00ades by which the Trans\u00adfer Con\u00adtact has express\u00adly and vol\u00adun\u00adtar\u00adi\u00adly object\u00aded through opt-in means)<\/li>\n<li>A domain name was already in \u201clock sta\u00adtus\u201d pro\u00advid\u00aded that the Reg\u00adis\u00adtrar pro\u00advides a read\u00adi\u00adly acces\u00adsi\u00adble and rea\u00adson\u00adable means for the Reg\u00adis\u00adtered Name Hold\u00ader to remove the lock sta\u00adtus.<\/li>\n<li>The trans\u00adfer was request\u00aded with\u00adin 60 days of the cre\u00adation date as shown in the reg\u00adistry Whois record for the domain name.<\/li>\n<li>A domain name is with\u00adin 60 days (or a less\u00ader peri\u00adod to be deter\u00admined) after being trans\u00adferred (apart from being trans\u00adferred back to the orig\u00adi\u00adnal Reg\u00adis\u00adtrar in cas\u00ades where both Reg\u00adis\u00adtrars so agree and\/or where a deci\u00adsion in the dis\u00adpute res\u00ado\u00adlu\u00adtion process so directs).<\/li>\n<\/ul>\n<hr>\n<p><a id=\"foot1\" name=\"foot1\"><\/a><sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#text1\">1<\/a><\/sup> A graph\u00adic rep\u00adre\u00adsen\u00adta\u00adtion of the life cycle of a typ\u00adi\u00adcal gTLD Reg\u00adis\u00adtered Name is locat\u00aded at <a href=\"http:\/\/www.icann.org\/en\/registrars\/gtld-lifecycle.htm\" target=\"_blank\" rel=\"noopener\">http:\/\/www.icann.org\/en\/registrars\/gtld-lifecycle.htm<\/a>. This dia\u00adgram may be use\u00adful to refer to for more infor\u00adma\u00adtion on the post-expi\u00adra\u00adtion sta\u00adtus of domain names.<\/p>\n<p><a id=\"foot2\" name=\"foot2\"><\/a><sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#text2\">2<\/a><\/sup> There are for\u00admal tech\u00adni\u00adcal names for domain name sta\u00adtus\u00ades, aris\u00ading out of the com\u00admu\u00adni\u00adty-based Inter\u00adnet draft Request for Com\u00adments. The sta\u00adtus\u00ades required here are set by the Reg\u00adis\u00adtrar. When a reg\u00adis\u00adtra\u00adtion is in one of these sta\u00adtus\u00ades, the domain can\u00adnot be delet\u00aded and the reg\u00adis\u00adtra\u00adtion can\u00adnot be mod\u00adi\u00adfied. The Reg\u00adis\u00adtrar must alter the sta\u00adtus in order for any mod\u00adi\u00adfi\u00adca\u00adtion to occur.<\/p>\n<p><a id=\"foot3\" name=\"foot3\"><\/a><sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#text3\">3<\/a><\/sup> There are many oth\u00ader poten\u00adtial ways to \u201cinfringe the legal rights\u201d of oth\u00aders, and poten\u00adtial Reg\u00adis\u00adtered Name Hold\u00aders are encour\u00adaged to seek inde\u00adpen\u00addent advice if they are con\u00adcerned that the reg\u00adis\u00adtra\u00adtion or use of a domain name may vio\u00adlate some\u00adone else\u2019s rights.<\/p>\n<p><a id=\"foot4\" name=\"foot4\"><\/a><sup><a href=\"https:\/\/www.nameshield.com\/en\/raa-en#text4\">4<\/a><\/sup> There could be oth\u00ader juris\u00addic\u00adtions that are able to decide a dis\u00adpute about the use of a reg\u00adis\u00adtered name, but those addi\u00adtion\u00adal juris\u00addic\u00adtions are not spec\u00adi\u00adfied in the RAA.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Back\u00adground: One of the new pro\u00advi\u00adsions added to the 2009 RAA requires ICANN to devel\u00adop in con\u00adsul\u00adta\u00adtion with reg\u00adis\u00adtrars a web\u00adpage that iden\u00adti\u00adfies avail\u00adable reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties. This pub\u00adlished doc\u00adu\u00adment is the result of ini\u00adtial input from a joint work\u00ading group of the GNSO Coun\u00adcil and the At-Large Advi\u00adso\u00adry Com\u00admit\u00adtee and sub\u00adse\u00adquent con\u00adsul\u00adta\u00adtions with\u2026&nbsp;<a href=\"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/\" class rel=\"bookmark\">Read More \u00bb<span class=\"screen-reader-text\">Registrar\u2019s Accred\u00adi\u00adta\u00adtion Agree\u00adment<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":120,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"wp_typography_post_enhancements_disabled":false,"editor_plus_copied_stylings":"{}","_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","footnotes":""},"class_list":["post-122","page","type-page","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Registrar&#039;s Accreditation Agreement - Nameshield<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Registrar&#039;s Accreditation Agreement - Nameshield\" \/>\n<meta property=\"og:description\" content=\"Back\u00adground: One of the new pro\u00advi\u00adsions added to the 2009 RAA requires ICANN to devel\u00adop in con\u00adsul\u00adta\u00adtion with reg\u00adis\u00adtrars a web\u00adpage that iden\u00adti\u00adfies avail\u00adable reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties. This pub\u00adlished doc\u00adu\u00adment is the result of ini\u00adtial input from a joint work\u00ading group of the GNSO Coun\u00adcil and the At-Large Advi\u00adso\u00adry Com\u00admit\u00adtee and sub\u00adse\u00adquent con\u00adsul\u00adta\u00adtions with&hellip;&nbsp;Read More &raquo;Registrar\u2019s Accreditation Agreement\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/\" \/>\n<meta property=\"og:site_name\" content=\"Nameshield\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"19 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/registrars-accreditation-agreement\\\/\",\"url\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/registrars-accreditation-agreement\\\/\",\"name\":\"Registrar's Accreditation Agreement - Nameshield\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/#website\"},\"datePublished\":\"2016-07-18T10:58:41+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/registrars-accreditation-agreement\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/registrars-accreditation-agreement\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/registrars-accreditation-agreement\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Legal information\",\"item\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/legal-info\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Registrar&#8217;s Accreditation Agreement\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/\",\"name\":\"Nameshield\",\"description\":\"Online Assets Security\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.nameshield.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Registrar's Accreditation Agreement - Nameshield","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/","og_locale":"en_US","og_type":"article","og_title":"Registrar's Accreditation Agreement - Nameshield","og_description":"Back\u00adground: One of the new pro\u00advi\u00adsions added to the 2009 RAA requires ICANN to devel\u00adop in con\u00adsul\u00adta\u00adtion with reg\u00adis\u00adtrars a web\u00adpage that iden\u00adti\u00adfies avail\u00adable reg\u00adis\u00adtrant rights and respon\u00adsi\u00adbil\u00adi\u00adties. This pub\u00adlished doc\u00adu\u00adment is the result of ini\u00adtial input from a joint work\u00ading group of the GNSO Coun\u00adcil and the At-Large Advi\u00adso\u00adry Com\u00admit\u00adtee and sub\u00adse\u00adquent con\u00adsul\u00adta\u00adtions with&hellip;&nbsp;Read More &raquo;Registrar\u2019s Accreditation Agreement","og_url":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/","og_site_name":"Nameshield","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"19 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/","url":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/","name":"Registrar's Accreditation Agreement - Nameshield","isPartOf":{"@id":"https:\/\/www.nameshield.com\/en\/#website"},"datePublished":"2016-07-18T10:58:41+00:00","breadcrumb":{"@id":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.nameshield.com\/en\/legal-info\/registrars-accreditation-agreement\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Legal information","item":"https:\/\/www.nameshield.com\/en\/legal-info\/"},{"@type":"ListItem","position":2,"name":"Registrar&#8217;s Accreditation Agreement"}]},{"@type":"WebSite","@id":"https:\/\/www.nameshield.com\/en\/#website","url":"https:\/\/www.nameshield.com\/en\/","name":"Nameshield","description":"Online Assets Security","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.nameshield.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/pages\/122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/comments?post=122"}],"version-history":[{"count":0,"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/pages\/122\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/pages\/120"}],"wp:attachment":[{"href":"https:\/\/www.nameshield.com\/en\/wp-json\/wp\/v2\/media?parent=122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}