Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”
1.6.2 Response format: Registrar Name: Example Registrar, Inc. Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxx@xxxxxxx.xxx WHOIS Server: whois.example-‐registrar.tld Referral URL: xxxx://xxx.xxxxxxx-‐registrar.tld Admin Contact: Xxx Registrar Phone Number: +1.3105551213 Fax Number: +1.3105551213 Email: joeregistrar@example-‐registrar.tld Admin Contact: Xxxx Registrar Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: janeregistrar@example-‐registrar.tld Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216 Email: johngeek@example-‐registrar.tld >>> Last update of WHOIS database: 2009-‐05-‐29T20:15:00Z <<<
Registrar and Transfer Agent To maintain, at its expense, a registrar and transfer agent for the Stock.
Registrar, Transfer Agent and Paying Agent The Issuer shall maintain (i) an office or agency where Notes may be presented for registration (“Registrar”), (ii) an office or agency where Notes may be presented for transfer or for exchange (“Transfer Agent”) and (iii) an office or agency where Notes may be presented for payment (“Paying Agent”). The Registrar shall keep a register of the Notes (“Note Register”) and of their transfer and exchange. The registered Holder of a Note will be treated as the owner of such Note for all purposes and only registered Holders shall have rights under this Indenture and the Notes. The Issuer may appoint one or more co-registrars, one or more co-transfer agents and one or more additional paying agents. The term “Registrar” includes any co-registrar, the term “Transfer Agent” includes any co-transfer agent and the term “Paying Agent” includes any additional paying agents. The Issuer may change any Paying Agent, Transfer Agent or Registrar without prior notice to any Holder. The Issuer shall notify the Trustee in writing of the name and address of any Agent not a party to this Indenture. If the Issuer fails to appoint or maintain another entity as Registrar, Transfer Agent or Paying Agent, the Trustee shall act as such. The Issuer or any of its Subsidiaries may act as Paying Agent, Transfer Agent or Registrar. The Issuer initially appoints The Depository Trust Company, its nominees and successors (“DTC”) to act as Depositary with respect to the Global Notes. The Issuer initially appoints the Trustee to act as the Paying Agent, Transfer Agent and Registrar for the Notes and to act as Custodian with respect to the Global Notes.
Registrar and Paying Agent The Company shall maintain an office or agency where Notes may be presented for registration of transfer or for exchange ("Registrar") and an office or agency where Notes may be presented for payment ("Paying Agent"). The Registrar shall keep a register of the Notes and of their transfer and exchange. The Company may appoint one or more co-registrars and one or more additional paying agents. The term "
ICANN testing registrar Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement.
1. Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website.
2. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.)
3. Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination.
a. Registry Operator will include a provision in its Registry-‐Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name.
b. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request.
c. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-‐discrimination by establishing, publishing and adhering to clear registration policies.
d. Registry Operator of a “Generic String” TLD may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.
Registrar, Paying Agent and Conversion Agent (a) The Company shall maintain one or more offices or agencies where Securities may be presented for registration of transfer or for exchange (each, a “Registrar”), one or more offices or agencies where Securities may be presented or surrendered for payment (each, a “Paying Agent”), one or more offices or agencies where Securities may be presented for conversion (each, a “Conversion Agent”) and one or more offices or agencies where notices and demands to or upon the Company in respect of the Securities and this Indenture may be served. The Company will at all times maintain a Paying Agent, Conversion Agent, Registrar and an office or agency where notices and demands to or upon the Company in respect of the Securities and this Indenture may be served in the Borough of Manhattan, The City of New York. One of the Registrars (the “Primary Registrar”) shall keep a register of the Securities and of their transfer and exchange. At the option of the Company, any payment of cash may be made by check mailed to the Holders at their addresses set forth in the register of Holders.
(b) The Company shall enter into an appropriate agency agreement with any Agent not a party to this Indenture, provided that the Agent may be an Affiliate of the Trustee. The agreement shall implement the provisions of this Indenture that relate to such Agent. The Company shall notify the Trustee of the name and address, and any change in the name or address, of any Agent not a party to this Indenture. If the Company fails to maintain a Registrar, Paying Agent, Conversion Agent, or agent for service of notices and demands in any place required by this Indenture, or fails to give the foregoing notice, the Trustee shall act as such. The Company or any Affiliate of the Company may act as Paying Agent (except for the purposes of Section 5.01 and Article 9).
(c) The Company hereby initially designates the Trustee as Paying Agent, Registrar, Securities Custodian and Conversion Agent, and designates the Corporate Trust Office of the Trustee as the office or agency of the Company for each of the aforesaid purposes and as the office or agency where notices and demands to or upon the Company in respect of the Securities and this Indenture may be served.
Registrar The term “
Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLD, the A-‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Registrars (a) All domain name registrations in the TLD must be registered through an ICANN accredited registrar; provided, that Registry Operator need not use a registrar if it registers names in its own name in order to withhold such names from delegation or use in accordance with Section 2.6. Subject to the requirements of Specification 11, Registry Operator must provide non-‐discriminatory access to Registry Services to all ICANN accredited registrars that enter into and are in compliance with the registry-‐registrar agreement for the TLD; provided that Registry Operator may establish non-‐discriminatory criteria for qualification to register names in the TLD that are reasonably related to the proper functioning of the TLD. Registry Operator must use a uniform non-‐discriminatory agreement with all registrars authorized to register names in the TLD (the “Registry-‐Registrar Agreement”). Registry Operator may amend the Registry-‐Registrar Agreement from time to time; provided, however, that any material revisions thereto must be approved by ICANN before any such revisions become effective and binding on any registrar. Registry Operator will provide ICANN and all registrars authorized to register names in the TLD at least fifteen (15) calendar days written notice of any revisions to the Registry-‐Registrar Agreement before any such revisions become effective and binding on any registrar. During such period, ICANN will determine whether such proposed revisions are immaterial, potentially material or material in nature. If ICANN has not provided Registry Operator with notice of its determination within such fifteen (15) calendar-‐day period, ICANN shall be deemed to have determined that such proposed revisions are immaterial in nature. If ICANN determines, or is deemed to have determined under this Section 2.9(a), that such revisions are immaterial, then Registry Operator may adopt and implement such revisions. If ICANN determines such revisions are either material or potentially material, ICANN will thereafter follow its procedure regarding review and approval of changes to Registry-‐Registrar Agreements at <xxxx://xxx.xxxxx.xxx/en/resources/registries/rra-‐amendment-‐procedure>, and such revisions may not be adopted and implemented until approved by ICANN.
(b) If Registry Operator (i) becomes an Affiliate or reseller of an ICANN accredited registrar, or (ii) subcontracts the provision of any Registry Services to an ICANN accredited registrar, registrar reseller or any of their respective Affiliates, then, in either such case of (i) or (ii) above, Registry Operator will give ICANN prompt notice of the contract, transaction or other arrangement that resulted in such affiliation, reseller relationship or subcontract, as applicable, including, if requested by ICANN, copies of any contract relating thereto; provided, that ICANN will treat such contract or related documents that are appropriately marked as confidential (as required by Section 7.15) as Confidential Information of Registry Operator in accordance with Section 7.15 (except that ICANN may disclose such contract and related documents to relevant competition authorities). ICANN reserves the right, but not the obligation, to refer any such contract, related documents, transaction or other arrangement to relevant competition authorities in the event that ICANN determines that such contract, related documents, transaction or other arrangement might raise significant competition issues under applicable law. If feasible and appropriate under the circumstances, ICANN will give Registry Operator advance notice prior to making any such referral to a competition authority.
(c) For the purposes of this Agreement: (i) “Affiliate” means a person or entity that, directly or indirectly, through one or more intermediaries, or in combination with one or more other persons or entities, controls, is controlled by, or is under common control with, the person or entity specified, and (ii) “control” (including the terms “controlled by” and “under common control with”) means the possession, directly or indirectly, of the power to direct or cause the direction of the management or policies of a person or entity, whether through the ownership of securities, as trustee or executor, by serving as an employee or a member of a board of directors or equivalent governing body, by contract, by credit arrangement or otherwise.
Transfer Agent and Registrar The Trustees shall have power to employ a transfer agent or transfer agents, and a registrar or registrars, with respect to the Shares. The transfer agent or transfer agents may keep the applicable register and record therein, the original issues and transfers, if any, of the said Shares. Any such transfer agents and/or registrars shall perform the duties usually performed by transfer agents and registrars of certificates of stock in a corporation, as modified by the Trustees.
