As of January 1, 2018.
This document summarizes the policies, procedures and rules applicable to the .nowruz registry and the ongoing policies applicable to registrations and renewals of domain names ending with .nowruz.
The launch phases listed below are subject to the approval of ICANN and can be found on the ICANN website at https://newgtlds.icann.org/en/program-status/sunrise-claims-periods
Details for each phase are as follows:
- Sunrise – minimum of 60 days and is a “End Date Sunrise”
- General Availability – standard pricing
Sunrise: January 26, 2018 to March 27, 2018
General Availability: March 27, 2018
Early Access Program is where a domain registered during the first 5 (five) days of General Availability is subject to an Early Access Program fee and will vary depending on the day of registration. Details on the fees by day are found on the CoCCA registrar console. See Early Access Program Policy.
The registry reserves the right to modify or amend this Policy which will be effective ninety (90) days after posting notice on the .nowruz Registry website located at nic.nowruz, the CoCCA Registrar Console and giving notice to .nowruz accredited Registrars.
In the event a change of control of the Registry Operator subject to its approval by ICANN, shall not require any further notices under this policy and the policies will remain in full force and effect.
Domain Name Registration Rules for .NOWRUZ
Accepted characters and combinations
- Classic (Non IDN) domain names consist of:
- Characters a to z
- Digits 0 through 9
- Hyphen (-)
- Cannot start nor end with a hyphen (-)
- Cannot have a hyphen in third and fourth position, unless the first two characters are ‘xn’ and the domain name can be converted to a valid IDN.
- IDNs consist of:
- Digits 0 through 9
- Hyphen (-)
- Unicode characters from the Perso-Arabic Alphabet
- Cannot start nor end with a hyphen (-).
- Cannot have a hyphen in third and fourth position.
Domain Name Length and IDNs
Domain names must be at least three (3) characters long and cannot be longer than 63 characters in length. Domain name length does not include the length of .nowruz extension. IDN domain names should be converted to ACE string before registration. Domain name length restrictions will apply after ACE string conversation.
If the domain is an Arabic IDN Labels must start with an Arabic Letter and no European numbers may be present, and vice versa.
Common Rules for Registration
These Rules apply to the registration, renewal, transfer, modification, suspension and deletion of Domain Names and to other transactions with respect to Domain Name Registrations.
Registration requests will be processed on a first come, first served basis
Registration requests must be in EPP format specified by Asia Green IT Systems or registrations should be completed from registry backend panel by registrar company.
The Registrar must have sufficient deposit or credit in their registry account to cover any fees charged by AGIT. The Registry will not accept a Registration Application and will not renew a Registrations at the end of the applicable Term unless it has received payment in full from the Registrar. Names requiring a Registration Application or that result in the release of a registrations will be in accordance with Registry Policies and requirements as set out by ICANN.
Registration Term, Expiry Date and Renewal Policies of Domain Names
Domain names can be registered between one year to ten years. The domains expiry date cannot exceed ten years. For example, if a domain name has two years remaining to expiry, then it will not be allowed to renew more than eight years.
Notification of the termination or expiration for a registration for any reason whatsoever is the responsibility of the Registrar and not the Registry.
The payment of any fees due may be made to the Registry via a Registrar. The Registry is not responsible for any failure on behalf of the Registrar resulting in the non-registration, non-renewal or termination of the registration.
Certain .nowruz domain names have been blocked by Asia Green IT Systems Ltd. Şti. This means that they may not be registered. Additionally, subject to the provisions of a contractually mandated Schedule of Reserved Names including ING/NGO Names, Country Codes, Country names and other ICANN mandated reserved names. The status of these names as “reserved” may be altered in conjunction with ICANN.
Two-letter domain names have been blocked as well due to ICANN restrictions. Two-letter domain names except two-letter country codes may be released upon ICANN’s permission.
The registry has reserved some domain names for its own use for the registry operation.
Availability of names is also subject to Registry Reserved names, which are names reserved by the Registry for its use. The Registry may also establish a “Prohibited Names List”, which names will be blocked from availability for registration.
The Registry may withhold any quantity of names for inclusion in “Premium Names Lists” or other means of distribution at future determined time and rates. Additionally, the Registry reserves the right to reserve additional names as Registry Reserved Names at any time in its sole discretion and to allocate such names in according with ICANN requirements and Registry Policies.
The Registry may block names which are subject to additions and modifications from time to time. Blocked names are not available for registration. The blocked names include names blocked by ICANN.
Acceptable Use and Anti-Abuse Policy
All .nowruz domain names are subject to this policy. This policy may be revised from time to time, subject to giving ninety (90) days’ notice to .nowruz accredited Registrars.
This Acceptable Use Policy (“AUP”) governs the use of registrants or users of .nowruz domain names and add-on Registry services. This policy is intended to provide integrity and security of domain name services and is not a mechanism to resolve disputes between third parties and .nowruz registrants. The Registry reserves the right to modify the AUP subject to giving ninety (90) days’ notice to .nowruz accredited Registrars only (and is not required to provide notice to registrants).
The Registry is trusted to supply an unbiased platform and support the free-flow of information across the Internet. As such, the Registry does not monitor or exercise control over the content of any site, email or message using .nowruz domain names.
The Registry reserves the right to deny, cancel or transfer any registration or service, or place any domain name(s) on registry lock, hold, or similar status, as it deems necessary, at its sole discretion and without notice:
- To protect the integrity, security, and stability of the domain name system
- To comply with any applicable court orders, laws, or requests or rulings from law enforcement agencies, government agencies, or other organizations, or dispute resolution proceedings
- To avoid any liability, civil or criminal, on the part of the Registry, as well as its affiliates, subsidiaries, officers, directors, and employees or its service providers
- To enforce the terms of the registration agreement
- To respond to or protect against any form of malware (which includes, without limitation, malicious code or software that may affect the operation of the Internet)
- To comply with specifications of any industry group or recognized authority on Internet stability (i.e., RFCs)
- To correct mistakes made by the Registry or any registrar in connection with the domain name registration, or
- For the non-payment of any fees owed
The following, which is not exhaustive, are prohibited from use and constitute registration abuse which may result in registry hold, transferring, cancelling, suspending or deleting of the domain names in the .nowruz TLD. The Registrar shall include the following in its Registrant Agreement in respect of a .nowruz domain name, the Registrant shall not:
- Upload, post, email, transmit or otherwise make available (collectively, “Transmit”) any content that is unlawful, harmful, abusive, threatening, invasive of another’s privacy or otherwise damaging
- Harms a minor(s) in any way
- Impersonate any person or entity, including, but not limited to, an official, forum leader, celebrity, guide or host, or falsely state or otherwise misrepresent its affiliation with a person or entity
- Forge headers or otherwise manipulate identifiers in order to disguise the origin of any content transmitted
- Transmit any content that the Registrant does not have a right to make available under any law or under contractual or fiduciary relationships (such as inside information, proprietary and confidential information learned or disclosed as part of employment relationships or under nondisclosure agreements)
- Transmit any content that infringes any patent, trademark, trade secret, copyright or other proprietary rights (“Rights”) of any party
- Transmit any unsolicited or unauthorized advertising, “junk mail,” “spam,” “chain letters,” “pyramid schemes,” or other abusive or harmful material
- Transmit any content that contains software viruses or any other computer code, files or programs designed to interrupt, destroy or limit the functionality of any computer software or hardware or telecommunications equipment
- Interferes with or disrupts servers or networks, or disobey any requirements, procedures, policies or regulations of networks
- Relay email from a third party’s mail servers without the permission of that third party
- Use “robots” or otherwise harvest other’s email address(es) from a site for purposes of sending unsolicited or unauthorized material
- Abusively upload, post, email, or transmit the same message, URL, or posts multiple times
- Intentionally or unintentionally violate any applicable local, state, national or international law, including, any rules of any national or other securities exchange, and any regulations having the force of law
- “Stalk” or harass another or engage in cyber bullying
- Register a generic term during the sunrise period
- Distribute malware, operate botnets, or perform phishing
- Use domain for piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in any illegal activity
All registrants must comply with all applicable laws including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct) and applicable consumer laws in respect of fair lending, debt collection, disclosure of data and financial regulations.
If a registrant is collecting and maintaining sensitive health, financial or similar data, they must comply with applicable laws on the provision of such services and including security measures applicable to that sector.
In the event that a Registrant has registered a domain name that infringes the rights of another, the Registry reserves the right in cooperation with the sponsoring Registrar to cancel or transfer such domain name registration, and take further action against the Registrant.
All .nowruz domain names are subject to ICANN’s policies, including the dispute resolution procedures of a UDRP, URS and/or the rights of trademark holders as enforced by courts of law.
This AUP is to assist registrants in the lawful use of their domain names and does not exhaustively cover all potential abuses of domain names which may result in the suspension, transfer, cancellation or locking of a .nowruz domain name.
The Registry is not bound or obliged to adjudicate any dispute between parties or take any action, and cannot and does not accept any responsibility for any loss or damage a registrant or any other person may suffer as a result of any action or omission by the Registry or by any other person under the Acceptable Use Policy. The Registry may directly adjudicate a dispute if it deems necessary or refer the dispute to a third-party dispute resolution service.
The Registry reserves the right to employ additional abuse mitigation mechanisms to prevent the abuse and/or mitigate abusive domains including the collaboration with relevant organizations on abuse related issues.
Launch Plan and Policy
This document describes Launch Policy for the .nowruz TLD (“Registry TLDs”).
All applications must be submitted through Registrars in accordance with all Registry Policies, the requirements of ICANN and Trademark Clearing House (“TMCH”) along with the Registry Operator-Registrar agreement.
Applicants acknowledge and agree that an application for registration of a specific domain name does not necessarily result in actual registration. Contractual rights and privileges only enter into force with actual registration within, or following the completion of, the related phase of the Launch Period under circumstances described in this Policy, Registration Policy and Auction Policy, where applicable.
The Registry Operator shall execute the Launch Policy in cooperation with Registrars and TMCH.
Timeframe for the Launch Period is set forth in the Launch Schedule and launch phases are described briefly below:
Sunrise: Only TMCH validated trademark holders will be able to apply within the Sunrise Period, and requested domain names will be allocated to successful applicants on a “first come, first served” basis.
Early Access Period: EAP means a period running concurrently with the Sunrise Period during which Applications for a domain name may be received from any interested eligible party.
Landrush: Everyone will be able to apply for available domain names within the Landrush Period. Contentions due to multiple applications for the same domain name will be resolved through auction.
General Availability: Everyone will be able to apply for available domain names and requested domain names will be allocated to successful applicants on a “first come, first served” basis.
|Period||Duration||Claims Period||Start Date||End Date|
|Early Access Program||30 days||yes|
|General Availability||30 days|
The Registry Operator has reserved certain names from registration in the TLDs under the Reserved Name Policy. Reserved names may be made available at a later date via a mechanism to be determined by the Registry Operator. Additionally, the Registry Operator may, at its sole discretion, reserve certain domain names as “premium” and make them subject to a premium registration fee.
The Registry Operator may amend or update this Policy from time to time at its sole discretion and based on the requirements of ICANN.
Early Access Program Policy
The Early Access Program (EAP) provides registrants with the opportunity to secure their .nowruz domain name early in a special launch phase.
EAP replaces a traditional landrush period commencing the first five days of the .nowruz General Availability period. Interested individuals, organizations, businesses and others can register names on a first-come, first-served basis.
Registrars are uniquely positioned to use EAP to reach the most focused and motivated registrants. EAP can be tailored to registrars’ marketing efforts, including marketing to registrants prior to a domain’s launch or accepting “pre-registrations.”
Registrars interested in offering .nowruz EAP can either contact Asia Green IT System Ltd. Şti. or CoCCA (www.coccaregistry.net) to offer for technical specifications and requirements.
EAP helps registrants immediately secure the domain names they’ve always wanted. It also provides brands with an opportunity to obtain non-trademarked domain names that can assist in the protection of the products or services or to influence a market vertical.
Early access registrations will be made available for the first five days of .nowruz’s General Availability. Each day of the EAP will begin at 8:00 UTC and end at 8:00 UTC the following calendar day.
Please contact an accredited registrar for additional information.
The Registry Operator is committed to ensuring that all Trademark Rights Holders have adequate protections for their intellectual property assets. As such, the Registry will implement, “60 Day End Date” Sunrise(s), as defined by ICANN: (http://newgtlds.icann.org/en/about/trademark–clearinghouse/rpmrequirements–30sep13–en.pdf).
This Sunrise Policy (“Policy”) defines the registration policies and eligibility requirements for registrations Sunrise Period.
These provisions describe the processes, procedures, and rules for all sunrises for the Registry’s top-level domains (TLDs). The Registry Operator shall offer a Sunrise Period as a rights protection mechanism for qualifying trademark holders with a corresponding Signed Mark Data (“SMD”) file generated by TMCH, before registration is made available to the general public.
In order to participate in the Sunrise Period, the Applicant must:
- Have met all the requirements to obtain a SMD file as described in the TMCH Guidelines;
- Meet any of the additional requirements that Registry Operator has described in this Policy or any other policy issued by ICANN or the Registry Operator;
- At the time of submitting an application, provide the SMD file received from the TMCH Sunrise and Claims Operator;
- Only submit an application for a Label contained in the SMD file; and
- Apply for a domain name that is not reserved, blocked, placed on hold or locked.
In addition, for a Sunrise application to be qualified as eligible, the Applicant must submit the corresponding SMD file through a Registrar and the requested domain names must meet the “identical match” criteria described by ICANN and TMCH. The submitted SMD files shall be validated with TMCH by the Registrar.
Applications missing a valid SMD File, containing an invalid SMD file or where the application misses any other requirements set out in Section 6 shall be rejected by the Registrar. Applicants whose applications have been rejected shall be informed by the Registrar within reasonable time.
Successful applications shall be processed in chronological order of receipt and allocated on a “first come, first served” basis.
The Sunrise Period shall be in effect from the date so described in the Launch Schedule. Once commenced, the Registry Operator may extend the duration of the Sunrise Period through its website or via any other means it deems appropriate.
Sunrise Registration Periods
Registrations may be purchased in yearly increments of no less than 1 (one) year and no more than 10 (ten) years, commencing on the date that the domain name is registered. Unless otherwise terminated, such registration will expire on the same day of the month the registration was created, unless it was created on February 29, in which case it will expire on March 1.
Unless otherwise stated in this Policy, the Registry Operator, via the Registry Service Provider, will allocate a Domain Name if:
- The Domain Name Label meets the requirements set out above
- The Domain Name Label and the information contained in the Registrar’s request meet the requirements in the Terms and Conditions (Acceptable Use Policy)
- The Domain Name Label is available
- The Registrar is in good standing with the Registry
- Non-refundable sunrise application fee has been paid for each eligible domain name
- Standard Domain Name Registration Fee has been paid for each eligible domain name
Sunrise Resolution Process
If two or more Sunrise Applicants are received during the .nowruz sunrise period and qualify for the same second-level domain name, the Registry will hold an ascending bid auction facilitated by a reputable third party domain auction provider. Auction dates and rules will be provided to the Applicants within a reasonable time period with the winner of the auction resolving the contention.
Registry Operator Rights
The Registry Operator reserves the right to identify domain names available during any launch phase, which shall be available through EPP or any other registration or distribution mechanism, as Premium Domain Names. Any such Premium Domain Names may not be available for allocation or registration during the Sunrise period.
Domains not available in the Sunrise Registration Period shall be subject to a 90-day Claims Period as set forth in the Trademark Clearinghouse Requirements, as posted at http://www.icann.org/en/resources/registries/tmch-requirements, which may be revised by ICANN from time to time.
The Registry shall be entitled but not obligated to reject a Sunrise Application or to delete, revoke, cancel, suspend or transfer a Sunrise Registration:
- To enforce Registry policies and ICANN Requirements, each as amended from time to time
- That is not accompanied by complete and accurate information, or where required, information is not updated or corrected, as required by ICANN Requirements or Registry policies
- To protect the integrity and stability of the operation or management of the Registry
- To comply with applicable laws, regulations, policies or any holding, order, or decision by a competent court or administrative authority, or any dispute resolution service provider the Registry may retain to oversee the arbitration and mediation of disputes
- To establish, assert, or defend the legal rights of the Registry or a third party, or to avoid any actual or potential civil or criminal liability on the part of or damage to the Registry or its affiliates, subsidiaries, contracted parties, officers, directors, representatives, employees, contractors, and stockholders
- To correct mistakes made by the Registry or any Registrar in connection with a Sunrise Registration
- If the Registry receives notice that the SMD File is under dispute; or
- As otherwise provided in the Registrar terms and conditions or Registry-Registrar agreement
Sunrise Dispute Resolution Policy
This Sunrise Dispute Resolution Policy (SDRP) describes the process and standards that will be applied to resolve challenges alleging that a domain name has been registered, registration has been declined or is in violation of the SDRP. This SDRP will not be applied to Registry-reserved names in the TLD.
A complainant, complainant’s counsel, or complainant’s counsel’s firm, that is found to be responsible for filing three or more SDRP complaints (in any TLD, .nowruz or otherwise) deemed to be frivolous may be barred from further use of this policy at the Registry’s discretion. A frivolous complaint comes from a complainant that has habitually lodged vexatious complaints, persistently and without grounds. In denying use of this policy, the Registry or the Dispute Resolution Providers may consider the number of complaints lodged under this Policy or any similar third-party registry policies and paths of dispute resolution, which were resolved in favor of a respondent, or otherwise consider a pattern of abusing such policies.
A registered domain name in the TLD will be subject to an administrative proceeding upon submission of a complaint that the Sunrise Registration was improper under one or more of the following criteria.
a. Improper Sunrise Registration Application
A complaint under this section shall be required to show by reasonable evidence that a registered domain name in the TLD does not comply with the provisions of the Registry’s Sunrise Program. The complaint must prove one or more of the following elements:
- 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
- The domain name is not identical to the mark on which the registrant based its Sunrise registration; or
- 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 .nowruz TLD shall be brought before 60 days after the close of the sunrise period.
Evidence and Defenses
Panelists will review the Registry’s Sunrise Criteria, allocation requirements, or community-based eligibility requirements which are required to be submitted with the Complaint, as applicable, in making its decision.
Harmless error. A Respondent may produce evidence to show that, although the sunrise registration was granted 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.
The remedies available to a complainant for a proceeding under this SDRP shall be limited to:
a. Improper Sunrise Registration
If the Panelist finds that the domain name was improperly registered during the Sunrise period, the sole remedy for a Complaint filed under SDRP 2(a) shall be cancellation of the registration and return of the cancelled domain name to the pool of available names 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 an SDRP dispute is brought by an auction bidder for the same domain name, the auction will be suspended until the dispute is resolved.
a. Dispute Resolution Provider / Selection of Procedure
A Complaint under this SDRP shall be submitted to the National Arbitration Forum (“Forum”) by submitting the complaint directly to the Forum. The Forum will administer the proceeding and select a qualified and eligible Panelist (“Panelist”). The Forum has established Rules for National Arbitration Forum’s Sunrise Dispute Resolution Policy (“Rules”), setting forth a fee schedule and other technical and process requirements for handling a dispute under this SDRP. The proceedings under this SDRP will be conducted according to this SDRP and the applicable Rules of the Forum.
b. Registry’s or Registrar’s Involvement
Neither the Registry nor registrar will participate in the administration or conduct of any proceeding before a Panelist. In any event, neither the Registry nor the registrar is or will be liable as a result of any decisions rendered by the Panelist. Any sunrise-registered domain names in the TLD 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 in the TLD, against which a complaint has been filed, will be as shown in the registrar’s publicly available 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.
The registrant of a registered domain name in the TLD shall be promptly notified by the Forum 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 Forum shall promptly notify all named parties in the dispute, as well as the registrar and the Registry of any decision made by a Panelist.
(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 state whether a registered domain name in the TLD is to be cancelled or the status quo maintained; and
(iii) Decisions made under this SDRP will be publicly published by the Forum 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 Registrar 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 Forum) 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:
- evidence satisfactory to the Registry of an agreed resolution between the parties
- evidence satisfactory to Registry that registrant’s lawsuit has been dismissed or withdrawn or
- a copy of an order from such court dismissing such lawsuit or otherwise directing disposition of the registered domain name.
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, shall remain subject to all representations and warranties made in the course of registration of a disputed domain name.
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.
Indemnification / Hold Harmless
The parties shall hold the registrar, the Registry, the Forum, and the Panelist harmless from any claim arising from operation of the SDRP. Neither party may name the registrar, the Registry, the Forum, or the Panelist as a party or otherwise include the registrar, the Registry, the Forum, or the Panelist in any judicial proceeding relating to the dispute or the administration of the SDRP policy. The parties shall indemnify, defend and hold harmless the registrar, the Registry, the Forum, 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, Forum, 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. The complainant shall be directly and solely liable to the registrant in the event the complaint is granted in circumstances where the registrant is lawfully entitled to registration and use of the registered domain name(s) in the TLD.
Relation to Other Dispute Resolution Policies
This SDRP is in addition to and complementary with the Uniform Domain Name Dispute Resolution Policy (“UDRP”), the Uniform Rapid Suspension System (“URS”) and any charter, nexus, or eligibility dispute policies adopted by ICANN or the Registry.
Effect of Other Proceedings
The administrative proceeding under the SDRP shall not prevent either party from submitting a dispute concerning the registered domain name in the TLD 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 outcome of such other proceeding.
The Registry reserves the right to modify this SDRP at any time subject to the terms of its MoU with the Forum. Such revised SDRP shall be posted on the Forum 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 the SDRP in effect at the time it was invoked will apply until the dispute is concluded. In the event that registrant objects to a change in this SDRP, the sole remedy is to cancel the registration, provided that registrant will not be entitled to a refund of any fees paid in connection with such registration.
Upon the commencement of the General Availability, available names will be allocated via Accredited Registrars on a first-come, first-served basis subject to the Registry Policies, ICANN requirements and the law and regulations of Turkey. All available domain names will be open to such registration.
No additional requirements apply to the applications submitted during General Availability, other than those set forth in Section 6.
A Registrar sponsoring an Applicant can submit an Application for Registration or may modify a Registration on behalf of the Domain Name Holder.
The first five (5) days of General Availability will consist of an Early Access Program (EAP) where domain registrations will be subject to additional fees. More details including the fee schedule can be found on the CoCCA Registrar Console.
By submitting an application for a domain name, an Applicant represents and warrants that: the Applicant has the authority to make an application; the application is made in good faith, for lawful purposes and does not infringe the rights of any third party; the information provided is current, complete, and accurate, and that the Applicant agrees to correct and update the information to ensure that it remains current, complete and accurate; any requests for further information or clarification from the Registry Operator or the Registrar will be responded promptly and accurately.
All Applicants must meet the following requirements, as well as the qualifications required by ICANN and TMCH as may be amended from time to time: a complete application must be submitted in accordance with the Registry Policies, and applicable fee(s) must be paid through the Registrar to the Registry Operator within the specific timeframe described in the Launch Schedule, applications must be forwarded to the Registry Operator through an ICANN-accredited Registrar who has signed the Registry Operator- Registrar Agreement with the Registry Operator, additional information must be provided, if requested by the Registry Operator or the Registrar.
Without limitation, applications may be rejected at the Registry Operator’s sole discretion, under any of the following circumstances:
- If the application is not in complete compliance with this Policy
- If it is necessary to protect the integrity and stability of the systems of the Registry Operator and BERO and/or the operation and/or administration of the TLDs
- If it is required to prevent any legal action against the Registry, the Registry Operator or BERO, or to comply with ICANN requirements or Turkish laws and regulations and any order or decision of Turkish judicial or administrative authorities
- If it is required to avoid liability on the part of the Registry Operator, the Registry and BERO and their contractors, subcontractors, affiliates, directors, employees, representatives, service providers and agents
The Registry Operator is also entitled to delete, revoke, cancel, suspend or transfer a registration, under the circumstances described in the Registration Policy.
In order to meet ICANN requirements, the Registry Operator shall provide a “Claims Period” for the TLDs. The Claims Period shall be applicable for the Early Access Program and Landrush Periods and first 90 (ninety) days of the General Availability. If, within the Claims Period, an Applicant submits an application for a domain name that is an identical match to a trademark record in TMCH, the Registrar shall forward a claims notice to such an Applicant. In this event, the Applicant will be required to explicitly confirm the information contained within the Claims Notice in order to proceed with the registration.
Applicants acknowledge and agree to have sole and direct liability for damages suffered by any third party injured as a consequence of a registration request for and/or the registration of a name in the TLD(s) under this Policy. Applicants also acknowledge and agree to indemnify and hold the Registry, the Registry Operator and BERO and their affiliates, subsidiaries, contractors, subcontractors, officers, directors, representatives, employees, and stockholders harmless for any claims, causes of action, damages, or injuries resulting from their actions, omissions, or errors. Applicants may be required by the Registry Operator, at its sole discretion, to provide reasonable and sufficient surety of indemnification against any costs or fees incurred by the Registry Operator as a consequence of third party claims arising from the applicant’s registration request for and/or the registration of a name in the TLD(s) under this Policy.
The applicable fees for applications made during the Launch Period shall be as follows:
Early Access Program and Landrush Period Applicants must pay application fees that are non-refundable. Registration fee will be taken if an application is successful. Domain name renewal fee will be required to be paid if the registrant desires to extend the registration period. Auction fee and final bid price will be applicable where an auction process is executed in relation to Landrush applications.
Applicants agree that there may be other applicable fees required by the Registrar, Auction Provider, TMCH or other related parties involved in the process.
All Applicants agree to participate in and abide by any determinations made as part of the General Dispute Resolution Policy and acknowledge that registrations for the Sunrise Period may be challenged through the Sunrise Dispute Resolution Policy.
The applicable fees for applications made during the Launch Period shall be as follows:
- Early Access Program and Landrush Period Applicants must pay application fees that are non-refundable
- Registration fee will be taken if an application is successful
- Domain name renewal fee will be required to be paid if the registrant desires to extend the registration period
- Auction fee and final bid price will be applicable where an auction process is executed in relation to Landrush applications
- Applicants agree that there may be other applicable fees required by the Registrar, Auction Provider, TMCH or other related parties involved in the process
- All Applicants agree to participate in and abide by any determinations made as part of the General Dispute Resolution Policy and acknowledge that registrations for the Sunrise Period may be challenged through the Sunrise Dispute Resolution Policy.
This Policy (“Policy”) defines the Data Publication Service (Whois) as required by ICANN in the Registry Agreement. Interlink Co., Ltd. (“Registry Operator”) is required to collect and provide domain name registration information (“Whois Data”) for a variety of purposes.
The Registry provides Thick Whois access to Whois Data through a standard text-based network protocol on Port 43. Whois Data can also be accessed on the Registry’s website using a standard web interface at www.nic.earth. Both interfaces are publicly available at no cost to the user and are reachable worldwide. This service is available to any Internet user and the use of such service does not require prior authorization or permission.
Asia Green IT System Ltd. Sti. the Registry Operator (“Registry”) for .nowruz, has collected this information for the WHOIS database through an ICANN-Accredited Registrar. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .nowruz registry database. Registry makes this information available to you “as is” and does not guarantee its accuracy. Failure to locate a record in the Whois database is not indicative of the availability of a domain name. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances, will you use this data:
- To allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone
- In contravention of any applicable data and privacy protection acts
- To enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without Registry’s prior written permission.
Registry reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms.
Security and Stability Considerations
Abuse of the Registry’s Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Such queries by non-authorized parties will be limited and unauthorized queries may result in responses that do not include data sets representing significant portions of the registration database.
The Registry will employ a blacklist to block access to Whois Data by those found to violate this Policy or any Registry policy. At the Registry’s sole and complete discretion, individual Internet protocol (“IP”) addresses or IP ranges may be blocked from accessing Whois Data.
When using the Registry Operator’s Whois service, consider the following:
- The Whois service is not a replacement for standard EPP commands;
- Whois Data is not considered authoritative for registered domain objects;
- The Whois service may be scheduled for downtime during production or operation, testing and evaluation maintenance periods;
- Queries to the Whois service may be “throttled” that is, if too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access).
Information regarding the Registry’s searchable Whois service is available on its website at www.nic.nowruz.
Conditions for Registrars Offering Privacy and Proxy Services
Accredited registrars may elect to offer Privacy and Proxy Services for registrations in the .nowruz TLD. In such an event, registrars must ensure that the actual WHOIS data is obtained from the registrant and must maintain accurate records of such data. Registrars shall maintain compliance with any future specifications of Privacy and Proxy Services developed by ICANN.
In the event that the registration information collected is masked by privacy or proxy services, registrars must provide Law Enforcement Agencies (“LEA”) with the actual WHOIS data upon receipt of a verified request in order to establish liability for all actions in relation to a domain name.
In addition, where a domain name is removed from the root zone, the domain name record may still appear in the gTLD WHOIS database so that the name and entities can be investigated by LEA should they elect to become involved.
The AGIT Registry operating the .nowruz Top Level Domain (TLD) and is subject to applicable privacy Laws. AGIT and the Registry Service Provider CoCCA are subject to the privacy laws of Turkey and Australia. The Registry collects information about visitors to the AGIT websites and .nowruz registrants through a variety of different means and is stored and accessed in a number of different methods. At any time, the Registry or its Service provider may modify this Policy. Modifications shall be effective upon the posting of the Policy on the .nowruz Registry website and giving ninety (90) days prior written notice to .nowruz accredited Registrars.
On the protection of individuals with regard to the processing of personal data and the free movement of such data and any applicable local legal requirements regarding data privacy in the territories in which we operate (“applicable data privacy law”).
The Information We Collect and How We Use It
Unless the purposes for collecting personal information are obvious and the user voluntarily provides his or her personal information for those purposes, we will communicate the purposes for which personal information is being collected, either orally or in writing, before or at the time of collection.
We will only collect client, customer, member information that is necessary to fulfill the following purposes:
- To collect Doman Name Registration, Administrative, Billing Technical Contacts, a registrar will collect: contact name, organization, Street address, state/province, postal code, country, phone, fax, email and payment information; Note that payment information is not shared to the Registry
- To collect Registration Information: registrant information, sponsoring registrar, name servers, DNSSEC records, the creation and expiration date of the domain name, transfer authorization codes, status codes
- To verify identity
- To open and manage an account
- To deliver requested services
- To publish Whois Information
- To publish DNS zone files used in the functioning of domains (domain name, name servers, DNSSEC) – this information can be accessed by third parties who also have access to the zone files and through public DNS Services
- To ensure a high standard of service to our users
- To meet regulatory and legal requirements;
- To support the security and stability of the Internet
- To aggregate information and statistics for the purposes of monitoring use in order to maintain and develop it. The information will identify any individual or undertaking but we may provide it to third parties.
We will obtain user consent to collect, use or disclose personal information (except where, as noted below).
Consent can be provided electronically or it can be implied where the purpose for collecting using or disclosing the personal information would be considered obvious and the user voluntarily provides personal information for that purpose.
We may collect, use or disclose personal information without the user’s knowledge or consent in the following limited circumstances:
- When the collection, use or disclosure of personal information is permitted or required by law
- In an emergency that threatens an individual’s life, health, or personal security
- When we require legal advice from a lawyer
- To protect ourselves from fraud
- To investigate an anticipated breach of an agreement or a contravention of law
- To combat intellectual property and trademark infringement
Where your employer is a subsidiary within a group of companies, we may disclose information relating to business conducted through the AGIT Registry by you on behalf of your employer (which information may identify you as the sender and recipient of the relevant messages) to the parent company of your employer’s group.
We also reserve the right to disclose the information we have collected about you to our professional advisers and to any assignee of our rights (on the basis that such assignees use such information only for the purposes of the operation of the AGIT Registry).
Where links have been provided to other web site(s), please be aware that we are not responsible for the content or privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of any other site that collects personally identifiable information.
How we Protect Your Information
For the purposes of data privacy, the Registrar is the data controller of the personal information processed in relation to the AGIT Registry.
The AGIT Registry will be hosted on a server operated by the Registrar or by a third party on its behalf. The AGIT Registry server is currently located in secure premises in Ireland. Your personal data will be processed by the Registrar (or any other third party to whom we may outsource the hosting or operation of the AGIT Registry website) in accordance with applicable data privacy law. The server will not be relocated to a country which does not provide a similar level of legal protection for personal data without your being notified first.
We will take appropriate measures including the introduction of IT security and operational measures to protect the information on the AGIT Registry website. The AGIT may only be accessed via the public internet using, in certain cases, a unique user I.D. and password. We will take steps to restrict the information which is available to users of the AGIT Registry so far as practicable to that which is necessary for their involvement in the AGIT Registry.
We have installed a system to ensure that communications between the AGIT Registry and its users travel along an encrypted connection, commonly referred to as SSL, that uses digital server identities to help ensure that information you provide is passed only to the AGIT Registry.
When you transmit information to the AGIT Registry, your browser will be provided with a digital certificate confirming that you have accessed our website and communications between you and the AGIT Registry will be encrypted. Firewalls are used to attempt to block unauthorised traffic to the servers and databases and the actual servers are located in a secure location which can be accessed only by authorised personnel.
We also take appropriate measures to keep your information confidential. The Registrar’s internal procedures cover the storage, access and disclosure of your information. Where appropriate, please remember to log out of the AGIT Registry when not using it to prevent unauthorised access.
We use “cookies” on this site. A cookie is a piece of data stored on a site visitor’s hard drive to help us improve your access to our site and identify repeat visitors to our site. For instance, when we use a cookie to identify you, you would not have to log in a password more than once, thereby saving time while on our site. Cookies can also enable us to track and target the interests of our users to enhance the experience on our site. Usage of a cookie is in no way linked to any personally identifiable information on our site.
 Applicant Guidebook 4 June 2012, Module 5, Page 8, Article 6.2.4. A dispute under this section also addresses the TLD Criteria from ICANN’s Trademark Clearinghouse Rights Protection Mechanism Applicant Guidebook 4 June 2012, Module 5, Page 8, Article 6.2.4. A dispute under this section also addresses the TLD Criteria from ICANN’s Trademark Clearinghouse Rights Protection Mechanism Requirements [published 30 September 2013], Article 2.3.6 and Article 188.8.131.52. The Forum’s SDRP does not interact with (nor instruct) the Trademark Clearinghouse and is limited to adjudicating disputes over the Registry’s registration and allocation of domain names during the sunrise period.
 For the purposes of analysis of this element, neither the gTLD itself, nor the “dot,” shall be considered.
 A Registry may, through its agreement with registrars, instead require the registrar to perform the lock and/or implementation steps.
 A Registry may, through its agreement with registrars, instead require the registrar to perform the lock and implementation steps.
 The Forum may correct typographical errors without notice.