RRPproxy Homepage
RRPproxy Homepage

.ngo

API commands

Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.

Domain Registration

(API Command reference » AddDomain)
Command
command         = AddDomain
domain          = yourdomain.ngo
period          = (INT)
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0	= (NAMESERVER)
nameserver1 	= (NAMESERVER)

After a successful registration of the domain, it will be transfer locked from the registry for a period of 60 days.

All registrants have to be validated, wherefore a link is provided in the response of an AddDomain command:

  • [RESPONSE]
    code = 200
    description = Command completed successfully [The domain registration is requested. To finish the registration please follow the link and complete the verification process: https://www.ngoood.ngo?d1=0994ab8d-df85-46bf-ae46-2317b2014d34]
  • Registrants will have 360 days from the domain create date to complete the validation process. If no action is taken, the validation process will expire after this period and the registration request will fail.

Domain Modification

(API Command reference » ModifyDomain)
Standard command
command = ModifyDomain
domain  = yourdomain.ngo

Change of registrant

Exception
command         = ModifyDomain
domain          = yourdomain.ngo
ownercontact0   = (CONTACT)

All registrants have to be validated, wherefore a link is provided in the response of the ModifyDomain command similar to the response of the AddDomain command.

ICANN OwnerChange

  • If the FoA mode is in place(default), the link will NOT be returned in the ModifyDomain response(DA will receive the response as shown for AddDomain). The verification link is included in the modification event after the losing and gaining registrant have approved the IRTP:
    • REGISTRAR:registrar1
      DATE:2018-12-18 11:19:51
      INDEX:1234
      CLASS:DOMAIN_MODIFICATION
      SUBCLASS:MODIFICATION_PENDING
      domain:example.ngo
      jobid:1234
      cltrid:ABCDEFE3-87BA-4653-81D4-D51CE9C034C9
      svtrid:ABCDEF4B-AEA3-46B6-9887-FBD86AB59D24
      reason:ownerchange pending; The ownerchange is requested. To finish the ownerchange please follow the link and complete the verification process: https://www.ongood.ngo?d1=83f59b8f-416d-455c-a717-ba3a96b79139
      ownerchange_status:successful
      losing_registrant:P-ABC1
      gaining_registrant:P-ABC2
  • StatusDomain response example:
    • [RESPONSE]
      code = 200
      description = Command completed successfully
      ...
      property[x-ngo-verification-link][0] = https://www.ongood.ngo?d1=1234567890
      property[x-ngo-verification-until][0] = 2019-12-20 00:00:00

Domain Renewal

(API Command reference » RenewDomain)
Command
command    = RenewDomain
domain     = yourdomain.ngo
period     = (INT)
expiration = (INT)

Domain Deletion

(API Command reference » DeleteDomain)
Command
COMMAND = DeleteDomain
DOMAIN = yourdomain.ngo

Domain Transfer

(API Command reference » TransferDomain)
Command
command = TransferDomain
domain = yourdomain.ngo
action = REQUEST
auth = (TEXT)

Transfer procedure

  • After the transfer has been requested, our backend system sends a confirmation email to the Owner/Admin-C according to the WHOIS of the respective domain. In order to initiate the transfer successfully it is important, that this email is confirmed.
  • After confirmation the transfer is initiated through the official registry and the losing registrar will receive the transfer request.
  • The losing registrar will also send an email to the Owner/Admin-C. allowing him/her to deny the transfer. If you do not respond to the email of the losing registrar, then the transfer will get processed successfully after 5 days.

If the Email-Address in the WHOIS is invalid, then the transfer cannot be processed.If this is the case, then kindly contact your current registrar and ask him to update the WHOIS information accordingly.

Transfer notes

  • A .ngo domain transfer must be initiated with a so-called authorisation code, which can be obtained from the current registrar through the owner or Admin-C of the domain.
  • Ensure that your respective domain does not have a lock-status (REGISTRAR-LOCK or HOLD). This can be seen in the WHOIS.
  • If the domain is locked, then the owner can demand that the domain will be unlocked.
  • Please note that we are only allowed to initiate a gTLD transfer after confirmation of the "ICANN Form of Authorization" by the current registrant. The policies can be viewed under http://www.icann.org/transfers/
  • After a successful transfer of the domain, it will be transfer locked from the registry for a period of 60 days.

Auth-Codes

The format for auth info requires a minimum length of 8 characters and a maximum length of 32 characters.

Additionally, auth info must contain at least one of each of the following three character types:

  • Alphabetic characters: a-z; A-Z
  • Numeric characters: 0-9
  • Special characters: !;<=$%?&@[()]*^+-,'-{.|/}:~

Domain Restore

(API Command reference » RestoreDomain)
Command
command = RestoreDomain
domain  = yourdomain.ngo

Domain Extensions

X-NGO-VERIFICATION-LINKContains the verification link received after a successful registration request.
X-NGO-VERIFICATION-UNTILContains the date until which the domain owner can validate his information. If the validation process is not finished until this date, the pending registration request will fail and the domain is released into public availability.

Domain Restrictions

Public Interest Registry has worked closely with the global NGO community to develop a validation process for NGOs and ONGs seeking to register .ngo domains. Seven criterias are used to define an NGO or ONG for the purpose of validation:

  1. 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.
  2. Non-profit making/non-profit-focused entities. While many NGOs and ONGs engage in commercial activities or generate revenue in support of theirs missions, members of the .ngo community do not recognize profits or retain earnings.
  3. Limited government influence. Recognizing that many .ngo organisations 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.
  4. 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 a .ngo is voluntary.
  5. Active Organisations. Members of the .ngo community are actively pursuing their missions on a regular basis.
  6. Structured. Members of the .ngo community, whether large or small, operate in a structured manner (e.g., under bylaws, codes of conduct, organizational standards, or other governancestructures.)
  7. Lawful. Members of the .ngo community act with integrity within the bounds of law. NGOs and ONGs participating as members in the .ngo community must certify that they adhere to the above .ngo Eligibility Criteria.

VALIDATION:

.ngo/.ong: Changes to the Registration Validation Process

PIR implemented changes to the registration process for .ngo/.ong domains that allow registrants to complete registration using self-certification instead of the former pre-validation process. Registrants must no longer leave the check-out flow to activate their domains.

Here are the changes:

  • The domain name is live once registration is completed.
  • The mandatory 2-year re-validation is no longer required.
  • Resellers must add a checkbox for the self-certification during their checkout process with a link to the .ngo/.ong Registration Policies:

I, the registrant, understand and agree to the .NGO and .ONG Registration policies and certify that my organization meets the eligibility requirements therein.

Please note that it is not the responsibility of the registrar to store the self-certification information. It is the registrant's responsibility to determine whether the domain name bundle registration infringes or violates someone else's rights. It is also the registrant's responsibility to determine whether the domain name bundle registration complies with the .ngo/.ong registration policies.

PIR conducts random audits of .ngo/.ong domain bundle registrations and reserves the right to cancel, transfer or modify a domain name in accordance with their policies.

BUNDLED REGISTRATION:

  • Please note that the TLDs .ONG and .NGO are included in one registration.
  • If you register .ONG, the same domain name will be registered under .NGO too, and vice versa.
  • Only the .NGO domain name will appear in your RRPproxy account domain list. All changes made to one domain will automatically be reflected on the other, apart from the DNSSEC information.

Supported IDN Scripts

The following IDN scripts are supported by .ngo.
Provide the LANGUAGE TAG corresponding to your desired IDN within the AddDomain command as X-IDN-LANGUAGE extension.

GermanDE
SpanishES

Get more information of "IDN tables", which represent permitted code points (letters) allowed for Internationalised Domain Name registrations in particular registries on IANA Repository of IDN Practices.

Wedomains :)