Revision as of 13:29, 6 August 2021 (view source) WikiAdmin (Talk | contribs) (→‎Nameserver: - clarified that vanity nameservers are not supported - see https://jira.centralnic.com/browse/REGSDL-2405) ← Older edit		Latest revision as of 18:10, 15 October 2024 (view source) Timo (Talk | contribs) (→‎Dispute)
Line 171:		Line 171:
	=== Dispute ===		=== 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.	+	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 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.		But please note that DENIC will only communicate with the ADMIN or with the Domain OWNER who is listed in the public whois-database.

---

Latest revision as of 18:10, 15 October 2024

.DE is the official country code Top-Level-Domain (ccTLD) of Germany (Deutschland). A .DE Domain is normally used by companies or private entities who are located in Germany.

Introduced	1986
Country	Germany
Registry	DeNIC eG
IDN Capable	Yes
Webpage	Register .DE

Contents 1 Registry 2 Periods 3 API 3.1 Domain Registration 3.2 Domain Transfer 3.3 Delete Domain 3.4 Restore Domain 3.5 Ownerchange 4 TLD specific 4.1 Nameserver 4.2 Transit 4.3 Dispute 4.4 Trustee 4.5 General Request and Abuse contact 4.6 AuthInfo Restrictions 4.7 Transfer with AuthInfo 4.7.1 Requirements for a .DE authorization code 5 Addons 6 RegistrarOC 6.1 Restore Process

[edit] Registry

TLD	.de
Registry	DeNIC eG
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.denic.de
WHOIS-Update	Real-Time
Min. Characters	1
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 5 Admin Contacts: Required: 0 / Maximum: 1 Tech Contacts: Required: 0 / Maximum: 3 Billing Contacts: Required: 0 / Maximum: 3
{{{Possible Extensions}}}
IDN capable	Yes
Restore capable	Real-Time
Handle Updates	Supported (partially)
Registration System	Real-Time
Allowed number of NS	0 to 13
Registry Nameservercheck	Yes
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Attribute
Root Nameserver Update	2 hours
SEC DNS Interface	KEY data interface
Transferclass	Pull
Transfer Periods	reset, 1 year / 1 month added
Transfer Authcode required	Yes
Transfer Real-Time	Yes
Transfer Lock	Yes
Transfer Confirmation (Request / Approve)	- / -
Owner Change by	Update

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1 year / 1 month
Add Grace Period	0 days
Accounting Period	-1 week
Finalization Period	0 days
Failure Period	1 day
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	0 days
Explicit Renewals	No
Renewal Periods	1 year / 1 month

[edit] API

[edit] Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
X-DE-GENERAL-REQUEST = (URI-TEMPLATE)
X-DE-ABUSE-CONTACT = (URI-TEMPLATE)
X-DE-ACCEPT-TRUSTEE-TAC = 0 | 1
auth = <TEXT> | <NULL>
transferlock = 0 | 1 | <NULL>
subuser = <TEXT> | <NULL>

[edit] 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>
X-DE-GENERAL-REQUEST = (URI-TEMPLATE)
X-DE-ABUSE-CONTACT = (URI-TEMPLATE)

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

[edit] Delete Domain

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

command = DeleteDomain
domain = (DOMAIN)

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

[edit] 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

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

[edit] Ownerchange

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

[edit] TLD specific

[edit] Nameserver

Nameservers must be configured in advance.

Please note that DENIC has very strict requirements on how nameservers should be configured.

One of these restrictions affect the use of vanity nameservers. If you are using your own vanity nameservers pointing at the IP Addresses of nameservers operated by HEXONET and receive an error "118 - Inconsistent set of NS RRs (IP, NS host names)", please use the HEXONET nameservers assigned to your account (ns1xxx.ispapi.net, ns2xxx.ispapi.net, ns2xxx.ispapi.net) instead.

You can test your configuration using DENIC's web based ZoneCheck. For additional information on how the DENIC Zonecheck tool works and the most common errors, please refer to the documentation available on that page.

Nameserver-Refresh: Please note that the DENIC ROOT Nameservers are refreshed every uneven hour at half past.

[edit] 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

[edit] 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 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.

[edit] Trustee

Due to the introduction of the GDPR policy, the DENIC registry no longer requires a local presence in Germany prior to the registration of .DE domain names. However, the registry may request that a local contact be named in case of a legal dispute or if any problem is reported to the registry. Upon request by the registry, the domain holder must provide a contact person in Germany who is responsible for receiving the service of official or judicial documents. For this reason, HEXONET's trustee service will continue to be available as an optional service. The trustee service will operate as follows: we will add the trustee partner’s email address as a secondary email address to the original registrant contact. If a domain should be subject to a complaint, our trustee partner will also be notified and can then provide a valid German postal address.

The trustee-service can be activated with the following parameter:

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

[edit] General Request and Abuse contact

It is possible to set a "General Request" and a Abuse" contact information for .DE domains. This contact confirmation consists of a email (mailto link) or a contact form (HTTP/HTPS URL) through which the "General Request" or "Abuse" contact can be reached. In the DENIC web whois this information is publicly displayed. This information can be set via the parameters X-DE-GENERAL-REQUEST and X-DE-ABUSE-CONTACT, the only accepted values are valid URI templates. If not specified a default will be set which is https://send-message.ispapi.net/domain/owner for the general request contact and mailto:[email protected] for the abuse contact.

[edit] AuthInfo Restrictions

Length: The AuthInfo must be 8 to 16 characters long.

Permitted characters: A, B, C, D, E‚ F, G, H, J, K, L, M, N, P, Q, R, S, T, U, V, W, X, Y, Z a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s, t, u, v, w, x, y, z 2, 3, 4, 5, 6, 7, 8, 9 +, -, /, *

The following characters are not permitted: I (uppercase i), l (lowercase l), O (uppercase O), o (lowercase o), 0 (zero) and 1

This is to avoid characters that are frequently mixed up..

[edit] 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.

[edit] Requirements for a .DE authorization code

Minimum: 8 characters
Maximum: 16 characters

Valid characters:

A, B, C, D, E, F, G, H, J, K, L, M, N, P, Q, R, S, T, U, V, W, X, Y, Z
a, b, c, d, e, f, g, h, i, j, k, m, n, p, q, r, s, t, u, v, w, x, y, z
2, 3, 4, 5, 6, 7, 8, 9
+, -, /, *

Invalid characters:

I (uppercase i), l (lowercase l), O (uppercase O), o (lowercase o), 0 (zero) and 1

[edit] Addons

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:

Addon Class	Parameter to (de)activate *1)	Renewal term *2)	Affected Parameters *3)
Trustee	X-DE-ACCEPT-TRUSTEE-TAC = 0 | 1	1 month	ADMINCONTACT
Trustee	X-DE-ACCEPT-TRUSTEE-TAC = 0 | 1	1 month	OWNERCONTACT0EMAIL1

[edit] RegistrarOC

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.