.NGO

NGO stands for non-governmental organisation. NGOs are organisations whose mission and activities are broadly centered on improving the human condition and, are non-governmental, non-profit and non-criminal. ONG is the abbreviated translation for non-governmental organisation in romance languages.

.NGO
Overview
Introduced	2015
Category	Culture & Community
Registry	Public Interest Registry
IDN Capable	Yes
Dispute Policy	ICANN Rules
Webpage	Register .NGO
Legal Information
Legal	TBA

Registry

TLD	-
Registry	PIR
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.pir.org
WHOIS-Update	Real-Time
Min. Characters	3
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 1 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	Yes
Restore capable	Real-Time
Handle Updates	Supported
Registration System	Real-Time
Allowed number of NS	0 to 13
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
Root Nameserver Update	Real-Time
SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer ACK by	Registrar
Transfer NACK by	Registrar
Transfer Lock	Yes
Owner Change by	ICANN-TRADE

Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-5 days
Finalization Period	1 day
Failure Period	44 days
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	5 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

Registration Eligibility and Validation

The Registry uses seven distinct characteristics to define an NGO: registrant hereby certifies that it meets the following .NGO and .ONG eligibility requirements when it purchases its .NGO and .ONG domain name bundle(s):

• Focused on acting in the public interest. Whether in support of education or health, the environment or human rights, members of the NGO & ONG community work for the good of humankind and/or the preservation of the planet and do not promote discrimination or bigotry.
• Non-profit focused entities. While many NGOs & ONGs engage in commercial activities or generate revenue in support of their missions, members of the NGO & ONG community do not recognise profits or retain earnings.
• Limited government influence*. Recognising that many NGOs have important interactions with government, not least for reasons of funding (which may include receipt of some government funding in support of their programs), members of the NGO & ONG community decide their own policies, direct their own activities and are independent of direct government or political control.
• Independent actors*. Members of the NGO & ONG community should not be political parties nor should be a part of any government. Participation in the work of an NGO or ONG is voluntary.
• Active Organisations. Members of the NGO & ONG community are actively pursuing their missions on a regular basis.
• Structured. Members of the NGO & ONG community, whether large or small, operate in a structured manner (e.g., under bylaws, codes of conduct, organisational standards, or other governance structures.)
• Lawful. Members of the NGO & ONG community act with integrity within the bounds of law.

PIR has determined that organizations formed under the laws of the People’s Republic of China (or any territory thereof) do not meet the criteria “Limited Government Influence” and “Independent Actors.” Accordingly, prospective registrants from China and its territories should not register .NGO and .ONG bundles as they will not meet PIR’s Eligibility Requirements. In the event PIR discovers that a .NGO and .ONG bundle is registered by an organization organized under the laws of the People’s Republic of China (or any territory thereof), PIR will delete the registration bundle for failing to meet our Eligibility Requirements.

PIR is a U.S. company subject to U.S. law. Registrant hereby certifies that neither it nor any of its subsidiaries or, to its knowledge, any director, officer, or employee of Registrant or any of its subsidiaries is a person who (a) is the target of any laws administered by the United States Department of the Treasury’s Office of Foreign Assets Control (“OFAC”) or any other United States governmental entity imposing economic sanctions and trade embargoes, or (b) is located, organized or resident in a country or territory that is, or whose government is, the target of sanctions imposed by OFAC or any other United States governmental entity. Re*gistrant understands and agrees that PIR does not permit registrations from Registrants residing in or organized under any such country in the .ngo and .ong TLDs.* In the event PIR discovers that any .ngo and .ong bundle is registered by a Registrant that would not be permitted by any OFAC restrictions (or other restrictions imposed by U.S. law), the domain name bundle will be deleted.

Technical Bundling with .ONG

Please note that the TLDs .ONG and .NGO are no longer included in one registration. On June 1st 2022, the responsible registry has separated .NGO and .ONG domains. Since then, registrants are able to register .NGO and .ONG domains separately. In addition, the registry has allocate new .ONG domains for all registrants of the .NGO and .ONG bundles which existed at that time.

API

Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
X-NGO-ACCEPT-REGISTRATION-TAC = 1

OPTIONAL

auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

Please see the section below called TLD Specific for futher explanation on the registration process

Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar.

Please note that HEXONET is acting in compliance with ICANN Transfer Guidelines. The respective policies can be viewed under http://www.icann.org/transfers/ :

As soon as you have submitted a transfer request, the HEXONET system start the transfer through the official registry and the losing registrar will receive the transfer request. The losing registrar will then send an email to the domain registrant/administrative contact, allowing them to deny the pending transfer. If there is no response received within 5 days, the transfer will automatically be processed.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

auth = (TEXT)

OPTIONAL

period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

subuser = (TEXT)
renewalmode = (NULL) | (TEXT)

Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

TLD specific

Authorization code

There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a .COM domain:

• Minimum 8 characters
• having at least one (1) numeric,
• one (1) alphabetic, and
• one (1) special character

You may generate a valid random auth code by adding this parameter to the ModifyDomain command:

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

generaterandomauth = 1

Addons

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Addon Class	Parameter to (de)activate *1)	Renewal term *2)	Affected Parameters *3)
Proxy (WHOISTRUSTEELITE_ORG)	X-ACCEPT-WHOISTRUSTEELITE-TAC = 0 | 1	1 month	All Contacts
Proxy (WHOISTRUSTEE_ORG)	X-ACCEPT-WHOISTRUSTEE-TAC = 0 | 1	1 month	All Contacts

*1) Parameter to (de)activate: When accessing our backend through the API, you can either activate the addon with X-ACCEPT-WHOISTRUSTEELITE-TAC=1 or deactivate it with
      X-ACCEPT-WHOISTRUSTEELITE-TAC=0

*2) Renewal Term: Is the minimum renewal term of the "Addon Class"

*3) If you are using a "Proxy" Domain Addon normally all contact handles are affected (registrant, admin, tech, and billing contact).
      
      

RegistrarOC

ICANN Whois Data Reminder Policy (WDRP)

At least annually, a registrar must present to the registrant the current Whois information, and remind the registrant that provision of false Whois information can be grounds for cancellation of his domain name registration. Registrants must review their Whois data, and make any corrections.

ICANN Registrar Data Escrow Program (RDE)

Under the data escrow provision of the Registrar Accreditation Agreement (RAA), all ICANN-accredited registrars must regularly deposit a backup copy of their gTLD registration data with ICANN through ICANN's arrangement with Iron Mountain or they may elect to use a Third Party Provider of RDE services that has been approved by ICANN.

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.

Please do not initiate a restore directly at the registry (e.g. using the registrar webinterface). All restore operations must be performed through our system.