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
.ADAC	Allgemeiner Deutscher Automobil-Club e.V. (ADAC)	zentrale.adac.de	View

1) At least during the initial months or even years following the delegation of the .ADAC gTLD to the Applicant, this extension is likely going to be a so-called “single registrant TLD” as contemplated by ICANN in Article 4.5 of the template Registry Operator Agreement (“Transition of Registry upon Termination of Agreement”). For the avoidance of doubt, a “single registrant TLD” is a TLD where “(i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for its own exclusive use, and (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator.”
This will allow the Applicant to build awareness amongst its membership and the Internet community at large that the .ADAC gTLD exists, that the domain names registered under .ADAC and the content provided on the websites to which those domain names point are managed by ADAC.
At a later stage, in addition to ADAC, its Stakeholders will possibly be entitled to register domain names in .ADAC. That is to say, one of the main eligibility criteria will be that the interested party wishing to register a domain name in the .ADAC TLD is either a member of the Applicant or has a sufficiently close link to the ADAC community.
In any event, ADAC reserves the right to change or restrict any policies, procedures and practices at any point in time if it is of the opinion that there would be a risk that the reputation of the ADAC brand would be damaged.
2) The domain names to be registered by ADAC and, as the case may be at a later stage, its Stakeholders, will likely be limited to the following:
a) registered trademarks of ADAC;
b) names of the regional and local clubs of ADAC;
c) names of the individual members of ADAC;
d) names of departments within ADAC;
e) names of foundations and social initiatives supported by ADAC;
f) names of events (e.g. motorsports events) organized by ADAC;
g) names of directors and officers of the Applicant and its subsidiaries, including its employees;
h) names of subsidiaries;
i) names of foundations and sponsorships established or supported by the Applicant;
j) names of third parties who provide services on behalf of the Applicant to its members and third parties who offer products and services on favorable terms to the Applicant’s members.;
k) names of co-operation and business partners;
l) etc.
Furthermore, ADAC envisages registering a fair number of generic words that are directly or indirectly related to the services and products offered to and the activities organized by the various members of ADAC.
In addition to that, the Applicant will likely require that second-level names meet certain technical and syntax requirements such as that
a) the A-label will have to consist exclusively of the letters A-Z (case insensitive, however including special characters that are part of the German alphabet, such as e.g. “ä” and “ö”), the numbers 0-9 and the hyphen (“-“), subject to the restrictions set out below;
b) the domain name cannot begin or end with a hyphen (“-“);
c) underlined characters will not be allowed;
d) the domain name cannot exceed 63 characters (excluding the TLD);
e) the domain name will have to have a minimum length of 1 character.
The Applicant will reserve the right to itself to grant exemptions from some or even all of these requirements.
Moreover, the Applicant will possibly draw up a list of reserved names which will not be available for registration and also put possibly special provisions in place for geographic names (see reply to Question 22 below), The Applicant will however reserve the right to allocate to and register a domain name mentioned on the list of reserved names in the name of a party indicated by the Applicant.
3) The Applicant will likely require that the content and use made by a registrant of a second-level domain name in the .ADAC TLD clearly relates to the ADAC community, e.g. by way of
a) providing information on the activities of the Applicant, its regional or local clubs or a third party affiliated with the Applicant (e.g. vintage car clubs);
b) offering products and services to the members of the Applicant, some of which may be on favorable terms for its members;
c) etc.
The Applicant will in any case require that all content and use offered under the .ADAC TLD complies with all applicable laws, including, but not limited to, trademark laws, criminal laws, data protection laws etc. To that end, ADAC will likely require applicants for a second-level domain name registration to warrant that
a) to their knowledge, the registration of the domain name will not infringe upon or otherwise violate the rights of any third party;
b) the applicant is not submitting the domain name registration request and, upon registration, will not use the domain name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and⁄or contrary to good and fair business practices; and
c) it will not knowingly use the domain name in violation of any applicable laws or regulations, including third party interests; and
d) it will keep the WHOIS information related to the domain name accurate and up-to-date at all times, both with its accredited registrar and ADAC.
ADAC reserves the right to change or restrict any policies, procedures and practices at any point in time if it is of the opinion that there would be a risk that the reputation of the ADAC brand would be damaged by the content or use made by a registrant of a second-level domain name in the .ADAC TLD.
4) Prior to the registration of a domain name in .ADAC, ADAC will require its legal and intellectual property department to review the list of these domain names on a regular basis in order to satisfy itself that they will not infringe the rights of third parties. In addition, ADAC might install a complaints point of contact who can be addressed if a third party deems its rights being violated by a second-level domain name in .ADAC. This complaints point of contact will be installed within the organization of the Applicant and will conduct an investigation of the complaint, if need be in cooperation with external legal advisers. Since the Applicant already offers diverse content under different domain names it has considerable experience in monitoring and ensuring compliance with the applicable laws. The Applicant will be able to leverage on this considerable experience but is committed to invest additional resources should the operation of .ADAC require so.
Furthermore, any party will likely be entitled to request the complaints point of contact for further clarification or information with respect to a second-level domain name registration prior to or following the procedures which will be published on .ADAC. The complaints point of contact may mediate between the complainant and the (prospective) registrant and will likely have the right and the powers to suspend, cancel or delete an application for or a registered second-level domain name. No fees will likely be charged by ADAC or the complaints point of contact in connection with any such mediation or remedy, which will likely be the only remedy offered by ADAC to the complainant.
The Applicant’s domain name registration policies will contain clear rules and procedures with respect to:
a) verifying, on a regular ⁄ spot-check basis, that the registrant of a particular domain name still meets the eligibility requirements for being a .ADAC domain name registrant;
b) verifying on a regular ⁄ spot-check basis, that the content provided under .ADAC domain names is in line with the acceptable use policies and marketing guidelines issued by ADAC from time to time in relation websites operating under the .ADAC gTLD.
In case of complaints from third parties arising after the registration of a domain name that likely infringes the trademark rights of a third party, the registrant will be contractually obliged to
a) conduct any such proceedings before an ICANN approved dispute resolution service provider in accordance with the UDRP, the URS, the Rules for UDRP and URS and any relevant supplemental rules, as made available on the relevant websites and⁄or the Rules for URS and any relevant supplemental rules, as made available on the relevant websites); and
b) to participate in good faith in any domain name dispute initiated by a third party complainant under the UDRP or URS against the registrant in compliance therewith and with the Rules for UDRP and⁄or URS.