Knowledge Base

Check for answers to your questions by searching by keywords, or check categories below.

.ong

This article describes the procedures and requirements of .ong domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration via RCP or API requires:

Before a registration is active, the registrant is required to confirm that his organisation meets the eligibility criteria and that they are an authorised representative of the organisation. During the order process, you can do this by checking a checkbox in the reseller control panel. After this confirmation, a link will be provided (also in the control panel) to enable the registrant to undergo the Public Interest Registry validation process.

This is how the letter looks like:

Dear %username%,
Thank you for your interest in registering the 'domainname.ngo' domain name.
As you know, each application for a domain name in the .NGO and .ONG domain must be verified prior to activation. In accordance with the .NGO and .ONG Registration Policy which you accepted during the registration process (see http://pir.org/policies/ngo-ong-policies/registration-policies-for-ngo-ong/), the registry has developed a simple process to walk you through the verification steps; this is the first step in that process.
You only have until %DATE% to complete the verification process OR YOUR NAME WILL BE DELETED and you will need to register it again (if it is still available) in order to activate it.
The first step is for you to click on the link below and either create or log into your account.
https://www.url.ngo?d1=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXX
Once you have signed in to your account, you will be asked for certain information that will be used by the .NGO and .ONG Verification Team to verify your eligibility.
Please note that it is your responsibility to ensure that the verification process is completed, including the registry’s evaluation of the material requested in this email, by %DATE,TIME%, or your domain registration will be deleted. WE STRONGLY ENCOURAGE YOU TO BEGIN TODAY AND PROVIDE THE REQUIRED INFORMATION WELL BEFORE %DATE,TIME%, as evaluation of your materials will take time.
Please click on the link above and provide the information requested by the Registry as soon as possible. If you have any questions, please contact your provider customer service.
Regards,
Registrar.eu

Registrants will have 360 days to complete this, during which time the domain will be placed on server hold. Every 2 years, re-validation is required. If validation is not finished within 360 days, the domain is deleted by the registry; no refund applies. Refunds will not be provided for registrations that fail to qualify as an .ONG or for registrants who do not complete the validation process. If domain registration can not be accepted due to reason caused on registry's side (e.g. domain name is pre-reserved etc.) registry will make a refund.

A registrant registering an .ong domain automatically gets the corresponding .ngo domain and vice versa. The registration fee is required for only one of those domain names. The domains share all data (contacts, nameservers, ...) except for DNSSEC keys.

Successful domain transfer via RCP or API requires:


During the transfer period which can take 6 days, the current provider or the owner can reject to the transfer.

The registration period after a successful transfer will extend with 1 year, unless the transfer is ordered within the domain's auto-renew grace period at the previous registrar.

Problems transferring your domain?
Please take a look at this extended article for possible solutions.

Authorization code required yes
Method of confirmation authcode,email
Registration period after transfer extends
Average transfer time Max. 6 days
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .ong domains is available.

Owner change (trade)

  • requested as a normal domain update via RCP or API
  • processed realtime
  • both previous and new registrant will receive an e-mail. This is a notification only, no action is required.
  • registrant e-mail address verification applies

Other update

  • requested via RCP or API
  • processed realtime

 

If as part of the update the domain owner’s e-mail address changes, we’re obliged to start a contact verification process if this new e-mail address was not verified before.

Delete

Explicit delete

  • Requested via RCP or API
  • processed realtime
  • will directly result in quarantine (redemption period)  (no soft quarantine applies)


Expiration
In case the domain expires (not renewed in time);

  • will not be deleted directly at the registry
  • will lead to soft quarantine, followed by regular quarantine

Restore / reactivate

  • restore / reactivation supported via RCP or API
  • quarantine periods can be found under
    Detailed extension information > Technical information > Quarantine period
  • After quarantine, 5 days PendingDelete period (restore not possible)
Registry
Domain lifecycle
Technical information
  • DNSSEC support: yes
  • Minimum length: 3 characters
  • Maximum length: 63 characters
  • Allowed characters: a-z, 0-9, -
  • IDN characters: yes
  • Registration period: 1-10 years
  • Renewal date offset: 0 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
  • Soft quarantine period: 44 days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 28 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
Restrictions
  • Local presence required? no
  • Does Openprovider provide local presence services? n/a
  • Local activity required? no
  • Correct nameserver configuration required? no
  • Registration is limited to NGOs/ONGs
Policies
  • Rules for Uniform Domain Name Dispute Resolution Policy: http://www.icann.org/en/help/dndr/udrp/rules
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:
Was this article helpful?
0 out of 0 found this helpful