Revision as of 19:26, 15 May 2015 (view source) WikiAdmin (Talk | contribs) ← Older edit		Revision as of 19:27, 15 May 2015 (view source) WikiAdmin (Talk | contribs) Newer edit →
Line 171:		Line 171:
	Validation URL: https://www.OnGood.ngo?d1=<X-REGISTRANT-CLAIMID>		Validation URL: https://www.OnGood.ngo?d1=<X-REGISTRANT-CLAIMID>
−	[[File:Ngo_ClaimID.png|200px]]	+	[[File:NGO_ClaimID.png|200px]]

---

Revision as of 19:27, 15 May 2015

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

Contents 1 Registration Eligibility and Validation 2 Technical Bundling with .ONG 3 Registry 4 Periods 5 API 5.1 Domain Registration 5.2 Domain Transfer 5.3 Delete Domain 5.4 Restore Domain 5.5 Ownerchange 6 TLD specific 6.1 Validation and ClaimID 6.2 Authorization code 7 Addons 8 RegistrarOC 8.1 ICANN Whois Data Reminder Policy (WDRP) 8.2 ICANN Registrar Data Escrow Program (RDE) 8.3 Restore Process

Registration Eligibility and Validation

Step 1 (During Registration): NGOs participating as members in the OnGood community must certify the following

• Focused on acting in the public interest. Whether in support of education or health, the environment or human rights, members of the NGO 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 engage in commercial activities or generate revenue in support of their missions, members of the NGO 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 community decide their own policies, direct their own activities and are independent of direct government or political control.
• Independent actors. Members of the NGO 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 community are actively pursuing their missions on a regular basis.
• Structured. Members of the NGO 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 community act with integrity within the bounds of law.

Step 2 (via Email Post Registration): Provide the name[s] the NGO conducts business and specific governmental certification information. The NGO will be asked to provide their formal name and other names they do business, the country they are formally registered with to do business and any applicable identifying information, e.g., a tax identification or registration certification number

Step 3 (via Email Post Registration): Provide other credential information to demonstrate status as an NGO. The final step involves providing additional information to demonstrate NGO status

Validation: Registry will notify registrants of their pass or fail status. Passing validation will immediately result in the release of server hold and the registrant will have access to their domain name. For entities registering subsequent domain name bundles, all domains will have their validation term synced to the most recent registration. As a registrant benefit, this will simplify the re-validation process by having one validation date for all domains, regardless of multiple registration dates. Registrants purchasing additional domain names will simply need to confirm the accuracy of the validation data previously supplied. When transferring a domain that has not expired to a new registrant, the new registrant will be required to complete validation.

Technical Bundling with .ONG

Registration of domains in .ngo|.ong are technically “bundled.” This means that by registering and purchasing a domain in the .ngo TLD, for example, the NGO registrant is also registering and purchasing the corresponding name in the .ong TLD (and vice-versa for registrations in .ong). The Registrant cannot, for example, purchase “example.ngo” by itself; by purchasing the domain “example.ngo” the Registrant is also necessarily purchasing the domain “example.ong” due to the technical bundling of domains in .ngo|.ong.

• If the Registrant takes a particular action concerning the registration of a domain registered in .ngo (such as transferring or deleting the registration), the same action must also be taken for the corresponding .ong domain (and vice-versa).
• If any Registry, Registrar or Service Provider policies change concerning a domain registered in .ngo (including, but not limited to, denying, suspending, revoking, transferring or modifying the information or services provided in relation to any domain name), the Registry, Registrar or Service Provider will necessarily take the same action against the corresponding domain registered in the .ong TLD (and vice-versa).

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

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)

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

Validation and ClaimID

Upon initial registration, a ClaimID with property X-REGISTRANT-CLAIMID will be assigned to every .NGO domain. This value is available in the Control Panel under the 'Miscellaneous' tab for the respective .NGO domain name. To validate, the registrant will need to visit the OnGood.ngo website with their proper ClaimID appended as follows.

Validation URL: https://www.OnGood.ngo?d1=<X-REGISTRANT-CLAIMID>

200px

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

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.