Registries

.basketball

This TLD is operated by Roar.Basketball LLC Incorporated, (the “Registry” or “Registry Operator”). The Registry imposes certain conditions for the registration of domain names in its TLDs. As set out in our terms and conditions, by placing an order with us you unconditionally agree to be bound by these conditions as follows:

  1. Registrant agrees to abide by .BASKETBALL registry policies.
  2. Registrant agrees that non-standard domains have non-uniform renewal registration pricing such that the Registration Fee for a domain name registration renewal may differ from other domain names in the same TLD.
  3. Registrant agrees to comply with all applicable laws including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct) and applicable consumer laws in respect of fair lending, debt collection, organic farming (if applicable), disclosure of data and financial regulations.
  4. Registrants are prohibited 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. Engaging in prohibited conduct may result in suspension or termination of the Registered Name either by the Registrar or Registry.
  5. Registrants who collect and maintain sensitive health and financial data, must comply with applicable laws on the provision of such services and include security measures applicable to that sector.
  6. Registrant acknowledges that the registration of the Registered Name is subject to:
    1. the Uniform Domain Name Dispute Resolution Policy (“UDRP”), located at http://www.icann.org/udrp/udrp-rules-24oct99.htm (and up dated from time to time) and http://www.icann.org/dndr/udrp/policy.htm together with the UDRP Rules and all Supplemental Rules of any UDRP provider; and
    2. the Uniform Rapid Suspension System (“URS”), located at http://newgtlds.icann.org/en/applicants/urs, together with the URS Rules and all Supplemental Rules of any URS provider (such link location and rules may be updated from time to time.)
  7. Registrant shall indemnify, defend and hold harmless the Registry Operator, CentralNic and each of their subcontractors, and the directors, officers, employees, affiliates and agents of each of them, from and against any and all claims, damages, liabilities, costs andexpenses, including reasonable legal fees and expenses, arising out of or relating to the Registrant’s domain name registration. This indemnification obligation survives the termination or expiration of the Registration Agreement.
  8. Registrant will comply with the following requirements:
    1. ICANN standards, policies, procedures, and practices for which Registry Operator has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and
    2. operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Registry Operator in a non-arbitrary manner and applicable to all registrars, including affiliates of Registry Operator, and consistent with ICANN’s standards, policies, procedures, and practices and Registry Operator’s Registry Agreement with ICANN. Additional or revised Registry Operator operational standards, policies, procedures, and practices for the Registry TLD shall be effective upon notice ninety (90) days prior notice by Registry Operator to Registrar unless mandated by ICANN with a shorter notice period. If there is a discrepancy between the terms required by the Registry-Registrar Agreement and the terms of the Registrar’s Registration Agreement, the terms of the Registry-Registrar Agreement shall supersede those of the Registrar’s Registration Agreement.
  1. Registrant consents to the use, copying, distribution, publication, modification and otherprocessing of Registrant’s Personal Data by Registry Operator and its designees and agents in a manner consistent with the purposes specified pursuant to the handling of personal data, including data escrow requirements as determined by ICANN.
  2. Registrant agrees to submit to proceedings commenced under ICANN’s Uniform Domain Name Dispute Resolution Policy (“UDRP”), and submit to proceedings commenced under ICANN’s Uniform Rapid Suspension System (“URS”), under ICANN’s related rules.
  3. Registrant will correct and update the registration information for the Registered Name during the registration term for the Registered Name.
  4. When applicable, Registrant agrees to be bound by the terms and conditions of the initial launch of the Registry TLD, including without limitation the Sunrise period, the Community Priority Periods, the procedure and process for compliance with the ICANN Trademark Clearinghouse and any Sunrise Dispute Resolution Policy, and further to acknowledge that Registry Operator has no liability of any kind for any loss or liability resulting from the proceedings and processes relating to the Sunrise period or the Community Priority Periods, including, without limitation:
    1. the ability or inability of a registrant to obtain a Registered Name during these periods, and
    2. the results of any dispute over a Sunrise registration.
  5. Registrant acknowledges and agrees that the Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion;
    1. to protect the integrity and stability of the registry;
    2. to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process;
    3. to avoid any liability, civil or criminal, on the part of Registry Operator, as well as its affiliates, subsidiaries, officers, directors, and employees and those of CentralNic;
    4. per the terms of the Registration Agreement or,
    5. to correct mistakes made by Registry Operator or any Registrar in connection with a domain name registration. Registry Operator also reserves the right to place upon registry lock, hold or similar status a domain name during resolution of a dispute. Registry Operator will provide Registrar notice via EPP command, email or phone call of any cancelation, transfers, changes or registry lock made to any registration by Registry Operator (in respect of a domain sponsored by the Registrar).
  6. Registrant shall provide accurate and reliable contact details and promptly correct and update them during the term of the Registered Name registration, including: the full name, postal address, email address, voice telephone number, and fax number if available of the Registrant; name of authorized person for contact purposes in the case of a Registrant that is an organization, association, or corporation; and the following data elements:
    1. The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; and
    2. The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name.
  7. Registrant’s provision of inaccurate or unreliable information, or its failure promptly to update information provided to Registrar, shall constitute a material breach of this agreement and be a basis for cancellation of the Registered Name registration.
  8. The Registry Operator is entitled to, at any time, verify:
    1. the truth, accuracy, and completeness of any information provided by the Registrant to Registry Operator, and
    2. the compliance by the Registrant with the applicable Registry and ICANN policies.

Registrant shall fully comply and cooperate with Registry Operator in connection with such verification and furnish all requested documentation as Registry Operator may reasonably require to complete the verification.

We use cookies on this site to enhance your user experience. By clicking any link on this page you are giving your consent for us to set cookies.

No; give me more information