This article describes the procedures and requirements of .de domain names.
Click on the subject below to open the dropdown for more information.

Successful domain registration via RCP or API requires:

  • two or more pre-configured nameservers or a nameserver group
  • the owner must have a postal address in Germany (use domicile if no such)

Nameservers must be configured according to registry requirements and return an authoritative answer before the domain is requested in order to get the domain resolving. If the zone was not correctly created before the registration, make sure the zone is correct, wait 15 minutes and update the domain via your control panel.

  • Authorization code validity - 8-30 days

NB: error message after successful transfer indicates that nameservers are not updated. Nameserver update failure descriptions

Additional notes on a .de transfer

  • If current registrar refuses to supply authcode - request assistance from Openprovider support. Authcode is sent by the registry via postal mail. Additional costs apply
  • Domain owner is not notified of successful domain transfer
  • Domains currently in hard quarantine can be transferred - authInfo2 required
Authorization code required yes
Method of confirmation authcode
Registration period after transfer restarts
Average transfer time Realtime
Advanced and simple transfers available Contact our Sales department to check if easy transfer of 100 or more .de domains is available.
  • Domicile must be disabled prior to authcode request
  • Authorization code validity - 24 hours


Owner change (trade)

  • Trade - via RCP or API, by updating the owner handle
  • Confirmation - via email to losing and gaining domain owners

Other update

  • Domain updates - via RCP or API. Nameserver update takes up to 2 hours

NB: if errors encountered during update, refer to the article


  • Delete - via RCP or API.
    • Options:
      • Delete immediately - puts domain hard quarantine for 28 days. If not restored within this period, domain is deleted
      • Give the domain back to the registry - domain is deleted in Openprovider, but stays active in the registry. DENIC becomes domain owner's supplier, sends login details to DENIC's TRANSIT system to owner via postal mail. From this point on, domain deletion possible only by written request of domain owner


Restore / reactivate

  • Restore - via RCP or API within 29 days after delete
  • If domain is in TRANSIT - restore possible by requesting a transfer. Authcode must be requested by domain owner from registry directly via TRANSIT

NB: if domain owner lost login details to TRANSIT, password reset can be requested via application form

Technical information
  • DNSSEC support: yes
  • Min: 1
  • Max: 63
  • Letters and numbers
  • IDN: Yes, https://www.denic.de/wissen/idn-domains/idn-zeichenliste/
  • Registration period: 1 year
  • Renewal date offset: 1 days
    The number of days before the registry's expiration date, that Openprovider requires the domain to be renewed or expired. More info.
    Note that the dates as shown in your Openprovider account are always leading, even if they do not match the renewal date offset mentioned here.
  • Soft quarantine period: n/a days
    During this period, following after an expiration, the domain can be restored for free. This period does not apply if the domain is deleted explicitly. More info.
  • Quarantine period: 29 days
    During this period, an expired or deleted domain name can be reactivated at an additional fee.
  • Local presence required? no
  • Does Openprovider provide local presence services? yes
  • Local activity required? no
  • Correct nameserver configuration required? yes
  • Nameservers must be configured and return an authoritative answer before the domain is requested.
  • If a legal case is issued to DENIC about a domain with a holder who is not domiciled in Germany, the domain holder must name a person in Germany as responsible for receiving the service of official or court documents.
  • Trustee services are available and are subject to additional costs per period on top of renewal costs.
  • Domain guidelines: http://www.denic.de/en/denic-domain-guidelines.html
  • Terms and conditions: http://www.denic.de/en/bedingungen.html
  • Dispute policy: http://www.denic.de/en/domains/dispute.html
Registration agreement The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:
Was this article helpful?
0 out of 0 found this helpful