.link

API commandsExtensionsRestrictionsIDN

Important

There are Reserved Domains available for this TLD. These domains are shown as ‘available’ in CNR, but they can be registered only with under specific conditions of the registry, which need to be addressed offline. Once a Reserved Domain is allocated to a customer, then this domain can be registered and managed in CNR (e.g. based on a token provided by the registry).

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.

AddDomainModifyDomainRenewDomainDeleteDomainTransferDomainRestoreDomain

Domain Registration

(API Command reference » AddDomain)

Exception

command               = AddDomain
domain                = yourdomain.link
period                = 1
ownercontact0         = (CONTACT)
admincontact0         = (CONTACT)
techcontact0          = (CONTACT)
billingcontact0       = (CONTACT)
nameserver0           = (CONTACT)
nameserver1           = (CONTACT)
X-CHALLENGE-QUESTION0 = (TEXT)
X-CHALLENGE-ANSWER0   = (TEXT)
X-CHALLENGE-QUESTION1 = (TEXT)
X-CHALLENGE-ANSWER1   = (TEXT)
X-CHALLENGE-QUESTION2 = (TEXT)
X-CHALLENGE-ANSWER2   = (TEXT)

Extensions help set up the3 security questions and answers for the domain and they are optional.

Domain Modification

(API Command reference » ModifyDomain)

Command

command = ModifyDomain
domain  = yourdomain.link

Domain Renewal

(API Command reference » RenewDomain)

Command

command    = RenewDomain
domain     = yourdomain.link
period     = (INT)
expiration = (INT)

Domain Deletion

(API Command reference » DeleteDomain)

Command

COMMAND = DeleteDomain
DOMAIN = yourdomain.link

Domain Transfer

(API Command reference » TransferDomain)

Command

command = TransferDomain
domain = yourdomain.link
action = REQUEST
auth = (TEXT)

Transfer Procedure

• The transfer is submitted to the registry and the losing registrar is automatically notified by them.
• The losing registrar sends an email to the owner (and optionally admin) contact, informing about the transfer; this may include options to approve and/or deny the transfer. If neither explicitly approved nor denied, the transfer will be automatically finalized after 5 days.

Transfer Notes

• A .link 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.

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.link

Domain Extensions

X-CHALLENGE-ANSWER	Answer to security question 1-3 to identify the registrant - OPTIONAL
X-CHALLENGE-QUESTION	Security question 1-3 to identify the registrant in the event of emergencies - OPTIONAL

Domain Restrictions

There are no restrictions for .link

Supported IDN Scripts

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

Cyrillic	CYRL
Chinese	ZH
French	FR
German	DE
Italian	IT
Japanese	JA
Portuguese	PT
Spanish	ES

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.