";
$fields = "username=".urlencode($username)."&password=".urlencode($password);
$result = execute_request("login", $fields, $authid);
$result = parse_response($result);
$authid = $result["response_header"]["auth-sid"];
if (!$authid) {
print "no auth-id was obtained - probably due to wrong username or password";
exit;
}
//now asking for the domain list
$pattern = "*";
$fields = "pattern=".urlencode($pattern);
$result = execute_request("query-domain-list", $fields, $authid);
$result = parse_response($result);
print_r($result["response_header"]);
print "< br /> ";
print_r($result["response_body"]);
```
## Python
### Introduction
Python is easy to use with DMAPI. Our examples are tested with python 3 on Windows and Linux, but should work on all platforms.
Running the Python example will look like:
```
$ ./dmapi-example.py
Request-URL: https://dmapi.ote.joker.com/request/login
Login: Status-Code: 0
Request-URL: https://dmapi.ote.joker.com/request/query-domain-list
Domain List: Status-Code: 0
domain: another-privacy-test.com
expiration_date: 2018-06-30
domain: another-privacy-test.net
expiration_date: 2020-06-30
Request-URL: https://dmapi.ote.joker.com/request/logout
Logout: Status-Code: 0
```
### Login and list your domains
```python
#!/usr/bin/env python
import requests
dmapiURL = 'https://dmapi.ote.joker.com'
dmapiUser = 'username'
dmapiPassword = 'password'
def main():
loginResponse = login(dmapiUser,dmapiPassword)
print("Login: Status-Code:", loginResponse.header['Status-Code'])
if loginResponse.header['Status-Code'] !='0':
print(loginResponse.header['Status-Text'])
return
sessionId = loginResponse.header['Auth-Sid'];
print("")
domainResponse = domainList(sessionId,1,5)
print("Domain List: Status-Code:", domainResponse.header['Status-Code'])
print("")
domains = domainResponse.resultListWithNames()
for domain in domains:
for key, value in domain.items():
print(" %s: %s" % (key, value))
print("")
logoutResponse = logout(sessionId)
print("Logout: Status-Code:", logoutResponse.header['Status-Code'])
# implement dmapi commands as functions
def login(username,password):
parameters = { 'username': username, 'password': password }
message = sendCommand('login', parameters)
return message;
def logout(sessionId):
parameters = { 'auth-sid': sessionId }
message = sendCommand('logout', parameters)
return message;
def domainList(sessionId, list_from=1, list_to=""):
parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to }
message = sendCommand('query-domain-list', parameters)
return message;
# general dmapi command call
def sendCommand(command,parameter={}):
try:
url = dmapiURL+'/request/'+command
print("Request-URL: ", url)
response = requests.get(url, params=parameter)
# print URL with parameters for debugging purposes
# print("Request-URL: ", response.url)
if response.status_code != requests.codes.ok:
raise CommandError("Command Failed! HTTP Status Code: %s" % response.status_code)
return DmapiResponse(response.text)
except requests.ConnectionError as e:
raise CommandError("Connection Error: %s" % str(e))
except requests.HTTPError as e:
raise CommandError("Http Error: %s" % str(e))
except CommandError as e:
raise
except Exception as e:
raise CommandError("Unexpected Error: %s" % str(e))
class DmapiResponse():
def __init__(self,responseBody):
parts = responseBody.split("\n\n",1)
if len(parts)>0:
self.header = self.__parseKeyValueList(parts[0])
if len(parts)>1:
self.body = parts[1]
def __parseKeyValueList(self,text):
lines = text.split("\n")
keyValueList = {}
for line in lines:
keyValue = line.split(' ',1)
key = keyValue[0].rstrip(':')
value = keyValue[1]
keyValueList[key] = value
return keyValueList
def __getSeparator(self):
if self.header.get('Separator') == 'TAB':
return "\t"
else:
return " "
def resultList(self):
lines = self.body.split("\n")
resultList = []
separator = self.__getSeparator()
for line in lines:
values = line.split(separator)
resultList.append(line.split(separator))
return resultList
def resultListWithNames(self):
columnNames = self.resultListColumns()
resultList = []
if len(columnNames) > 0:
rawList = self.resultList()
resultList = []
for row in rawList:
columns = {}
for idx, column in enumerate(row):
columns[columnNames[idx]] = column
resultList.append(columns)
return resultList
def resultListColumns(self):
if 'Columns' in self.header:
columnsText = self.header['Columns']
columns = columnsText.split(',')
return columns
else:
return []
def resultValues(self):
return self.__parseKeyValueList(self.body)
class CommandError(Exception):
def __init__(self, value):
self.value = value
def __str__(self):
return repr(self.value)
# call main function
try:
main()
except CommandError as e:
print("Error:", str(e).strip("'"))
```
### Login and list all A and CNAME records
```python
#!/usr/bin/env python
import requests
dmapiURL = 'https://dmapi.joker.com'
dmapiUser = 'username'
dmapiPassword = 'password'
def main():
loginResponse = login(dmapiUser,dmapiPassword)
#print("Login: Status-Code:", loginResponse.header['Status-Code'])
if loginResponse.header['Status-Code'] !='0':
print(loginResponse.header['Status-Text'])
return
sessionId = loginResponse.header['Auth-Sid'];
#print("")
dnsZoneListResponse = dnsZoneList(sessionId,"")
#print("DNS Zone List: Status-Code:", dnsZoneListResponse.header['Status-Code'])
dnslist = dnsZoneListResponse.resultList()
for row in dnslist:
domain = row[0]
expiration = row[1]
#print(" domain: %s" % (domain))
#print(" expiration: %s" % (expiration))
#print("")
dnsZoneResponse = dnsZoneGet(sessionId, domain)
#print("DNS Zone GET for %s: Status-Code:" % (domain), dnsZoneResponse.header['Status-Code'])
zoneEntries = dnsZoneResponse.resultList()
for entry in zoneEntries:
#print(' '.join(entry))
if len(entry)<5:
continue
eLabel = entry[0]
eType = entry[1]
ePriority = entry[2]
eTarget = entry[3]
eTTL = entry[4]
if eType == 'A' or eType == 'CNAME':
print(("%s.%s\t%s" % (eLabel,domain,eTarget)).lstrip('@.'))
logoutResponse = logout(sessionId)
#print "Logout: Status-Code:", logoutResponse.header['Status-Code']
# implement dmapi commands as functions
def login(username,password):
parameters = { 'username': username, 'password': password }
message = sendCommand('login', parameters)
return message;
def logout(sessionId):
parameters = { 'auth-sid': sessionId }
message = sendCommand('logout', parameters)
return message;
def domainList(sessionId, pattern="", list_from=1, list_to=""):
parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to, 'pattern': pattern }
message = sendCommand('query-domain-list', parameters)
return message;
def dnsZoneList(sessionId, pattern="", list_from=1, list_to=""):
parameters = { 'auth-sid': sessionId , 'from': list_from, 'to': list_to, 'pattern': pattern }
message = sendCommand('dns-zone-list', parameters)
return message;
def dnsZoneGet(sessionId, domain):
parameters = { 'auth-sid': sessionId , 'domain': domain }
message = sendCommand('dns-zone-get', parameters)
return message;
# general dmapi command call
def sendCommand(command,parameter={}):
try:
url = dmapiURL+'/request/'+command
#print("Request-URL: ", url)
response = requests.get(url, params=parameter)
# print URL with parameters for debugging purposes
# print("Request-URL: ", response.url)
if response.status_code != requests.codes.ok:
raise CommandError("Command Failed! HTTP Status Code: %s" % response.status_code)
return DmapiResponse(response.text)
except requests.ConnectionError as e:
raise CommandError("Connection Error: %s" % str(e))
except requests.HTTPError as e:
raise CommandError("Http Error: %s" % str(e))
except CommandError as e:
raise
except Exception as e:
raise CommandError("Unexpected Error: %s" % str(e))
class DmapiResponse():
def __init__(self,responseBody):
parts = responseBody.split("\n\n",1)
if len(parts)>0:
self.header = self.__parseKeyValueList(parts[0])
if len(parts)>1:
self.body = parts[1]
def __parseKeyValueList(self,text):
lines = text.split("\n")
keyValueList = {}
for line in lines:
keyValue = line.split(' ',1)
key = keyValue[0].rstrip(':')
value = keyValue[1]
keyValueList[key] = value
return keyValueList
def __getSeparator(self):
if self.header.get('Separator') == 'TAB':
return "\t"
else:
return " "
def resultList(self):
lines = self.body.split("\n")
resultList = []
separator = self.__getSeparator()
for line in lines:
values = line.split(separator)
resultList.append(line.split(separator))
return resultList
def resultListWithNames(self):
columnNames = self.resultListColumns()
resultList = []
if len(columnNames) > 0:
rawList = self.resultList()
resultList = []
for row in rawList:
columns = {}
for idx, column in enumerate(row):
columns[columnNames[idx]] = column
resultList.append(columns)
return resultList
def resultListColumns(self):
if 'Columns' in self.header:
columnsText = self.header['Columns']
columns = columnsText.split(',')
return columns
else:
return []
def resultValues(self):
return self.__parseKeyValueList(self.body)
class CommandError(Exception):
def __init__(self, value):
self.value = value
def __str__(self):
return repr(self.value)
# call main function
try:
main()
except CommandError as e:
print("Error:", str(e).strip("'"))
```
## C#
Applications for domain management with DMAPI are very easy to create using MS Visual Studio. This example code logs into the Joker.com system using DMAPI requests.
It provides a domain listing, whois lookup and "Email verification".
This has been tested using Visual Studio 2008 and 2010, but should work with any version, and also with free Visual Studio Express and .NET versions from 3.5 onwards. Please find the source code as an attachment below.
We also provide this as a windows binary to try without the need of building it before. In case you run Windows 10 with "Smartscreen", you have to click on "more information" to execute this, since this binray of course is not signed by a "manufacturer"...
This is how this will look like:
# Email Gateway
# Basics
## How does the PGP/GPG-Mailinterface work?
Using the Joker.com email interface, you may send 'commands' to a special address at Joker.com by email. Those commands may consist of registration orders, domain renewals or modifications.
The Joker.com mail interface address is disclosed once you signed up as a reseller.
The emails making up the commands follow a simple format, which is described here in section 'Requests'.
For security reasons, each request which is sent to the mail gateway has to be signed using PGP or GPG. This means, you need to have a pgp/gpg-installation on your machine. Some tools which can be used for this:
- [Gnu GPG](http://www.gnupg.org/ "http://www.gnupg.org/")
- [Enigmail for Thunderbird](http://www.enigmail.net/home/ "http://www.enigmail.net/")
Emails which are not signed correctly will not be processed. All requests to the gateway have to be sent as PGP/GPG signed mails to the Joker mail-robot (you will receive the exact address if you have registered yourself as a reseller).
Mails are expected to be sent in the "**traditional**" format (signature is part of the message body), **not** (for example) in MIME encapsulated format!
The actual request (the command to be peroformed) has to be put into the subject of the email. Further details (for example the full qualified domain name) have to be put in the message body.
**Example:**
**Subject**: modify domain
\-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
tld:org
sld:dummy
ns1-handle:ns1.dummy.org
ns2-handle:ns2.dummy.org
\-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD7DBQE6ZtMfzWqd+drNYRURAuW4AJ4nRewOrNc+yLMmmCouVcMP3v5nWQCdHUlf
tJk/gOuFmDnIs3JS+7eRjnA=
=Fwmc
\-----END PGP SIGNATURE-----
## Where are the replies of the mail-gateway sent?
The replies of the gateway are generally sent to the "reply-to"-address. In order to specify that address, you will have to fill in the reply-to-field within the e-mails you send to the mail-gateway.
## How do I change my robot-email-address?
The Joker.com system identifies you using your pgp-signature and your email-address, so you have to provide a new pgp-key, if you want to change your robot-email-address. Without changing the pgp-key, our system cannot grant you access to the domains, you have registered at joker.com.
Please, follow the 3 steps below to **change your robot-email-address**.
1. Create a new contact with your new email-address using the mail-gateway.
2. Change the billing-c of **all** your domains using this new contact, which contains the new robot-email-address. Use the "list domains"-request for a listing of your domains.
3. Go to [https://joker.com/index.joker?mode=resellerpages&stage=step13b](https://joker.com/index.joker?mode=resellerpages&stage=step13b) and provide your new email-address and your new pgp-key and wait for our response mail.
## What is the Joker.com public key?
Please verify e-mails from Joker.com using the following public key:
```
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mIsEPOorJQEEAJauWOOvusxn9GFEPjZnQ3x/48OfaPwSN4cIF5ezpUT6FycZQa+q
eUnNlS+bj80ULXnyyigmkUGwEtW/Qoyd55RM983pr4KtuHSMSU9gCN1syuHlDOAm
71u6irfv5RaHbJXauMCAgUKn+dBNZVZyUTm9aW2pudcwY45apF2tieTZAAYptClq
b2tlci5jb20gc2lnbmVyIHNlcnZpY2UgPGluZm9Aam9rZXIuY29tPoiyBBMBAgAc
BQI8/NifAhsDBAsHAwIDFQIDAxYCAQIeAQIXgAAKCRAm3eE0EUTiIx9RA/9HGDrD
cVM6PjZHr5jpT4svpv7xrjVRn2OIR+s80RuBAnLyAWOflqJ9342SYD8C7BMAqYm4
wXvC3/yvbQEAqsmJ5Bbq2NV+KDepahTtL8SUQ6TkOSUd9NDOvLoQWVI6o1Dz/3MG
HLJfNtx6067Sq8pP8PuYyscPyZ7/uiUilyOrqg==
=O/7Q
-----END PGP PUBLIC KEY BLOCK-----
```
## Should I use PGP or GPG?
It does not matter if you use PGP or GPG, the version is not important as well. Just make sure that your program is able to put PGP signatures into your mail in the format described above.
Please have a look at the following web sites to get the newest versions and lots of explanation on the programs.
[http://www.pgpi.org/](http://www.pgpi.org/)
[http://www.gnupg.org/](http://www.gnupg.org/)
ATTENTION:
Users of GPG have to use the following flag:
gpg --clearsign --force-v3-sigs ....
Otherwise our system will reject your signed mails.
# Macros
## E-mail Address
**@email**
This means an email address in the following format:
**Valid values** (.com/.net only):
foo@bar.com
foo@bar.com#1
foo@bar.com#15
**Invalid values:**
Hans Nase <hans@foo.com>
hans@foo.com (Hans Nase)
**Valid values** (.org/.info/.biz/.de/.cn only):
foo@bar.com
foo-bar@bar.com
**Invalid values:**
Hans Nase <hans@foo.com>
hans@foo.com (Hans Nase)
foo@bar.com#15
## .com Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CCOM-<number>,
e.g. CCOM-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@comcont** or **@same-as**) (.com only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:CCOM-176269
admin-contact-handle:CCOM-176229
tech-contact-handle:CCOM-176269
billing-contact-handle:CCOM-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .com-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .net Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CNET-<number>, e.g. CNET-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@netcont** or **@same-as**) (.net only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:CNET-176269
admin-contact-handle:CNET-176229
tech-contact-handle:CNET-176269
billing-contact-handle:CNET-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .net-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .org Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CORG-<number>, e.g. CORG-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@orgcont** or **@same-as**) (.org only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:CORG-176269
admin-contact-handle:CORG-176229
tech-contact-handle:CORG-176269
billing-contact-handle:CORG-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .org-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .info Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format C<number>-LRMS, e.g. C176269-LRMS.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@infocont** or **@same-as**) (.info only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:C176269-LRMS
admin-contact-handle:CAFI-007
tech-contact-handle:C176269-LRMS
billing-contact-handle:CAFI-008
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .info-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .biz Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created.
ATTENTION
According to the rules of NEULEVEL, the fieldlength for most of the requestfields are limited to 30 characters. Please check very carefully the definitions of the request fields.
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
Please, keep in mind, that if you are using the concatenation of **fname** and **lname**, you have to care that the sum of both fields should not be longer than 30 characters.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,30} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,30} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,30} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,30} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,30} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,30} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,30} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,30} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,10} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,30} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,30} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,17} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,17} | no |
**An existing contact** (**@bizcont** or **@same-as**) (.biz only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle: CNEU-12345
admin-contact-handle: CNEU-12345
tech-contact-handle: CNEU-12345
billing-contact-handle: CNEU-12345
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .biz-requests the contact handles for (.com/.net/.org/.info)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
Note that for .biz-requests the contacthandles for (.info)-contacts are not allowed. If you referencing to a shortcut like C176269-LRMS, you will get an error.
## .mobi Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COMO-<number>, e.g. COMO-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@mobicont** or **@same-as**) (.mobi only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:COMO-176269
admin-contact-handle:COMO-176229
tech-contact-handle:COMO-176269
billing-contact-handle:COMO-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .mobi-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .name Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CNAM-<number>, e.g. CNAM-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fname** and lname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@namecont** or **@same-as**) (.name only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:CNAM-176269
admin-contact-handle:CNAM-176229
tech-contact-handle:CNAM-176269
billing-contact-handle:CNAM-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .name-requests the contact handles for (.com/.net)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .us Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COUS-<number>, e.g. COUS-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@uscont** or **@same-as**) (.us only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:COUS-176269
admin-contact-handle:COUS-176229
tech-contact-handle:COUS-176269
billing-contact-handle:COUS-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format CODE-<number>, e.g. CODE-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | yes, but for admin-c and tech-c only
|
**An existing contact** (**@decont** or **@same-as**) (.de only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:CODE-176269
admin-contact-handle:CODE-176229
tech-contact-handle:CODE-176269
billing-contact-handle:CODE-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .de-requests the contact handles for (.com/.net/.org/.info/.biz/.cn)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## .cn Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COCN-<number>, e.g. COCN-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no
|
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no
|
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COME-<number>, e.g. COME-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no |
**An existing contact** (**@mecont** or **@same-as**) (.me only)
This means an existing contact handle in the JOKER-DATABASE.
Examples:
owner-contact-handle:COME-176269
admin-contact-handle:COME-176229
tech-contact-handle:COME-176269
billing-contact-handle:COME-176269
In case you have entered a non-existing contact handle, the system will send you an errormail.
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
The **@same-as** makro always replaces the value for the specified contact handle with the email address of the makrotarget. If the referenced contact has to be created with this request, it takes the result handle.
Keep in mind that for .me-requests the contact handles for (.com/.net/.org/.info/.biz/.de)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.
## Nameserver
**@ns** - the definition of an existing nameserver
You have to provide a valid nameserver handle. Implicit nameserver creation is not allowed.
Examples:
ns1.foo.bar.net
ns2.foo.bar.net
ns3.foo.bar.net
## Language code
**@language** - one of the following language codes
| Languagecode | Language |
| AFR | Afrikaans |
| ALB | Albanian |
| ARA | Arabic |
| ARM | Armenian |
| AZE | Azerbaijani |
| BAQ | Basque |
| BUL | Bulgarian |
| BUR | Burmese |
| CAT | Catalan |
| CHI | Chinese |
| CZE | Czech |
| DAN | Danish |
| DUT | Dutch |
| ENG | English |
| EST | Estonian |
| FAO | Faroese |
| FIN | Finnish |
| FRE | French |
| GEO | Georgian |
| GER | German |
| HEB | Hebrew |
| HIN | Hindi |
| HUN | Hungarian |
| ICE | Icelandic |
| ITA | Italian |
| JPN | Japanese |
| KOR | Korean |
| KUR | Kurdish |
| LAO | Lao |
| LAV | Latvian |
| LIT | Lithuanian |
| MAC | Macedonian |
| MAL | Malayalm |
| NEP | Nepali |
| NOR | Norwegian |
| PER | Persian |
| POL | Polish |
| POR | Portuguese |
| RUM | Romanian |
| RUS | Russian |
| SAN | Sanskirt |
| SCC | Serbian |
| SCR | Croatian |
| SLO | Slovak |
| SLV | Slovenian |
| SPA | Spanish |
| SWA | Swahili |
| SWE | Swedish |
| SYR | Syriac |
| TAM | Tamil |
| THA | Thai |
| TIB | Tibetan |
| TUR | Turkish |
| UKR | Ukrainian |
| URD | Urdu |
| UZB | Uzbek |
| VIE | Vietnamese |
| ZHO | Chinese |
# DNS / URL-Forwarding
## Create a dns-configuration
**Introduction**
With this request you can create or modify a zonefile at the joker-nameserver.
You can add A-Records, CNAME-Records, MX-Records, a nameservice-based Url-forwarding and a frame-based Url-forwarding. Modifing the TTL is not possible.
The format of this request is a little bit different from the other requests. Please check the given examples for how to specify the different zonefile-records.
**ATTENTION:
**
You have to change the nameservers for a domain to the nameservers of joker.com first!
- a.ns.joker.com
\- b.ns.joker.com
\- c.ns.joker.com
If you would like to use the joker-nameservice, you will have to use **all** joker-nameservers.
It is **not** possible to use the joker-nameservice
- for primary nameservice only
- for secondarynameservice only
**All** joker-nameservers
- are configured to deny all zone-fetching requests!
- do not query foreign nameservers!
**Request Fields**
Definition of this request
| request-field | valid values | required |
| domains0 | @fqdn | yes |
| A | @a\_record | no |
| CNAME | @cname\_record | no |
| MX | @mx\_record | no |
| URL | @url\_record | no |
| FRAME | @url\_record | no |
Example 1: **create dns-config** (without url-forwarding and without wildcard-matching)
subject: create dns-config \[your reference id\]
domains0:hansnose.net
A:www:194.33.110.19
A:mail:194.33.110.19
A:mail2:194.33.110.20
A:@:194.33.110.10
MX:www.hansnose.net:70:mail.nrw.net
MX:www.hansnose.net:80:mail2.nrw.net
MX:@:70:mail.hansnose.net
MX:@:80:mail2.hansnose.net
CNAME:www3:some.other.domain.com
Example 2: **create dns-config** (with wildcard-matching)
subject: create dns-config \[your reference id\]
domains0:hansnose.net
A:www:194.33.110.19
A:@:194.33.110.19
A:\*:194.33.110.20
Example 3: **create dns-config** (with dns**-**based url-forwarding)
subject: create dns-config \[your reference id\]
domains0:hansnose.net
A:www:194.33.110.19
A:@:194.33.110.19
URL:www2:http://www.sone.other.domain.com/index.html
*(that means, the url within the browserbar is changing to the target address)*
Example 4: **create dns-config** (with frame**-**based url-forwarding)
subject: create dns-config \[your reference id\]
domains0:hansnose.net
A:www:194.33.110.19
A:@:194.33.110.19
FRAME:www2:http://www.sone.other.domain.com/index.html
*(that means, the url within the browserbar is **not** changing to the target address)*
## Delete a dns-configuration
**Introduction**
With this request you can delete a zonefile at the joker-nameserver.
**Request fields**
mailsubject: delete dns-config \[your reference id\]
Definition of this request
| request-field | valid values | required |
| domains0 | @fqdn | yes |
Example 1: **delete dns-config**
subject: delete dns-config \[your reference id\]
domains0:hansnose.net## List a dns-configuration
**Introduction**
With this request you can get a listing of a current zonefile.
**Request fields**
mailsubject: list dns-config \[your reference id\] definition of this request
| request-field | valid values | required |
| domains0 | @fqdn | yes |
Example 1: **list dns-config**
subject: list dns-config \[your reference id\]
domains0:hansnose.net
# Domains
## Create an order
**Introduction**
create <tld>-order
Valid values for <tld>:
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
- eu
- xxx
- asia
- me
With this request you can register one or more domains.
You have to provide the following information within the request:
- domain name(s),
- owner-contact-handle,
- admin-contact-handle,
- tech-contact-handle,
- billing-contact-handle,
- nameserver information,
- additional services, if required.
You can register up to 501 domains with one request.
If you register more than one domain with a request, all domains registerd with this request will have the same contact and nameserver structure.
There are two new requestfields within this request:
- name
- address-3
ATTENTION
Please, refer to the table for the corresponding contact handles.
**Request fields**
mailsubject: create <tld>-order \[your reference id\]
Definition of this request
| tld | request field |
| domains\[0..500\] | period
| language\[0..500\]
|
| com | \[a-z0-9-\]{1,63}\\.com | ^(\[1..9\]{1})$
| @language
|
| net | \[a-z0-9-\]{1,63}\\.net | ^(\[1..9\]{1})$
|
| org | \[a-z0-9-\]{1,63}\\.org | ^(\[1..9\]{1})$
|
| info | \[a-z0-9-\]{1,63}\\.info | ^(\[1..9\]{1})$
|
| biz | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.biz | ^(\[1..9\]{1})$
|
| mobi | \[a-z0-9-\]{1,63}\\.mobi | ^(\[1..9\]{1})$
|
| name | \[a-z0-9-\]{1,63}\\.name | ^(\[2..9\]{1})$
|
| us | \[a-z0-9-\]{1,63}\\.us | ^(\[2..9\]{1})$ |
| de | \[a-z0-9-\]{1,63}\\.de | ^(\[1..9\]{1})$
|
| cn | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.cn | ^(\[1..9\]{1})$
|
| eu | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.eu | ^(\[1..9\]{1})$
|
| me | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.me | ^(\[1..9\]{1})$ |
| asia | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.asia | ^(\[1..9\]{1})$ |
| xxx | \[a-z0-9\]\[a-z0-9-\]{1,61}\[a-z0-9\]\\.xxx | ^(\[1..9\]{1})$ |
| required | yes | yes | no (IDN domains only)
|
| tld | ns1-handle | ns1-handle
| ns1-handle | ns1-handle
| ns1-handle
| ns1-handle |
| <tld> | @ns |
| required | yes | yes | no |
### .COM order
**Example 1:** create com-order with implicit contact-handle-creation of the owner-contact
subject: create com-order \[your reference id\]
domains0:xn--hans-mller-feb.com
language0:AFR
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create com-order with implicit nameserver-creation
subject: create com-order \[your reference id\]
domains0:minus-109.com
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-handle:CCOM-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create com-order with implicit contact-handle-creation of all contacts
subject: create com-order \[your reference id\]
domains0:minus-109.com
domains1:minus-10a.com
domains2:minus-10b.com
domains3:minus-10c.com
domains4:minus-10d.com
domains5:minus-10e.com
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .NET order
**Example 1:** create net-order with implicit contact-handle-creation of the owner-contact
subject: create net-order \[your reference id\]
domains0:xn--hans-mller-feb.net
language0:AFR
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create net-order with implicit nameserver-creation
subject: create net-order \[your reference id\]
domains0:minus-109.net
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-handle:CCOM-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CCOM-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create net-order with implicit contact-handle-creation of all contacts
subject: create net-order \[your reference id\]
domains0:minus-109.net
domains1:minus-10a.net
domains2:minus-10b.net
domains3:minus-10c.net
domains4:minus-10d.net
domains5:minus-10e.net
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .ORG order
**Example 1:** create org-order with implicit contact-handle-creation of the owner-contact
subject: create org-order \[your reference id\]
domains0:xn--hans-mller-feb.org
language0:AFR
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CORG-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create org-order with implicit nameserver-creation
subject: create org-order \[your reference id\]
domains0:minus-109.org
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-handle:CORG-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CORG-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create org-order with implicit contact-handle-creation of all contacts
subject: create org-order \[your reference id\]
domains0:minus-109.org
domains1:minus-10a.org
domains2:minus-10b.org
domains3:minus-10c.org
domains4:minus-10d.org
domains5:minus-10e.org
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .INFO order
**Example 1:** create info-order with implicit contact-handle-creation of the owner-contact
subject: create info-order \[your reference id\]
domains0:xn--hans-mller-feb.info
language0:AFR
domains1:minus-10a.info
domains2:minus-10b.info
domains3:minus-10c.info
domains4:minus-10d.info
domains5:minus-10e.info
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:C282828-LRMS
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create info-order with implicit nameserver-creation
subject: create info-order \[your reference id\]
domains0:minus-109.info
domains1:minus-10a.info
domains2:minus-10b.info
domains3:minus-10c.info
domains4:minus-10d.info
domains5:minus-10e.info
period:2
owner-contact-handle:C176269-LRMS
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:C176219-LRMS
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create info-order with implicit contact-handle-creation of all contacts
subject: create info-order \[your reference id\]
domains0:minus-109.info
domains1:minus-10a.info
domains2:minus-10b.info
domains3:minus-10c.info
domains4:minus-10d.info
domains5:minus-10e.info
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .BIZ order
**Example 1:** create biz-order with implicit contact-handle-creation of the owner-contact
domains0:xn--hans-mller-feb.biz
language0:AFR
domains1:minus-10a.biz
domains2:minus-10b.biz
domains3:minus-10c.biz
domains4:minus-10d.biz
domains5:minus-10e.biz
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 2:** create biz-order with implicit nameserver-creation
subject: create biz-order \[your reference id\]
domains0:minus-109.biz
domains1:minus-10a.biz
domains2:minus-10b.biz
domains3:minus-10c.biz
domains4:minus-10d.biz
domains5:minus-10e.biz
period:2
owner-contact-handle:CNEU-123
admin-contact-handle:CNEU-124
tech-contact-handle:CNEU-125
billing-contact-handle:CNEU-126
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create biz-order with implicit contact-handle-creation of all contacts
subject: create biz-order \[your reference id\]
domains0:minus-109.biz
domains1:minus-10a.biz
domains2:minus-10b.biz
domains3:minus-10c.biz
domains4:minus-10d.biz
domains5:minus-10e.biz
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .MOBI ORDER
**Example 1:** create mobi-order with implicit contact-handle-creation of the owner-contact
subject: create mobi-order \[your reference id\]
domains0:xn--hans-mller-feb.mobi
language0:AFR
domains1:minus-10a.mobi
domains2:minus-10b.mobi
domains3:minus-10c.mobi
domains4:minus-10d.mobi
domains5:minus-10e.mobi
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:COMO-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create mobi-order with implicit nameserver-creation
subject: create mobi-order \[your reference id\]
domains0:minus-109.mobi
domains1:minus-10a.mobi
domains2:minus-10b.mobi
domains3:minus-10c.mobi
domains4:minus-10d.mobi
domains5:minus-10e.mobi
period:2
owner-contact-handle:COMO-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:COMO-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create mobi-order with implicit contact-handle-creation of all contacts
subject: create mobi-order \[your reference id\]
domains0:minus-109.mobi
domains1:minus-10a.mobi
domains2:minus-10b.mobi
domains3:minus-10c.mobi
domains4:minus-10d.mobi
domains5:minus-10e.mobi
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .NAME ORDER
**Example 1:** create name-order with implicit contact-handle-creation of the owner-contact
subject: create name-order \[your reference id\]
domains0:xn--hans-mller-feb.net
language0:AFR
domains1:minus-10a.name
domains2:minus-10b.name
domains3:minus-10c.name
domains4:minus-10d.name
domains5:minus-10e.name
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CNAM-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create name-order with implicit nameserver-creation
subject: create name-order \[your reference id\]
domains0:minus-109.name
domains1:minus-10a.name
domains2:minus-10b.name
domains3:minus-10c.name
domains4:minus-10d.name
domains5:minus-10e.name
period:2
owner-contact-handle:CNAM-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CNAM-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create name-order with implicit contact-handle-creation of all contacts
subject: create name-order \[your reference id\]
domains0:minus-109.name
domains1:minus-10a.name
domains2:minus-10b.name
domains3:minus-10c.name
domains4:minus-10d.name
domains5:minus-10e.name
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .US ORDER
**Example 1:** create us-order with implicit contact-handle-creation of the owner-contact
subject: create us-order \[your reference id\]
domains0:xn--hans-mller-feb.us
language0:AFR
domains1:minus-10a.us
domains2:minus-10b.us
domains3:minus-10c.us
domains4:minus-10d.us
domains5:minus-10e.us
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nose
owner-contact-address-1:horsefair mews
owner-contact-postal-code:4711
owner-contact-city:romsey
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:COUS-123
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create us-order with implicit nameserver-creation
subject: create us-order \[your reference id\]
domains0:minus-109.us
domains1:minus-10a.us
domains2:minus-10b.us
domains3:minus-10c.us
domains4:minus-10d.us
domains5:minus-10e.us
period:2
owner-contact-handle:COUS-123
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:COUS-13323
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create us-order with implicit contact-handle-creation of all contacts
subject: create us-order \[your reference id\]
domains0:minus-109.us
domains1:minus-10a.us
domains2:minus-10b.us
domains3:minus-10c.us
domains4:minus-10d.us
domains5:minus-10e.us
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .DE ORDER
**Example 1:** create de-order with implicit contact-handle-creation of the owner-contact
subject: create de-order \[your reference id\]
domains0:minus-10x.de
language0:GER
domains1:minus-10a.de
domains2:minus-10b.de
domains3:minus-10c.de
domains4:minus-10d.de
domains5:minus-10e.de
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nase
owner-contact-address-1:Musterstrasse 11
owner-contact-postal-code:4711
owner-contact-city:Musterhausen
owner-contact-country:DE
owner-contact-phone:49 13383794 504040
owner-contact-fax:49 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CODE-1007
ns1-handle:ns.gonzo.net
ns2-handle:ns2.gonzo.net
**Example 2:** create net-order with implicit nameserver-creation
subject: create de-order \[your reference id\]
domains0:minus-109.de
domains1:minus-10a.de
domains2:minus-10b.de
domains3:minus-10c.de
domains4:minus-10d.de
domains5:minus-10e.de
period:2
owner-contact-handle:CODE-1007
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:CODE-1007
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create net-order with implicit contact-handle-creation of all contacts
subject: create de-order \[your reference id\]
domains0:minus-109.de
domains1:minus-10a.de
domains2:minus-10b.de
domains3:minus-10c.de
domains4:minus-10d.de
domains5:minus-10e.de
period:2
owner-contact-email:gonzo@nose.net
owner-contact-individual:Y
owner-contact-fname:gonzo
owner-contact-lname:nase
owner-contact-address-1:Musterstrasse 11
owner-contact-postal-code:4711
owner-contact-city:Musterhausen
owner-contact-country:DE
owner-contact-phone:49 13383794 504040
owner-contact-fax:49 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nase
admin-contact-address-1:Musterstrasse 11
admin-contact-postal-code:4711
admin-contact-city:Musterhausen
admin-contact-country:DE
admin-contact-phone:49 13383794 504040
admin-contact-fax:49 13383794 504040
tech-contact-email:gonzo@nose.net
tech-contact-individual:Y
tech-contact-fname:gonzo
tech-contact-lname:nase
tech-contact-address-1:Musterstrasse 11
tech-contact-postal-code:4711
tech-contact-city:Musterhausen
tech-contact-country:DE
tech-contact-phone:49 13383794 504040
tech-contact-fax:49 13383794 504040
billing-contact-email:gonzo@nose.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nase
billing-contact-address-1:Musterstrasse 11
billing-contact-postal-code:4711
billing-contact-city:Musterhausen
billing-contact-country:DE
billing-contact-phone:49 13383794 504040
billing-contact-fax:49 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .CN ORDER
**Example 1:** create cn-order with implicit contact-handle-creation of the owner-contact
subject: create cn-order \[your reference id\]
domains0:xn--hans-mller-feb.cn
domains1:minus-10a.cn
domains2:minus-10b.cn
domains3:minus-10c.cn
domains4:minus-10d.cn
domains5:minus-10e.cn
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 2:** create cn-order using existing cn-handles
subject: create cn-order \[your reference id\]
domains0:minus-109.cn
domains1:minus-10a.cn
domains2:minus-10b.cn
domains3:minus-10c.cn
domains4:minus-10d.cn
domains5:minus-10e.cn
period:2
owner-contact-handle:COCN-123
admin-contact-handle:COCN-124
tech-contact-handle:COCN-125
billing-contact-handle:COCN-126
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create cn-order with backreferences using @same-as
subject: create cn-order \[your reference id\]
domains0:minus-109.cn
domains1:minus-10a.cn
domains2:minus-10b.cn
domains3:minus-10c.cn
domains4:minus-10d.cn
domains5:minus-10e.cn
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
### .EU ORDER
**Example 1:** create eu-order with implicit contact-handle-creation of all contacts
subject: create eu-order \[your reference id\]
domains0:xn--hans-mller-feb.eu
domains1:minus-10a.eu
domains2:minus-10b.eu
domains3:minus-10c.eu
domains4:minus-10d.eu
domains5:minus-10e.eu
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-email:gonzo@nose.net
admin-contact-individual:Y
admin-contact-fname:gonzo
admin-contact-lname:nose
admin-contact-address-1:horsefair mews
admin-contact-city:romsey
admin-contact-postal-code:4711
admin-contact-country:DE
admin-contact-phone:44 13383794 504040
tech-contact-email:willi@nose.net
tech-contact-individual:Y
tech-contact-fname:willi
tech-contact-lname:nose
tech-contact-address-1:horsefair mews
tech-contact-city:romsey
tech-contact-postal-code:4711
tech-contact-country:DE
tech-contact-phone:44 13383794 504040
billing-contact-email:isp@greatone.net
billing-contact-individual:Y
billing-contact-fname:gonzo
billing-contact-lname:nose
billing-contact-address-1:Melrose Plase
billing-contact-postal-code:4711
billing-contact-city:romsey
billing-contact-country:DE
billing-contact-phone:44 13383794 504040
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 2:** create eu-order using existing .eu-handles
subject: create eu-order \[your reference id\]
domains0:minus-109.eu
domains1:minus-10a.eu
domains2:minus-10b.eu
domains3:minus-10c.eu
domains4:minus-10d.eu
domains5:minus-10e.eu
period:2
owner-contact-handle:C123123
admin-contact-handle:C123124
tech-contact-handle:C123125
billing-contact-handle:C123126
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
**Example 3:** create eu-order with backreferences using @same-as
subject: create eu-order \[your reference id\]
domains0:minus-109.eu
domains1:minus-10a.eu
domains2:minus-10b.eu
domains3:minus-10c.eu
domains4:minus-10d.eu
domains5:minus-10e.eu
period:2
owner-contact-email:hans@nose.net
owner-contact-individual:Y
owner-contact-lname:nose
owner-contact-fname:hans
owner-contact-address-1:horsefair mews
owner-contact-city:romsey
owner-contact-postal-code:4711
owner-contact-country:DE
owner-contact-phone:44 13383794 504040
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
ns1-domain-name:nsxx1.gonzo.net
ns1-ip-address:194.201.101.1
ns2-domain-name:nsxx1.gonzo.net
ns2-ip-address:194.201.101.2
## Modify a domain
**Introduction**
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
With this request you can renew up to 500 domains at Joker.com.
You have to provide the following information within the request:
- the domainname(s),
- the renewalperiod or the desired expirationyear
You can renew up to 500 domains with one request.
Due to the fact, that you can renew more than 1 domain with one request, the format is a little bit different from the other requests. Please check the given examples on how to specify the renewal period.
If the sum of the expire time and the renewal time is more then 10 years, we will reject your request.
This request is not working for domains, which are located on the old system. For these domains you have to check the documentation of the old system.
If you provide the expire year, this request will rejected, if the current expire year is greater than the desired. This feature prevents an error in case 1 renew-request is sent twice by mistake.
**Request fields**
mailsubject: renew <tld>-domain \[your reference id\]
Definition of this request
You have to provide the domain name and the renewal period or the desired expire year using the format "YYYY" on one line. You have to seperate each field with a ":" (ASCII 058). The maximum for the renewal period is 9 years.
| request-field | valid values | required |
| domains\[0..500\] | \[a-z0-9-\]{1,63}\\.<tld>:(\[1-9\]|\\d{4}) | yes |
.COM renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:4
domains1:minus-119.com:4
domains2:minus-129.com:4
domains3:minus-139.com:4
domains4:minus-149.com:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:1
domains1:minus-119.com:2
domains2:minus-129.com:3
domains3:minus-139.com:4
domains4:minus-149.com:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:2005
.NET Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:4
domains1:minus-119.net:4
domains2:minus-129.net:4
domains3:minus-139.net:4
domains4:minus-149.net:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:1
domains1:minus-119.net:2
domains2:minus-129.net:3
domains3:minus-139.net:4
domains4:minus-149.net:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:2005
.ORG Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:4
domains1:minus-119.org:4
domains2:minus-129.org:4
domains3:minus-139.org:4
domains4:minus-149.org:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:1
domains1:minus-119.org:2
domains2:minus-129.org:3
domains3:minus-139.org:4
domains4:minus-149.org:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:2005
.INFO Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:4
domains1:minus-119.info:4
domains2:minus-129.info:4
domains3:minus-139.info:4
domains4:minus-149.info:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:1
domains1:minus-119.info:2
domains2:minus-129.info:3
domains3:minus-139.info:4
domains4:minus-149.info:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:2005
.BIZ Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:4
domains1:minus-119.biz:4
domains2:minus-129.biz:4
domains3:minus-139.biz:4
domains4:minus-149.biz:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:1
domains1:minus-119.biz:2
domains2:minus-129.biz:3
domains3:minus-139.biz:4
domains4:minus-149.biz:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:2005
.NAME Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:4
domains1:minus-119.name:4
domains2:minus-129.name:4
domains3:minus-139.name:4
domains4:minus-149.name:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:1
domains1:minus-119.name:2
domains2:minus-129.name:3
domains3:minus-139.name:4
domains4:minus-149.name:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:2005
.US Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:4
domains1:minus-119.us:4
domains2:minus-129.us:4
domains3:minus-139.us:4
domains4:minus-149.us:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:1
domains1:minus-119.us:2
domains2:minus-129.us:3
domains3:minus-139.us:4
domains4:minus-149.us:5
**Example 4:** renew 1 domain using the field expire year
subject: renew us-domain \[your reference id\]
domains0:minus-109.net:2005
.DE Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:4
domains1:minus-119.de:4
domains2:minus-129.de:4
domains3:minus-139.de:4
domains4:minus-149.de:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:1
domains1:minus-119.de:2
domains2:minus-129.de:3
domains3:minus-139.de:4
domains4:minus-149.de:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:2005
.CN Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:4
domains1:minus-119.cn:4
domains2:minus-129.cn:4
domains3:minus-139.cn:4
domains4:minus-149.cn:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:1
domains1:minus-119.cn:2
domains2:minus-129.cn:3
domains3:minus-139.cn:4
domains4:minus-149.cn:5
**Example 4:** renew 1 domain using the field expire year
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:2005
## Renew a domain
**Introduction**
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
With this request you can renew up to 500 domains at Joker.com.
You have to provide the following information within the request:
- the domainname(s),
- the renewalperiod or the desired expirationyear
You can renew up to 500 domains with one request.
Due to the fact, that you can renew more than 1 domain with one request, the format is a little bit different from the other requests. Please check the given examples on how to specify the renewal period.
If the sum of the expire time and the renewal time is more then 10 years, we will reject your request.
This request is not working for domains, which are located on the old system. For these domains you have to check the documentation of the old system.
If you provide the expire year, this request will rejected, if the current expire year is greater than the desired. This feature prevents an error in case 1 renew-request is sent twice by mistake.
**Request fields**
mailsubject: renew <tld>-domain \[your reference id\]
Definition of this request
You have to provide the domain name and the renewal period or the desired expire year using the format "YYYY" on one line. You have to seperate each field with a ":" (ASCII 058). The maximum for the renewal period is 9 years.
| request-field | valid values | required |
| domains\[0..500\] | \[a-z0-9-\]{1,63}\\.<tld>:(\[1-9\]|\\d{4}) | yes |
.COM renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:4
domains1:minus-119.com:4
domains2:minus-129.com:4
domains3:minus-139.com:4
domains4:minus-149.com:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:1
domains1:minus-119.com:2
domains2:minus-129.com:3
domains3:minus-139.com:4
domains4:minus-149.com:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew com-domain \[your reference id\]
domains0:minus-109.com:2005
.NET Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:4
domains1:minus-119.net:4
domains2:minus-129.net:4
domains3:minus-139.net:4
domains4:minus-149.net:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:1
domains1:minus-119.net:2
domains2:minus-129.net:3
domains3:minus-139.net:4
domains4:minus-149.net:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew net-domain \[your reference id\]
domains0:minus-109.net:2005
.ORG Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:4
domains1:minus-119.org:4
domains2:minus-129.org:4
domains3:minus-139.org:4
domains4:minus-149.org:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:1
domains1:minus-119.org:2
domains2:minus-129.org:3
domains3:minus-139.org:4
domains4:minus-149.org:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew org-domain \[your reference id\]
domains0:minus-109.org:2005
.INFO Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:4
domains1:minus-119.info:4
domains2:minus-129.info:4
domains3:minus-139.info:4
domains4:minus-149.info:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:1
domains1:minus-119.info:2
domains2:minus-129.info:3
domains3:minus-139.info:4
domains4:minus-149.info:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew info-domain \[your reference id\]
domains0:minus-109.info:2005
.BIZ Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:4
domains1:minus-119.biz:4
domains2:minus-129.biz:4
domains3:minus-139.biz:4
domains4:minus-149.biz:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:1
domains1:minus-119.biz:2
domains2:minus-129.biz:3
domains3:minus-139.biz:4
domains4:minus-149.biz:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew biz-domain \[your reference id\]
domains0:minus-109.biz:2005
.NAME Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:4
domains1:minus-119.name:4
domains2:minus-129.name:4
domains3:minus-139.name:4
domains4:minus-149.name:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:1
domains1:minus-119.name:2
domains2:minus-129.name:3
domains3:minus-139.name:4
domains4:minus-149.name:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew name-domain \[your reference id\]
domains0:minus-109.name:2005
.US Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:4
domains1:minus-119.us:4
domains2:minus-129.us:4
domains3:minus-139.us:4
domains4:minus-149.us:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew us-domain \[your reference id\]
domains0:minus-109.us:1
domains1:minus-119.us:2
domains2:minus-129.us:3
domains3:minus-139.us:4
domains4:minus-149.us:5
**Example 4:** renew 1 domain using the field expire year
subject: renew us-domain \[your reference id\]
domains0:minus-109.net:2005
.DE Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:4
domains1:minus-119.de:4
domains2:minus-129.de:4
domains3:minus-139.de:4
domains4:minus-149.de:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:1
domains1:minus-119.de:2
domains2:minus-129.de:3
domains3:minus-139.de:4
domains4:minus-149.de:5
**Example 4:** renew 1 domain using the field expirationyear
subject: renew de-domain \[your reference id\]
domains0:minus-109.de:2005
.CN Renewal
**Example 1:** renew 1 domain for 1 year using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:1
**Example 2:** renew 5 domains for 4 years using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:4
domains1:minus-119.cn:4
domains2:minus-129.cn:4
domains3:minus-139.cn:4
domains4:minus-149.cn:4
**Example 3:** renew 5 domains for different years using the field period
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:1
domains1:minus-119.cn:2
domains2:minus-129.cn:3
domains3:minus-139.cn:4
domains4:minus-149.cn:5
**Example 4:** renew 1 domain using the field expire year
subject: renew cn-domain \[your reference id\]
domains0:minus-109.cn:2005
## Transfer a domain
**Introduction**
transfer <tld>-domain
Valid values for <tld>:
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
With this request you can transfer a domain from 1 registrar to Joker.com.
You have to provide the following information within the request:
- the domain name,
- the auth-id,
- the billing-contact-handle,
You can transfer 1 com domain with one request.
If you transfer a domain to Joker.com the domain will be renewed for one year.
As you can see, we dont need information about the owner-contact. We will detect this information from the whois of the current registrar and we will create the contact-handle for the owner-contact automatically.
You need to provide us with a so called auth-id. You have to ask the current registrar for this auth-id. If you provide an invalid auth-id, the transfer will be declined by the current registrar.
As you can see, we need the billing-contact-handle. We recommend using a billing-handle with the email-address of your "robot-email". If you use a contact-handle with a different e-mail than your robot e-mail, you can't administer the transfered domain using the webinterface and the person with access to the email, which is shown in the provided billing-handle will have access using the web-interface.
If you don't have a com-contact-handle with your "robot-email", you have to create a com-handle using the "create com-contact" request.
We do not need information about the nameservers. This information will be detected from the whois of the current registrar and we will create the nameservers if necessary.
This procedure implies, that an owner change or change of nameservers during the transfer-process is not possible.
**Request fields**
mailsubject: transfer <tld>-domain \[your reference id\]
ATTENTION:
You can transfer 1 domain with one request.
Definition of this request
| request-field | valid values | required |
| domains0 | \[a-z0-9-\]{1,63}\\.<tld> | yes |
| auth-id | .\*
| yes
|
| billing-contact-handle | Please, refer to the table below.
| yes |
TRANSFER COM DOMAIN
**Example 1:** transfer com-domain
subject: transfer com-domain \[your reference id\]
domains0:minus-109.com
auth-id:0293XaAdA
billing-contact-handle:CCOM-1234
TRANSFER NET DOMAIN
**Example 1:** transfer net-domain
subject: transfer net-domain \[your reference id\]
domains0:minus-109.net
auth-id:0293XaAdA
billing-contact-handle:CNET-1234
TRANSFER ORG DOMAIN
**Example 1:** transfer org-domain
subject: transfer org-domain \[your reference id\]
domains0:minus-109.org
auth-id:0293XaAdA
billing-contact-handle:CORG-1234
TRANSFER INFO DOMAIN
**Example 1:** transfer info-domain
subject: transfer info-domain \[your reference id\]
domains0:minus-109.info
auth-id:0293XaAdA
billing-contact-handle:C176269-LRMS
TRANSFER BIZ DOMAIN
**Example 1:** transfer biz-domain
subject: transfer biz-domain \[your reference id\]
domains0:minus-109.biz
auth-id:0293XaAdA
billing-contact-handle:CNEU-123
TRANSFER NAME DOMAIN
**Example 1:** transfer name-domain
subject: transfer name-domain \[your reference id\]
domains0:minus-109.name
auth-id:0293XaAdA
billing-contact-handle:CNAM-1234
TRANSFER US DOMAIN
**Example 1:** transfer us-domain
subject: transfer us-domain \[your reference id\]
domains0:minus-109.us
auth-id:0293XaAdA
billing-contact-handle:COUS-1234
TRANSFER DE DOMAIN
**Example 1:** transfer de-domain
subject: transfer de-domain \[your reference id\]
domains0:minus-109.de
auth-id:0293XaAdA
billing-contact-handle:CODE-1234
TRANSFER CN DOMAIN
**Example 1:** transfer cn-domain
subject: transfer cn-domain \[your reference id\]
domains0:minus-109.cn
auth-id:0293XaAdA
billing-contact-handle:COCN-1234
## Delete a domain
**Introduction**
With this request you can delete a domain at Joker.com.
You have to provide the following information within the request:
- domain name(s),
- the special flag force
ATTENTION:
If you delete a domain within the first 72 hours after the registration, the registration-fee will be refunded to your account.
If Joker.com receives the delete-request more than 72 hours after the registration, you have to provide the flag "force:1", in order to accept that the registration-fee will not be refunded to your account. If you do not send the "force:1" in such a case, the request will be rejected.
**Request fields**
mailsubject: delete domain \[your reference id\]
Definition of this request
Please, do not forget to provide the domain name and the force-flag set to 1 if the domain is older 72h.
| request-field | valid values | required |
| tld | (com|net|org|info|biz|mobi|name|de|cn|eu|us) | yes |
| sld | \[a-z0-9-\]{1,63} | yes |
| force | 1|0 | no |
DELETE COM DOMAIN
**Example 1:** delete a domain during the first 72 hours after registration
subject: delete domain \[your reference id\]
tld:com
sld:frezel
**Example 2:** delete a domain after the first 72 hours after registration
subject: delete domain \[your reference id\]
tld:com
sld:frezel
force:1
**Example 3:** delete a domain only for the case that a refund is possible!
subject: delete domain \[your reference id\]
tld:com
sld:frezel
force:0
## List domains
**Introduction**
list domains
With this request you can get a list (lexicographically sorted) of all the domains, you have currently registered at joker.com.
You have to provide the target-registry within the request:
- cno = .com/.net
- com = .net
- net = .net
- org = .org
- info = .info
- biz = .biz
- mobi = .mobi
- name = .mobi
- de = .de
- cn = .cn
- eu = .eu
- us = .us
LIMITATIONS:
- Only 20.000 domains are listed. If you have more than 20.000 domains under 1 registry at joker.com, you have to track the domain names yourself.
- In case you have more than 20.000 domains at joker.com under 1 registry, this request will not work for you. The listing would be incomplete and it will be missing random domains.
- This request works only with the new joker.com system.
**Request fields**
mailsubject: list domains \[your reference id\]
Definition of this request:
| request-field | valid values | required |
| target | com|net|org|info|mobi|name|biz|de|cn|eu|us | yes |
LIST DOMAINS
**Example 1:** list domains for .com-domains
subject: list domains \[your reference id\]
target:com
**Example 2:** list domains for .net-domains
subject: list domains \[your reference id\]
target:net
**Example 3:** list domains for .org-domains
subject: list domains \[your reference id\]
target:org
**Example 4:** list domains for .info-domains
subject: list domains \[your reference id\]
target:info
**Example 5:** list domains for .biz-domains
subject: list domains \[your reference id\]
target:biz
**Example 6:** list domains for .de-domains
subject: list domains \[your reference id\]
target:de
**Example 7:** list domains for .cn-domains
subject: list domains \[your reference id\]
target:cn
## Lock a domain
**Introduction**
lock domain
With this request you can lock a domain in order to prevent fraudulent transfer attempts. If a domain is locked, each transfer-request from a foreign registrar will be declined.
You have to provide the following information within the request:
- domain name
You can lock 1 domain with one request.
**Request fields**
mailsubject: lock domain \[your reference id\]
Definition of this request
| request-field | valid values | required |
| fqdn | @fqdn | yes |
**Example 1:** lock a domain
subject: lock domain \[your reference id\]
fqdn:minus-109.com
## Unlock a domain
**Introduction**
unlock domain
With this request you can unlock a domain. If you want to transfer a domain to a foreign registrar, the domain has to be unlocked.
You have to provide the following informations within the request:
- domain name
You can unlock 1 domain with one request.
**Request fields**
mailsubject: unlock domain \[your reference id\]
Definitions of this request
| request-field | valid values | required |
| fqdn | @fqdn | yes |
**Example 1:** unlock a domain
subject: unlock domain \[your reference id\]
fqdn:minus-109.com
## Get Auth-id
**Introduction**
With this request you can retrieve the auth-id for a particular domain. That request is needed only for the TLD's .org/.info/.biz.
You have to provide the following information within the request:
- domain name
You can retrieve the auth-id for 1 domain with one request.
**Request fields**
mailsubject: get auth-id \[your reference id\]
Definition of this request
| request-field | valid values | required |
| fqdn | @orgdom | @infodom | @bizdom | @cndom | @eudom | @usdom[ ](https://joker.com/faq/content/45/183/en/valid-domain-names.html) | yes
|
**Example 1:** retrieve the auth-id for a .org-domain
subject: get auth-id \[your reference id\]
fqdn:minus-109.org
**Example 2:** retrieve the auth-id for a .biz-domain
subject: get auth-id \[your reference id\]
fqdn:minus-109.biz
**Example 3:** retrieve the auth-id for a .eu-domain
subject: get auth-id \[your reference id\]
fqdn:minus-109.eu
## Grant Roles/Domain Permissions, Internal Transfer
**Introduction**
With this request you can assign 'Roles' (permissions) of domains to other Joker.com users. The special role "creator" is an equivalent to an internal transfer of that domain to another Joker.com user.In this case, the domain is assigned to the receiving account, including all rights and permissions on this domain.
There are two variants to use this functionality: If the user id (Joker.com user account id) is given, and the account id matches the associated email address, the role is applied immediately - there will be no request for confirmation on the receiver's side. In case the user id is not given, but only the email address, the transaction has to be acknowledged by the receiver. For this, he will get an email, containing a link and a key. Either the link has to be clicked, or the key has to be applied using Joker.com (=> Transfer). This can also be used for users which do not yet have a Joker.com account.
You have to provide the following parameters:
- domain name (the domain you want to grant somebody else permissions on)
- destination client email (the email address of the user you want to receive permissions)
The following parameters are optional:
- destination client id (ID of Joker.com account - always shown in the upper right on Joker.com, also conforms to "reseller id" - must match the 'destination client email')
- desired role (type of permission you want to assign to "client email" resp. "client id" - one of "admin|tech|billing|creator"; "creator" means "all permissions" and is equivalent to an **internal transfer** or 'assignment' - also see 'roles ')
**Request fields**
mailsubject: joker-internal-transfer \[your reference id\]
Definition of this request
Valid values for <tld>: **all** Joker.com tlds
| request-field | valid values | required |
| fqdn | \[a-z0-9-\]{1,63}\\.<tld> | yes
|
| destination-client-email
| @email | yes
|
| destination-client-id
| \[0-9\]+
| no
|
| desired-role
| admin|tech|billing|creator (if omitted, default is 'creator') | no
|
**Example 1:** assign 'billing'-role to user 123456 (direct)
subject: joker-internal-transfer \[your reference id\]
```
body:
fqdn:exampledomain.com
destination-client-email:example-user@gmail.com
destination-client-id:123456
desired-role:billing
```
```
Example 2: assign 'creator'-role to user 'example-user@gmail.com' (internal transfer with invitation)
```
subject: joker-internal-transfer \[your reference id\]
body:
```
fqdn:exampledomain.com
destination-client-email:example-user@gmail.com
desired-role:creator
```
# Contacts
## Create a contact
**Introduction**
create <tld>-order
Valid values for <tld>:
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
- eu
With this request you can create person contacts. You can create 1 contact with one request.
ATTENTION:
You will find the request-field "individual" within the request-definition. if you set it to "Y", you have to provide the request-fields "lname" and "fname" or "name". If you set it to "N", you have to provide information in the request-field "organization".
As the whois for .com shows a field called person, the rules for generating this field are the following:
If you provide the field "name", the whois is showing always the values of this field, regardless of "fname" and "lname".
If you only provide the field "fname" and the field "lname", we will generate the field "name" as the result of the concatenation of "fname" + " " + "lname".
The result of "create com-contact" is a reference which is following the format:
- CCOM-<number> e.g. CCOM-176269 for a .com domain.
- CNET-<number> e.g. CNET-176269 for a .net domain.
- CORG-<number> e.g. CORG-176269 for a .org domain.
- C<number>-LRMS e.g. C176269-LRMS for a .info domain.
- CNEU-<number> e.g. CNEU-176269 for a .biz domain.
- COMO-<number> e.g. COMO-176269 for a .mobi domain.
- CNAM-<number> e.g. CNAM-176269 for a .name domain.
- COUS-<number> e.g. COUS-176269 for a .us domain.
- CODE-<number> e.g. CODE-176269 for a .de domain.
- COCN-<number> e.g. COCN-176269 for a .cn domain.
- C<number> e.g. C176269 for a .eu domain.
**Request fields**
mailsubject: create <tld>-contact \[your reference id\]
Definition of this request
ATTENTION
According to the rules of DENIC, you have to provide a faxnumber for the admin-c and the tech-c of a **.de** domain.
| request-field | valid values
| required
|
| com|net|org|info|mobi|name|us|de | biz|cn|eu |
| individual
| \[YN\]
| yes
|
| lname | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if individual = Y
|
| fname | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if individual = Y
|
| name | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if fname **and/or**
lname are not given
|
| title | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no
|
| organization | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if individual = N
|
| address-1
| \[\\x20-\\x7e\]{1,80}
| \[\\x20-\\x7e\]{1,30}
| yes
|
| address-2
| \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no |
| address-3
| Only for biz/cn/eu | \[\\x20-\\x7e\]{0,30}
| no
|
| postal-code | \[\\x20-\\x7e\]{1,50}
| \[\\x20-\\x7e\]{1,10} | yes
|
| city | \[\\x20-\\x7e\]{1,80}
| \[\\x20-\\x7e\]{1,30}
| yes
|
| state | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no
|
| country | @country
| yes
|
| email | @email
| yes
|
| phone | \[\\x20-\\x7e\]{1,50}
| \[\[\\x20-\\x7e\]{1,17}
| yes
|
| fax | \[\[\\x20-\\x7e\]{0,50}
| \[\[\\x20-\\x7e\]{0,17}
| yes (for admin-c and
tech-c of .de only)
|
CREATE COM CONTACT
Example 1: create com-contact (name will be generated from fname and lname)
subject: create com-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
Example 2: create com-contact (fname and lname will be ignored)
subject: create com-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE NET CONTACT
Example 1: create net-contact (name will be generated from fname and lname)
subject: create net-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
Example 2: create net-contact (fname and lname will be ignored)
subject: create net-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE ORG CONTACT
**Example 1:** create org-contact (name will be generated from fname and lname)
subject: create org-contact \[your reference id\]
email:gonzo@nose.org
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create org-contact (fname and lname will be ignored)
subject: create org-contact \[your reference id\]
email:gonzo@nose.org
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE INFO CONTACT
**Example 1:** create info-contact (name will be generated from fname and lname)
subject: create info-contact \[your reference id\]
email:gonzo@nose.info
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create info-contact (fname and lname will be ignored)
subject: create info-contact \[your reference id\]
email:gonzo@nose.info
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE BIZ CONTACT
**Example 1:** create biz-contact (name will be generated from fname and lname)
subject: create biz-contact \[your reference id\]
email:gonzo@nose.biz
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create biz-contact (fname and lname will be ignored)
subject: create biz-contact \[your reference id\]
email:gonzo@nose.biz
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE NAME CONTACT
**Example 1:** create name-contact (name will be generated from fname and lname)
subject: create name-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create name-contact (fname and lname will be ignored)
subject: create name-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE US CONTACT
**Example 1:** create us-contact (name will be generated from fname and lname)
subject: create us-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create us-contact (fname and lname will be ignored)
subject: create us-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE DE CONTACT
**Example 1:** create de-contact (name will be generated from fname and lname)
subject: create de-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:Musterstrasse 19
address-2:App. 1
postal-code:4711
city:Musterstadt
country:DE
phone:49 13383794 504040
**Example 2:** create net-contact (fname and lname will be ignored)
subject: create net-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:Musterstrasse 19
address-2:App. 1
postal-code:4711
city:Musterstadt
country:DE
phone:49 13383794 504040
CREATE CN CONTACT
**Example 1:** create cn-contact (name will be generated from fname and lname)
subject: create cn-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create cn-contact (fname and lname will be ignored)
subject: create cn-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CREATE EU CONTACT
**Example 1:** create eu-contact (name will be generated from fname and lname)
subject: create eu-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** create eu-contact (fname and lname will be ignored)
subject: create eu-contact \[your reference id\]
email:gonzo@nose.net
individual:Y
fname:gonzo
lname:nose
name:Mr. Gonzo Nose
address-1:horsefair mews
address-2:App. 1
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
## Modify a contact
**Introduction**
With this request you can modify person contacts. You can modify 1 contact with one request. Unspecified request-fields will be ignored.
ATTENTION:
After changing the content of the specified contact, the whois information is automatically updated.
Keep in mind that you have to provide the numerical suffix of a handle.
- If you want to make an address change within the owner-record of a domain, you have to send a "modify com-domain"-request after changing the content of the specified handle.
- Only contact-handles, which are created by the reseller or where the e-mail within the contact is matching the reseller's robot-email can be changed.
Definition of this request
| request-field | valid values
| required
|
| com|net|org|info|mobi|name|us|de | biz|cn|eu |
| handle
| Please, refer to the table below.
| yes
|
| individual
| \[YN\] | yes |
| lname | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no, if name is given
|
| fname | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no, if name is given |
| name | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if fname **and/or**
lname are not given
|
| title | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no
|
| organization | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| yes, if individual = N
|
| address-1
| \[\\x20-\\x7e\]{1,80}
| \[\\x20-\\x7e\]{1,30}
| yes
|
| address-2
| \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no |
| address-3
| Only for biz/cn/eu | \[\\x20-\\x7e\]{0,30}
| no
|
| postal-code | \[\\x20-\\x7e\]{1,50}
| \[\\x20-\\x7e\]{1,10} | yes
|
| city | \[\\x20-\\x7e\]{1,80}
| \[\\x20-\\x7e\]{1,30}
| yes
|
| state | \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no
|
| country | @country
| yes
|
| email | @email
| yes
|
| phone | \[\\x20-\\x7e\]{1,50}
| \[\[\\x20-\\x7e\]{1,17}
| yes
|
| fax | \[\[\\x20-\\x7e\]{0,50}
| \[\[\\x20-\\x7e\]{0,17}
| yes (for admin-c and
tech-c of .de only)
|
MODIFY COM CONTACT
**Example 1:** modify com-contact
subject: modify com-contact \[your reference id\]
handle:CCOM-1235
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY NET CONTACT
**Example 1:** modify net-contact
subject: modify net-contact \[your reference id\]
handle:CNET-1235
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY ORG CONTACT
**Example 1:** modify org-contact
subject: modify org-contact \[your reference id\]
handle:CORG-1235
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY INFO CONTACT
**Example 1:** modify info-contact
subject: modify info-contact \[your reference id\]
handle:C293829-LRMS
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
**Example 2:** modify info-contact (new naming convention for info-handles)
subject: modify info-contact \[your reference id\]
handle:CAFI-007
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY BIZ CONTACT
**Example 1:** modify biz-contact
subject: modify biz-contact \[your reference id\]
handle:CNEU-12345
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY NAME CONTACT
**Example 1:** modify name-contact
subject: modify name-contact \[your reference id\]
handle:CNAM-1235
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY US CONTACT
**Example 1:** modify us-contact
subject: modify us-contact \[your reference id\]
handle:COUS-1235
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
MODIFY DE CONTACT
**Example 1:** modify de-contact
subject: modify de-contact \[your reference id\]
handle:CODE-1235
address-1:Musterstrasse 1
postal-code:47011
city:Musterstadt
country:DE
phone:44 13383794 504040
MODIFY EU CONTACT
**Example 1:** modify eu-contact
subject: modify eu-contact \[your reference id\]
handle:C12345
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
## Change an address
**Introduction**
change <tld>-address
Valid values for <tld>:
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
With this request you can change the address of the domain owner.
ATTENTION:
It is not possible to change the following fields of the owner-record:
- individual
- lname
- fname
- title
- organization
- email
**Request fields**
mailsubject: change com-address \[your reference id\]
Definition of this request
| request-field | valid values | required |
com|net|org|info|mobi|name|us|de | biz|cn
|
| domains0 | \[a-z0-9-\]{1,63}\\.<tld> | yes |
| address-1 | \[\\x20-\\x7e\]{1,80} | \[\\x20-\\x7e\]{1,30}
| no |
| address-2 | \[\\x20-\\x7e\]{0,80} | \[\\x20-\\x7e\]{0,30}
| no |
| address-3
| \[\\x20-\\x7e\]{0,80}
| \[\\x20-\\x7e\]{0,30}
| no
|
| postal-code | \[\\x20-\\x7e\]{1,50} | \[\\x20-\\x7e\]{0,30}
| no |
| city | \[\\x20-\\x7e\]{1,80} | \[\\x20-\\x7e\]{1,30}
| no |
| state | \[\\x20-\\x7e\]{0,80} | \[\\x20-\\x7e\]{0,30}
| no |
| country | @country | no |
| phone | \[\[\\x20-\\x7e\]{1,50} | \[\[\\x20-\\x7e\]{1,17}
| no |
| fax | \[\[\\x20-\\x7e\]{0,50} | \[\[\\x20-\\x7e\]{0,17}
| no |
CHANGE .COM ADDRESS
**Example 1:** change com-address
subject: change com-address \[your reference id\]
domains0:gonzo.com
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .NET ADDRESS
**Example 1:** change net-address
subject: change net-address \[your reference id\]
domains0:gonzo.net
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .ORG ADDRESS
**Example 1:** change org-address
subject: change org-address \[your reference id\]
domains0:gonzo.org
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .INFO ADDRESS
**Example 1:** change info-address
subject: change info-address \[your reference id\]
domains0:gonzo.info
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .BIZ ADDRESS
**Example 1:** change biz-address
subject: change biz-address \[your reference id\]
domains0:gonzo.biz
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .NAME ADDRESS
**Example 1:** change name-address
subject: change name-address \[your reference id\]
domains0:gonzo.name
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .US ADDRESS
**Example 1:** change us-address
subject: change us-address \[your reference id\]
domains0:gonzo.us
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .DE ADDRESS
**Example 1:** change de-address
subject: change de-address \[your reference id\]
domains0:gonzo.de
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .CN ADDRESS
**Example 1:** change cn-address
subject: change cn-address \[your reference id\]
domains0:gonzo.cn
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
## Change an owner
**Introduction**
With this request you can change the owner of a .com/.net/.org/.info./.mobi/.name/.biz/.de/.cn/.eu./us-domain.
**Request fields**
mailsubject: change owner \[your reference id\]
Definition of this request
| request-field | valid values | required |
| domains0 | \[a-z0-9-\]{1,63}\\.(com|net|org|info|mobi|biz|de|cn|eu|us) | yes |
| email | an email **without** the numerical suffix | no |
| individual | \[YN\] | no |
| name ***(.com,.net,.org,.info,.biz,.mobi,.de,.cn,.eu,.us only)*** | \[\\x20-\\x7e\]{0,80} | no |
| lname | \[\\x20-\\x7e\]{0,80} | no |
| fname | \[\\x20-\\x7e\]{0,80} | no |
| title | \[\\x20-\\x7e\]{0,80} | no |
| organization | \[\\x20-\\x7e\]{0,80} | no |
| address-1 | \[\\x20-\\x7e\]{0,80} | no |
| address-2 | \[\\x20-\\x7e\]{0,80} | no |
| postal-code | \[\\x20-\\x7e\]{0,50} | no |
| state | \[\\x20-\\x7e\]{0,80} | no |
| city | \[\\x20-\\x7e\]{0,80} | no |
| country | @country | no |
| phone | \[\\x20-\\x7e\]{0,50} | no |
| fax
lock-opt-out
| \[\\x20-\\x7e\]{0,50}
\[YN\]
| no
no
|
CHANGE .COM OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.com
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .NET OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.net
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .ORG OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.org
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .INFO OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.info
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .BIZ OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.biz
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .NAME OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.name
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .US OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.us
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .DE OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.de
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
CHANGE .CN OWNER
**Example 1:** change owner
subject: change owner \[your reference id\]
domains0:gonzo.cn
fname:hans
lname:nose
address-1:horsefair mews
postal-code:4711
city:romsey
country:DE
phone:44 13383794 504040
## .asia Contacts
**new-handle** (implicit creation of a new contact)
This means the definition of a new contact. if a contact with the provided email address exists in the JOKER-DATABASE, a new contact will be created. The reference for the created handle is following the format COAS-<number>, e.g. COAS-176269.
ATTENTION:
The name of the request field depends on the context. If you want to create a contact for the owner-contact, you have to replace the ".." at the beginning of the fieldname with "owner-contact".
If you want to create a contact for the admin-contact, you have to replace the ".." at the beginning of the fieldname with "admin-contact".
If you want to create a contact for the tech-contact, you have to replace the ".." at the beginning of the fieldname with "tech-contact".
If you want to create a contact for the billing-contact, you have to replace the ".." at the beginning of the fieldname with "billing-contact".
There is a new request field called **name** within the contact definition. This field is mandatory, if you do not provide the **fnamelname**. You have to provide the request field **name**, if **fname** and **lname** are not found. This is very important for the whois output. Everytime a field **person** is shown. If you are using the request field name, the whois is showing the value for **name**, regardless the content of the request fields **fname** and **lname**. If you do not provide the request field **name** but your are providing the request fields **fname** and **lname**, the whois is showing the concatenation of these fields.
There is also a new request field called **address-3** within the contact definition. This field is not mandatory, it is simply the 3rd line of the address.
| request-field | valid values | required |
| ".."-individual | \[YN\] | yes |
| ".."-lname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-fname | \[\\x20-\\x7e\]{0,80} | no, if name is given |
| ".."-name | \[\\x20-\\x7e\]{0,80} | yes, if fname **and/or** lname are not given |
| ".."-title | \[\\x20-\\x7e\]{0,80} | no |
| ".."-organization | \[\\x20-\\x7e\]{0,80} | yes, if individual = N |
| ".."-address-1 | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-address-2 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-address-3 | \[\\x20-\\x7e\]{0,80} | no |
| ".."-postal-code | \[\\x20-\\x7e\]{1,50} | yes |
| ".."-city | \[\\x20-\\x7e\]{1,80} | yes |
| ".."-state | \[\\x20-\\x7e\]{0,80} | no |
| ".."-country | @country | yes |
| ".."-email | @email | yes |
| ".."-phone | \[\[\\x20-\\x7e\]{1,50} | yes |
| ".."-fax | \[\[\\x20-\\x7e\]{0,50} | no
|
It is also possible to set a reference to a contact definition, which has been made earlier within the current request. To do so, please use the following syntax:
admin-contact-handle:same-as-owner-contact
tech-contact-handle:same-as-admin-contact
billing-contact-handle:same-as-tech-contact
With this request you can create an entry for a nameserver in the Joker.com database. If a nameserver is created, you can reference this nameserver using the hostname during a "create order"-request.
ATTENTION:
Only nameservers, which Joker.com is respondsible for, will be shown with the ip-address in the whois-output.
If you submit a "create-ns"-request for a nameserver under a domain, which is not registered with Joker.com or for a nameserver under a country-code-domain, the values for the ip-addresses are ignored.
**Request fields**
mailsubject: create <tld>-ns \[your reference id\]
| request-field | valid values | required |
| ns-domain-name | (\[a-z0-9-\]{1,63}\\.)+(@country|com|net|org|int|edu|mil|biz|info|mobi|name) | yes |
| ns-ip-address | @ip | yes |
CREATE COM NAMESERVER
Example 1: create com-ns
subject: create com-ns \[your reference id\]
ns-domain-name:ns1.dummy.com
ns-ip-address:194.111.43.1
CREATE NET NAMESERVER
Example 1: create net-ns
subject: create net-ns \[your reference id\]
ns-domain-name:ns1.dummy.net
ns-ip-address:194.111.43.1
CREATE ORG NAMESERVER
Example 1: create org-ns
subject: create org-ns \[your reference id\]
ns-domain-name:ns1.dummy.org
ns-ip-address:194.111.43.1
CREATE INFO NAMESERVER
Example 1: create info-ns
subject: create info-ns \[your reference id\]
ns-domain-name:ns1.dummy.info
ns-ip-address:194.111.43.1
CREATE BIZ NAMESERVER
Example 1: create biz-ns
subject: create biz-ns \[your reference id\]
ns-domain-name:ns1.dummy.biz
ns-ip-address:194.111.43.1
CREATE NAME NAMESERVER
Example 1: create name-ns
subject: create name-ns \[your reference id\]
ns-domain-name:ns1.dummy.name
ns-ip-address:194.111.43.1
CREATE US NAMESERVER
Example 1: create us-ns
subject: create us-ns \[your reference id\]
ns-domain-name:ns1.dummy.us
ns-ip-address:194.111.43.1
CREATE DE NAMESERVER
Example 1: create de-ns
subject: create de-ns \[your reference id\]
ns-domain-name:ns1.dummy.de
ns-ip-address:194.111.43.1
CREATE CN NAMESERVER
Example 1: create cn-ns
subject: create cn-ns \[your reference id\]
ns-domain-name:ns1.dummy.cn
ns-ip-address:194.111.43.1
CREATE EU NAMESERVER
Example 1: create eu-ns
subject: create eu-ns \[your reference id\]
ns-domain-name:ns1.dummy.net
ns-ip-address:194.111.43.1
## Modify a nameserver
**Introduction**
modify <tld>-ns
Valid values for <tld>:
- com
- net
- org
- info
- biz
- mobi
- name
- us
- de
- cn
- eu
With this request you can change the ip-address of a nameserver in the Joker.com database.
ATTENTION:
Only nameservers, which Joker.comis respondsible for, will be shown with the ip-address in the whois-output, so only these nameservers could be changed.
If you submit a "modify-ns"-request for a nameserver under a domain, which is not registered with Joker.com or for a nameserver under a country-code-domain, this request will be ignored.
**Request fields**
mailsubject: modify <tld>-ns \[your reference id\]
Definition of this request
| request-field | valid values | required |
| ns-handle | (\[a-z0-9-\]{1,63}\\.)+(@country|com|net|org|int|edu|mil|biz|info|mobi|name) | yes |
| ns-ip-address | @ip | yes |
MODIFY COM NAMESERVER
**Example 1:**
modify com-ns
subject: modify com-ns \[your reference id\]
ns-handle:ns1.dummy.com
ns-ip-address:194.111.43.1
MODIFY NET NAMESERVER
**Example 1:**
modify net-ns
subject: modify com-ns \[your reference id\]
ns-handle:ns1.dummy.com
ns-ip-address:194.111.43.1
MODIFY ORG NAMESERVER
**Example 1:**
modify org-ns
subject: modify org-ns \[your reference id\]
ns-handle:ns1.dummy.org
ns-ip-address:194.111.43.1
MODIFY INFO NAMESERVER
**Example 1:**
modify info-ns
subject: modify info-ns \[your reference id\]
ns-handle:ns1.dummy.info
ns-ip-address:194.111.43.1
MODIFY BIZ NAMESERVER
**Example 1:**
modify biz-ns
subject: modify biz-ns \[your reference id\]
ns-handle:ns1.dummy.biz ns-ip-address:194.111.43.1
MODIFY NAME NAMESERVER
**Example 1:**
modify name-ns
subject: modify name-ns \[your reference id\]
ns-handle:ns1.dummy.name
ns-ip-address:194.111.43.1
MODIFY US NAMESERVER
**Example 1:**
modify us-ns
subject: modify us-ns \[your reference id\]
ns-handle:ns1.dummy.us
ns-ip-address:194.111.43.1
MODIFY DE NAMESERVER
**Example 1:**
modify de-ns
subject: modify de-ns \[your reference id\]
ns-handle:ns1.dummy.de
ns-ip-address:194.111.43.1
MODIFY CN NAMESERVER
**Example 1:**
modify cn-ns
subject: modify cn-ns \[your reference id\]
ns-handle:ns1.dummy.cn
ns-ip-address:194.111.43.1
MODIFY EU NAMESERVER
**Example 1:**
modify eu-ns
subject: modify eu-ns \[your reference id\]
ns-handle:ns1.dummy.com
ns-ip-address:194.111.43.1
# Other Requests
## Support
**Introduction**
With this request you can send a question to the support team at Joker.com. Only questions, which are sent to the e-mail gateway are accepted.
ATTENTION:
Please, make sure that you sign your message with the keyset sent by you to Joker.com during your reseller registration. Please, also make sure not to include any characters that are not part of the 7-bit ASCII standard and do not use trailing blanks (i.e. every non blank line has to end with a non-whitespace character).
**Request fields**
mailsubject: support \[your reference id\]
Example 1
subject: support \[your reference id\]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Enter your question here.
Dont forget the fqdn in question
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD7DBQE6ZtMfzWqd+drNYRURAuW4AJ4nRewOrNc+yLMmmCouVcMP3v5nWQCdHUlf
tJk/gOuFmDnIs3JS+7eRjnA=
=Fwmc
-----END PGP SIGNATURE-----
# Examples
## Complete set of examples to download
We offer all examples summarized in a textfile. The file is attached to this article. As it has a lot of examples, it is recommended to use the search function of your text editor to find information.
# Plugins
# Joker.com WHMCS Plugin
## WHMCS Registrar Module
[WHMCS](https://www.whmcs.com/ "WHMCS") is a popular web hosting and automation solution, which includes billing and support options. If you are using WHMCS for your hosting activities, you may interface Joker.com with WHMCS' domain functionality to easily order and manage domains from within WHMCS. 1)
Joker.com maintains a registrar module for WHMCS, which offers a great load of features to interface Joker.com seamlessly from within WHMCS.
The latest Plugin version is always available on our [GitHub ](https://github.com/joker-registrar/joker-whmcs/releases "Joker.com GitHub Account")account.
The following registrar core functionality is provided:
- register domains
- initiate transfers
- perform renewals
- allow viewing and changing of nameservers
- allow viewing and changing of WHOIS information of domains
- usable with any TLD Joker.com offers
- TLD & Pricing Sync
Additionally, also these features are provided:
- create/edit email forwards
- create/edit dns records for joker-ns
- fetch auth id ("EPP Code")
- sync of expiration date
- order whois privacy protection with domain registration, transfer and renewal
- switch easily between production and testing environment (OT&E)
#### Installation:
Please extract the contents of the **ZIP archive** which you will find at the top left of this page into the folder
***modules/registrars/joker/***
of your **WHMCS** installation.
In case you want to register **.FI** domains, please add the contents of the file "**additionalfields.txt**" to "**resources/domains/additionalfields.php**".
In case you are registering **.EU** domains, please note that as of plugin version **1.3.4** you should remove the **"\[.eu\]"**-section from "**resources/domains/additionalfields.php**", since they now have been implemented by WHMCS directly.
The configuration of the Joker.com registrar module is done by using the **WHMCS admin section**. For this, please login as "admin" into your WHMCS installation, and navigate to
**Setup -> Products/Services -> Domain Registrars**
Pick "Joker.com" from the list, "Activate" the plugin, and enter your Joker.com
Reseller's credentials - **the same you are using for DMAPI**.
Alternatively, you also may use Joker.com API keys.
You also may choose to use the "TestMode" for dry run on our OT&E platform, or to configure the free Joker.com nameservers as a default for new domains.
Once activated, you may always change these settings by clicking on "Configure".
Don't forget to "Save Changes" after doing so.
#### Usage:
You will find most options for domains in section "**Clients -> Domain registrations**" - **click on the domain name** to see all domain details.
A special command there is "**Sync**" at the '**Registrar Commands**' - this will trigger a manual sync of a domain's status and expiration date with Joker.com, in case it was modified outside of WHMCS.
This is usually also done automatically by the '**WHMCS domainsync cron**' - please make sure that you added this with your WHMCS installation.
Please send us your feedback:
Enjoy!
1) the WHMCS plugin is provided "as-is" without any further obligation or promise of quality or reliability. The normal Joker.com Terms & Conditions apply. WHMCS Limited is responsible for the functionality and availability of the WHMCS system.
**Versions**
Version History
New in version 1.3.7
- fixed Joker.com DNS list
New in version 1.3.6
- fixed DMAPI get-transfer-auth-id request
New in version 1.3.5
- optimized DMAPI timings
New in version 1.3.4
- changed Joker.com default nameservers to the new ones
- added support for the .EU contact extensions
New in version 1.3.3
- added premium renewal price update in manual sync
New in version 1.3.2
- added support for language of IDN domains
New in version 1.3.1
- added support for .eu country of citizenship
- added use of WHMCS admin contact
New in version 1.3.0
- added support for TLD & Pricing Sync
New in version 1.2.5
- added support for premium domains
New in version 1.2.4
- fixed issue with domain syncronisation cron
New in version 1.2.3
- fixed issue with puny code in the domain availability check
New in version 1.2.2
- fixed an issue with .uk domain contacts
New in version 1.2.1
- fixed some issues with the domain availability check
New in version 1.2.0
- added dnssec management
New in version 1.1.5
- fix for .eu expiration date / redemption grace period problem
New in version 1.1.4
- added account balance check for domain transfers
- added a config option to enable automatic restore from redemption grace period if renew is not possible
New in version 1.1.3
- added account balance check for domain renewals
New in version 1.1.2
- fixed contact information change for WHMCS 7.x
New in version 1.1.1
- fixed toggling of id protection
New in version 1.1.0
- domain availability check
- own CRON job script, for registration status check
New in version 1.0.4:
- use API key instead of user/password credentials
- maintain privacy settings for domain
``domain:joker.com`
Possible replies are:
| status of the domain | answer |
|---|
| domain is available: | domain:joker.com **free** |
| domain is registered already: | domain:joker.com **registered** |
| domain status is unknown (registry down, etc): | domain:joker.com **unknown** \[optional error text\]
|
# TLD List and Assosiated Contact Prefixes
This table lists the prefixes used for contact handles, which define how names and address data are referenced for each TLD. A contact handle such as **CODO-8463533** represents an underlying domain contact record (e.g., “John Doe” and their associated details).
Because TLDs can migrate between providers, we recommend checking this page periodically to ensure the information is up to date.
# News and Updates
[More News at Joker.com](/faq/books/jokercom-faq-en/chapter/new-at-jokercom-Vz2)
# RPanel.io: Reseller Profile, Orders & DMAPI Key Management
#### Latest Frontend Additions to our Reseller Portal RPanel.io
---
##### Reseller Profile Management Made Easy
Managing your **Reseller Profile** is now more convenient than ever! With our latest update, you can **edit and update your reseller information** effortlessly in **rpanel.io**:
How can you use it? For example:
- Customize your **WHOIS signature**
- Set up **white label for notification emails**
- Define your **landing page for authorization forms**
****
Take full control of your reseller identity and branding - all in one place. Log in to **rpanel.io** and explore the new feature today!
---
##### Smarter Order Management and Export
We’re excited to introduce a new addition to our Reseller's portal, **rpanel.io** that makes managing your orders easier than ever! You can find it under **Orders** in the user menu:
With this latest update, you can now view your orders **- both paid and payment-free transactions for the last three months** - at a glance. Effortlessly filter them any way you like and **download them as a CSV file** for seamless record-keeping and analysis:
This enhancement gives you **more control, better visibility, and improved efficiency** in handling transactions. Whether you're tracking payments or organizing order details, rPanel.io now works even harder for you!
---
##### DMAPI Key Management
Managing your **DMAPI keys** just got a whole lot easier! You can access the API keys management section over the user menu:
With our latest update, you can now **create, delete, and modify API keys** directly in **rpanel.io** - all with customizable access levels.
Whether you need full control or limited permissions, this new feature gives you the flexibility to manage your API keys securely and efficiently.
# Rpanel.io Update: Enhanced Dashboard Features
We’ve made some exciting improvements to the Rpanel.io dashboard to make the **promotions overview** easier to navigate:
- **TLD List Upgrade** – Now displays both regular and promotional prices
- **Promos Section Fixes** – Smoother navigation with paging, plus new search and download options.
- **Upcoming Promos** – Easily filter upcoming promotions and download them in just a click.
These updates are designed to give you more transparency, flexibility, and a convenient overview of the current and upcoming promotions.
#### DMAPI Update: Promo Requests
**DMAPI** now supports **retrieving current and upcoming promotions**. For full details on usage, please see our [FAQ](https://joker.com/faq/books/reseller-documentation-en/page/other-requests#bkmrk-query-promos-list)
# Rpanel.io Update: Order List and Transfer Overview
#### Enhanced Order List
We’ve made improvements to the **order list** to make your workflow smoother:
- Filter orders by **status** and/or **cost -** free or paid operations
- Export your **filtered list as CSV** for easy reporting and analysis
This may be a small addition, but it brings a big boost to **usability and efficiency**, helping you quickly find what you need and work more effectively.
#### Track Every Move: New Domain Transfer Overview in Rpanel.io
Managing domain transfers just got a whole lot clearer. With the new **enhanced transfer overview**, you can now:
- See **exact dates** for transfers, both in the on-screen list and in CSV exports
- Get a full picture with an **overview of outgoing transfers** in addition to incoming ones
This upgrade gives you **complete visibility into your transfer activity**, making it easier than ever to track, report, and stay in control of your domains.
# New Feature: Virtual Zones
**Virtual Zones** provide enhanced flexibility and control by allowing you to create and manage DNS zones even if a domain is not yet using Joker.com’s nameservice.
With Virtual Zones, you can:
- **Prepare DNS records in advance** before switching nameservers, ensuring a smooth and uninterrupted transition.
- **Set up DNS while a domain transfer is still in progress**, so the configuration is ready the moment the transfer completes.
- **Activate Joker.com nameservers instantly** once your zone is fully configured - without any downtime.
This feature significantly simplifies and streamlines the process of migrating DNS to Joker.com, making transitions more reliable and secure.
#### Create Virtual Zone at Rpanel.io
In Domain Overview, click "Prepare DNS":
The DNS editor indicates Virtual Zone mode with an additional header:
Add your records, click "Save":
The zone is now prepared and will automatically become active as soon as you switch to the nameservers of Joker.com.
If you prepared the zone before the transfer, it will remain editable even if the transfer is already in process.
Please note: Preparation of zones of domains which do have DNSSEC enabled is **not supported**. DNSSEC has to be temporarily switched off, before a zone can be prepared.
Please find [HERE](https://joker.com/faq/books/jokercom-faq-en/page/new-feature-virtual-zones) how to create virtual zones at Joker.com
# RPanel: New Unified Domain Search
We’ve upgraded RPanel’s search functionality to make finding domains faster and more flexible than ever.
**What’s new:**
- **Unified search:** Standard and advanced search criteria now work together seamlessly, so you can combine multiple filters in a single query.
- **Improved advanced search:** Advanced criteria are now integrated with standard search, clearly showing which filters are active. You’ll also see the number of active filters.
- **Powerful queries:** Easily search for complex conditions, like domains where the registrant contains *‘John’* and the *‘domain problem’* flag is active, for example, suspended domains.
- **Comprehensive contact search:** All contact attributes can now be used in searches, giving you complete control over filtering by registrant, admin, or technical contacts.
**Why it matters:**
These improvements save time, reduce errors, and facilitate easier management of large portfolios. Whether you’re troubleshooting, analysing domains, or supporting clients, RPanel now gives you the full picture - faster and more efficiently.
# Rpanel.io: Improvements in the Domain Overview
We’ve upgraded the Rpanel.io domain overview to make managing large domain portfolios faster, clearer, and more intuitive. The improved interface now includes a richer set of filters, allowing you to pinpoint exactly the domains you need to review or update.
#### New and Enhanced Filters
You can now filter domains by:
- **DNSSEC Status** – See whether DNSSEC is *active* or *inactive* at a glance.
- **Auto-Renew Status** – Quickly find domains with auto-renew turned *on* or *off*.
- **Premium Domain Flag** – Filter *premium* vs. *non-premium* domains easily.
- **Domain Problems** – Identify domains requiring attention, such as *suspended*, *invalid address*, or *unverified* status.
- **Expiration Status** – Instantly view which domains are *expired* or still active.
- **Redemption Grace Period (RGP)** – Check whether domains are currently in *RGP*.
- **Joker Nameservers Usage** – Find domains using or not using *Joker.com default nameservers*.
- **Domain Lock** – Filter by *locked* or *unlocked* domains for easier transfer preparations.
- **Privacy Protection** – Sort domains based on whether *WHOIS privacy* is enabled or disabled.
These additions make it significantly easier to audit your portfolio, generate reports, and take bulk actions with precision.
# RPanel Update: Enhanced Registrant Verification Tools
We’re excited to introduce a new improvement to the **Registrant Verification** section in rpanel.io - designed to make verification management faster, clearer, and more efficient for our resellers.
#### **What’s New?**
You can now **search and filter** verification records directly by:
- Domain name
- Email address
This enhancement makes it significantly easier to identify specific verification tasks, especially for resellers managing a large volume of registrations. No more scrolling through long lists - simply enter the domain or email you’re looking for and get instant results.