.gdn
API Commands
Section titled “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
Section titled “Domain Registration”(API Command reference » AddDomain)
command = AddDomaindomain = yourdomain.gdnperiod = (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.
Domain Modification
Section titled “Domain Modification”(API Command reference » ModifyDomain)
command = ModifyDomaindomain = yourdomain.gdnDomain Renewal
Section titled “Domain Renewal”(API Command reference » RenewDomain)
command = RenewDomaindomain = yourdomain.gdnperiod = (INT)expiration = (INT)Domain Deletion
Section titled “Domain Deletion”(API Command reference » DeleteDomain)
COMMAND = DeleteDomainDOMAIN = yourdomain.gdnDomain Transfer
Section titled “Domain Transfer”(API Command reference » TransferDomain)
command = TransferDomaindomain = yourdomain.gdnaction = REQUESTauth = (TEXT)Transfer Procedure
Section titled “Transfer Procedure”- A .gdn domain transfer must be initiated with a so-called authorisation code, (auth-code) which can be obtained from the current registrar through the owner/admin contact of the domain.
- Ensure that your respective domain does not have a lock-status (clientTransferProhibited and/or serverTransferProhibited). This can be seen in WHOIS.
- If the domain has a client-side transfer lock, the owner can ask the current registrar to have the lock removed.
These procedures only apply for domain transfers between registrars. For internal transfers between resellers, please consult our documentation about internal transfers/usertransfers.
Transfer Notes
Section titled “Transfer Notes”- A .gdn 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
Section titled “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
Section titled “Domain Restore”(API Command reference » RestoreDomain)
command = RestoreDomaindomain = yourdomain.gdnDomain Restrictions
Section titled “Domain Restrictions”There are no restrictions for .gdn
IDN Information
Section titled “IDN Information”- .CN Chinese Table Version 4.0 provided by CNNIC on 2005-03-31
- .TW Chinese Table Version 4.0.1 provided by TWNIC on 2009-07-15
- .JP Japanese Table Version 1.2 provided by JPRS on 2005-08-30
- .KR Korean Table Version 1.0 provided KRNIC on 2004-03-25
Supported IDN Scripts
Section titled “Supported IDN Scripts”The following IDN scripts are supported by .gdn.
Provide the LANGUAGE TAG corresponding to your desired IDN within the AddDomain command as X-IDN-LANGUAGE extension.
| Arabic | AR |
|---|---|
| Chinese | ZH |
| Japanese | JP |
| Korean | KR |
| Russian | RU |
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.