.de

DENIC supports so called NSentries which can be used instead of name servers.

• A and MX records are supported (CNAME and other records cannot be set)
• wildcards (*) can only be used for MX, but not for A records.
• only the corresponding domain name or subdomain name can be set as NSentry
• NSentries can be used with AddDomain, ModifyDomain or TransferDomain command
• up to 5 NSentries can be set using extension "X-DE-NSENTRY0" - "X-DE-NSENTRY4"
• either NSentries OR nameservers can be used
• if both values have been provided, the nameservers are ignored
• if neither configured nameservers nor NSentries have been provided in AddDomain command, a default NSentry will be set in order to prevent the domain from deletion
• the complete set of NSentries is always updated
• .de does not use name server objects; instead, only glue records are supported, wherefore a ModifyDomain has to be issued and a ModifyNameserver is not sufficient

A change of the registrant for a .de domain can be done by specifying the new owner contact handle with the ModifyDomain command. Please note, that you need a signed confirmation form of the old and new owner, in case of a review of the ownerchange by DeNIC. It is not possible to change the name and or organization within a contact handle after the domain has been registered. You have to create a new handle and modify the domain with this new handle.

As .de domains can only be registered on a monthly or yearly basis, they cannot be renewed explicitly. To renew a .de domain you have to set the domain renewal mode or default renewal mode to AUTORENEW or RENEWONCE.

Please note that you're only allowed to delete .de domains, if you have the authorization of the domain owner.

If you don't have the authorization of the owner you can push a domain to the registry (DeNIC Transit) with the PushDomain command or by setting the domain renewal mode to "AUTOEXPIRE".

• Within the period of four weeks mentioned in the TRANSIT letter, the registrant must either have transferred his domain to a new provider or deleted the domain. If the registrant doesn't do either of these things, the domain will be transferred for administration to DENICdirect service, and the registrant will have to pay the corresponding charges in accordance with DENIC's current price list.

For most TLDs there is no difference between AUTODELETE and AUTOEXPIRE. But there is a difference for .de domain names. If a .de domain is set to AUTODELETE it will be deleted at the end of the registration period at the registry. In this case you will be able to restore the domain. If a .de domain is set to AUTOEXPIRE it will be pushed to DENIC TRANSIT at the end of the registration period. Please remember that you need an authorization in order to delete a .de domain.

If a .de domain is in Transit, you have two possibilities:

• The registrant wants to delete his domain but is not in possession of the Transit letter from DENIC for whatever reason: Transit Deletion Form
• Since the domain was not deleted, it cannot be restored but must rather be transferred back to RRPproxy, wherefore an authinfo is required: Set Authinfo Form for domain in Transit

.de transfers are possible. Upon successfully transfering a .de domain, it is automatically renewed for one year. Please note that when a .de domain is transferred successfully, then the registration period starts from the beginning. Please also refer to the Denic information provided for further details Provider Change with AuthInfo.

Now, it is possible to transfer a .de domain name during RGP but therefore it is mandatory to provide all contacts and two correctly configured name servers within the TransferDomain command.

The transfer has to be initiated with an authcode. You can set an authorization code via webinterface or API. It is not possible to change the authorization code and anything else (nameserver, contacts) at the same time.

Requirements for a .de authorization code

• The authInfo will need to have at least twelve but not more than 16 characters.
• Valid characters are: 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 are: I (uppercase i), l (lowercase l), O (uppercase o), o (lowercase o) and 0 (zero) and 1
• Two different codes are available: AuthInfo1 and AuthInfo2.
• Once you set the authorization code it will be valid for a period of 30 days or until you delete it.
• In the case that both codes are requested, you can use each of them for the transfer of domains.
• You can only apply for AuthInfo1 for domains that are administered by us.
• You are able to request AuhtInfo2 for any domain name. The code will then be sent by certified mail to the domain holder respectively to the Admin-C by DENIC.
• Please notice that the request for an AuthInfo2 is not free of charge.

AuthInfo2 is only necessary if your current provider is not willing or able to provide you with the current AuhInfo1. Then, you have the ability to order an AuthInfo2 through your new registrar. After this has been initiated, a letter will be sent to the owner-c or admin-c (if owner-c has no German address) by mail. Please note that this is NOT free of charge.

After a .de domain has been deleted, it will enter the RGP (Redemption Grace Period) which allows to restore the domain within 30 days. The RGP should protect against domain loss by accidental deletion. If no reactivation takes place in this period the domain will be deleted after 30 days. Domains with an ongoing dispute are excluded from this RGP rule and will be deleted directly and irrevocably.

Upon the deletion af a domain name, the domain status in the whois first changes to "RedemptionPeriod". If a AuthInfo2 code is requested during the Redemption Grace Period the period is reset to 30 days. .DE domains that are registered with another provider and are in the RGP can be restored with a TransferDomain command (when specifying the AuthInfo2 code) and transferred to RRPproxy.

If a .de domain expires it will be pushed into TRANSIT at the DENIC registry. Further information on DENIC TRANSIT can be found at Denic Transit page .

Please note: after DENIC policy changes (GDPR), DENIC only accepts auth-code request forms from the domain owner. Our trustee (admin contact) is therefore no longer possible to request auth-codes.