Root-‐zone Information Publication. ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 2095 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 103 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 22 contracts
Samples: Registry Agreement (Verisign Inc/Ca), Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 17 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.xxxxx://xxx.xxxx.xxx/domains/root/.
Appears in 13 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 10 contracts
Samples: Registry Agreement (Verisign Inc/Ca), Registry Agreement (Verisign Inc/Ca), Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format reasonably specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 5 contracts
Samples: Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement, TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.xxxx://xxx.xxxxx/xxx/xxxxxxx/xxxx.
Appears in 5 contracts
Samples: Aero TLD Sponsorship Registry Agreement, Aero TLD Sponsorship Registry Agreement, Coop Sponsored TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 5 contracts
Samples: Registry Agreement, GTLD Agreement, GTLD Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 4 contracts
Samples: Registry Agreement, Registry Agreement, Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.xxxx://xxx.xxxxx.xxx/domains/root.
Appears in 3 contracts
Samples: Museum Registry Agreement, Museum Registry Agreement, .Museum Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry Operator TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 2 contracts
Samples: Registry Agreement, Sponsored TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 2 contracts
Samples: Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-‐ zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 1 contract
Samples: Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Appears in 1 contract
Samples: Registry Agreement
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format reasonably specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN. ARTICLE IV TERM OF AGREEMENT
Appears in 1 contract
Samples: Sponsored TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.xxxxx://xxx.xxxxx/xxx/xxxxxxx/xxxx.
Appears in 1 contract
Root-‐zone Information Publication. ICANN’s 's publication of root-‐zone root- zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN.
Appears in 1 contract
Samples: Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.httx://xxx.xxxx.xxx/xxxxxxx/root/.
Appears in 1 contract
Samples: Registry Agreement
Root-‐zone Information Publication. ICANNICANN'sICANN’s publication of root-‐zone root-zone contact information for the Registry Operator TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN ICANN. at xxxx://xxx.xxxx.xxx/domains/root/.xxxx://xxx.xxxxx.xxx/domains/root.
Appears in 1 contract
Samples: TLD Registry Agreement
Root-‐zone Information Publication. ICANN’s publication of root-‐zone root-zone contact information for the Registry TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.ICANN. authoritative root server system. The nameserver changes and publication of root zone information have been simplified in the 2007 agreement.
Appears in 1 contract
Samples: www.icann.org
