General FAQ
Global Whois
Domain Types
Overview
FAQ
New TLD listing
Trademark Clearinghouse
E-mail Template
Template Help
New TLDs
Overview
IDN Extensions
IDN character set
FAQ
Whois
Register Online
Naming Convention
E-mail Template
Template Help
Registration Terms
.de Domains
Overview
IDN Extensions
FAQ
Whois
Register Online
E-mail Template
Template Help
Registration Terms
The .eu Code of Conduct
.eu Domains
.biz
.com/.net
.info
.name
.org
Generic Domains
.aero
.asia
.coop
.mobi
.museum
.tel
.xxx
Sponsored Domains
New ccTLD's at Knipp
FAQ
.ac Ascension Island
.af Afghanistan
.ag Antigua and Barbuda
.at Austria
.au Australia
.be Belgium
.bz Belize
.ca Canada
.cc Cocos (Keeling) Islands
.ch/.li Switzerland and Liechtenstein
.cn China
.co Colombia
.cx Christmas Island
more...
ccTLDs
Special Types
ENUM
FAQ
E-mail Template
Template Help
Registration Terms
Overview
Become a Customer
FAQ
Printed Forms
Documentation
Domain Registration System
Knipp RRI Toolkit
Unified Registry Announcements
Open Source Software
Questions and Answers
Application Form
Premium-Partner-Program (P3)
Redirection FAQ
Service Bundle
FAQ
Technical Background
Countries Overview
Character Sets
Converter
Example Website
Internationalized Domain Names (IDN)
Price List
Glossary
Support
Domain Management
ironDNS
TANGO REGISTRY SERVICES
mambo⁺

Instructions for filling out the e-mail application form
for ENUM domains

Follow this link to the e-mail application form.
This page describes the most important parameters of the e-mail application form. The respective parts of the template are shown within a colored area, with helpful comments located below them. Self-explanatory parameters like email will not be mentioned here.
The e-mail application form is intended for experts and the automated processing by robots. You will need technical experience to fill out the form, e.g. to give the correct information in section 6. If you are not sure about the meaning of all the terms, you should use the comfortable web interface of our DRS.
The form is divided into multiple sections:


E-mail application form

Introduction (section 0)

#-----------------------------------------------------------------------
#   |       |
#   | knipp |                        Knipp Medien und Kommunikation GmbH
#    -------
All the lines beginning with # are comments and can be ignored. These lines are only used to improve structure and readability. The same is true for blank lines. They are only used to clearly arrange the form and can be added or deleted arbitrarily.
         section: 0
The application form is divided into several sections. Each section forms a chapter by itself and is separated from the other chapters by the key section. Do not remove these lines.
          doc-id: appli-en-enum.txt
         version: 1.0.0
Is required for further processing by Knipp. Please do not delete.
       reference:
You can insert any text you like here. This text will be quoted in all of the responses of our system. This allows for an easy recognition and classification of your applications by your robots, if you want to automatically process our responses.
You might want to use this field to indicate reference numbers of your customers, for example, or a contract number, etc.

Registration data (section 1)

           section: 1
              mode:
            domain:
           comment:
          language: de
          authinfo:
      new-authinfo:
With the mode-parameter you can define if you wish to perform a new registration ( mode: new), a transfer from another registrar (a so-called »Konnektivitätskoordination« - coordination of connectivity, mode: kk), an update ( mode: update), or a deletion ( mode: delete). An update can be used to modify the contact data or to change the WWW forwardings, for instance. If you leave the mode-parameter empty, a new registration will be initiated.
Important: If you choose mode: update you must fill out all sections, not only the parts to change. For mode: delete, only the sections 0, 1, 7, and 8 may be filled. The sections from 2 to 6 may not appear. Likewise, no authinfo-fields (see below) may be used for a deletion.
Deletion: When deleting a domain via e-mail template, the domain is marked for immediate deletion, i.e. the requested end date is set to the date and time of the receipt of order. The effective deletion from our system, however, does only take place in the course of specific maintenance phases that are scheduled in regular intervals. Thus, the deletion can be canceled by using our web interface until the beginning of the next maintenance phase.
Next to domain, the complete domain name has to be given. For example: domain: 3.0.7.9.1.3.2.9.4.e164.arpa. Only one domain name can be given per e-mail application form.
The field comment can be used to save a free-text comment about this domain.
With the language parameter you can specify a language code for the domain name. The language code can be used to determine possible alternative notations of the name. Especially in asian regions it occurs that there are several different ways to represent the same term. Some registries offer to include possible alternative notations in a registration or to block their registration by third parties. Knipp's DRS is already featured with this option, so you can use this field to specify a language code.

Domain holder (section 2)

Note: Formerly, the DENIC used to collect these data in a rather unstructured way in descr-fields. Since May 2005, the contact information for the holder is collected in specialized form fields (like street, city, etc.) and stored with a so-called »holder handle« (see below).
            person:
      organization:
The registrant is the designated holder of the domain. This can be a natural person or a legal person.
In case of a natural person, only person has to be filled out. If the holder is a legal person (e.g. a company), you have to specify it at organization in any case. Nevertheless, a contact person must also be given at field person
              type:
A contact can be of one of the types listed in section 4. When creating a new contact for a registrant, the field type is mandatory, when changing an existing contact it is prohibited.
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
           country:
The parameter address-1 is intended for the street address. Filling this field is mandatory. address-2 and address-3 can be used for additional entries (for the zip-code or other add-ons).
The postal-code-parameter (mandatory field) is intended for the zip/postal code, while city (mandatory as well) holds the name of town. The mandatory country-parameter is required to hold the international country code representation according to ISO-3166, like »DE«, »AT«, or »CH«. This field is case-insensitive (so using »de« or »De« will work as well), but it may not contain periphrases like »Germany« or »Switzerland«!
             phone:
               fax:
Specifying a phone number in field phone is mandatory. The number has to be given in the following format: +CCC.NNNNN, where CCC represents the country code (e.g. 49 for Germany) and NNNN is the actual number including the area code. Using a plus sign in front of the country code and a dot to separate it from the rest of the number is mandatory, too. Example: +49.8912345678
If a fax number is available, it can be specified at fax. The format has to be the same as in phone.
            handle:
handle provides an alternative way to specify contact data. With every successful registration of a domain, a handle is being created for every contact provided during the registration process. Once you have a handle for a set of contact data, you don't have to manually fill out the fields if you want to use the same data again. Instead, it suffices to specify the appropriate handle in this field. This saves you a lot of typing. If you fill out the fields and enter a handle at the same time, the values specified in the fields will be ignored and those from the handle will be taken instead.
Example: handle: DENIC-60-DRS1000000.
Important: The different top level domains each require their own set of handles. For example, .biz handles can not be used for .de domains, even if both handles specify the same contact data!

Administrator (section 3)

The administrator is an authorized person who is acting on behalf of the registrant. He can, for example, request modifications of a domain. The administrator and the holder of a domain can be the same person. The administrator can be a legal department or an external office, as it is often the case with larger companies.
              type:
Important: Generally speaking, a contact can be of one of the types listed in section 4. For the administrator, however, only type: person is allowed.
            person:
This field has to be filled.
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
           country:
             phone:
               fax:
             email:
            handle:
The parameters have to be filled out in the same way as described for the domain holder (or by specifying a handle).

Technical contact (section 4)

The technical contact is the contact person for technical concerns. He is responsible for operating the name servers, for instance.
              type:
            person:
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
           country:
             phone:
               fax:
             email:
            handle:
These fields must be filled out in the same way as for the administrator contact. Alternatively, you can specify an adequate handle. However, for this contact you must fill out the fax field. For type, you can use the values as listed below.
Type
Description
org
Use this type to specify an organization. You don not have to enter an person in this case.
person
This type is used for a natural person.
role
This type specifies some kind of group that may consist of several natural persons. A typical usage is »webmaster«, for example, or »accounting«.

Zone contact (section 5)

The contact for the zone data is the entity that is responsible for the contents of the name server.
              type:
            person:
      organization:
         address-1:
         address-2:
         address-3:
       postal-code:
              city:
           country:
             phone:
               fax:
             email:
            handle:
These fields must be filled out in the same way as for the administrator contact. Alternatively, you can specify an adequate handle. However, for this contact you must fill out the fax field.
[ServletException in:/domains/types/enum/appli-help.en.jsp] File "/domains/includes/appli-help/section6_start_de.en.jsp" not found'
Imprint|Privacy Statement
print (c) 1996-2017 Knipp Medien und Kommunikation GmbH|webmaster@knipp.de