Registry Policy

.VEGAS REGISTRY POLICIES

‍1. Definitions

2. General Registration Policy

3. Sunrise Registration Policy

4. Sunrise Dispute Resolution Policy

5. Landrush Registration Policy

6. Reserved and Premium Names Policy

7. General Availability Registration Policy

8. WHOIS Policy

9. Anti-Abuse/Acceptable Use Policy

10. Dispute Resolution Policy

11. Privacy Policy

12. ICANN Designated Exclusive Registration Period Policies (Collision Names Only)

‍1. CERTAIN DEFINITIONS

‍Where used in the .Vegas TLD("TLD") policies relating to the launch or registration of domain names in the TLD, the following definitions shall apply. Said definitions must be read in conjunction with the general policies of Dot Vegas, Inc.("Registry") relating to the launch and operation of the TLD, applicable Registrant Agreements, applicable ICANN policies and procedures, and applicable Registrar policies, as amended from time to time.

1. 'ASCII' means the American standard code for information interchange.

2. 'Applicant' means a natural person, company, or organization submitting a domain name application.

3. 'Domain Name' means a domain name in and maintained by the Registry’s database consisting of at least the domain name character string and TLD together, separated by a dot (e.g.,“yourdomain.vegas”).

4. 'Domain Name Character String' means the characters to the left of the dot that precedes the TLD (e.g., in the domain name “yourdomain.vegas”, “yourdomain” is the character string).

5. 'IDN' means Internationalized Domain Name and includes any Domain Name Character String which contains non-ASCII characters of any type.

6. 'Registrar' means a Domain Name registrar sponsoring an applicant for a Domain Name Registration that is (i)accredited by ICANN and (ii) has entered into a Registry-Registrar Agreement with the Registry.

7. 'Registry' means Dot Vegas, Inc., a Nevada corporation.

8. 'Registry Website' means www.nic.vegas or such other TLD-specific URL which the Registry may designate as its primary website for administering and managing the TLD.

9. 'SMD File' is the file issued by the TMCH proving that the TMCH application data for one or more TMCH-Sunrise eligible terms–typically a trademark–have been successfully validated and entered into the TMCH database.

10. 'Sunrise Period' means the period designated by the Registry during which holders of SMD Files may submit Sunrise applications.

11. 'Sunrise Application' means the non-transferrable, complete, technically correct request for a Domain Name registration submitted by a Registrar to the Registry during the Sunrise Period.

12. 'Sunrise Registration' means a Domain Name registration resulting from an approved Sunrise application.

13. 'TMCH' means the Trademark Clearing House, which is the mechanism made available for the validation and database management of rights protected terms, typically trademarks.

14. 'TMCH Guidelines' means the then effective guidelines found at http://www.trademark-clearinghouse.com.

‍2. GENERAL DOMAIN NAMES

REGISTRATION POLICY

‍Except as expressly modified relative to Sunrise Registrations, Reserved and Premium Domain Names, and "Founder" or "Pioneer" Names, this General Domain Name Registration Policy (“Policy”) of Dot Vegas, Inc. (the “Registry”) is to be read together with all Registry Policies, the Registrant's Agreement, andapplicable Registrar policies, as amended from time to time. Words and phrases used in this Policy shall have the same meaning attributed to them in the Registrant Agreement unless otherwise specified or the context clearly otherwise requires. Please note that the Registry may modify this Policy from time to time effective upon ninety (90) days notice by the Registry to interested parties including sponsoring registrars, provided that under certain conditions relating to changes in registration or renewal pricing, Registry must provide one hundred eighty (180) days notice pursuant to the Registry-Registrar Agreement. Such changes will be available on the Registry website at http://www.nic.vegas or such other URL as the Registry may designate, which shall satisfy all notice requirements set forth in this Policy. After the notice period expires, each time a user accesses or uses the Services, the user will be bound by the then effective General Domain Names Registration Policy.

PLEASE READ THIS POLICY CAREFULLY. BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.

‍1. Registrant Qualifications. Anyone, any where in the world, is qualified and eligible to register a .Vegas Domain Name. There are no nexus requirements associated with domain name registrations.

‍2. Acceptable Domain Name Character Strings. The Registry will not accept a domain name registration application unless the applied-for Domain Name meets the applicable requirements as defined in applicable RFCs for ASCII character strings, including the following technical and syntax requirements. The Domain Name Character String must: (a) consist only of ACSII characters, consist exclusively of the letters A-Z (case insensitive), the numbers 0-9, and hyphens; (b) not begin or end with a hyphen, or include consecutive hyphens in the third and fourth positions of the Domain Name Character String; (c) not exceed 63 characters excluding the TLD extension; and (d) unless otherwise modified by the Registry in its sole discretion, contain at least three characters (but may not be Domain Name Character Strings required to be blocked or reserved pursuant to ICANN policies, the Registry Agreement with ICANN, or other contractual agreements of the Registry).The Registry will not accept IDNs or Domain Name Character Strings containing non-ASCII characters until a future date designated by the Registry, in its sole discretion.

‍3. Term. Domain names may be registered in increments of one (1) year each for a minimum of one (1) year and a maximum often (10) years.

‍4. Renewal. Domain Names may automatically renew at the end of their term (the expiration date) in accordance with the terms of the Registrant Agreement with the sponsoring Registrar. Renewal pricing to a Registrant is set by the sponsoring Registrar. The standard grace period fixed by ICANN policies shall apply to the renewal of Domain Names.

‍5. No Third-Level or Sub-Domains. A Registrant of a Domain Name is not permitted or authorized to, and shall not offer, sell, license, sublicense to any third party whatsoever any third-level domain names (i.e. what.domainname.vegas) or other sub-domains associated with or derived from the registered Domain Name, or to use such third-level or other sub-domains except where such use is restricted solely for use by Registrant in conjunction with its operation of the Domain Name.

‍6. Contact information. Registrants must provide accurate contact information in accordance with ICANN requirements, as amended from time to time including but not limited to the following: Registrant address and contact information, names and contact information for administrative, technical, and billing contacts. All contact data, except for billing contact data, will be displayed in the WHOIS. The use of proxy registration data or proxy registration contacts is permitted consistent with applicable ICANN policy and the Registry's agreements with ICANN, registrars, and the Registry's WHOIS Policy set forth hereafter.

‍7. Transfers. Unless otherwise specifically modified or limited by the Registry in Agreements relating to domain name registrations allocated in the Sunrise Period, certain Premium Domain Names or domain names designated as "Founders" or "Pioneer" domain names, Registrants are allowed to transfer their second-level domains to the registrar of their choice. Registrants should contact their registrar of choice to learn about transfer procedures. Registrar-to-registrar transfers are not allowed in the sixty (60) days following the registration of a domain name, unless the Registry expressly waives said sixty (60) day period as allowed by ICANN policies. Except in the case of bulk transfers of domain names from the sponsoring registrar to a receiving registrar mandated by ICANN, a registrar-to-registrar transfer adds one year to the term of the domain name being transferred, with the one (1) year registration fee charged to the gaining registrar. Registrars may therefore charge the Registrant for the additional domain year. A bulk transfer mandated by ICANN shall not add an additional year to domain names subject thereto, and the gaining registrar shall not be entitled to charge Registrants thereof for an additional domain year.

‍8. Grace periods. In accordance with published ICANN rules and policies, as amended from time to time, certain grace periods exist to allow for the cancellation of transactions by Registrars within certain time periods. The Registry will adhere to such grace periods as ICANN may publish from time to time.

‍9. Name server information. To register a .Vegas Domain Name, the Registrant does not need to provide nameserver information. However, in order to appear in the zone file and resolve on the Internet, at least two (2) valid name servers must be associated with the Domain Name.

‍10. Cancellations, suspension, transfers, and changes. The Registry reserves the right, in its sole discretion, to deny, cancel or transfer any Domain Name registration or transaction, or place any Domain Name(s) or other transactions on Registry lock, hold or similar status(i) to protect the integrity and stability of the Registry's systems; (ii) to comply with any applicable laws, government rules or requirements, requests of law enforcement, ICANN Policies or Registry Policies, or any dispute resolution process; (iii) during the resolution of a dispute; (iv) to avoid any liability, civil or criminal, on the part of the Registry, as well as its affiliates, subsidiaries, officers, directors, and employees; (v) in respect of the Registry only, for violations of the registry-registrar agreement between the applicable Registrar and the Registry (for example, non-payment of fees)including, without limitation, any exhibits, attachments, or schedules thereto;(vi) to correct mistakes made by the Registry in connection with a Domain Name registration; (vii) following an occurrence of any of the prohibited activities described in violation of the Registry's Anti-Abuse/Acceptable Use Policy, or(viii) as otherwise provided for by the Registrant Agreement. Furthermore, the Registry reserves the right at any time, to verify (ix) the truth, accuracy, and completeness of any information provided by the Registrant to the Registry, whether directly, through a Registrar or otherwise; and (x) the compliance by the Registrant with the applicable Registry Policies. Registrants agree to fully comply and cooperate with the Registry in connection with such verification and furnish all available documentation as the Registry may reasonably required to complete the verification.

‍11. Registration of ISO3166-1 Alpha 2 Standard Names. If the Registrant is registering a two-character ASCII name which is designated as a country code under ISO 3166-1 alpha-2 standard, Registrant agrees that Registrant will not in any way or manner whatsoever represent, infer or imply, directly or indirect, that Registrant or its business is affiliated with, endorsed or sponsored any government or country-code top level domain name manager. Any violation of this Section 11 shall constitute a material breach of these Registry Policies, specifically the Registry's Anti-Abuse/Acceptable Use Policy, and Registry shall be entitled to take such action against the Registrant and the domain name registration as described in Section 2 thereof.

3. SUNRISE REGISTRATION POLICY
‍
‍Dot Vegas, Inc. (the "Registry") will offer a Sunrise Period as a rights protection mechanism for qualifying mark holders before registration is made available to the general public. This Sunrise Period is designated as an "End-Date" Sunrise structure. This Sunrise Registration Policy (the "Policy") must be read in conjunction with other Registry Policies, and is also incorporated by reference into the Registry-Registrar Agreement and Registrar-Registrant Agreements associated with Domain Names registered in the .Vegas TLD("TLD") during the Sunrise Period.

‍1. Sunrise Registration Period. The Sunrise Period will commence at 19:00 hours UTC, June 2, 2014 and terminate at 19:00hours UTC, August 1, 2014. During the Sunrise Period, only those holders of SMD Files obtained through registration with the Trademark Clearing House will be authorized to submit Sunrise applications. Successful Sunrise registrations will be allocated in the TLD after the Sunrise Period concludes. All Sunrise Applications will be subject to the terms and conditions set forth herein, along with such other terms and conditions that may be found in applicable Registry policies, the Registry Agreement with ICANN, the Registry-Registrar Agreement with qualifying Registrars and the Registrant Agreement with registrants.

‍2. Application Process Overview. The following process applies to Sunrise applications: a) SMD Files submitted with Sunrise applications are validated by the Registry (or an agent designated by Registry to conduct validations of Sunrise applications). Sunrise applications missing a valid SMD File or containing an invalid SMD File will be rejected by the Registry. b) Domain names for which a valid Sunrise application has been received that (1) meet the Sunrise Registration eligibility criteria described herein and (2) were submitted in accordance with Registry policies, ICANN Requirements, and the Registry-Registrar Agreement, will be allocated to the applicant following the close of the Sunrise Period. c) If more than one Sunrise application for the same Domain Name Character String meet the eligibility criteria described herein, the Sunrise applications will be submitted to an auction provider designated by the Registry and the Domain Name will be awarded in accordance with applicable auction rules and procedures. d) Domain Names awarded to successful Sunrise applicants at auction will be allocated by the Registry following the conclusion of such auction and those Domain Names shall be subject to the terms of the Sunrise Registration registrant agreement.

‍3. Sunrise Application Fee and Domain Name Registration Fee Payments.

‍a. Application Fee. Each Sunrise application must be accompanied by a non-refundable Application fee fixed by the Registry and paid to the sponsoring Registrar for the applied-for Domain Name. Only those Sunrise applications which include payment of the Application fee will be accepted by the Registry.

‍b. Domain Name Registration Fee. Successful Sunrise Applicants must pay the designated Domain Name Registration Fee before allocation of the applied-for Domain Name to the applicant. This Registration Fee is in addition to the Sunrise Application Fee. In this regard, the Registry has designated certain Domain Names as 'Premium' Domain Names and have priced those Domain Names accordingly. Designated Premium Domain Names may also beheld by the Registry on its Reserved Domain Names List. All Domain Names that have NOT been designated as 'Premium' Domain Names or are not held on the Registry's Reserved Domain Names List are deemed non-premium or normal domain names. Sunrise applicants applying for a Domain Name that has been designated a 'Premium' Domain Name or which is being held on the Registry's Reserved Domains List must pay the Registration Fee for the applied-for Domain Name as may be fixed by the Registry.

‍c. Domain Name Renewals. The renewal price for Domain Names registered during the Sunrise Period will be set by the applicable Registrar sponsoring the Domain Name at the time of renewal. Renewal grace periods are fixed by the Registrant Agreement as well as the Registry's standard General Domain Name Registration Policy which can be found at http://www.nic.vegas or such other URL as the Registry may designate for its Registry Policies.

‍4. Auctions. If more than one Applicant submits a valid Sunrise application for the same Domain Name, the Registry will notify the applicable Registrar(s) at the end of the Sunrise Period. The prevailing Applicant for the Domain Name will be determined at an auction hosted by an auction provider of the Registry's choice (“Auction Provider”).The auction process will be governed by the terms and conditions published by the Auction Provider and available on the Registry Website (“Auction Rules”). Registration Fees for 'Premium' Domain Names and Reserved Domain Names as set by the Registry shall be deemed the 'minimum bid' for Domain Names subject to auctions here under. Domain Names awarded to successful Sunrise applicants at auction will be allocated by the Registry, typically within seven (7) days of notification from the Auction Provider that the auction has concluded and the Registration Fees have been paid.

‍5. Limitations on Transfer of 'Premium' Domain Names. In accordance with the terms of the Sunrise Registration registrant agreement, Domain Names registered in the Sunrise Period which the Registry has deemed to be 'Premium' Domain Names or which may be on the Reserved Domain Names List at the time of registration may not be transferred by the Registrant to any party (including any natural person, company, organization,subsidiary or affiliate company of the Registrant) during the initial registration term except in those instances where such Domain Name(s) are included as part of a sale or acquisition of all or substantially all of the business or other operations of the Registrant. The Registry reserves the right to require the Registrant to produce such documentation of the sale or acquisition transaction which evidences compliance with this condition to transfer.

‍6. Processing Sunrise Registrations. The Registry will not process a Sunrise Application unless the Registry has: (a) validated the SMD File with the TMCH, and (b) received, or has, in its discretion, reasonable assurance of payment from the Registrar of all applicable fees, including the registration fee and the non-refundable, one-time Sunrise Application fee for the Sunrise Application.

‍7. TMCH, SMD Files, and Domain Name Character String Requirements. Sunrise Applications may only be submitted by a Registrar sponsoring the Sunrise applicant and must include an SMD File corresponding to the Domain Name Character String.

‍8. Eligible Applicants. Each applicant must meet the qualifications specified by ICANN requirements and detailed in the TMCH Guidelines, as amended from time to time.

‍9.SMD File Requirements. The applicant must submit a valid SMD File along with its Sunrise application.

‍10.Registration. The Registry will create a Domain Name registration and allocate the Domain Name to the Applicant if: (a)The Domain Name meets the requirements set forth in the TLD's General Domain Name Registration Policy; (b) The Domain Name and the information contained in the Registrar’s request meet the requirements in the Registry-Registrar Agreement; (c) The Domain Name is available; (d) The applicant is eligible to register the applied-for Domain Name; (e) The required Sunrise Application Fee and designated Registration Fee have been paid to the sponsoring Registrar; and (f) The sponsoring Registrar is in good standing with the Registry.

‍11. Sunrise Applicant Notification. Notification to Sunrise applicants will be as follows: (a) At the end of the Sunrise Period, the Registry will notify Registrars who sponsored a Sunrise application of applicable Sunrise Registration allocations. (b) In the event two or more Sunrise applications are received for the same Domain Name, the Registry will notify the Registrar(s) who sponsored such Sunrise applications and advise them of the impending auction for the Domain Name. (c) Registrars receiving notice of a pending auction must pass on such notice to their Sunrise applicants. (d) At the conclusion of an auction for a Domain Name, the sponsoring Registrar(s) for Sunrise applications will receive a message informing which Sunrise application prevailed in the auction and was allocated the Domain Name and which application lost in the auction. (e) The Registry will notify theTMCH of successful Sunrise applications once the corresponding Sunrise Registration has been made. The Registry may also publish all or any portion of a pending Sunrise Application online (e.g., via Whois).

‍12. The Registry’s Rights regarding Sunrise Applications and Registrations: The Registry reserves the right, in its sole discretion, to deny, cancel, modify or transfer any Domain Name registration or transaction, or place any Domain Name(s) or other transactionson Registry lock, hold or similar status (i) to protect the integrity and stability of the Registry's systems; (ii) to comply with any applicable laws, government rules or requirements, requests of law enforcement, ICANN Policies or Registry Policies, or any dispute resolution process; (iii) during the resolution of a dispute; (iv) to avoid any liability, civil or criminal, on the part of the Registry, as well as its affiliates, subsidiaries, officers, directors, and employees; (v) in respect of the Registry only, for violationsof the Registry-Registrar agreement between the applicable Registrar and the Registry (for example, non-payment of fees) including, without limitation, any exhibits, attachments, or schedules thereto; (vi) to correct mistakes made by the Registry in connection with a Domain Name registration; (vii) following an occurrence of any of the prohibited activities described in violation of the Registry's Anti-Abuse/Acceptable Use Policy, (viii) to require that any Sunrise applicant filing a dispute or other action contesting the Registry's Sunrise Registration or Sunrise Dispute Policy deposit with the Registry a minimum of $20,000 but not more than $50,000 to cover all costs incurred by the Registryin the event the Sunrise applicant is not successful in receiving a decision awarding the relief sought in such dispute or contest action; or (ix) as otherwise provided for by the applicant's or Registrant's Registrant Agreement. Furthermore, the Registry reserves the right at any time, to verify(x) the truth, accuracy, and completeness of any information provided by the Registrant to the Registry, whether directly, through a Registrar or otherwise; and (xi) the compliance by the Registrant with the applicable RegistryPolicies. Registrants agree to fully comply and cooperate with the Registry in connection with such verification and furnish all available documentation as the Registry may reasonably required to complete the verification.

‍4. SUNRISE DISPUTE RESOLUTION POLICY

1. Scope and Purpose. The Registry has developed and adopted this Sunrise Dispute Resolution Policy ("SDRP") which must be read in conjunction with the other Registry policies, and is also incorporated by reference into the Registry-Registrar Agreement and Registrar-Registrant Agreements associated with Domain Names registered in the .Vegas TLD("TLD"). This SDRP describes the process and standards that will be applied to resolve challenges alleging that a domain name has been improperly registered, or has been declined to be registered, in violation of the Registry’s SDRP criteria. This SDRP will not be applied to Domain Names designated as 'Premium' Domain Names or which are held on the Registry's Reserved Domain Names List. Registry has implemented an End-Date Sunrise meaning that applications for the registration of Domain Names will be accepted for a period of 60 days from the commencement date of the Sunrise Registration Period, but will not be registered to Applicants until said 60 day period has expired and verification procedures completed. Additionally, in the event more than one registration application is submitted for the same Domain Name, the conflict will be resolved through an auction process between the submitting Applicants as set forth hereafter. Any challenges initiated under the SDRP must be initiated prior to the close of the Sunrise Registration Period.

‍2. Definitions. In this SDRP, the following words and phrases shall have the following meanings: (a) Dot Vegas Website.www.nic.vegas/policies/sdrp or such other URL designated by the Registry as its primary registry website. (b) Complainant. A person (legal ornatural) who makes a complaint under the SDRP. (c) Identical Match. The Domain Name label is an identical match to the trademark, meaning that the label consistsof the complete and identical textual elements of the mark in accordance with section 4.2.1 of the TMCH Guidelines. In this regard: 1. For a trademark exclusively consisting of letters, words, numerals and/or special characters: the recorded name of the mark is an identical match to the reported name as long as all characters are included in the trademark record provided to the TMCH and in the same order in which they appear on the trademark certificate. 2. For marks that do not exclusively consist of letters, words, numerals, or special characters: the recorded name of the trademark is an identical match to the reported name aslong as the name of the trademark includes letters, words, numerals, keyboard signs, and punctuation marks that are: (i) predominant, (ii) clearly separable or distinguishable from the device element, and (iii) all predominant characters are included in the trademark record submitted to the TMCH in the same order they appear in the mark. (c) Panel or Panelist. The person or organization appointed by the Provider to provide a written decision in relation to the dispute arising under this SDRP. Dot Vegas Inc has contracted with the National Arbitration Forum (http://domains.adrforum.com/). (d) Provider. The dispute resolution provider appointed by the Registry as to administer resolution of disputes arising under this SDRP. (e) Respondent. The applicant or registrant of the Domain Name(s) subject to a complaint under this SDRP. (f) SMD File. A signed mark datafile issued by the TMCH signifying that the TMCH has verified that the trademark contained in the SMD File meets the requirements for inclusion in theTMCH in accordance with TMCH Guidelines in force at the time when a complaint under this SDRP is filed. (g) Sunrise Period. That period of time during which holders of SMD Files may submit domain name applications for a Domain Name before registration becomes available to the general public. (h) TMCH. Trademark Clearinghouse (http://www.trademark-clearinghouse.com) (i) TMCH Guidelines. Guidelines published by the TMCH for mark holders and agents to inform them about the eligibility requirements for inclusion of marks in the TMCH and Application insunrise services.

‍3. Relation to Other Dispute Resolution Policies. Disputes regarding the validity of an SMD File are subject to a separate TMCH dispute process and should be submitted to the TMCH using the dispute resolution procedures outlined in http://trademark-clearinghouse.com/dispute prior to the initiation of acomplaint under the SDRP. In the event the TMCH issues a finding of a non-compliant SMD File, the Registry may disqualify the Sunrise application or, in the event that non-compliance is detected after the Sunrise period, delete the applicable domain name(s). The SDRP is in addition and complimentary to ICANN's Uniform Domain Name Dispute Resolution Policy("UDRP"), the Uniform Rapid Suspension System ("URS"), and any other applicable charter, nexus or eligibility dispute policies implemented by ICANN or the Registry. The SDRP shall not prevent any party from submitting a dispute concerning the Domain Name in the TLD to concurrent administrative proceedings or to a court of competent jurisdiction for independent resolution during the pendency of a SDRP proceeding. The SDRP may be terminated (in the sole discretion of the Panel as to the competence of such jurisdiction) indeference to the outcome of such other proceeding.

‍4. Applicable Disputes. A registered Domain Name will be subjectto an administrative proceeding upon submission of a complaint that the Sunrise Registration was improper under the following criteria. (a) Improper Sunrise Registration-Trademarks: A Complainant under this section shall be required to show by reasonable evidence that a registered Domain Name does not comply with the provisions of the Registry’s Sunrise Policies. The complaint must prove one or more of the following elements: i) at time the challenged Domain Name was registered, the registrant did not hold a trademark registration of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty. (Applicant Guidebook, 4 June2012, Module 5, Page 8, Article 6.2.4). A dispute under this section also addresses the TLD criteria from the TMCH Rights Protection Mechanism Requirements [published 30 September 2013], Article 2.3.6 and Article2.3.1.4.This SDRP does not interact with (nor instruct) the TMCH and is limited to adjudicating disputes over the Registry’s registration and allocation of Domain Names during the Sunrise Period; ii) the challenged Domain Name is not an Identical Match to the mark on which the registrant based its Sunrise registration. For the purposes of analysis of this element, neither the TLD itself, nor the “dot,” shall be considered; or iii) the trademark registration on which the registrant based its Sunrise registration is not of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty. (b) SDRP Effective Dates. Any SDRP claim brought under this Policy for Domain Names registered in the TLD shall be brought before the expiration of the Sunrise Period.

‍5. Evidence and Defenses. (a) Evidence. Panelists will review the Registry’s Sunrise criteria or allocation requirements as well as the SMD File and other relevant evidence, which are required to be submitted with the complaint, as applicable, in making its decision. (b) Defenses including Harmless error. A Respondent may produce evidence to show that, although the Sunrise registration was granted or based on submission of the wrong documents, or documents containing an error, the true and correct evidence existed at the time the Sunrise registration was applied for and, thus, the registration would have been granted.

‍6. Remedies. The remedies available to a Complainantfor a proceeding under this SDRP shall be limited to the cancellation of theregistration and return of the cancelled Domain Name to the pool of availablenames available for registration in the TLD.If the Complainant independently qualifies to register the Domain Name, either as a regular or defensive/blocking registrant, such application may be made to the Registry, or registrar, as applicable. In the event that one party to a Sunrise auction desires to bring a complaint under this SDRP against an opposing party to the same auction, the Registry will stop that auction process to allow resolution of a complaint under this Policy, if the Complainant notifies the Registry within the five (5) calendar days following the Registry’s notification of auction regarding the relevant Domain Name(s). Such notice must be in writing. The SDRP complaint shall be filed with the Provider within five (5) calendar days of the written notice. If the SDRP Complaint is not filed, the auction shall proceed as scheduled.

‍7. Procedure. (a) Dispute Resolution Provider /Selection of Procedure. A Complaint under this SDRP shall be submitted to the Provider by submitting the complaint directly to the Provider. The Provider will administer the proceeding and select a qualified and eligible Panel. The Complainant and Respondent will be bound by the rules and procedures of the Provider setting forth a fee schedule and other technical and process requirements for handling a dispute under this SDRP and the proceedings under this SDRP will be conducted accordance with this SDRP and the Providers rules and procedures. (b) Registry’s or Registrar’s Involvement. Neither the Registry nor sponsoring registrar will participate in the administration or conduct of any proceeding before a Panelist. In any event, neither the Registry nor the sponsoring registrar is or will be liable as aresult of any decisions rendered by the Panelist. Any Sunrise registered Domain Names involved in a SDRP proceeding will be locked against transfer to another domain name holder or another registrar during the course of a proceeding. The contact details of the holder of a registered Domain Name, against which acomplaint has been filed, will be as shown in the registrar’s publiclyavailable Whois database record for the relevant registrant. The Registry and the applicable registrar will comply with any Panelist decision and make all appropriate changes to the status of the Domain Name registration(s) in their Whois databases. (c) Parties. The Respondent shall be promptly notified by the Provider of the commencement of a dispute under this SDRP, and may contest the allegations of the complaint or show other cause why the remedy requested in the complaint should not be granted in accordance with this SDRP. In all cases, the burden of proof shall be on the Complainant, and default or other failure of the holder of the registered Domain Name shall not constitute an admission to any allegation of the complaint. The Provider shall promptly notify all named parties in the dispute, as well as the registrar and the Registry of any decision made by a Panelist. (d) Decisions. (i) The Panelist may state the basis on which the decision is issued in summary format and may include such commentary or guidance as the Panelist deems appropriate;(ii) the decision shall statewhether a registered Domain Name is to be cancelled or the status quo maintained; and(iii) decisions made under this SDRP will be publicly published by the Provider on its website. (e) Implementation of a Lock and the Decision. If a Panelist’s decision requires a change to the status of a registered Domain Name, the Registry will wait ten (10) business days after communication of the decision before implementing that decision, unless the registrant submits to the Registry (with a copy to the Provider) during that ten (10) day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that the registrant has commenced a lawsuit to preserve its claimed rights in a court of competent jurisdiction over the parties and the registered Domain Name. If such documentation is received, no further action shall be taken until the Registry receives (i) evidence satisfactory to the Registry of an agreed resolution between theparties; (ii) evidence satisfactory to Registry that registrant’s lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing such lawsuit or otherwise directing disposition of the registered Domain Name. A Registry may, through its agreement with registrars, require the registrar to perform the lock and/or implementation steps. (f) Representations and Warranties. Parties to a dispute under this SDRP shall warrant that all factual allegations made in the course thereof are true and correct to the best of their knowledge, and shall remain subject to all representations and warranties made in the course of registration of a disputed Domain Name.

‍8. Maintaining the Status Quo. During a proceeding under the SDRP, the registered Domain Name shall be locked against transfers between registrants and/or registrars and against deletion by registrants.

‍9. Indemnification/HoldHarmless. The parties shall hold the registrar, the Registry, the Provider, and the Panelist harmless from any claim arising from operation of the SDRP. Neither party may name the registrar, the Registry, the Provider, or the Panelist as a party or otherwise include the registrar, the Registry, the Provider, or the Panelist in any judicial proceeding relating to the dispute or the administration of the Policy. The parties shall indemnify, defend and hold harmless the registrar, theRegistry, the Provider, the Panelist and their respective employees, contractors, agents and service providers from any claim arising from the conduct or result of a proceeding under this SDRP. Neither the registrar, the Registry, Provider, the Panelist and their respective employees, contractors, agents and service providers shall be liable to a party for any act or omission in connection with any administrative proceeding under this SDRP or the corresponding rules of the Provider. The Complainant shall be directly and solely liable to the registrant in the event the complaint is granted incircumstances where the registrant is lawfully entitled to registration and use of the registered Domain Name(s).

‍10. Effect of Other Proceedings. The administrative proceeding under the SDRP shall not prevent either party from submitting a dispute concerning the registered Domain Name to concurrent administrative proceedings or to a court of competent jurisdiction for independent resolution during a pending SDRP administrative proceeding or after such proceeding is concluded. Upon notice of such other proceeding, the SDRP proceeding may be terminated (in the sole discretion of the Panelist) in deference to the outcomeof such other proceeding.

‍11. SDRP Modifications. Registry reserves the right to modify this SDRP at any time subject to the terms of its Agreement with the Provider. Such revised SDRP shall be posted on the Registry's Website at least thirty (30)calendar days before it becomes effective unless this SDRP has already been invoked by the submission of a complaint, in which event the version of theSDRP in effect at the time it was invoked will apply until the dispute is concluded. In the event that Respondent objects to a change in this SDRP, the sole remedy is to cancel the registration, provided that Respondent will not beentitled to a refund of any fees paid in connection with such registration.

5.LANDRUSH POLICY

‍The Registry has developed and adopted this Landrush Policy which is to be read together with the other Registry policies, and is also incorporated by reference into the Registry-Registrar Agreement and Registrant Agreements associated with Domain Names registered in the .Vegas TLD ("TLD"). All words and phrases used in this Policy shall have the same meaning attributed to them in the Registrant Agreement unless otherwise specified or the context clearly otherwise requires. Please note that the Registry may modify this Policy from time to time and such modifications shall be effective upon thirty (30) days notice by the Registry to interested parties including sponsoring registrars. Such changes will be available on the Registry website at http://www.nic.vegas or such other URL as the Registry may designate, which shall satisfy all notice requirements set forth in this Policy. After the notice period expires, each time a user accesses or uses the Services, the user will be bound by the then effective Landrush Policy.

PLEASE READ THIS POLICY CAREFULLY. BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BE BOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE. IF THE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.

‍1.Landrush Overview.Landrush is a limited-time opportunity forthose Domain Name applications who don’t qualify for Sunrise registration, butwant to secure a valued .Vegas Domain Name, and avoid first come, first servedgeneral availability registration.Landrush is open to members of the generalpublic and there are no qualification requirements needed to participate inthis phase.Landrush will run forapproximately twenty-eight (28) days beginning at 19:00 hours UTC on August 14,2014 and terminate at 19:00 hours UTC on September 10, 2014.During this limitedperiod, anyone may apply for .Vegas Domain Names, as an expression ofinterest.This phase is designed to offer any potential registrant theopportunity to obtain a desired Domain Name.At the end of the Landrush period,those applied-for Domain Names with a single eligible Applicant will beautomatically allocated to such sole Applicants.However, those Domain Nameswith more than one eligible Applicant will proceed to a closed auction betweenthe competing Applicants.2.Scope and Eligibility.An Applicant may submit applications inthe form provided by qualified registrars for any available Domain Names,meaning names that have not been (a) blocked, reserved or restricted by theRegistry, or (b) registered, awarded, or otherwise allocated prior tocommencement of the Landrush Period.As part of the Landrush application, theRegistry may request certain information about the Applicant, including withoutlimitation, name and contact information and other Whois information requiredby the Registry's agreement with ICANN, the Registry-Registrar Agreement or theRegistry's General Domain Name Registration policies.In order to be eligible to registerDomain Names during the Landrush Period, Applicants must identify the DomainName applied for, submit a completed application, and remit the LandrushApplication fee as more fully described below.3.Allocation. The Landrush available Domain Nameswill be allocated under the following conditions:a.At the end of the LandrushPeriod, the Registry will approve the Landrush application for an availableDomain Name submitted by an eligible Applicant where it is the sole applicationfor the specified Domain Name;b.At the end of the Landrushperiod, if more than one Landrush application is received for the identicalavailable Domain Name, the requests will be submitted to the Registry’s thirdparty auction provider who will conduct an auction to determine which Applicantwill be permitted to register the contested Domain Name.Domain Names awarded toeligible uncontested Applicants will be permitted to resolve followingconclusion of the Landrush period, and concurrent with the launch of thegeneral availability phase of the TLD launch.Domain Names awarded to theprevailing Applicant in a Landrush Auction will be permitted to resolvepursuant to the auction rules, as more fully described below;c.If the Domain Name CharacterString meets the requirements set forth in the Registry's General Domain NameRegistration Policies;d.The Domain Name and theinformation contained in the Registrar’s request meet the requirements in theRegistrar Terms and Conditions;e.The required Landrushapplication fee and Landrush Domain Registration Fee have been paid to thesponsoring Registrar; andf.The sponsoring Registrar is ingood standing with the Registry.4.Fees. Fees that may be collected during theLandrush Period include:a.Landrush domain registrationfee (except in the case of Landrush Auctions) – Varies per registrarb.Non-refundable application feefor each Domain Name applied for - $110c.In the case of a LandrushAuction, the winning auction bid amount5.Renewal Fees.The renewal price for Domain Namesregistered during the Landrush Period will be set by the applicable Registrarsponsoring the Domain Name at the time of renewal.Renewal grace periods andother terms of renewal are fixed by the Registrant Agreement as well as theRegistry's standard Domain Name Registration Policy which can be found at http://www.nic.vegas or such other URL as the Registrymay designate for its Registry Policies.6.Auctions.If multiple Applicants apply to registeran identical Domain Name during the Landrush Period, conflicting applicationswill be settled by an auction conducted by the Registry’s third party auctionprovider.Competing Applicants are not obliged to participate in an auction;instead, an Applicant may chose to withdraw its Landrush application.The finalauction price must be paid to the Auction Provider prior to allocation of theDomain Name.For full auction rules see www.namejet.com.The outcome of any auction shallbe deemed final and binding upon the parties.A party that either loses anauction or withdraws its Landrush application will not receive a refund of itsApplication fee which is non-refundable.7.Landrush Period DisputePolicy.Registry willnot participate in any way in any dispute between Landrush Period Applicantsand any party other than the Auction Provider, and in that case solelyregarding the use of the auction platform.All other disputes between LandrushPeriod Applicants and any other party shall be resolved between the applicableApplicant and such other party through any court, arbitration or otherproceeding that may be available to those parties.The Auction Provider provides anauction platform for registries to provide a mechanism through which competingapplications for Domain Names may be resolved during the Landrush Periodincluding through auctions.The Auction Provider has been appointed by theRegistry and the Auction Provider's terms of service, which are herein incorporatedinto this Policy by reference, will govern and control over any dispute whichmay arise during any of the auction processes.The Auction terms and conditionsare published by the Auction Provider and must be accepted before bidding canoccur in any auction for any Domain Names.8.The Registry’s Rightsregarding Landrush Applications and Registrations:The Registry reserves the right, in itssole discretion, to deny, cancel, modify or transfer any Domain Nameregistration or transaction, or place any Domain Name(s) or other transactionson Registry lock, hold or similar status (i) to protect the integrity andstability of the Registry's systems; (ii) to comply with any applicable laws,government rules or requirements, requests of law enforcement, ICANN Policiesor Registry Policies, or any dispute resolution process; (iii) during theresolution of a dispute; (iv) to avoid any liability, civil or criminal, on thepart of the Registry, as well as its affiliates, subsidiaries, officers,directors, and employees; (v) in respect of the Registry only, for violationsof the Registry-Registrar agreement between the applicable Registrar and theRegistry (for example, non-payment of fees) including, without limitation, anyexhibits, attachments, or schedules thereto; (vi) to correct mistakes made bythe Registry in connection with a Domain Name registration; (vii) following anoccurrence of any of the prohibited activities described in violation of theRegistry's Anti-Abuse/Acceptable Use Policy, or (viii) as otherwise providedfor by the Applicant's or Registrant's Registrant Agreement.Furthermore, theRegistry reserves the right at any time, to verify (ix) the truth, accuracy,and completeness of any information provided by the Registrant to the Registry,whether directly, through a Registrar or otherwise; and (x) the compliance bythe Registrant with the applicable Registry Policies.Registrants agree to fullycomply and cooperate with the Registry in connection with such verification andfurnish all available documentation as the Registry may reasonably required tocomplete the verification.

‍6. RESERVED AND PREMIUM DOMAIN NAMES POLICY

‍The Registry has developed andadopted this Reserved and Premium Name Policy which is to be read together withother Registry policies related both to the launch and ongoing administrationand management of the .Vegas top-level domain ("TLD") and theRegistrant Agreement.All words and phrases used in this Policy shall have thesame meaning attributed to them above or in the Registrant Agreement unlessotherwise specified or the context clearly otherwise requires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in thisPolicy.After the notice period expires, each time a user accesses or uses theServices, the then effective Reserved and Premium Domain Names Policy will bindthe user.PLEASE READ THIS POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.

‍1.Reserved Domain Names.A list of Reserved Domain Names has beencreated by the Registry and designated for Registry operations and use,including placement with one or more individuals, entities or organizationsthat are deemed 'founders' or 'pioneers' and other promotional activitiesconducted by the Registry.This list may also include certain Domain Names thatare reserved and restricted from registration by the public to comply withICANN policies and requirements.The Registry reserves the right to change,modify, delete or add Domain Names to the Reserved Domain Names List from timeto time in the Registry's sole discretion and without prior notice.2.Premium Domain Names.A list of Premium Domain Names has beencreated and reserved by the Registry due to their high worth andpopularity.These names will be made available for registration at various timesthrough participating Registrar channels, including through one or more premiumnames auctions, 'buy it now' offerings, and other distribution methodologies asthe Registry may decide to pursue in its sole discretion.The Registry reservesthe right to change, modify, delete or add Domain Names to the Premium DomainNames list from time to time in the Registry's sole discretion and withoutprior notice.Registrars may request the Reserved Domain Names list and PremiumDomain Names list from their Registry account manager.3.Allocation.Premium Domain Names will be allocated toRegistrants under the following conditions:a.In the case of Premium DomainNames that are registered through an authorized auction provider for which theauction bid price has been paid by the Registrant in accordance with the rulesof the sponsoring auction provider, such Domain Names will be permitted toresolve immediately if the general availability phase of the TLD launch hascommenced, and if general availability registration has not commenced, thenconcurrent with the launch of that phase;b.In the case of Premium DomainNames that are registered through an authorized Registrar pursuant to 'buy itnow' or other methodology for which the designated price has been paid by theRegistrant in accordance with the rules of the sponsoring Registrar, suchDomain Names will be permitted to resolve immediately if the generalavailability phase of the TLD launch has commenced, and if general availabilityregistration has not commenced, then concurrent with the launch of that phase;c.The Premium Domain Name meetsthe requirements set forth in the Registry's General Domain Name RegistrationPolicies;d.The Premium Domain Name and theinformation contained in the Registrar’s request meet the requirements in theRegistrar Terms and Conditions; ande.The required DomainRegistration Fee has been paid to the sponsoring Registrar; andf.The sponsoring Registrar is ingood standing with the Registry and has appropriate access. As used in this paragraph 3, theterm allocated or allocation means that a registration for a Domain Name iscreated, registered to the Registrant and permitted to resolve in the .Vegaszone of the DNS.4.Fees. Fees that may be collected for PremiumDomain Name registrations are:a.For Premium Domain Namesauctions, the winning auction bid amount.b.For 'buy-it-now' and otherregistration methodologies authorized by the Registry, the price fixed by thesponsoring Registrar.This amount may vary in accordance with various factors,including relevant valuations determined by the Registrar in consultation withthe Registry.c.For 'founders', ''pioneer' orRegistry designated promotional registrations, the consideration agreed tobetween the Registry and the applicable Registrant.5.Renewal Fees.The renewal price for Premium Domain Nameswill be set by the applicable Registrar sponsoring the Domain Name at the timeof renewal.Renewal grace periods and other terms of renewal are fixed by theRegistrant Agreement as well as the Registry's standard Domain NameRegistration Policy which can be found at http://www.nic.vegas or such other URL as the Registrymay designate for its Registry Policies.For 'founders', ''pioneer' or Registrydesignated promotional registrations, the consideration agreed to between theRegistry and the applicable Registrant as set forth in its RegistrantAgreement.6.Use Requirements for"Founder" or "Pioneer" Domain Names.In addition to and except as modified bythe provisions of the Registrant Agreement executed with the applicableRegistrant, Registrants of 'founder', 'pioneer' or other Domain Namesregistered in conjunction with promotional activities conducted by the Registryshall comply with the following minimum use and registration requirements:a.Registrant will operate theDomain Name(s) only for lawful purposes and not in violation of published ICANNand Registry policies. b.Except as required hereafter,Registrant will be solely responsible for and control all content, commerce,and use of the designated Domain Names.All cost associated with thedevelopment, maintenance and operation of the websites associated with theDomain Name(s) shall be borne by Registrant.c.Registrant acknowledges andagrees that the Domain Names are intended to be 'founder', 'pioneer' orpromotional domain names for the .Vegas TLD.As a result, during the term ofregistration of each Domain Name, Registrant will operate an active, functionalwebsite associated therewith capable of transacting commercial business,providing educational or similar information, or offering products and servicesfor purchase or subscription by the end user thereof.'Parked pages' or similarwebsites producing revenue primarily from CPC, CPM, CPA, or affiliate marketingactivities shall not be deemed "active, functional websites capable oftransacting commercial business, providing educational or similar information,or offering products and services for purchase or subscription by the end userthereof."Notwithstanding the foregoing, a compliant website associatedwith a Domain Name may be used to redirect end user traffic to one or morewebsites of Registrant designed to be the primary site or sites for thetransaction of commercial business provided such primary site or sites shall bea website using a .Vegas URL.Registrant shall not redirect end user traffic orpotential commercial transactions with end users accessing a registeredreserved name to any website or domain address which does not use a .VegasURL. d.Registrant is not permitted orauthorized to, and will not offer, sell, license, sublicense to any third partywhatsoever any third-level domain names (i.e. what.domainname.vegas) or othersub-domains associated with or derived from the Domain Name(s), or to use suchthird-level or other sub-domains except where such use is restricted solely forinternal use by Registrant in conjunction with its operation of the DomainName(s).e.Registrant will usecommercially reasonable efforts to actively promote and market the website(s)associated with the Domain Name(s) to end users worldwide, using such means andmethodologies as Registrant deems appropriate to establish and brand thewebsite(s).f.Registrant will not sell or otherwisetransfer rights in or to the Domain Name(s) to any 3rd party orfrom registrar to registrar for the greater of (i) 12 months from theregistration date, and (ii) the initial registration term.7.The Registry’s Rightsregarding Premium Domain Name Applications and Registrations:The Registry reserves the right, in itssole discretion, to deny, cancel, modify or transfer any Domain Nameregistration or transaction, or place any Domain Name(s) or other transactionson Registry lock, hold or similar status (i) to protect the integrity andstability of the Registry's systems; (ii) to comply with any applicable laws,government rules or requirements, requests of law enforcement, ICANN Policiesor Registry Policies, or any dispute resolution process; (iii) during theresolution of a dispute; (iv) to avoid any liability, civil or criminal, on thepart of the Registry, as well as its affiliates, subsidiaries, officers,directors, and employees; (v) in respect of the Registry only, for violationsof the Registry-Registrar agreement between the applicable Registrar and theRegistry (for example, non-payment of fees) including, without limitation, anyexhibits, attachments, or schedules thereto; (vi) to correct mistakes made bythe Registry in connection with a Domain Name registration; (vii) following anoccurrence of any of the prohibited activities described in violation of theRegistry's Anti-Abuse/Acceptable Use Policy, or (viii) as otherwise providedfor by the Applicant's or Registrant's Registrant Agreement.Furthermore, theRegistry reserves the right at any time, to verify (ix) the truth, accuracy,and completeness of any information provided by the Registrant to the Registry,whether directly, through a Registrar or otherwise; and (x) the compliance bythe Registrant with the applicable Registry Policies.Registrants agree to fullycomply and cooperate with the Registry in connection with such verification andfurnish all available documentation as the Registry may reasonably required tocomplete the verification.7.GENERAL AVAILABILITYREGISTRATION POLICYThis General AvailabilityRegistration Policy (“Policy”) of Dot Vegas, Inc. (the “Registry”) is to beread together with other Registry policies related both to the launch andongoing administration and management of the .Vegas top-level domain("TLD") and the Registrant Agreement.All words and phrases used inthis Policy shall have the same meaning attributed to them above or in theRegistrant Agreement unless otherwise specified or the context clearly otherwiserequires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in thisPolicy.After the notice period expires, each time a user accesses or uses theServices, the then effective General Availability Registration Policy will bindthe user.PLEASE READ THIS POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.1.General AvailabilityOverview.After theclose of a designated quiet period from September 10, 2014 to September 15,2014, the TLD will be open for registration of Domain Names at 19:00 hours UTCSeptember 15, 2014 through Registrars on a first-come, first-served basis,subject to the Registry Policies and ICANN requirements.All available DomainNames will be open for such registration.The general availability phase will nothave an ending date.2.Scope and Eligibility.An Applicant may submit applications inthe form provided by qualified Registrars for any available Domain Names,meaning names that have not been (a) blocked, reserved or restricted by theRegistry, or (b) registered, awarded, or otherwise allocated prior tocommencement of the General Availability Phase.3.Registration. The General Availability Phaseavailable Domain Names will be registered by a sponsoring Registrar submittingan Applicant's application for an available Domain Name for registrations.TheRegistry will create (or modify as the case may be) a Domain Name registrationif the following conditions are met:a.the Domain Name meets therequirements set forth in the Registry's General Domain Name RegistrationPolicy;b.the Domain Name and theinformation contained in the Registrar’s request meet the requirements in theRegistry-Registrar Agreement;c.the applied-for Domain Name isavailable for registration;d.the required DomainRegistration Fees have been paid to the sponsoring Registrar; andf.the sponsoring Registrar is ingood standing with the Registry.4.Fees. The only fee that may be collected duringthe General Availability Phase is the Domain Registration fee as fixed by thesponsoring Registrar.5.Renewal Fees.The renewal price for Domain Namesregistered during General Availability will be set by the applicable Registrarsponsoring the Domain Name at the time of renewal.Renewal grace periods andother terms of renewal are fixed by the Registrant Agreement as well as theRegistry's standard Domain Name Registration Policy which can be found at http://www.nic.vegas or such other URL as the Registrymay designate for its Registry Policies.6.General AvailabilityDispute Policy.TheRegistry will not participate in any way in any dispute between Domain NameApplicants and any party.Rather, all other disputes between Applicants and anythird party shall be resolved between the applicable Applicants and such otherparty through any court, arbitration or other proceeding that may be availableto those parties.At such time as a Domain Name has been registered andallocated to a Registrant, the Registry's Dispute Resolution Policy will governall disputes between the Applicant and third parties thereafter. Said DisputeResolution Policy can be found at http://www.nic.vegas or such other URL as the Registrymay designate for its Registry Policies.7.The Registry’s Rightsregarding General Availability Applications and Registrations:The Registry reserves the right, in itssole discretion, to deny, cancel, modify or transfer any Domain Nameregistration or transaction, or place any Domain Name(s) or other transactionson Registry lock, hold or similar status (i) to protect the integrity andstability of the Registry's systems; (ii) to comply with any applicable laws,government rules or requirements, requests of law enforcement, ICANN Policiesor Registry Policies, or any dispute resolution process; (iii) during theresolution of a dispute; (iv) to avoid any liability, civil or criminal, on thepart of the Registry, as well as its affiliates, subsidiaries, officers,directors, and employees; (v) in respect of the Registry only, for violationsof the Registry-Registrar agreement between the applicable Registrar and theRegistry (for example, non-payment of fees) including, without limitation, anyexhibits, attachments, or schedules thereto; (vi) to correct mistakes made by theRegistry in connection with a Domain Name registration; (vii) following anoccurrence of any of the prohibited activities described in violation of theRegistry's Anti-Abuse/Acceptable Use Policy, or (viii) as otherwise providedfor by the Applicant's or Registrant's Registrant Agreement.Furthermore, theRegistry reserves the right at any time, to verify (ix) the truth, accuracy,and completeness of any information provided by the Registrant to the Registry,whether directly, through a Registrar or otherwise; and (x) the compliance bythe Registrant with the applicable Registry Policies.Registrants agree to fullycomply and cooperate with the Registry in connection with such verification andfurnish all available documentation as the Registry may reasonably require tocomplete the verification.8.WHOIS POLICYThe Registry has developed andadopted this WHOIS Policy which is to be read together with other Registrypolicies and the Registrant Agreement.All words and phrases used in this Policyshall have the same meaning attributed to them in the Registrant Agreementunless otherwise specified or the context clearly otherwise requires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in thisPolicy.After the notice period expires, each time a user accesses or uses theServices, the then effective WHOIS Policy will bind the user.PLEASE READ THIS POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.1.Thick WHOIS.The Registry will include a thick WHOISdatabase both accessible on port 43 as well as on port 80 (http) as required inSpecification 4 of the Registry's ICANN Registry Agreement (“RegistryAgreement”).The WHOIS service is a standardfeature of domain name systems, and offers domain name and registrant dataavailable for members of the public to view or use.WHOIS comprises the recordassociated with a specified domain name.The purpose of the WHOIS service is toallow users to query a domain name to find out the identity and/or contactdetails of the registrant.2.ICANN requirements.The WHOIS data will be held by theRegistry in accordance with its Registry Agreement.The Registry will alsocomply with all the security, WHOIS, and privacy requirements required by ICANNwhether in the Consensus or Temporary Policies (as defined in the RegistryAgreement) or elsewhere. Where there is a conflict in a Registrant's agreementwith a registrar, or a registrar’s agreement with the Registry, and any ICANNrequirement on data, WHOIS and privacy, whether or not in force at the date ofthe respective agreement, the relevant ICANN requirements will prevail.3.Safeguarding securityand privacy.Uponregistration of a Domain Name and Registrant's execution of a RegistrantAgreement, the Registry may collect and utilize information and other datarequired to operate the Domain Name system (“DNS”) or as otherwise required byICANN. The Registry will take reasonable steps to maintain the security andprivacy of information or data that it may collect in connection with theplanned function and usage of Domain Names.The Registry will comply with allconfidentiality and security regulations in its jurisdiction of residence.TheRegistry has further ensured that its suppliers will take all reasonablemeasures to maintain the security and privacy of information collected from theRegistry.The WHOIS policy requires certainpersonal details to be published in the public domain.A Registrant may utilizea proxy registration service to protect Registrant's privacy, or for any otherlegitimate purpose.4.Conditions forRegistrars Offering Proxy Services.In the event that registrars elect to offer proxy or privacyservices, registrars must ensure that the actual WHOIS data is obtained fromthe Registrant and must maintain accurate records of such data.5.Law Enforcement:Where a proxy or privacy service is used,registrars must provide law enforcement agencies ("Law Enforcement”) withthe actual WHOIS data upon receipt of a verified request.Registrants should beaware that despite using a proxy registration service, actual WHOIS informationwould be provided to Law Enforcement upon request in order to establishliability for all actions in relation to a Domain Name. In addition, where aDomain Name is removed from the root zone, the Domain Name record may stillappear in the WHOIS database so that the name and entities can be investigatedby Law Enforcement should they elect to become involved.6.The Registry's effortsto promote WHOIS Accuracy.The Registry or its outsourced service providers may occasionallyreview, at their discretion, a random sampling of domain names within the.Vegas TLD to test the accuracy and authenticity of the WHOIS information. TheRegistry may examine the WHOIS data for evidence of inaccurate or incompleteWHOIS information.If such errors or missing information exists, notice shall beforwarded to the relevant registrar, who shall be required to address these deficiencieswith the relevant Registrants.7.Efforts to improveWHOIS Accuracy.Registrantsare required to provide accurate WHOIS contact details, and to keep thosedetails current.Registrars are obliged to obtain accurate WHOIS informationfrom all Registrants and to submit this data to the Registry for informationfor all Domain Names they sponsor.Pursuant to all ICANN and Registry policies,Registrants may access the WHOIS information at any time, and make amendmentswhere errors exist or to maintain accuracy. Registrants must immediately updateWHOIS information following any change in name, address, e-mail address,telephone, fax numbers or other required data.An omission or delay in amendingsuch information or informing the Registry of such changes may result inlocking or seizure of Registrant's Domain Name(s).8.Correcting errors.Registrant's first point of contact forcorrecting any WHOIS error is the Registrar.The Registrar is obligated toaccept written complaints from a Registrant or any third party regarding falseand/or inaccurate WHOIS data, which the Registrar is required to investigateand correct in accordance with its guidelines.If Registrant feels that an issuehas not been dealt with under the Registrar’s procedures, please read the Registry’sAnti-Abuse/Acceptable Use Policy.If Registrant feels that there has been anabuse, please submit a complaint directly to the Registry at abuse@nic.vegasor such other URL which the Registrydesignates for the posting of its Policies.9.ANTI-ABUSE/ACCEPTABLEUSE POLICYThe Registry has developed andadopted this Anti-Abuse/Acceptable Use Policy which is to be read together withother Registry policies and the Registrant Agreement.All words and phrases usedin this Policy shall have the same meaning attributed to them in the RegistrantAgreement unless otherwise specified or the context clearly otherwise requires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in thisPolicy.After the notice period expires, each time a user accesses or uses theServices, the then effective Anti-Abuse/Acceptable Use Policy will bind theuser.PLEASE READ THIS POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.1.General Principles:Abusive use(s) of domain names of the.Vegas TLD ("TLD") will not be tolerated.The nature of such abusescreates security and stability issues for the Registry, Registrars andRegistrants, as well as for users of the Internet in general.The Registrydefines abusive use as the wrong or excessive use of power, position orability, and incudes without limitation the following:a.Illegal or fraudulent actionsor activity;b.Spam:The use of electronicmessaging systems to send unsolicited bulk messages.The term applies to emailspam and similar abuses such as instant messaging spam, mobile messaging spam,and the spamming of Websites and Internet forums.An example, for purposes ofillustration, would be the use of email in denial-of-service attacks;c.Phishing:The use of counterfeitWeb pages that are designed to trick recipients into divulging sensitive datasuch as usernames, passwords, or financial data;d.Pharming:The redirecting ofunknowing users to fraudulent sites or services, typically through DNShijacking or poisoning;e.Willful distribution ofmalware:The dissemination of software designed to infiltrate or damage acomputer system without the owner's informed consent.Examples included, withoutlimitation, computer viruses, worms, keyloggers, and trojan horses;f.Fast flux hosting:Use of fastflux techniques to disguise the location of Websites or other Internet servicesor to avoid detection and mitigation efforts, or to host illegalactivities.Fast flux techniques use DNS to frequently change the location onthe Internet to which the domain name of an Internet host or name serverresolves.Fast flux hosting may be used only with prior permission of theRegistry;g.Botnet command andcontrol:Services run on a domain name that are used to control a collection ofcompromised computers or "zombies", or to direct denial-of-serviceattacks;h.Distribution of childpornography or obscene materials not protected by the U.S. Constitution orwhich is illegal in the country where Registrant resides; andi.Illegal access to othercomputers or networks:Illegally accessing computers, accounts, or networksbelonging to another party, or attempting to penetrate security measures ofanother individual's system (often known as "hacking").Also anyactivity that might be used as a precursor to an attempted system penetration(e.g. port scan, stealth scan, or other information gathering activity).2.Rights of the Registry:In accordance with the provisions of theRegistry-Registrar Agreement, the Registry reserves the right to deny, cancelor transfer any registration or transaction, or place any domain name(s) onRegistry lock, hold or similar status, that it deems necessary, in theRegistry's sole discretion, to:a.Protect the integrity and stabilityof the Registry;b.Comply with any applicablelaws, government rules or requirements, requests of law enforcement, or anydispute resolution process;c.Avoid any liability, civil orcriminal, on the part of the Registry, as well as its affiliates, subsidiaries,officers, directors, and employees;d.Comply with the terms of theRegistrant Agreement; ore.Correct mistakes made by theRegistry or any Registrar in connection with a domain name registration.The Registry also reserves theright to place on Registry lock, hold or similar status a Domain Name duringresolution of a dispute in accordance with the Registry's Dispute ResolutionPolicy.Abusive uses, as defined above, undertaken with respect to domain nameswithin the TLD shall give rise to the Registry's right to take such actionsunder the Registry-Registrar Agreement as the Registry deems appropriate in itssole discretion.To report potential abuse to the Registry please email abuse@nic.vegas or such other email address as maybe designated by the Registry to report abuse.10.DISPUTE RESOLUTIONPOLICYThe Registry has developed andadopted this Dispute Resolution Policy which is to be read together with otherRegistry policies, Registry-Registrar Agreement, and the RegistrantAgreement.All words and phrases used in this Policy shall have the same meaningattributed to them in the Registrant Agreement unless otherwise specified orthe context clearly otherwise requires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in thisPolicy.After the notice period expires, each time a user accesses or uses theServices, the then effective Dispute Resolution Policy will bind the user.PLEASE READ THIS POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.1.Purpose.Disputes related to a Registrant's DomainName will be subject to and governed by ICANN's Uniform Rapid Suspension Policy("URS") and/or Uniform Domain Name Dispute Resolution Policy("UDRP), both as applied and amended at http://newgtlds.icann.org/en/applicants/urs and http://www.icann.org/en/help/dndr/udrp, respectively.If the registration orreservation of Registrant's Domain Name is challenged by a third party, theRegistrant will be subject to the provisions specified in the applicable URSand/or UDRP in effect at the time the Registrant's Domain Name registration isdisputed by the third party, including all rules, processes and restrictionsset forth therein.The supplemental rules of the selectedadministrative-dispute-resolution service provider's will also apply to anydispute proceeding.The Registry will comply with the decision rendered by thedispute resolution service provider in any such proceeding, unless a validcourt order is presented which suspends or otherwise modifies said decision.2.Registrant'sRepresentations. Byapplying to register a Domain Name, or by asking a Registrar to maintain orrenew a Domain Name registration, the Registrant represents and warrants to theRegistry and Registrar that (a) the statements that Registrant made in itsRegistrant Agreement are complete and accurate; (b) to Registrant's knowledge,the registration of the Domain Name will not infringe upon or otherwise violatethe rights of any third party; (c) Registrant is not registering the DomainName for an unlawful purpose; and (d) Registrant will not knowingly use theDomain Name in violation of any applicable laws or regulations. It isRegistrant's responsibility to determine whether the Domain Name registrationinfringes or violates someone else's rights.3.Cancellations,transfers, and changes.The Registry reserves the right, in its sole discretion, to deny,cancel or transfer any Domain Name registration or transaction, or place anyDomain Name(s) or other transactions on Registry lock, hold or similar status(i) to protect the integrity and stability of the Registry's systems; (ii) tocomply with any applicable laws, government rules or requirements, requests oflaw enforcement, ICANN Policies or Registry Policies, or any dispute resolutionprocess; (iii) during the resolution of a dispute; (iv) to avoid any liability,civil or criminal, on the part of the Registry, as well as its affiliates,subsidiaries, officers, directors, and employees; (v) in respect of theRegistry only, for violations of the registry-registrar agreement between theapplicable Registrar and the Registry (for example, non-payment of fees)including, without limitation, any exhibits, attachments, or schedules thereto;(vi) to correct mistakes made by the Registry in connection with a Domain Nameregistration; (vii) following an occurrence of any of the prohibited activitiesdescribed in violation of the Registry's Anti-Abuse/Acceptable Use Policy, or(viii) as otherwise provided for by the Applicant's or Registrant's RegistrantAgreement.Furthermore, the Registry reserves the right at any time, to verify(ix) the truth, accuracy, and completeness of any information provided by theRegistrant to the Registry, whether directly, through a Registrar or otherwise;and (x) the compliance by the Registrant with the applicable RegistryPolicies.Registrants agree to fully comply and cooperate with the Registry inconnection with such verification and furnish all available documentation asthe Registry may reasonably require to complete the verification.11. PRIVACY POLICY(Registrant and User Data)The Registry has developed andadopted this Privacy Policy which is to be read together with together withother Registry policies, Registry-Registrar Agreement, and the RegistrantAgreement.All words and phrases used in this Policy shall have the same meaningattributed to them in the Registrant Agreement unless otherwise specified orthe context clearly otherwise requires.Please note that the Registry maymodify this Policy from time to time effective upon thirty (30) days notice bythe Registry to interested parties including sponsoring registrars.Such changeswill be available on the Registry website at http://www.nic.vegas or such other URL as the Registrymay designate, which shall satisfy all notice requirements set forth in this Policy.Afterthe notice period expires, each time a user accesses or uses the Services, thethen effective Privacy Policy will bind the user.PLEASE READ THIS PRIVACY POLICYCAREFULLY.BY ACCESSING OR USING THE SERVICES, THE READER EXPRESSLY AGREES TO BEBOUND BY THE TERMS DESCRIBED HEREIN AND ALL TERMS INCORPORATED BY REFERENCE.IFTHE READER DOES NOT AGREE TO ALL OF THESE TERMS, DO NOT USE THE SERVICES.1.General Statement.The Registry committed to protecting theprivacy of Registrants and those making use of its Internet domain nameregistry services (the “Services”).Registry will handle personal data providedto it by Registrars and Registrants in accordance with this Privacy Policy.2.External Websites.The Registry website and the Services maycontain links to external websites.The Registry is not responsible for andcannot control the content or privacy practices of other entities.Theseentities may have their own privacy policies and the Registry does not acceptany responsibility or liability for these policies.The reader should checkthese policies before submitting any personal data to their websites.3.Use of the Internet.The transmission of information via theInternet is not completely secure.Further, communicating via the Internet andother electronic means necessarily involves personal information passingthrough or being handled by third parties such as Internet serviceproviders.Although the Registry will do its best to protect personal data, theRegistry cannot guarantee the security of the information transmitted and anytransmission of information is at the user's own risk.4.Information Collectedand WHOIS Service.TheRegistry collects certain data from its contracted Registrars.Such dataincludes domain name registration information provided by Registrants toRegistrars, including, but not limited to: registered domain name, name serverdelegation, Registrant name, administrative and technical contact names,address, phone number, email address, and IP address (“WHOIS Data”).While theRegistry will comply with all requirements related to the accuracy of WHOISData under its Registry Agreement with the Internet Corporation for AssignedNames and Numbers ("ICANN), the Registry cannot guarantee that allpersonal data received is accurate or up to date and will not, therefore, beresponsible for any inaccuracies.To support the security of theInternet and ensure continuity in service, the Registry is required to maintaina service that provides WHOIS Data (the “WHOIS Service”).The WHOIS Service is availableto any Internet user, and its use does not require prior authorization orpermission.More information on the Registry's WHOIS Service is available in theAcceptable Use Policy, the Anti-Abuse Policy and WHOIS Policy, all of which areavailable on the Registry website.5.Other Use of and Accessto Personal Data. The Registry shall take all reasonable steps to protect personaldata collected from loss, misuse, unauthorized disclosure, alteration, ordestruction.Personal data supplied to the Registry will not be given, sold,rented, loaned, or otherwise disclosed to any third parties outside of theRegistry, except when the Registry has express permission or under specialcircumstances, such as when the Registry believes in good faith that disclosureis reasonably necessary to (i) comply with legal processes; (ii) enforce orcomply with agreements between the Registry and ICANN; (iii) enforce or complywith agreements between the Registry and Registrars; (iv) comply with policiesadopted from time to time by the Registry and posted under “Policies” on theRegistry website; or (v) protect the rights, property, or personalsafety ofRegistry, its contracted parties, customers, or the public.The Registry may share zone filedata (such as domain names and name servers) to third parties for lawfulpurposes.The Registry may also share personal data with vendors, escrow agents,consultants and other service providers (“Service Providers”) engaged by orworking with the Registry and who need access to such information to carry outtheir work for the Registry.The Registry is not responsible for the actions ofService Providers or other third parties, nor is the Registry responsible forany additional information provided directly to these Service Providers or otherthird parties by Registrars or Registrants.The Registry may from time totime use data submitted by Registrars for statistical analysis, provided thatany such analysis will not disclose individual non-public personal data andsuch non-public personal data only is used for internal business purposes.6.Protection of PersonalData.The Registryhas endeavored to put into place and maintain reasonable security measures inan effort to protect the security of non-public personal information while itis under the Registry’s control.Please be aware, however, that despite theRegistry’s best efforts, no security measures are perfect or impenetrable.7.Transfer of Ownership.The Registry reserves the right totransfer ownership of the Registry, its subsidiaries, or the Services(including the personal data collected by the Registry) to a third party in theevent of a sale, merger, liquidation, receivership or transfer of all orsubstantially all of the Registry's assets, or a subsidiary or line of businessassociated with the Registry.Such a transaction may involve the disclosure ofpersonal data to prospective or actual purchasers, or the receipt of it fromsellers.8.User Contact – Opt-out.From time to time, the Registry may notifyRegistrars and Registrants (“Users”) of new products, announcements, upgradesand updates.Users may opt-out of these promotional mailings by sending an emailwith their name to: compliance@nic.vegas or by contacting us at 6325 S. JonesBlvd., Suite 500, Las Vegas, NV 89118.The Registry reserves the right to sendUsers email related to business practices and systems operations, such asoutage notifications and quota warnings, even if the User has opted out ofpromotional mailings.9.Governing Law. This Privacy Policy and all issuesregarding this website are governed by the laws of the State of Nevada and aresubject to the exclusive jurisdiction of the courts located in Clark County,Nevada.10.Contacting theRegistry: Questionsabout this Policy or the Registry’s practices relating to the Services, shouldbe directed to the following address: compliance@nic.vegas or such other email address as theRegistry may direct in the future.12. ExclusiveRegistration Period Policies (Collision Names Only)Dot Vegas, Inc. (the"Registry") will offer a Sunrise Period as a rights protectionmechanism for qualifying mark holders before registration is made available tothe general public for those names appearing on the Name Collision OccurrenceAssessment list.This Exclusive Registration Period is designated as an ICANNSelected "Exclusive Registration Period" or "SunrisePeriod" herein.This Exclusive Registration Period Policy (the"Policy") must be read in conjunction with other Registry Policies,and is also incorporated by reference into the Registry-Registrar Agreement andRegistrar-Registrant Agreements associated with Domain Names registered in the.Vegas TLD ("TLD") during the Sunrise Period. 1.Exclusive RegistrationPeriod.ThisExclusive Registration Period will commence at 00:00 hours UTC, January 16,2015 and terminate at 00:00 hours UTC, February 15, 2015.During the SunrisePeriod, only those holders of SMD Files obtained through registration with theTrademark Clearing House will be authorized to submit Sunrise applications onlyfor those names appearing on the ICANN Name Collision Occurrence AssessmentList.Successful Sunrise registrations will be allocated in the TLD after theSunrise Period concludes.All Sunrise Applications will be subject to the termsand conditions set forth herein, along with such other terms and conditionsthat may be found in applicable Registry policies, the Registry Agreement withICANN, the Registry-Registrar Agreement with qualifying Registrars and theRegistrant Agreement with registrants.The Registry will extend availability ofits Sunrise Dispute Resolution Period to address disputes regarding itsregistration of Affected Names registered during this Exclusive RegistrationPeriod.2.Application ProcessOverview.Thefollowing process applies to Sunrise applications:a.SMD Files submitted withSunrise applications are validated by the Registry (or an agent designated byRegistry to conduct validations of Sunrise applications).Sunrise applicationsmissing a valid SMD File or containing an invalid SMD File will be rejected bythe Registry.b.Domain names for which a validSunrise application has been received that (1) meet the Sunrise Registrationeligibility criteria described herein and (2) were submitted in accordance withRegistry policies, ICANN Requirements, and the Registry-Registrar Agreement,will be allocated to the applicant following the close of the Sunrise Period.c.If more than one Sunriseapplication for the same Domain Name Character String meet the eligibilitycriteria described herein, the Sunrise applications will be submitted to anauction provider designated by the Registry and the Domain Name will be awardedin accordance with applicable auction rules and procedures.d.Domain Names awarded tosuccessful Sunrise applicants at auction will be allocated by the Registryfollowing the conclusion of such auction and those Domain Names shall besubject to the terms of the Sunrise Registration registrant agreement.3.Sunrise Application Feeand Domain Name Registration Fee Payments. a.Application Fee.Each Sunrise application must beaccompanied by a non-refundable Application fee fixed by the Registry and paidto the sponsoring Registrar for the applied-for Domain Name.Only those Sunriseapplications which include payment of the Application fee will be accepted bythe Registry. b.Domain NameRegistration Fee.SuccessfulSunrise Applicants must pay the designated Domain Name Registration Fee beforeallocation of the applied-for Domain Name to the applicant.This RegistrationFee is in addition to the Sunrise Application Fee.In this regard, the Registryhas designated certain Domain Names as 'Premium' Domain Names and have pricedthose Domain Names accordingly. Designated Premium Domain Names may also beheld by the Registry on its Reserved Domain Names List.All Domain Names thathave NOT been designated as 'Premium' Domain Names or are not held on theRegistry's Reserved Domain Names List are deemed non-premium or normal domainnames.Sunrise applicants applying for a Domain Name that has been designated a'Premium' Domain Name or which is being held on the Registry's Reserved DomainsList must pay the Registration Fee for the applied-for Domain Name as may befixed by the Registry.c.Domain Name Renewals.The renewal price for Domain Namesregistered during the Sunrise Period will be set by the applicable Registrarsponsoring the Domain Name at the time of renewal.Renewal grace periods arefixed by the Registrant Agreement as well as the Registry's standard GeneralDomain Name Registration Policy which can be found at http://www.the.vegas or such other URL as the Registrymay designate for its Registry Policies.4.Auctions. If more than one Applicant submits a validSunrise application for the same Domain Name, the Registry will notify theapplicable Registrar(s) at the end of the Sunrise Period.The prevailingApplicant for the Domain Name will be determined at an auction hosted by anauction provider of the Registry's choice (“Auction Provider”).The auctionprocess will be governed by the terms and conditions published by the AuctionProvider and available on the Registry Website (“Auction Rules”).RegistrationFees for 'Premium' Domain Names and Reserved Domain Names as set by theRegistry shall be deemed the 'minimum bid' for Domain Names subject to auctionshereunder.Domain Names awarded to successful Sunrise applicants at auction willbe allocated by the Registry, typically within seven (7) days of notificationfrom the Auction Provider that the auction has concluded and the RegistrationFees have been paid.5.Limitations on Transferof 'Premium' Domain Names. In accordance with the terms of the Sunrise Registration registrantagreement, Domain Names registered in the Sunrise Period which the Registry hasdeemed to be 'Premium' Domain Names or which may be on the Reserved DomainNames List at the time of registration may not be transferred by the Registrantto any party (including any natural person, company, organization, subsidiaryor affiliate company of the Registrant) during the initial registration termexcept in those instances where such Domain Name(s) are included as part of asale or acquisition of all or substantially all of the business or otheroperations of the Registrant.The Registry reserves the right to require theRegistrant to produce such documentation of the sale or acquisition transactionwhich evidences compliance with this condition to transfer.6.Processing SunriseRegistrations. TheRegistry will not process a Sunrise Application unless the Registry has: (a)validated the SMD File with the TMCH, and (b) received, or has, in itsdiscretion, reasonable assurance of payment from the Registrar of all applicablefees, including the registration fee and the non-refundable, one-time SunriseApplication fee for the Sunrise Application.7.TMCH, SMD Files, andDomain Name Character String Requirements. Sunrise Applications may only be submittedby a Registrar sponsoring the Sunrise applicant and must include an SMD Filecorresponding to the Domain Name Character String.8.Eligible Applicants. Each applicant must meet thequalifications specified by ICANN requirements and detailed in the TMCHGuidelines, as amended from time to time.9.SMD File Requirements. The applicant must submit a valid SMD Filealong with its Sunrise application.10.Registration.The Registry will create a Domain Nameregistration and allocate the Domain Name to the Applicant if:a.The Domain Name meets therequirements set forth in the TLD's General Domain Name Registration Policy;b.The Domain Name and theinformation contained in the Registrar’s request meet the requirements in theRegistry-Registrar Agreement;c.The Domain Name is available;d.The applicant is eligible toregister the applied-for Domain Name;e.The required SunriseApplication Fee and designated Registration Fee have been paid to thesponsoring Registrar; andf.The sponsoring Registrar is ingood standing with the Registry.11.Sunrise ApplicantNotification. Notificationto Sunrise applicants will be as follows:a.At the end of the SunrisePeriod, the Registry will notify Registrars who sponsored a Sunrise applicationof applicable Sunrise Registration allocations.b.In the event two or moreSunrise applications are received for the same Domain Name, the Registry willnotify the Registrar(s) who sponsored such Sunrise applications and advise themof the impending auction for the Domain Name.c.Registrars receiving notice ofa pending auction must pass on such notice to their Sunrise applicants.d.At the conclusion of an auctionfor a Domain Name, the sponsoring Registrar(s) for Sunrise applications willreceive a message informing which Sunrise application prevailed in the auctionand was allocated the Domain Name and which application lost in the auction.e.The Registry will notify theTMCH of successful Sunrise applications once the corresponding SunriseRegistration has been made.The Registry may also publish all or any portion ofa pending Sunrise Application online (e.g., via Whois).12.The Registry’s Rightsregarding Sunrise Applications and Registrations:The Registry reserves the right, in itssole discretion, to deny, cancel, modify or transfer any Domain Nameregistration or transaction, or place any Domain Name(s) or other transactionson Registry lock, hold or similar status (i) to protect the integrity andstability of the Registry's systems; (ii) to comply with any applicable laws,government rules or requirements, requests of law enforcement, ICANN Policiesor Registry Policies, or any dispute resolution process; (iii) during theresolution of a dispute; (iv) to avoid any liability, civil or criminal, on thepart of the Registry, as well as its affiliates, subsidiaries, officers,directors, and employees; (v) in respect of the Registry only, for violationsof the Registry-Registrar agreement between the applicable Registrar and theRegistry (for example, non-payment of fees) including, without limitation, anyexhibits, attachments, or schedules thereto; (vi) to correct mistakes made bythe Registry in connection with a Domain Name registration; (vii) following anoccurrence of any of the prohibited activities described in violation of theRegistry's Anti-Abuse/Acceptable Use Policy, (viii) to require that any Sunriseapplicant filing a dispute or other action contesting the Registry's SunriseRegistration or Sunrise Dispute Policy deposit with the Registry a minimum of$20,000 but not more than $50,000 to cover all costs incurred by the Registryin the event the Sunrise applicant is not successful in receiving a decisionawarding the relief sought in such dispute or contest action; or (ix) asotherwise provided for by the applicant's or Registrant's RegistrantAgreement.Furthermore, the Registry reserves the right at any time, to verify(x) the truth, accuracy, and completeness of any information provided by theRegistrant to the Registry, whether directly, through a Registrar or otherwise;and (xi) the compliance by the Registrant with the applicable RegistryPolicies.Registrants agree to fully comply and cooperate with the Registry inconnection with such verification and furnish all available documentation asthe Registry may reasonably required to complete the verification.