Email-Interface

Last change on 2020-10-21 • Created on 2020-03-25

Introduction

The Hetzner Registration Robot can be operated directly by using email templates or indirectly via the web interface, whereby the web interface only serves as a graphic generator for standard emails. The following descriptions regarding the format of emails therefore also apply to the use of the graphical user interface.

Basically, the Hetzner Registration Robot allows handles to be created in the WHOIS databases of DENIC, ABC and nic.at. DENIC handles are required for the registration of .de domains, ABC handles for the top level domains .com, .org, .net, .info, .biz and .eu and nic.at handles for .at domains. A new handle does not need to be registered for each domain, rather a person ́s handle should be used for all domains associated with that person. The details of the handle may be changed at any time.

In addition, the Robot makes it possible to administer nameserver entries. For registering a domain at a later stage, both nameservers need to already have been configured. The Robot enables you to set up the primary and the secondary nameserver. However, it is also possible to only use the secondary nameserver, while operating the primary nameserver yourself.

The Robot also takes over the complete registration of domain names for you. Top level .de domains are registered with DENIC eG by us directly. Please pay attention to the following description of the individual types of instruction and the restrictions on the kinds of information accepted.

General format of an instruction

Instructions must be PGP signed. First, the Public Key needs to be lodged with us.

Furthermore, instructions can also be encoded using our public key. This can be found in the Robot under menu item Administration-> Settings-> Public Key. Please note that at the same time, encoded instruction emails have to be signed with their private key also. We strongly recommend encryption for domain transfers as an Auth Code is necessary.

No special information needs to be given in the subject line, you are free to choose your own.

When the Robot responds it will attach your email instruction. The preset sequence of the fields in the instruction should not be changed. You may include any number of comments on your instruction as long as these are included in extra lines and do not include any key words for instruction fields.

The email address for the Robot is <robot@robot.first-ns.de>

Moreover, information which must be given at the top of the email should be written in bold type and comments as well as descriptions of the field content should be given in italics.

Handle administration

General notice

For specifying information in individual fields the following apply:

  • For specifying a top level domain the keyword tld must be used. In older versions of the Robot the keyword type was used along with it, which is now only used for specifying the type of handle.
  • The fields fname and lname only make sense with person handles. With company handles you must ignore both of these fields, otherwise the instruction cannot be processed. Exceptions to this are .biz/.eu/.info/.org handles. For these handles the fields fname and lname must always be given, even if it is a company
  • The field company must be in place for person as well as company handles. In this way you specify the name of the company for company handles. With a person handle you can use this field - except for .biz/.eu/.info/.org - to add a company to the first and last name. For person handles this field may also be left blank.
  • With the field country you must specify the respective double-digit country code elements. A list of all country code elements can be found at https://en.wikipedia.org/wiki/ISO_3166-1#Current_codes
  • Please give telephone and fax numbers in international format (example: +499831610061).

URI template

The URI template implements RFC 6570 and has the following structure.

Email Address

If you want to save an email address with the request handle for contact information, you can do this by using the following syntax:

mailto:info@mydomain.de

Of course you need to specify the correct email address here. In addition, you can also use this method:

mailto:info@mydomain.de?subject=Domain:{Ulabel}

In this case, <Domain:example.de> will be used in the email subject. And {Ulabel} will be used with the WHOIS-queried domain.

Website

If, for example, you want to save an online form for the contact address, you can use the following:

https://www.mydomain.de/contact

You can use the URI of your choice. You can use the following label if you want the WHOIS-queried domain to be transcribed:

https://www.mydomain.de/contact?domain={Ulabel}

Generating a handle

Person and company handle

The fields phone and fax are not required for .de handles and may be omitted.

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: handle
task: new
tld: [DE/CN/ORG/INFO/BIZ/EU/AT]
type: [PERSON/ORG]
fname: First name
lname: Last name
company: Company name
address: Street and house number
pcode: ZIP code
city: City
country: County code elements
phone: Telephone number (not for .de)
fax: Fax number (not for .de)
mail: Email address
handle: new

Request handle

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: handle
task: new
tld: DE
type: REQUEST
uri: URI Template
handle: new

Example instruction for a person handle

From: robot-sender@hetzner.de
Subject: Hello Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: handle
task: new
tld: DE
type: PERSON
fname: Markus
lname: Mustermann
company: Hetzner Online AG
address: Industriestrasse 6
pcode: 91710
city: Gunzenhausen
country: DE
phone: +499831610061
fax: +499831610062
mail: info@hetzner.de
handle: new
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Instruction example for a company handle

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: handle
task: new
tld: DE
type: ORG
company: Hetzner Online AG
address: Industriestrasse 6
pcode: 91710
city: Gunzenhausen
country: DE
phone: +499831610061
fax: +499831610062
mail: info@hetzner.de
handle: new
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Instruction example for a request handle

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: handle
task: new
tld: DE
type: REQUEST
uri: mailto:info@hetzner.de?subject=domain:{Ulabel}
handle: new
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Changing a handle

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: handle
task: upd
tld: [DE/CN/ORG/INFO/BIZ/EU/AT]
type: [PERSON/ORG/REQUEST]
fname: First name
lname: Last name
company: Company name
address: Street and house number
pcode: ZIP code
city: City
country: County code elements
phone: Telephone number
fax: Fax number
mail: Email address
handle: Handle to be changed

For information: For the specification of information in individual fields, the instruction "generate handle" follows in analogue form. Additionally, the handle to be changed must be given at the end. Please note that changes can not be made to the first and last name of a person handle or to the company name of a company handle.

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: handle
task: upd
tld: DE
type: PERSON
fname: Markus
lname: Mustermann
company: Hetzner Online AG
address: Industriestrasse 6
pcode: 91710
city: Gunzenhausen
country: DE
phone: +499831610061
fax: +499831610062
mail: info@hetzner.de
handle: DENIC-168-robot-1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Deleting a handle

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: handle
task: del
tld: [DE/CN/ORG/INFO/BIZ/EU/AT]
handle: Handle to be changed

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: handle
task: del
tld: DE
handle: DENIC-168-robot-1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJU
ecYFTMuXs24oXOj21rRVzEY=PTWh
-----END PGP SIGNATURE-----

Domain administration

Domain registration

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: ; Client number
job: domain
task: new
domain: Domain name ([a-zA-Z0-9-]{3,60}\.(de|com|net|org|info|biz|eu|at|co.at|or.at))
holder: DENIC-, ABC- or nic.at-Handle of domain holder
holder: DENIC-Handle of 2. domain holder (optional)
holder: DENIC-Handle of 3. domain holder (optional)
holder: DENIC-Handle of 4. domain holder (optional)
holder: DENIC-Handle of 5. domain holder (optional)
adminc: ABC or nic.at-Handle of administrator (blank for .eu, not for .de)
techc: ABC or nic.at-Handle of tech. contact (blank for .eu, not for .de)
zonec: ABC or nic.at-Handle of zone administrator (blank for .eu and .at, not for .de)
generalc: DENIC-Handle for general requests (only for .de)
abusec: DENIC-Handle for abuse requests (only for.de)
ns1: Hostname of primary nameserver
ns2: Hostname of secondary nameserver
ns3: Hostname of 3. nameserver (optional)
ns4: Hostname of 4. nameserver (optional)
ns5: Hostname of 5. nameserver (optional)

Information: The number of holder handles as well as the holder names for the handles must be consistent with the current domain information. Should the holder information still be on hand as a description, only one holder handle can be given, whose holder name must match with the description. The field authcode may only be specified if the new DENIC Change of Provider procedure is being used and an Auth Code for the domain has been created by the former provider previously.

Instruction example .de

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: new
domain: hetzner.de
holder: DENIC-168-Martin-Hetzner-1
generalc: DENIC-168-Martin-Hetzner-2
abusec: DENIC-168-Martin-Hetzner-2
ns1: ns1.first-ns.de
ns2: robotns2.second-ns.de
ns3: robotns3.second-ns.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Instruction example .com

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: new
domain: hetzner.com
holder: P-XYZ0815
adminc: P-XYZ0815
techc: P-XYZ0815
zonec: P-XYZ0815
ns1: ns1.first-ns.de
ns2: robotns2.second-ns.de
ns3: robotns3.second-ns.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Changing a domain

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: domain
task: upd
domain: Domain name ([a-zA-Z0-9-]{3,60}\.(de|com|net|org|info|biz|eu|at|co.at|or.at))
holder: DENIC-, ABC- or nic.at-Handle of domain holder
holder: DENIC-Handle of 2. domain holder (optional)
holder: DENIC-Handle of 3. domain holder (optional)
holder: DENIC-Handle of 4. domain holder (optional)
holder: DENIC-Handle of 5. domain holder (optional)
adminc: ABC or nic.at-Handle of administrator (blank for .eu, not for .de)
techc: ABC or nic.at-Handle of tech. contact (blank for .eu, not for .de)
zonec: ABC or nic.at-Handle of zone administrator (blank for .eu and .at, not for .de)
generalc: DENIC-Handle for general requests (only for .de)
abusec: DENIC-Handle for abuse requests (only for.de)
ns1: Hostname of primary nameserver
ns2: Hostname of secondary nameserver
ns3: Hostname of 3. nameserver (optional)
ns4: Hostname of 4. nameserver (optional)
ns5: Hostname of 5. nameserver (optional)

Information: If the field holder is used more than once for .de domains, the respective handles are not allowed to repeatedly appear there.

Instruction example .de

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: upd
domain: hetzner.de
holder: DENIC-168-Martin-Hetzner-1
generalc: DENIC-168-Martin-Hetzner-2
abusec: DENIC-168-Martin-Hetzner-2
ns1: ns1.first-ns.de
ns2: robotns2.second-ns.de
ns3: robotns3.second-ns.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Domain cancellation

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: domain
task: del
domain: Domain name ([a-zA-Z0-9-]{3,60}\.(de|com|net|org|info|biz|eu|at|co.at|or.at))

Information: With .de, .com, .net domains the instruction to delete is forwarded immediately on to the registry which as a result means that a .de domain is cancelled immediately and a .com or .net domain will be cancelled in 30 days. All other TLDs can only be cancelled at 30 days' notice to the end of the month. On receiving an instruction to cancel for a .org, .info, .biz, .eu or .at domain the Robot automatically establishes the next possible cancellation date, which is also quoted in the reply email. For example: Your instruction to cancel is sent to our Robot on 20.04.2011, which calculates the next possible cancellation date as 31.05.2011. On this day, we then send an instruction to delete to the relevant Registry. Please note that the domain can not be deleted immediately by the Registry on the cancellation date, rather the domain still remains registered up to the expiry date.

For example: Your instruction to cancel is sent to our Robot on 20.04.2011, which calculates the next possible cancellation date as 31.05.2011. On this day, we then send an instruction to delete to the relevant Registry.

Please note that the domain can not be deleted immediately by the Registry on the cancellation date, rather the domain still remains registered up to the expiry date.

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: del
domain: hetzner.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Domain Transit

(only possible for .de domains)

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: domain
task: transit
domain: Domain name ([a-zA-Z0-9-]{3,60}\.de)
disconnect: (no|yes)

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: transit
domain: hetzner.de
disconnect: no
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Starting ChProv Domain Transfer

(only possible for .de, .com, .net, .at domains)

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: domain
task: kk
domain: Domain name ([a-zA-Z0-9-]{3,60}\.(de|com|net|at))
holder: DENIC-, ABC- nic.at-Handle of domain holder
holder: DENIC-, ABC- nic.at-Handle of 2. domain holder (optional)
holder: DENIC-, ABC- nic.at-Handle of 3. domain holder (optional)
holder: DENIC-, ABC- nic.at-Handle of 4. domain holder (optional)
holder: DENIC-, ABC- nic.at-Handle of 5. domain holder (optional)
adminc: ABC- nic.at-Handle of administrator (not for .de)
techc: ABC- nic.at-Handle of technical contact (not for .de)
zonec: ABC- nic.at-Handle of zone administrator (not for .de)
generalc: DENIC-Handle for general requests (only for .de)
abusec: DENIC-Handle for abuse requests (only for .de)
ns1: Hostname of primary nameserver
ns2: Hostname of secondary nameserver
ns3: Hostname of 3. nameserver (optional)
ns4: Hostname of 4. nameserver (optional)
ns5: Hostname of 5. nameserver (optional)
authcode: ; Auth-Code der Domain (optional)

Information: The number of holder handles as well as the holder names for the handles must be consistent with the current domain information. Should the holder information still be on hand as a description, only one holder handle can be given, whose holder name must match with the description.

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: kk
domain: kk-domain.de
holder: DENIC-168-Martin-Hetzner-1
generalc: DENIC-168-Martin-Hetzner-2
abusec: DENIC-168-Martin-Hetzner-2
ns1: ns1.first-ns.de
ns2: robotns2.second-ns.de
ns3: robotns3.second-ns.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----

Generating an Auth Code

(only possible for .de domains)

If you would like to move your .de domain to another provider using the new DENIC Change of Provider procedure you can generate an Auth Code for your domain with this instruction. As soon as the Auth Code has been generated you will receive an email from the Robot. Then you can call up the Auth Code in the Robot under menu item Domains using the link view.

From: robot-sender@hetzner.de
Subject: Hallo Robot!

user: Client number
job: domain
task: authcode
domain: Domain name ([a-zA-Z0-9-]{3,60}\.de)

Instruction example

From: robot-sender@hetzner.de
Subject: Hallo Robot!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

user: K9999999999
job: domain
task: authcode
domain: kk-domain.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9rV0v4BzTKoUUrgMRAvi4AKCtwzjMz8V/qJCwb1ZWAYBNDYHsTQCfXXJUecYFTMuXs24oXOj21rRVzEY==PTWh
-----END PGP SIGNATURE-----
Table of Contents