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)

OPTIONAL

auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <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.
Domain transfers are processed in Real-Time.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER
auth = <TEXT>

OPTIONAL

order = CREATE | REPLACE | UPDATE

subuser = <TEXT> | <NULL>
period = <PERIOD>
transferlock = 0 | 1 | <NULL>

If the Authorization Code is correct, the transfer will be processed in real-time.

Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days.

command = DeleteDomain
domain = (DOMAIN)

REQUIRED

n/a

If you don't have the authorization of the owner you can push a domain to the registry (DeNIC Transit) with the PushDomain command:

 command = PushDomain
 domain = <DOMAIN>
 target = TRANSIT

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)

REQUIRED

n/a

OPTIONAL

renewalmode = <NULL> | <TEXT>
subuser = <TEXT>

Ownerchange

An Ownerchange is free of charge and can be done with the API ModifyDomain command.

Terms and conditions

Nameserver

Configured nameservers are required. A web based ZoneCheck is available. If you do not have your own nameservers, you have got the possibility to use a so-called NS-Entry. Nameserver-Refresh: Please note that the DENIC ROOT Nameservers will be refreshed every uneven hour at half past.

Transit

TRANSIT is the name that DENIC gives to a procedure, which makes sure that a domain holder does not lose his/her domain if it ceases to be administered by a DENIC member. You should understand a little about the background:

Usually, the request to register a domain is submitted to DENIC by a DENIC member acting on behalf of the customer. This DENIC member then goes on to handle all communications with DENIC concerning the domain on behalf of the domain holder. We call this "administering the domain". If, for whatever reason, the DENIC member ceases to administer the domain, DENIC tries to get in touch directly with the domain holder as part of its TRANSIT procedure in order to ensure that it will be possible to have the domain administered in future by a DENIC member appointed by the domain holder. DENIC will send a letter to the domain holder and issues an individual password. The domain holder can now use this password on a personalized web page to indicate for each domain concerned:

• which DENIC member is to administer the domain in future;
• whether DENIC is to administer it itself through the service DENICdirect;
• or whether the domain is to be deleted.

This procedure ensures that the rights of domain holders to their domains are safeguarded.

• DENIC Transit FAQ (English, German)
• DENIC Transfer Homepage

Dispute

If you should ever receive an Email from our system telling you that the the respective domain name is in a DISPUTE you should contact the DENIC-Legal Department for further information. They will provide you with the information you need for removing the so-called DISPUTE-ENTRY. But please note that DENIC will only communicate with the ADMIN or with the Domain OWNER who is listed in the public whois-database.

More Information: Even if DENIC does not become involved in pending disputes about domains, it can do something for you by placing a DISPUTE entry on the disputed domain. The main effect of this instrument is that the domain holder loses the right to transfer the domain to someone else, which prevents them from trying to shirk away from sorting the matter out with you. The only feasible transfer of the domain is to you and that, of course, remains possible. The DISPUTE entry made on the domain in your favour also guarantees that you will instantly become its holder if the existing holder deletes it. That is particularly advantageous for you, since the highest German court has ruled that an adversary may file for a court to order a domain holder to delete a domain but it cannot file for an order to transfer it. If there is a DISPUTE entry on the domain in your name, then it is enough for you to file for deletion and, thanks to the DISPUTE-entry mechanism, you are sure that you will then become the domain holder yourself. For this purpose, it is essential that the form applying for a DISPUTE entry also specifies the person who will become your administrative contact should such a case arise. This will accelerate the clearing procedure later on.

Trustee

.DE requires a local presence in order to register a domain. In most cases a local presence is required for either the owner or the admin-c (Admin-Contact) of that domain. In order to overcome this barrier and make specific TLDs unrestricted HEXONET offers so called Trustee Services for several TLDs which require a local presence, also for DE. Depending on the TLD, the Trustee Service is then either added to the existing contacts, or replaces one or more of the WHOIS contacts. Once replaced the Trustee acts on behalf of the registrant and thereby makes a registration of that specific TLD possible. The trustee-service can be activated with the following parameter:

X-DE-ACCEPT-TRUSTEE-TAC = 0 | 1

Transfer with AuthInfo

As from December 2008, DENIC and the DENIC members offered a new procedure to domain holders who want to change their provider. The central feature of this new procedure is the transmission of a password, which is called AuthInfo. The AuthInfo is valid exclusively for this specific action and is related to one specific domain. Two steps are required to be able to apply the procedure: First, the domain holder must request his/her provider to obtain an AuthInfo, which is then stored with DENIC. Then he/she starts a provider change with his/her new provider. Below you find a detailed description of these two steps.

To actually start the provider change, the domain holder communicates the AuthInfo to his/her new provider. The new provider, or more precisely the DENIC member administering the domain, can check with DENIC whether an AuthInfo has been stored (of cause without giving the actual character set of the AuthInfo). If an AuthInfo has been stored, the provider change request can then be transmitted to DENIC together with this AuthInfo.

When DENIC receives the provider change request, it checks first of all if a valid AuthInfo has been stored for the stated domain. If an AuthInfo exists and it matches the transmitted AuthInfo, the provider change is carried out immediately and the AuthInfo used for it is deleted. If the password is invalid, the provider change is rejected and the new provider is informed accordingly. If no AuthInfo is stored for the domain, the domain holder must contact his/her previous provider to clarify why no AuthInfo has been stored.

An AuthInfo enables a domain holder to carry out a holder change together with the provider change. This option is not available, however, if provisions to the contrary like an active DISPUTE apply. This distinguishes the new procedure from the asynchronous one, which only provides for a separate holder change. Other domain administration processes like updating the domain data or deletions cannot be executed by means of an AuthInfo.

If you want to transfer a .DE domain to another DENIC member you can set an AuthInfo1 code which will be valid for 30 days by simply assigning a new authorization code to the domain:

command=ModifyDomain
domain=<DOMAIN>
auth=<TEXT>

It is also possible to explicitly set or remove an AuthInfo1 code for a domain name.
You can set an AuthInfo1 code with the DENIC_CreateAuthInfo1 command:

 command=DENIC_CreateAuthInfo1
 domain=<DOMAIN>
 (optional)
 auth=<TEXT>
 x-de-authinfo1-expirationdate = <DATE>

You can remove an AuthInfo1 code with the DENIC_DeleteAuthInfo1 command:

 command = DENIC_DeleteAuthInfo1
 domain = <DOMAIN>

To create an AuthInfo2 for a .DE domain (gets generated directly at DENIC) you have to use DENIC_CreateAuthInfo2:

 command = DENIC_CreateAuthInfo2
 domain = <DOMAIN>

The AuthInfo2 code will be generated at DENIC. The DENIC sends a letter with the code to the registrant of the domain by post. A DENIC letter containing a AuthInfo2 code normally looks like this: DENIC AuthInfo2 letter.

Please note that when a .DE Domain is transferred successfully, then the registration period starts from the beginning.

The following overview shows you all available Domain Addons which can be used for this special kind of TLD. It also shows the respective API parameters which are required to activate the Domain Addons:

Restore Process