From HEXONET Wiki
(Created page with "{{Infobox nTLD | name = .ONG | image =200px | introduced = 2015 | category = Culture & Community | registry = Public Interest Registry | idn capable = ...") |
Revision as of 19:44, 16 March 2015
.ONG | |
Overview | |
Introduced | 2015 |
---|---|
Category | Culture & Community |
Registry | Public Interest Registry |
IDN Capable | Yes |
Dispute Policy | ICANN Rules |
Webpage | Register .ONG |
Legal Information | |
Legal | TBA |
Contents |
Registration Eligibility
NGOs (ONGs) participating as members in the OnGood community must certify:
- 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.
Registry
TLD |
- |
Registry | |
Dispute Policy | |
Registrar |
1api GmbH |
WHOIS-Server |
whois.pir.org |
WHOIS-Update |
Real-Time |
Min. Characters |
2 |
Max. Characters |
63 |
Character Set |
|
Limitations |
|
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
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
Landrush Application
REQUIRED
command = AddDomainApplication domain = (DOMAIN) class = LANDRUSH ownercontact0 = (CONTACT) admincontact0 = (CONTACT) techcontact0 = (CONTACT) billingcontact0 = (CONTACT) nameserver0 = (NAMESERVER) nameserver1 = (NAMESERVER) nameserver2 = (NAMESERVER)
OPTIONAL
EOI = <YOUR-EOI-APPLICATION-ID>
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