gTLD	Full Legal Name	E-mail suffix	Detail
.NGO	Public Interest Registry	pir.org	View

PIR’s goal is to provide the NGO Community an exclusive and immediately recognized home on the Internet. To achieve this goal and ensure that .NGO domain names are allocated in a manner that serves the NGO Community, PIR has developed a set of .NGO registration restriction policies and corresponding compliance and enforcement mechanisms.

The policies are built to match the need of the NGO Community based on feedback from NGO Community members; based on experience from the .ORG gTLD management since 2003; and generally established to ensure a higher security level for .NGO domain names than what currently is considered standard global requirements for gTLDs today.

.NGO Registration Policies
The registration policies in support of the NGO Community goals are described in the following summary and are detailed later in this section.
• Registrant Eligibility Requirements – all registrants must demonstrate affiliation through NGO membership organizations or through evidence of NGO status. PIR will work with membership organization, the NGO Community Advisory Council, and other members of the NGO Community to validate their eligibility.
• Name Selection Policy – ensures that only NGO Community relevant domain names are registered.
• Reserved Name Policy – names⁄types of domain names will initially be reserved from registration under .NGO.
• Registry Name Policy – names⁄types of domain names will be held from general availability, these will be used in support of the registry.
• Content and Use Restriction Policy – ensures that usage of the .NGO domain name corresponds with NGO Community activities.
• Compliance Functions – ensures ongoing compliance of the Registrant Eligibility Requirements, and the Content and Use Restriction Policy listed below.

The following policies support of the NGO Community goals and are detailed in subsequent Evaluation Questions of the application dedicated to such policies, as noted below.
• Abuse Prevention and Mitigation – includes the Anti-Abuse Policy which addresses the identification and prompt action taken on malicious use of domain names, and the Restriction Dispute Resolution Policy (RDRP) which ensures that disputes concerning any of the .NGO Registration Policies can be solved in an appropriate manner. Detailed descriptions of both policies can be found in response to Evaluation Question #28.
• Rights Protection Mechanisms – protects intellectual property holders under the Trademark Clearinghouse, Uniform Dispute Resolution Policy (UDRP), Uniform Rapid Suspension (URS), Registry Restrictions Dispute Resolution Procedures (RRDRP),Post-Delegation Dispute Resolution Policy (PDDRP), in addition to the Sunrise services and policies that can be found in response to Evaluation Question #29.

PIR will review all policies and processes on an annual basis with involvement from the PIR’s NGO Community Advisory Council and present the results to the NGO Community, allowing them to provide feedback.

Specific Policy Details

Registrant Eligibility Requirements: The .NGO domain registrations are open to NGO Community members. All registrants must demonstrate affiliation through NGO membership organizations or through evidence of NGO status. PIR will work with NGO membership organizations, the NGO Community Advisory Council, and other members of the NGO Community to validate their eligibility.

In consultation with PIR’s NGO Community Advisory Council PIR is reviewing potential NGO membership organizations who can verify the NGO status of registrants. NGO membership organizations include the following, and will expand over time:
• Global organizations: International associations and⁄or classification-based associations.
• Regional organizations: Associations across broad geographic areas, potentially including multiple countries or jurisdictions.
• Local organizations: Associations or groups that provide support and memberships at a country or local level.

During the registration process, the registrant will be asked to verify their eligibility and to demonstrate affiliation with a NGO member organization. Once the initial certification in step 1 of the verification process is confirmed, the domain is successfully created. If the .NGO registrant fails to provide any additional required information through step 2 of the verification process, the domain will be deleted and released back into the pool of available domains.

Content and Use Restriction Policy: Abusive use of the .NGO domain names will not be tolerated by PIR. The following use and content limitations apply:
• Overall the NGO domain name must be for a bona fide NGO use, as defined in the Restrictions Dispute Resolution in response to Evaluation Question #28.
• Websites must be developed with the intent to promote the corresponding .NGO registrant’s existing mission and activities, and not solely for commercialized or for-profit marketing usage.
• Use of the registered domain name to engage in activities inconsistent with the mission of a NGO is not allowed.
• Any illegal or fraudulent usage of the .NGO domain name is not allowed, including but not limited to phishing and pharming attacks, distribution of malware, and distribution of adult content.
• Registration and use of a domain name in violation of Rights Protection Mechanisms is not allowed.

Violations of any of the .NGO Registration Policies may be grounds for loss of registration, pursuant to the enforcement mechanism discussed below (with an appeal procedure).

Compliance Functions: While disputes will be managed directly by resolution providers, PIR will conduct random compliance audits across all the .NGO Registration Policies. Periodically PIRʹs compliance staff will audit a sample of .NGO registrations to verify claims to membership in a listed organization, name policy adherence, and compliance with the name and use policy.

If a registrant is found to not be in compliance the registrant will be notified that the domain will be placed on registry lock and that if the compliance issue is not cured the domain will be terminated.

As part of the compliance function PIR will also utilize its existing expertise, obtained through its management of .ORG, to monitor and take action on any abusive behavior taken place with .NGO domain names.

Name Selection Policy: The .NGO registrant must fulfill certain name policy criteria. PIR will employ the following restrictions concerning the names that eligible .NGO registrants can register. As such a .NGO registrant cannot register any name they wish but is limited by the following restrictions. A .NGO registered domain name may be:
1) the name of (entire or portion of) the NGO, e.g. its “doing business as” name,
2) an acronym representing the NGO,
3) a name that recognizes or generally describes the NGO, or
4) a name related to the mission or activities of the NGO.

Reserved Name Policy: The following names⁄types of domain names will initially be reserved from registration:
• All single- and two-character second-level domain names;
• Domains of an inappropriate nature, e.g., adult-related terminology, pursuant to a list defined by PIR and its NGO Community Advisory Council;
• Names provided by ICANN as required reserved names;
• A list of generic names defined by PIR and its NGO Community Advisory Council based on the overall criteria that the names represent the NGO Community in a general manner. Such names will be released in a specific RFP process ensuring that the names will benefit the NGO Community.

Registry Name Policy: The following names⁄types of domain names will be held from general availability; they will be used in support of the registry.
• Names to support registry operations, e.g., directory.ngo;
• Names to support PIR’s NGO Community Advisory Council.

Compliance and Enforcement Mechanisms
PIR will take both proactive and reactive measures to enforce the policies of the gTLD. Proactive measures are taken at the time of registration by requiring .NGO registrants to meet the .NGO Registration Policies and to agree to all policies and procedures of the gTLD. Reactive measures are addressed via our audit process and through our defined dispute resolution processes.

A violation of the .NGO Registration Policies will be enforced on a case-by-case, fact specific basis under the processes set forth below:
1. Any allegation that a domain name is not used primarily for NGO purposes shall be enforced under the provisions of the Restrictions Dispute Resolution Policy (ʺRDRPʺ) as described in Evaluation Question #28. The RDRP will be included as an appendix to the Registry Agreement. An appeal procedure is included in the RDRP.
2. Any alleged violation of the Rights Protection Mechanisms shall be enforced under the provisions contained in each of them.

Disputes resulting from violations of the .NGO Registration Policies will be resolved through the Compliance Functions and the Rights Protection Mechanisms. The Rights Protection Mechanisms (as detailed in Evaluation Question #29) will be made applicable by the ICANN-Accredited Registrarsʹ registration agreements with registrants. Proceedings under the Rights Protection Mechanisms will be conducted in accordance with the policies and procedures that will be included in an appendix to the Registry Agreement. As set forth in the Compliance Functions, the registry operator will review on a random basis, monitor, and verify that any particular domain name is being used primarily for NGO purposes and that a domain is being used in compliance with the Rights Protection Mechanisms processes.

Resource Plans
PIR will devote 2 compliance officers to handle compliance and disputes as they arise, although currently for .ORG this need is rare. Most compliance checks on registration eligibility are expected to be handled in an automated process.

gTLD	Full Legal Name	E-mail suffix	Detail
.merck	Merck KGaA	bettinger.de	View

The registration criteria for the “.MERCK” space will be tailored to serve the Merck Community and to provide clarity for Internet users. Specifically, the process will contain four components, consisting of: 1) registration restriction, including the prohibition of Reserved or Geographic second-level strings, 2) content restriction, ensuring that the “.MERCK” space is used only for Community purposes and for the benefit of the Community, 3) an ongoing monitoring and verification process, and 4) dispute resolution procedures. For the full text, see the “.MERCK” Registration Restrictions and Use Policy in Question 28.


A. Registration

- Eligibility Requirements. To be recognized as a member of the Merck Community, a Registrant must meet the Eligibility Requirements, which are:

- the Registrant is either Merck KGaA, the Registry Operator of the gTLD “.MERCK,” or is a company which is a fully owned subsidiary of Merck KGaA,
- the Registrant uses “Merck” as the sole element or as a component of its company name, and
- the Registrant uses as its umbrella brand the German figurative trademark No. 30130670, “MERCK”

If a member of the Merck Community wishes to register a “.MERCK” domain name it must first request, and receive, a Merck Community Membership ID from Merck KGaA. Additionally, it must request and receive an Approval Statement for the specific second level string, as detailed above under Question 18(b). The registrant must provide its Merck Community Membership ID in any application for a “.MERCK” domain name through an accredited registrar.

- Registration Process. Registration of a “.MERCK” domain name is done in 3 steps: Identification of the Registrant, Approval of the Domain Name, and Registration. A detailed outline of this process is provided above in section 18(b). After Registration, the holder of a “.MERCK” domain name must comply with the Acceptable Use Guidelines (see Question 18(c)).

- Application for a Merck Community Membership ID. A prospective registrant must request a Merck Community Membership ID from Merck KGaA prior to submitting a registration request to a registrar. Such request for a Merck Community Membership ID must provide evidence of the applicant’s Community Member status and an express agreement to the requirements set out in the “.MERCK” Registration Restrictions and Use Policy.

If Merck KGaA determines that the prospective registrant is a member of the Merck Community, Merck KGaA will issue a Merck Community Membership ID. If Merck KGaA declines to issue a Merck Community Membership ID, the prospective applicant may pursue a review of this decision through the “.MERCK” Eligibility and Functionality Reconsideration Policy (“MEFRP”)(see Question 29).

A.1 String Requirements

Second-Level Domain names within the “.MERCK” TLD must only include hyphens in the third and fourth position if they represent valid internationalized domain names in their ASCII encoding (for example ʺxn--ndk061nʺ), and must otherwise comply with any other applicable ICANN requirements.

A.2 Reserved Names

- The label “EXAMPLE” shall be reserved at the second level and at all other levels within the TLD at which Registry Operator makes registrations

- Two-character labels. All two-character labels shall be initially reserved. The reservation of a two-character label string may be released to the extent that Registry Operator reaches agreement with the government and country-code manager. The Registry Operator may also propose release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes

- Second-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the TLD: NIC, WWW, IRIS and WHOIS

- The List of Reserved Names shall be compiled by Merck KGaA and will be publicly posted online at [website to be determined]. Merck KGaA reserves the right to include new names in the list of reserved names, and to later add names to such list as it deems reasonably necessary for the benefit of the Merck Community

A.3 Country and Territory Names

The country and territory names contained in the following lists shall be initially reserved: the English short form of names on the ISO 3166-1 list; the UN’s Technical Reference Manual for the Standardization of Geographical Names, Part III; and the list of UN member states in 6 official languages, provided that specific names may be released to the extent that the Registry Operator reaches an agreement with the applicable government(s), and further provided that the Registry Operator may also propose release of these reservations, subject to ICANN review (full version at Q28).


B. Regulated second-level names within the “.MERCK” TLD

B.3 Eligibility

A registrant will be allowed to register any second-level name which follows the string requirements and common rules described above, and which has been previously approved by the Corporate Trademark Department at Merck KGaA in an Approval Statement issued to the registrant (outlined in 18(b)).

B.4 Allocation
Domain names will be allocated on a ʺfirst come, first servedʺ basis, subject to Merck KGaA Corporate Trademark Department’s prior approval. Registrations must further the mission and purpose of the Merck Community, not infringe any third-party rights, and comply with any applicable laws, government rules or requirements.

Merck KGaA has the authority to make changes to any domain name registration in the “.MERCK” space for the benefit of the Merck Community at large. Any registrant who disputes an action taken by Merck KGaA regarding a registration will have recourse under the MEFRP.

B.5 Registration Rules

Registration period and renewals. A “.MERCK” domain name may be registered or renewed subject to the current terms and conditions offered by the concerned Registrar.

Continuing eligibility. If a “.MERCK” registrant ceases to be a member of the Merck Community, then its “.MERCK” domain names may immediately be revoked and⁄or transferred at the discretion of Merck KGaA. Additionally, Merck KGaA will undertake ongoing monitoring activities to ensure that all registrants of “.MERCK” domain names remain bona fide members of the Merck Community. Additionally, if a registrant fails to comply with the terms and conditions set out in the “.MERCK” Registration Restrictions and Use Policy, Merck KGaA may in its sole discretion elect to transfer, cancel or revoke any relevant domain name registration(s) held by said registrant.

Transfers. A “.MERCK” domain name registrations may be transferred where: a) the company to whom the “.MERCK” domain name is to be transferred to meets the criteria set out in the “.MERCK” Registration Restrictions and Use Policy, b) the prescribed fee is paid, and c) Merck KGaA has previously approved the transfer of the domain name registration from the Transferor to the Transferee.


C. Content and Acceptable Use

Acceptable Use of “.MERCK”. All registrants will agree to abide by the Acceptable Use Guidelines established in the “.MERCK” Registration Restrictions and Use Policy. At a minimum, all “.MERCK” domain names shall be used to further the mission and purpose of the Merck Community, and to display only content related to the Community’s activities.

Furthermore, “.MERCK” domains shall not be used in any way that infringes third parties’ rights, is in breach of any applicable laws, government rules or requirements, to undertake any illegal or fraudulent actions (including spam or phishing activities), to defame the Merck Community, its businesses, employees, etc., to display pay-per-click links through a “parked” page; or to “warehouse” or otherwise fail to use the domain name to link to active content.

The “.MERCK” domain space shall be used for the benefit of the Merck Community at large. Merck KGaA will monitor the space and shall have the right to revoke any domain name registration or re-allocate any domain name registration to a different Community member should Merck KGaA deem such action appropriate for the benefit of the Community. Any registrant who disagrees with a decision taken by Merck KGaA regarding a domain name it has registered will have recourse under the MEFRP.


D. Ongoing Monitoring and Verification

Merck KGaA will “police” the Merck Community’s online space, which will reduce the risk of abuse. Merck KGaA will operate a verification system to prevent the misuse of Membership IDs and to ensure compliance with the “.MERCK” Registration Restrictions and Use Policy. Verification may be conducted by Merck KGaA directly or an assignee.

The verification process will ensure that each registrant still qualifies as a member of the Merck Community, and that domain names link to appropriate content.

Merck KGaA, as the Registry Operator, is responsible to the members of the Merck Community for the effective management of the “.MERCK” space, and accordingly will reserve the right in the “.MERCK” Registration Restrictions and Use Policy to make changes to domain name registrations (including their cancellation or transfer) as deemed necessary in the best interests of the Community at large. Any registrant who disagrees with a decision taken by Merck KGaA regarding a registration will have recourse under the MEFRP.


E. Dispute Resolution

A number of dispute resolution mechanisms will be available to third parties and⁄or Merck Community members including the: Trademark Post-Delegation Dispute Resolution Procedure, Registry Restrictions Dispute Resolution Procedure, Uniform Domain Name Dispute Resolution Policy, Uniform Rapid Suspension System, Charter Eligibility Dispute Resolution Policy, and the .MERCK Eligibility and Functionality Reconsideration Policy (see Question 29).