Reseller Documentation (EN)

General Info, Tools, APIs

General Information

General Information

What is an "OT+E" System?

OT&E stands for Operational Test & Evaluation, which is a type of testing and evaluation system that is designed to avoid any impact on real data or assets such as registered domains or contacts.

At Joker.com, we have an OT&E system that is essentially a duplicate of our main system, with special "fake" registries that are used for testing and evaluation purposes. This allows our resellers to test their scripts and methods using the Joker.com API and tools, without having to worry about making changes to real data.

With our OT&E system, resellers can perform domain orders and object manipulations in a simulated environment, allowing them to test their systems and make any necessary changes before going live with their services. This helps to ensure a smooth and error-free experience for our resellers and their customers.

Our OT&E system mainly consists of:

In case you are interested in using these systems, please consider becoming a reseller of Joker.com.

Our resellers benefit from discounts of up to 40% on all prices.

General Information

Why would I register as a Reseller?

Without a doubt, there are plenty of compelling reasons to join our reseller program. Let's explore the exciting advantages you can enjoy:

General Information

How to register as Joker.com Reseller?

Please click here for more information on how to register as a Joker.com reseller.

General Information

Who could become a Reseller?

Whether you're an individual or a company, you are eligible to become a Joker.com reseller. If you have five domains or more, it's definitely worth considering the reseller opportunity.

General Information

Is there a fee for becoming a Reseller?

No, becoming a Joker.com reseller is free.
However, resellers have to fund their account with Joker.com in advance (pre-payment).
You are free to decide to what extend to fund your account.
 
Every time you place an order, the amount for this order will be deducted from your account. This is especially useful to guarantee reliable auto-renewals, in case you chose to make use of this feature.

General Information

How to update my Reseller data?

To modify your personal data, your standards for registration, whois templates and more, please login to Joker.com using your reseller credentials.

Then in the dashboard, click on 'Reseller Area'. under "Quick Access" section, and then choose 'Update Reseller Data', or use the menu 'Resellers', followed by 'Reseller's Profile'

You will find more settings like 'language for system emails' or 'auto renewal' in 'Your Account', or also in the menu 'My Joker' followed by 'My Profile'.

General Information

How to add existing domains to my portfolio?

Transition to a reseller account

If you decide to let your Joker.com login account migrate to a Joker.com Reseller account, all your domains will be added automatically to this Reseller account.

 

Moving a domain from Joker.com User A to User B (cooperative)

If you own the existing domain, using another Joker.com account, please visit "My Domains" from the "Domains" menu.

Click on the "menu" icon ("hamburger" icon on the right) of the domain you want to move, and choose "Grants".

Choose "Assignement" (= "Internal transfer") as "Role", enter the email address of the account holder to whom the domain should be transferred to, add a comment/description if you which, and press "add".

You may then add more domains; please press "save" when you are done.

After this, a transfer-link is sent to the email address you entered. You will also find this as a "pending" record in the "Grants" dialogue mentioned above. The "transfer link" will be valid for 7 days.

The recipient of the transfer-link imports the domain simply by clicking on this link.

As an alternative, this email also contains an "internal transfer key", which can be used using "Domain Transfer" on Joker.com ("internal transfer").

 

Moving a domain from Joker.com User A to User B (claim)

If you want to "move" or claim domains from one Joker.com account (regular or reseller) to another Joker.com account (e.g. your new reseller account), please choose "Change Ownership or Permissions of a Domain" from the "Domains" menu.

Enter your domain, and "proceed" - depending on the Whois data and current ownership of the domain, you might have to send in a document.

Procedure with Email Gateway

If you want to 'move' domains owned by other Joker.com login accounts, you can do this easily using the Roles & Grants system to perform an Internal Transfer to the account of choice.

General Information

What is the 'admin' email address for?

A Joker.com reseller usually has two registered email addresses with Joker.com, one for the 'robot' emails, and another for administrative tasks.

Reseller news and monthly invoices will be sent to the administrative address. The 'robot' address corresponds to the standard address associated to the Joker.com login.

All notifications resulting from domain orders, renewals and modifications will be sent to this address.

This address for notifications can be changed easily in 'My Profile'.

General Information

What is the so called 'Additional Whois Signature' for?

The "Additional Whois Signature" is part of the data asked during the registration as a Joker.com reseller.

Those input fields are optional, but if you provide them, they will be used to publish your strings in global whois for your domains.

This way your customers can identify you as their domain provider.

The strings you provide will be shown as "Sponsoring Reseller".

Please note: You can provide or modify this data at any time in the Reseller's Area.

General Information

What is the Joker.com PGP/GPG-Key?

This is Joker.com's  public GPG/PGP key - you may use it to verify signed mails sent from Joker.com:

-----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-----

 

 

General Information

If I want to leave Joker.com one day, do I have to expect problems transferring my domains?

Joker.com respects its customers and provides outgoing transfers as normal operations.

There are no additional of hidden fees associated with a outgoing transfer.


General Information

What is the minimum amount I have to pay in advance to become a reseller?

Currently, there is no minimum funding requirement for your reseller account. Your discount will be based on the revenue you generated in the past, allowing you the flexibility to grow at your own pace. 

For more information, please also see Joker.com Reseller Subscription.

General Information

Do I have to pay VAT?

No VAT is charged for:

VAT is charged for

Swiss and Liechtenstein customers are free from paying VAT until December 31st 2017. Legislation will change there on Jan 1st 2018, which means we have to charge the VAT rate there as well - unless you provide us with a UID.

General Information

What is the difference between a reseller and a retail customer?

As a reseller, you benefit from several additional options:

General Information

Should I use PGP?

PGP or GPG is only needed in case you want to make use of the email gateway to order, renew or manage domains. If you want to use the API, RPanel or the Website, PGP is not needed.

General Information

May I use several methods in parallel to access my domains?

Yes, this is possible. However, you should make sure that you don't issue the same orders on the same object twice, i.e. if you you send a renewal request through the mail interface, and do the same using dmapi, the domain will be renewed twice.

General Information

How to renew a domain without having funds in my account?

Please logoff from Joker.com, and then visit "Renew your Domains" from the "Domains" menu.

You will then see a "Simple Renewal", where you can renew any domain with any payment method.

You may also use another Joker.com account, or create a new one for this. Only if you are logged in using your regular reseller account, the system always uses the reseller funds for payments.

As an alternative, you also may put only some small funds into your reseller account, just to allow for regular renewal.

Using PayPal instantly adds funds to your account.

Reseller Control Panel

Reseller Control Panel

The Reseller Control Panel

RPanel Next is the next generation of our Reseller Control Panel.

It has been created from scratch, focussed to provide you with the ultimate tool to handle all needs of a domain's business.

The application is pretty self-explanatory, but here is a short list of what's important to know about this tool. But you definitely should give it a try!

 

       

Reseller Control Panel

The Joker.com PHP Client

Joker.com provides this tool as an fully working example of how to make use of the Joker.com API (DMAPI).

The Joker PHP Client is a lightweight web interface, demonstrating how to implement a full-featured domain handling.

The source code of this web interface is freely available for download on Sourceforge, so that our resellers could run it on their own site! The API used in this tool is called DMAPI and it is a Joker.com domain registration system offered as Web service (API).
 
The Joker PHP Client is of course also provided as a hosted service by Joker.com, and can be reached as rcp.joker.com.

Please try it out. Log in with your Joker.com reseller account, and operate carefully with it as it is completely functional. Your feedback as a reseller will be greatly appreciated and will help us to improve this application.
 
Requirements:
    Web server
    PHP 5.x
    Web browser

Summary:
    Reseller Control Panel is destined to handle any domain operations
    which are offered by the domain registrar Joker.com.
    Currently it can:
 
Download:
    You can get the newest version at http://sourceforge.net/projects/joker-client/.

Installation:
    Please see Installation of Joker PHP Client, and there is also an INSTALL file in the distribution package.

Support:
    You can contact us through our support area.
Reseller Control Panel

Installation of Joker.com PHP Client

To successfully install this client application, you need a basic knowledge of Web servers, PHP and file systems.

In principle the installation is only a copy and run. The first thing to do is to ensure, that your Web server runs PHP files, and if not to configure it appropriately.

Quick installation:

 1. Untar or unzip the distribution (be sure to unzip the subdirectories):

tar -xzvf package_name_x.x.x.tar.gz

in your webserver's document root. If you don't have direct access to your document root, put the files in a directory on your local machine, and transfer the directory on your web server using, for example, ftp.

 2. Ensure that all the scripts have the appropriate owner (if PHP is running in safe mode, having some scripts with an owner different from the owner of other scripts will be a problem). Be sure that the application can write log files, temp files and sessions. This means that the folders specified in config.php should be made writeable for the application.

 3. This application needs cURL to communicate with DMAPI. You have to have the cURL PHP module enabled. If you run Windows it is provided with every instance of PHP and has to be uncommented in php.ini. Do not forget to restart your webserver after enabling the module. If you run Linux then this module has to be compiled and included. If you wonder how to do this, please read the PHP manual dealing with cURL (http://php.net/curl).

Problems were reported when "zend.ze1_compatibility_mode" is set to "on" in PHP 5.2.5. In lower versions this setting caused no problems.

 5. Open the file <www.your-host.com>/<your-install-dir>/index.php in your browser. The Joker.com PHP client should now display a welcome screen with a login dialog.

Have fun and don't forget to send feedback!

Reseller Control Panel

Usability Hints

Some notes:

DMAPI

DMAPI

Basics

Commonalities for all requests

 DMAPI-Server URL

This is the service address which has to be used for all requests:

https://dmapi.joker.com

This is how a request looks like:

https://dmapi.joker.com/request/<name-of-request>?<name-of-parameter-1>=<value-of-parameter-1>

&<name-of-parameter-2>=<value-of-parameter-2>&auth-sid=<your-session-id>

Header fields which are returned by most requests

Tracking Id Unique server-assigned tracking id, assigned to almost all requests 
Status-Code 0 if no error occured, otherwise other than 0
Status-Text Human readable error description
Result ACK or NACK (= "Acknowlegded" or "Not Acknowledged") 
Error May be returned if (and only if) the request was rejected, in this case reason(s) will be provided. Presence of this line in headers is indicative for that processing didn't take place.
Warning Indicative of non-fatal processing or validation problems
Proc-Id Joker.com processing ID 
HTTP error codes 200 if everything is OK (request was accepted and processed or queued for processing), otherwise the reason will be provided in Error header lines (or, if this is absent, HTTP error code should be used).

 

IMPORTANT: Every request (except "login") requires the presence of the Auth-Sid variable ("Session ID"), which is returned by the "login" request (login). An active session will expire after some inactivity period (default: 1 hour).

 In case you are using a browser to access this service, the session id will be set as a cookie, hence need not to be specified as Auth-Sid (unless cookies are not supported or turned off). In any case, Auth-Sid has precedence, if provided.

 Requests consist of these parts:

Whois Privacy Services

Privacy services are available for most generic top level domain names. The availablitiy of privacy services is indicated in Joker.com's price list and domain search.

 For requests "domain-register" and "domain-transfer-in-reseller", there exists an additional parameter "privacy":

For "domain-renew", the additional parameter privacy works similar:

 

To order privacy services for existing domains, the new request "domain-privacy-order"can be used:

    domain=example.com
    period=12 (in months, as usual)
    expyear=2016 (privacy expiration year, similar to domain renewal request)
    privacy=basic|pro 

    If neither period nor expyear is provided, then privacy is ordered for
    remaining domain lifetime, whatever it is.

Example:
https://dmapi.joker.com/request/domain-privacy-order?domain=example.com&privacy=basic&auth-sid=<your-current-session-id>

 

The request "domain-set-property" allows to manage privacy services for domains which already do have a valid privacy service subscription:

Samples:

Ordering domain with privacy:

https://dmapi.joker.com/request/domain-register?domain=example.com&period=12&owner-c=CCOM-1&billing-c=CCOM-1&admin-c=CCOM-1&tech-c=CCOM-1&ns-list=a.ns.joker.com:b.ns.joker.com&privacy=pro&auth-sid=<your-current-session-id>

 

Renew domain and order privacy:

https://dmapi.joker.com/request/domain-register?domain=example.com&period=12&privacy=basic&auth-sid=<your-current-session-id>

 

Request incoming transfer and enable privacy:

https://dmapi.joker.com/request/domain-transfer-in-reseller?domain=example.com&transfer-auth-id=zigzag&billing-c=CCOM-1&admin-c=CCOM-1&tech-c=CCOM-1&privacy=pro&auth-sid=<your-current-session-id>

 

Temporarily disable privacy (assuming that it is active):

https://dmapi.joker.com/request/domain-set-property?domain=example.com&privacy=off&auth-sid=<your-current-session-id>

 

Fetch real contact data from privacy protected domain:

https://dmapi.joker.com/request/query-whois?domain=example.com&internal=1&auth-sid=<your-current-session-id>

 

NOTE: Not retrieved replies will be kept on the server for a period of 30 days, after this time,  only the status of specific request will be available (success or failure).

IMPORTANT: Please also note that the registration/renewal period is in MONTHS, NOT YEARS

DMAPI

Account and Handling

login

Login with Username & Password

 

Requires (mandatory):

username Joker.com username (email address)
password Joker.com password

Returns:

Auth-SID Authenticated Session ID, must be provided with any other request (parameter auth-sid)
List of TLDs List of domain TLDs which are available to the reseller.

To be able to use the entire API, you must have a reseller account with Joker.com (and use this account to log in).

 Example:

  https://dmapi.joker.com/request/login?username=johndoe&password=mypass

Login with API Keys

Instead of using your user- and password credentials, you may also use so called 'API keys' for login. This way, you can create several DMAPI access facilities, which has several advantages:

Create your API keys in 'My Profile' in section 'Manage Joker.com API access keys'

Example usage:

https://dmapi.joker.com/request/login?api-key=Key_created_in_your_Profile_at_Joker.com

The result is the same as for "login"-request, you have to use the provided auth-sid for the subsequent actions.

logout

Returns: Nothing

Used to forcibly close (terminate) a session. The session identified by Auth-SID may not be used anymore to send requests. Normally not required as session will timeout anyway (default: 1 hour).

result-list

Accepts:

pending     

get results of requests still in progress

showall get all results incl. deletes using result-delete
period

get results for specifed period of days (default: 90)

date get results received on (or before) specified date. When date is specified, parameter "period" will be applied to this date (instead of today) and defaults to 1
offset

start dispalying results from specified position

limit only get number of results specified by limit
status

get results having specified status (ack/nack/?)

count-only  

when set to 1, only count number of records and return single line in format "Records: N"

All following filters may use patterns ("*" and "?")

rtype

get results for requests of specified type (domain-register/etc)
objid

get results for specified object ids (domain names, contacts, hosts)

procid get results for specified proc-id
svtrid get results for specifued SvTrId
cltrid get results for specified ClTrId

 Returns:

List of answers from joker.com (one per line):

TimeStamp SvTrId Proc-ID request-type status ClTrId

Where:

TimeStamp: The time when request was made, YYYYMMDDHHMMSS
SvTrID: Tracking-Id associated with this request.
Proc-ID: Proc-Id associated with this request.
request-type: The type of the request.
request-object: The object name (host, domain or contact handle)
status: ack, nack or ?, where ack means that request was completed successfully.
ClTrId: User specified transaction ID, or "-" if nothing was provided by the user

 Example:

https://dmapi.joker.com/request/result-list?auth-sid=20ddb8c3b2ea758dcf9fa4c7f46c0784

result-retrieve

Accepts:

Proc-ID One of these must be specified. If both are specified, SvTrId has precedence.
SvTrID

Returns:

Answer (processing result) associated with specified Tracking/Processing ID.

If detailed information (content) is not available, only status will be returned

Please note:

Since there is no requirement of uniqueness for user-specified transaction ids, it is not possible to use them to retrieve specific results. 

Example:

  https://dmapi.joker.com/request/result-retrieve?proc-id=8181810&auth-sid=<your-current-session-id>

result-delete 

Accepts:

Proc-ID

One of these must be specified. If both are specified, SvTrId has precedence

SvTrID

Returns:

A descriptive message (confirmation) in case of success.

This request will delete the content (not the status) of a reply to an asynchronous request. Deleted results will not be listed anymore when using result-list.

query-profile 

Returns:

Returns reseller profile data in format "key: value". May be used to query account balance

 Example:

https://dmapi.joker.com/request/query-profile?auth-sid=20ddb8c3b2ea758dcf9fa4c7f46c0784


DMAPI

Domains

query-domain-list

Accepts (optional)

pattern Pattern to match (globbing, like "dom*")

from

Start from this item in list

to

End by this item

showstatus   

Returns additional column, showing domain status; may be 0 or 1

showgrants

Returns additional column, showing domain grants; may be 0 or 1

showprivacy    

Returns additional columns, showing privacy status; may be 0 or 1

The following columns will be added:

privacy-status - shows the currently active privacy status
privacy-origin - shows the privacy status, which was bought
privacy-expiration - shows the expiration date of privacy

Returns

List of registered domains and their expiration dates (one per line, separated by whitespace). If "showstatus" is present, the the list will be with three columns, the last one showing domain status (like "lock,autorenew" etc - comma separated).

Example:

https://dmapi.joker.com/request/query-domain-list?pattern=a*&showstatus=1&auth-sid=<your-current-session-id>

domain-register

Requires (mandatory)

domain     
Domain name to register
period Registration period in months (not in years!)
status Set domain status (only "production" is accepted so far)
owner-c Owner contact handle
billing-c Billing contact handle
admin-c Administrative contact handle
tech-c Technical contact handle
ns-list List of name servers, delimited by colon

Accepts (optional)

autorenew if set to "1", domain will be autorenewed upon expiration
language

3 letter language code for IDN domains

registrar-tag     

Registrar tag, also known as "Membership token", currently only needed for .XXX domains

privacy

basic|pro|none - adds whois privacy subscription to domain order, see also Whois Privacy Services

max-price

maximum price user is willing to pay for a domain registration, renewal or transfer. If provided, it must be a number (fractions allowed) above 0.

If not provided and domain has non-standard pricing, or if max-price is lower than actual domain price at the moment of registration, the request will fail.
If max-price is higher than the actual domain price, then only the actual price will be deducted

 This request allows to register a domain.

You must have registered contacts (handles) to be able to register a domain.(=> contact-create, query-contact-list)

Important: Please note that the registration period is in months, not years. In most cases, this number is a multiple of 12.

Example:

https://dmapi.joker.com/request/domain-register?domain=example.com&period=12&status=production&owner-c=COCO-4711&billing-c=COCO-4712&admin-c=COCO-4712&tech-c=COCO-4712&ns-list=a.ns.joker.com,b.ns.joker.com,c.ns.joker.com&auth-sid=<your-current-session-id>

domain-renew

Requires (mandatory)

domain domain name to renew
period renewal period in months (not in years!)

expyear

the wanted expiration year (e.g. '2014')

Accepts (optional)

privacy          basic|pro|none|keep - adds whois privacy subscription to domain renewal
 

none: explicitly do a renew without privacy services, even if currently privacy is enabled

keep: renew with the same level of privacy service which is currently active for the domain

see also Whois Privacy Services

max-price
 

maximum price user is willing to pay for a domain registration, renewal or transfer. If provided, it must be a number (fractions allowed) above 0.

If not provided and domain has non-standard pricing, or if max-price is lower than actual domain price at the moment of registration, the request will fail.
If max-price is higher than the actual domain price, then only the actual price will be deducted

With this request you can renew the domain. Please be aware that all renewals are not refundable.

"expyear" is a safety option which can be used instead of "period" to renew domain till specified year (not longer). If you use "period", and by mistake send the request more than once, domain will be renewed again, while with "expyear", it will not be renewed if it's expiration year is greater or equals to specified.

Only one of "period" or "expyear" may be used, but not both.

 Please note:

Example:

  https://dmapi.joker.com/request/domain-renew?domain=example.com&period=12&auth-sid=<your-current-session-id

domain-modify

Requires (mandatory)

domain domain name to modify

Accepts (optional)

billing-c domain contact data to modify
admin-c
tech-c
ns-list   list of new nameservers delimited by colon ":" (it will replace existing nameservers!)
registrar-tag 

Registrar tag, also known as "Membership token", currently used for .XXX domains

dnssec

if specified, allows setting or removal of DNSSEC keys for domain. If not specified, DNSSEC records will not be changed. Value of "0" will remove DNSSEC, value of "1" will add DNSSEC (and ds-N parameters must be provided)

 ds-1            list of DNSSEC parameter sets (min. 2, max. 6) for DNSSEC enabled domains
 ds-2            for com/net/org/tv/cc each entry has format:
 ds-3                tag:alg:digest-type:digest
 ds-4            for de:
 ds-5                protocol:alg:flags:pubkey-base64
 ds-6


With this request you can modify

 Please only specify contact handles which you want to modify, all unspecified handles will be left as is.

 For DNSSEC, you will find more information here .

Example:

 Example for adding a key (and enabling DNSSEC):

Example for removing DNSSEC information:

domain-delete

Requires (mandatory)

domain   
domain name to delete

Accepts (optional)

force      
if present and set to '1', 'Y' or 'Yes', the domain will be deleted even if older than 72 hours.


With this request you can delete a domain.

If you delete a domain (gTLDs only) within the first 72 hours after the registration, the registration-fee will be refunded to your account.

To delete a domain which is registered for more than 72 hours, you must specify "force=1", otherwise the request will be rejected.
Please note: The number of refundable deletions of domains per month is limited, and depends on the number of domains in a portfolio, and the related TLD registry.

Example:

domain-owner-change

Requires

domain domain name to change the owner of
name (optional) full name (if empty, fname + lname will be used)
fname first name
lname last name
title (optional)
individual (optional) Y, Yes, N, No
organization   (optional if individual)
email mailaddress of the contact
address-1 street address
address-2 (optional)
address-3 (optional)
city
state (optional)
postal-code
country ISO country code (2 letters)
phone
extension (optional)
fax (optional)
   
lock-opt-out (optional) yes, no  (new IRTP-C: do not apply a 60 days transfer lock to the domain)


With this request you can change the visible WHOIS owner of a domain.

Either "name" or "lname" and "fname" must be provided. Fields not marked as optional are mandatory, and must not be empty.

For the revised ICANN IRTP-C (change of registrar) policy, please also visit our documentation.

Example:

1
https://dmapi.joker.com/request/domain-owner-change?domain=example.com&fname=John&lname=Doe&email=johnd@someisp.com&address-1=Smartroad1&city=Smalltown&postal-code=40122&country=US&phone=+1.422.8001&auth-sid=<your-current-session-id>

domain-lock

Requires (mandatory)

domain domain name to lock


With this request you can lock a domain to prevent from fraudulent transfer attempts.

If a domain is locked, each transfer-request from a foreign registrar will be declined.

 Example:

https://dmapi.joker.com/request/domain-lock?domain=example.com&auth-sid=<your-current-session-id>

domain-unlock

Requires (mandatory)

domain domain name to unlock


With this request you can unlock a domain.

If you want to transfer a domain to a foreign registrar, it has to be unlocked.

 Example:

https://dmapi.joker.com/request/domain-unlock?domain=example.com&auth-sid=<your-current-session-id>

domain-transfer-in-reseller

Requires (mandatory)

domain full qualified domain name to transfer to Joker.com
transfer-auth-id AUTH-ID required for all domains except .eu
owner-c new owner contact handle to be used for transferred domain

 

Accepts (optional)

admin-c

new admin contact handle

tech-c new tech contact handle
billing-c new billing contact handle
status

new domain status to be set after transfer (lock, production)

period

renewal period in months, not in years! [not in use, please leave empty]

autorenew

Autorenew flag for the domain (0 or 1); if not set explicitly, defaults to 1

ns-list 

list of colon-separated nameservers

privacy basic|pro|none - adds whois privacy subscription to domain transfer, see also Whois Privacy Services
max-price

maximum price user is willing to pay for a domain registration, renewal or transfer. If provided, it must be a number (fractions allowed) above 0.

If not provided and domain has non-standard pricing, or if max-price is lower than the actual domain price at the moment of registration, the request will fail.
If max-price is higher than the actual domain price, then only the actual price will be deducted

 

With this request you can initiate a transfer of the domain from another registrar to Joker.com.

You have to provide a valid AUTH-ID (you have to request this from the current provider of the domain). 

Please note:

Example:


domain-set-property

Requires (mandatory)

domain domain name or pattern
pname property name 
pvalue property value (may be empty)

 With this request you can set a property (flag) for a domain or a set of domains, selected by wildcard pattern.

List of available properties and their effects:

autorenew

0 or 1

If set to 1, the domain will be automatically renewed on expiration (if you have enough funds in your account)

whois-opt-out

 0 or 1

currently only used for .tel domains; if set to 1, owner information will not be shown in whois

privacy

off or basic or pro (if available)

If an empty value is provided, then the property will be cleared, i.e. the default will be used.

Example:


domain-get-property


Requires

domain domain name
pname property name (same as in domain-set-property)

With this request you can query the value of a specific property set for a domain. 

It returns a single line, which looks like:

1
autorenew: 0

Example:

domain-transfer-get-auth-id

Requires

domain domain name to get AUTH-ID for

 Retrieves domain's Auth-ID, which is required when transfering domains to another registrar.

This request is not real-time, i.e. you have to check detailed reply (use "result-retrieve") to get the Auth-ID.

 Please note:

Every request will generate a new Auth-ID, thus rendering any previously requested Auth-ID invalid.

 Example:

domain-transfer-control

This request allows to retrieve status information for all pending transfers. Additionally, transfers can be cancelled, or the FOA email can be re-sent. 

Parameters:

        action                  One of: list, show, resend-foa, cancel
        domain                  Domain name to control transfer of (ignored when action=list)
 

action=list

When action=list, this request returns a list (columns are separated by tabs) of all currently pending transfers:

        <domain> <state> <owner-email> <admin-email>

where <state> is one of (listed in "natural" transition order):

                IN_DB
                PAYMENT_PREPARED
                PAYMENT_ACQUIRED

                PENDING_FOA_SENDING

                        Joker.com could not parse the recipient of the FOA.
                        Manual action from Joker.com is required and happens
                        during office hours, thus in worst case it may take
                        few days (during weekend or holidays).

                FOA_BEEN_SENT
                
                        FOA is sent and Joker.com is waiting for owner's
                        reaction. Owner has 5 days to react, thus the state
                        may last up to 5 days.
                        
                FOA_NACK                FOA is rejected
                FOA_ACK                 FOA is accepted

                REGISTRY_REQUEST_SENT

                REGISTRY_REQUEST_RECEIVED_NOW_WAITING
                
                        FOA had been accepted, transfer request is sent
                        and the losing registrar has to release the domain.
                        This state may take up to 5 days, we could do nothing
                        to speed it up.
                        While in this state, transfer may be cancelled
                        by using "action=cancel".

                REGISTRY_CANCELATION_PENDING
                
                        The user has requested cancel of domain transfer
                        by using "action=cancel".

                DOMAIN_WITH_JOKER_PENDING_COMPLETE
                
                        The domain is actually with Joker.com, but either
                        we haven’t noticed yet (batch pending) or manual
                        work is necessary.
                        Please contact Joker.com if this state lasts longer
                        than 1 hour.

                PAYMENT_COMMITTED

                TRANSFER_PROCESSED_SUCCESSFULLY

action=show

When action=show, the status of a specified domain is returned like:

        domain: example.com
        status: FOA_BEEN_SENT
        owner_email: owner@example.com
        admin_email: admin@example.com
        transfer-id: 123456

action=resend-foa

When action=resend-foa, FOA will be resent (only possible in state FOA_BEEN_SENT).

action=cancel

When action=cancel, the (pending) transfer will be cancelled.

Returns

Status code is 1000 for successful request, or >= 2000 otherwise.

Example

https://dmapi.joker.com/request/domain-transfer-control?domain=example.com&action=resend-foa

domain-check

Requires (mandatory)

domain domain name to check

Accepts (optional)

check-price If provided, specifically check the price for: create, renew, transfer, restore
period    

If provided, price will be calculated based on specified period. Period may be specified in years (values from 1 to 10) or in traditional for DMAPI months (>= 12, must be a multiple of 12).

language        

Relevant only for IDN domains, specifies language as 2 letter (ISO 639.1) or 3 letter (ISO 639.2) code:

https://www.loc.gov/standards/iso639-2/php/code_list.php

   

With this request you can check if a domain is available for registration, and what type of domain pricing will be applied for different types of orders.

Returns one or more lines with key-value pairs as follows:

domain-status: <status>

<status> can be one of:

available     regular domain (non-premium) available for registration
premium premium domain available for registration
unavailable     domain is not available for registration


If <status> is "unavailable", then domain-register request will fail, though domain-transfer-* and domain-renew (if domain is with Joker.com) are possible, of course.

domain-status-reason: <status-reason>

Provides human-readable description why domain is unavailable for registration, like blocked, reserved, registered etc.
May be absent if registry does not provide specific reason. Should not be parsed as value is registry dependent and could be virtually anything.

domain-class: <class>

Specifies price-class. Anything but "standard" is considered "premium", though some registries use "tier-1", "premium", "BBB" etc.
Mostly a hint, values except "standard" should not be interpreted as they have no useful meaning and vary among registries.

domain-price-<type>: <price> <currency> <period>y

Reports domain price, where <type> will be value provided in check-price parameter, i.e. create, renew, transfer, restore.

domain-price-promo: <start> <end>

<start> and <end> are ISO timestamps in format like 2019-07-01T00:00:00.000Z

For domains that have promotional pricing, this provides start and end timestamps of promotional period. Usually its mere presence means that promo-pricing is in effect, but to be sure values have to be checked explicitly.
If "domain-status" returned "premium" or "domain-class" returned anything but "standard", then the parameter max-price must be present in register/transfer/renew requests.

Full response example (web.blog):

    domain-status: unavailable 
    domain-status-reason: blocked
    domain-class: standard
    domain-price-create: 8.21 USD 1y
    domain-price-promo: 2019-09-01T00:00:00.000Z 2019-12-31T23:59:59.000Z

Example:

https://dmapi.joker.com/request/domain-check?domain=example.com&auth-sid=<your-current-session-id>

DMAPI

Contacts

query-contact-list

Accepts:

pattern pattern to match (against handle)
from start from this item in list
to end by this item in list
tld limits output to contact handles which may be used with specified toplevel domain (tld), like "com".
extended-format provides additional information for every contact listed: name & organization. May be "1" or "0", defaults to "0"

Returns:

List of registered contacts (handles), one per line.

When "extended-format" is requested, output columns are separated by tabs ("\t"), and "Columns" header provides column names.

 Example:

https://dmapi.joker.com/request/query-contact-list?pattern=coco-47*&tld=com&auth-sid=<your-current-session-id>

contact-create

Requires:

tld target TLD where this contact is intended to be used.
name full name (if empty, fname + lname will be used)
fname first name (required for .FI contacts)
lname last name (required for .FI contacts)
title (optional)
individual (optional) Y, Yes, N, No
organization (optional if individual)
email mailaddress of the contact
address-1 street address
address-2 (optional)
city
state (optional)
postal-code
country ISO country code (2 letters)
phone
fax (optional)
lang language to use for .EU contacts

app-purpose

required for .US contacts

nexus-category

required for .US contacts
nexus-category-country required for .US contacts
account-type required for .UK contacts, if used as owner contact
company-number

required for .UK contacts with specific account types

orgid

required for .SE/.NU contacts

vatid

(optional) for .SE/.NU contacts

x-ficora-type

required for .FI contacts

x-ficora-is-finnish (yes/no) required for .FI contacts
x-ficora-registernumber  required for .FI contacts, if ficora-type is company
x-ficora-identity required for .FI contacts, if type is person and finnish
x-ficora-birthdate required for .FI contacts, if type is persion and not finnish
x-ficora-legalemail (optional) for .FI contacts

Either "name" or "lname" and "fname" must be provided. 

Fields not marked '(optional)' are mandatory (and must not be empty).

Parameters "lname" and "fname", if provided, will be converted to "name" (simple concatenation of "fname" and "lname"), because registries support only "name" format. In general, use of "fname" and "lname" is deprecated, and support for these fields will be removed in version 1.2.

"orgid" represents Swedish personal or organisational number and is required for .SE/.NU contacts.

It starts with ISO 3166 Alpha-2 country code in square brackets. If the country code for Sweden is given [SE] a valid Swedish personal or organisational number must be given (6 digits, dash, 4 digits), otherwise 1 to 123 characters can follow.

If organization is empty and the country code for Sweden [SE] is given, orgid must be a personal number, not an organisational number.

"vatid" is optional for .SE/.NU contacts. It starts with a two letter country code (uppercase), followed by an optional space, followed by a country specific string containing digits 0-9, and letters a-z and A-Z, maximum 64 Chars.

For .fi contacts:

"x-ficora-type" is required for .fi contacts. The following values are accepted: privateperson, company, corporation, institution, politicalparty, township, government, publiccommunity

"x-ficora-registernumber" is required if x-ficora-type is set to "company".

"x-ficora-is-finnish" is always required for .fi contacts: yes = finnish company or person, no = not a finnish person or company

"x-ficora-identity" is required for .fi contacts, if x-ficora-type is set to 'privateperson' and x-ficora-is-finnish is set to 'yes'

"x-ficora-birthdate" is required for .fi contacts, if x-ficora-type is set to 'privateperson' and x-ficora-is-finnish is set to 'no' in the following date format "YYYY-MM-DD".

Please note:

 Example:

https://dmapi.joker.com/request/contact-create?tld=com&name=John Doe&email=johnd@someisp.com&address-1=Smartroad 1&city=Smalltown&postal-code=40122&country=US&phone=+1.422.8001&auth-sid=<your-current-session-id

contact-modify

Requires:

handle contact handle to modify.

Accepts:

Field names exactly like in contact-create request, except that omitted fields won't be modified. That is, if you specify a field, it will be used as a new value, if you omit it, the old value will remain.

The field "tld" is not relevant for this request and will be ignored if present.

contact-delete

Requires:

handle contact handle to delete

With this request you can delete previously registered contacts 

Example:

https://dmapi.joker.com/request/contact-delete?handle=coco-4711&auth-sid=<your-current-session-id>

DMAPI

Nameservers

query-ns-list

Accepts:

pattern pattern to match (against host name, like "ns.dom*")

full

include IPs if non-zero (0 or 1)

 Returns:

List of registered name servers, one per line.

If "full" is non-zero, then the list will include IP addresses, IPv4 (2nd column) and IPv6 (3rd column).

Columns will be separated by tab ("\t") character. If specific IP is not present (say, there is only IPv4 or IPv6), it will be listed as "-".

 Example of list with IPs:

1
2
ns.example.com 1.2.3.4 -
ns6.example.com - FE80:0000:0000:0000:0202:B3FF:FE1E:8329

Example:

  https://dmapi.joker.com/request/query-ns-list?pattern=*my-own-ns*&full=1&auth-sid=<your-current-session-id>

ns-create

Requires:

host Full qualified host name
ip IPv4 address (must not be from IANA's reserved range)
ipv6 IPv6 address (short notation like fec0::17 is accepted)


With this request a new nameserver can be registered with the registry. This is needed to use a nameserver with glue records.

Either an IPv4 or IPv6 address is required.

ns-modify or host-modify

Requires:

host full qualified host name
ip IPv4 address (must not be from IANA's reserved range)
ipv6 IPv6 address (short notation like 'fec0::17' is accepted)

With this request you can modify the IP address of a registered nameserver. 

ns-delete or host-delete

Requires:

host Full qualified host name

With this request you can delete a registered nameserver.

DMAPI

Modify Zonedata

dns-zone-list

Accepts:

pattern Pattern to match (globbing, like "dom*")

Returns:

List zones (domains) which are managed and served by Joker.com name
servers. Zones are listed one per line.

dns-zone-get

Requires:

domain Zone (domain) name to fetch data from

Returns:

Returns list of zone records.

The format of zone is as follows (one record per line):

<label> <type> <pri> <target> <ttl> <valid-from> <valid-to> <parameters(s)> 

Where:

label

subdomain/redirection label, relative to current zone, or '@' (which means current zone name)

type

record type (A, AAAA, MX, CNAME, URL, MAILFW, TXT, NAPTR, DYNA, DYNAAAA, SRV, CAA)

pri

numeric value, meaningful only for types MX, NAPTR and SRV, must be 0 for all other types

target

record target/value. Must be quoted if contains spaces

ttl

record TTL (time to live) in seconds

valid-from

record is not valid before this time (UNIX timestamp) or 0

valid-to

record is not valid after this time (UNIX timestamp) or 0

parameters 

record-specific parameter(s)

All values from "name" to "ttl" are mandatory for every record.

<valid-to> and <valid-from> are not implemented yet, so usually are 0, and may be omitted if there are no other parameters required.

<parameters(s)> are record dependent, used in NAPTR, MAILFW, FRAME and URL records.

<ttl> must be at least 60 for all records except NAPTR and SVC, where it can be 0 (meaning: no caching). For MAILFW/URL/FRAME <ttl> is irrelevant and assumed to be 60 seconds (i.e., any change will be
in effect within 60 seconds from zone change).

<pri> preference value for MX records, priority/weight for SRV records and order/preference for NAPTR records. For any other record, the value must be 0.

Examples of zone records:

 www A 0 127.0.0.1 86400
www AAAA 0 fec0::17 86400

@ MX 10 mail.example.com. 86400

redirect URL 0 http://joker.com 86400

Sets redirection from redirect.joker.com to http://joker.com (assuming that current zone is "joker.com").

frame FRAME 0 http://joker.com 86400 0 0 "Header: Frame-Forward" "head" "title" "body"

Sets frame-based redirection similar to URL redirection.

For FRAME record, extra parameters are as follows:


username MAILFW 0 redirected@example.com 86400 0 0 1

This MAILFW records makes redirection of mail sent to username@joker.com (assuming that current zone name is "joker.com") to redirected@example.com, extra parameter ("1") specifies that spam-filtering should be used.

naptr NAPTR 10/100 replacement 86400 0 0 "flags" "service" "regex"

This NAPTR record has order 10 and preference 100. Only one of "replacement" or "regex" may be
specified, if "regex" is specified, "replacement" must be "." (without quotes), if "replacement"
is specified, "regex" must be empty string. Quotes are mandatory for all extra parameters.
For details please consult RFC 2915, or look here: http://de.wikipedia.org/wiki/NAPTR

_ldap._tcp SRV 10/100 ldap.example.com:389 60

This SRV record has priority 10, weight 100, target "ldap.example.com" and port "389" with TTL 60 seconds. Please consult RFC 2782 for details.

txt TXT 0 "key=value" 86400

Quoting of values for TXT records is mandatory.

caa   CAA 0   issue "letsencrypt.org" 86400
caa   CAA 0   issuewild "letsencrypt.org" 86400

caa   CAA 0   iodef "mailto:certissues@example.com" 86400

For more information about CAA records please check Wikipedia. 

www CNAME 0 example.com. 86400

Two special record types, DYNA and DYNAAAA, are used in case if DynDNS is active.
They have same meaning as corresponding "A" and "AAAA" records, except that their targets may be updated using Joker DynDNS service.

To enable/disable DynDNS service, and to define username/password used to access it, the record format is as follows:

$dyndns=yes:username:password

username/password may not contain spaces or colon (":") characters. If "no" is specified instead of "yes", DynDNS will be turned off (i.e. DYN* entries will have no effect).

In case if there are any errors, zone modification will not be accepted. All errors will be reported for every erroneous line, so if there are more than one, you will be able to see all detected errors.

dns-zone-put

Requires:

domain

Zone (domain) name to store data to

zone

URL encoded zone data

Returns:

Replace current zone for provided domain with specified value.

Field "zone" will be parsed as multiline text (so usual line erminators are expected).

Warning: This request will overwrite current zone, i.e. all current ecords will be replaced by new records.

The format of zone is as follows (one record per line):

<label> <type> <pri> <target> <ttl> <valid-from> <valid-to> <parameters(s)>

DMAPI

Rights and Roles

grants-list

Requires:

domain

Full qualified domain name

Accepts:

showkey Show invitation access key

Get a list of active and pending grants. 

Returns lines in the following format (space-separated):

invitation <nr> <scope> <key> domain <domain-name> <role> - - - <invitee-email> <nick-name> grant <nr> <scope> domain <domain-name> <role> <inviter-username> <invitee-username> <invitee-userid> <invitee-email> <nick-name> 

 Where:

<nr> record number
<scope>    Grant/Invite id (used to uniquely identify records for revocation)
<key> Invitation access key, present only when "showkey" is non-zero; it has meaning only for pending invitations, and always is "-" for grants
<domain-name> domain name (identical to domain in request)
<role> one of @admin/@billing/@tech/@creator
<inviter-username> your username (owner of the domain)
<invitee-username> username of invited user
<invitee-userid>
[leave empty] user-ID of invited user  
<nick-name> name or comment you want to assign to this role

grants-invite

Request parameters:

name value

mandatory

domain Full qualified domain name

 yes

email

Email of user to be invited to accept a role for 'domain'

 yes

role

Role offered (@admin/@billing/@tech/@creator)

 yes

client-uid     

receiving Joker.com user id as shown on Joker.com - also conforms to reseller-id

 no

nick-name

Name or comment for this role/grant for later identification (defaults to email)

 no

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's portfolio, including all rights and permissions on this domain.

There are two variants to use this functionality: If the client-uid (Joker.com user account id) is given, and the client-uid matches the associated user's email address in our system, the role is applied immediately - there will be no request for confirmation on the receiver's side. In case the client-uid is not given, but only the email address, the transaction has to be acknowledged by the receiving user. For this, he will get an email ('invitation'), 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.

Returns status only (ok or not). Email is sent if request was succesfull.

grants-revoke

Requires:

domain full qualified domain name

role

Role to be revoked from domain (@admin/@billing/@tech/@creator)

scope

identifier from 'grants-list' request

type

type of the record to revoke - "grant" or "invitation"

Deletes an issued grant (permission) of a domain, or a pending invitation for a grant. 

Returns status only (ok or not). Email is sent if request was succesfull.

DMAPI

Other Requests

query-object

Accepts:

domain  
Domain name      
Exactly one of those must be specified. Only objects registered with Joker.com may be queried.
contact Contact handle
host Nameserver

Returns:

Information about specified object (similar to whois), in format "key: value".

This request is deprecated - please use ' query-whois' instead.

query-whois

Accepts:

domain  
Domain name Exactly one of those must be specified. Only objects registered with Joker.com may be queried.
contact Contact handle
host Nameserver

Returns:

Information about specified object (similar to whois), in the format "key: value".

The difference to the query-object request is, that this request reflects actual (live) data in Joker.com database, while query-object may show data which not yet up-to-date.

wa-email-list

Lists all domains and owner emails of domains from your portfolio which are pending whois (email) verification.

For Whois validation, the email address of the owner contact of a newly created, transfered or modifed gTLD has to be verified.This verification is done by sending an email to the owner contact, which contains a unique key in a link. When this link is clicked, the related email address is set to "validated".

 For full ICANN policy, please see Whois-Validation.

Requires: Nothing

Returns:

email-address<TAB>domain-name<TAB>verification-expiration-date

  email-address<TAB>domain-name<TAB>verification-expiration-date

 

 Where:

email-address 
email address of the domain owner which is pending verification
domain-name domain name where email is the owner
verification-expiration-date
verification deadline, i.e. if by this date and time (specified in standard ISO format) email is not positively verified, the domain name listed may be deactivated
Example:
  https://dmapi.joker.com/request/wa-email-list?auth-sid=<your-current-session-id>

wa-email-details

Returns email verification status and the associated domain for provided verification key (whois verification, email validation).If there is more than one domain using the email address to be verified, output will have one line per domain. 

For full ICANN policy, please see Whois-Validation. 

Requires:

key Verification key sent to owner by verification email


Returns:

status<TAB>email<TAB>domain

Where: 

status 
is 'verification', if 'key' is a valid verification key
email email address 'key' has been sent to
domain related domain

Sample:

https://dmapi.joker.com/request/wa-email-details?key=<key-to-query>&auth-sid=<your-current-session-id>

wa-email-validate

Triggers a new email verification. In case the original verification email got lost or did not succeed otherwise, this request will send a new email. The original key will be automatically included.

This request returns special response header "Result", which will contain "ACK" if the validation request has been sent successfully, or "NACK" otherwise, e.g. if the email address is not in "verification pending" status, or already verified (whois verification, email validation).

 For full ICANN policy, please see Whois-Validation.

Requires:

email   Email address to send validation request to. This must be domain owner's email address.

 Returns:

Result: ACK    validation request has been sent
Result: NACK   no validation request has been sent for this email

 Sample:

https://dmapi.joker.com/request/wa-email-validate?email=<email-of-owner>&auth-sid=<your-current-session-id>

wa-email-verify

Set an email address to 'validated' by using the correct key, and voting with 'yes'.

This request returns a special response header "Result", which will contain "ACK" if the verification has been accepted or "NACK" otherwise, e.g. in case the key is not correct (whois verification, email validation).

This is usefull e.g. in case you want to implement your own indivídual landing page for your customers. The URL for this landing page can be set in Joker.com's 'Reseller Settings'.

For full ICANN policy, please see Whois-Validation.

 Requires:

key      Verification key sent to owner by verification email
answer Answer to verification request - "yes" or "no"

If the answer is "yes", the verification status is set to "verified" and email is confirmed as valid, if the answer is "no", then verification status is set to "invalid". If there is no answer before verification deadline (normally 15 days), the status is also set to "invalid".

Returns

Result: ACK    validation request has been successful
Result: NACK   validation request has been rejected or failed
Sample:
  https://dmapi.joker.com/request/wa-email-verify?key=<key-to-use>&answer=[yes|no]&auth-sid=<your-current-session-id>

domain-privacy-order

This request adds a subscription to Whois Privacy Services to an existing domain name.

A summary of all privacy related DMAPI commands is also available at DMAPI Whois Privacy Services.

 Requires (mandatory):

domain domain name to order privacy service for

privacy

basic|pro

Accepts (optional):

period renewal period in months (not in years!)

expyear

the wanted expiration year (e.g. '2016')

"expyear" is a safety option which can be used instead of "period" to order privacy until the specified year (not longer).

If you use "period", and by mistake send the request more than once, the order would be executed again, while with "expyear", it will not be renewed if it's expiration year is greater or equals to the specified one.

Only one of "period" or "expyear" may be used, but not both.

 If neither period nor expyear is provided, then privacy is ordered for the remaining domain lifetime, whatever it is.

 Important: Please note that registration period is in months, not years! In most cases, this number is a multiple of 12.

 Example:

  https://dmapi.joker.com/request/domain-privacy-order?domain=example.com&privacy=pro&auth-sid=<your-current-session-id

This would order privacy service "pro" for the same period as the current term of the domain "example.com".

cor-verify

Authorizes a 'Change of Registrant' (COR) according to the ICANN IRTP-C policy as of 2016-12-01.

Please find the full documentation of the process at Joker.com here, the original ICANN policy is available here.

 This request can be used if you did not setup a verification 'push' URL with our provided module (see link above), or you want to use the standard email procedure.

 This request returns special response header "Result", which will contain "ACK" if the authorization request has been sent successfully, or "NACK" otherwise, e.g. if the key sent does not match the transaction.

 Requires:

key     authorization key (provided in COR confirmation request)
answer answer to confirm the COR - "yes" or "no"

If the answer is "yes", the change-of-registrant will be executed, if in case of "no", it will be rejected. Please also note the new flag 'lock-opt-out' in 'domain-owner-change' if you do not want to lock the domain after the COR for 60 days.
Returns:

Result: ACK    authorization key has been accepted
Result: NACK   authorization key has not been accepted

 Sample:

https://dmapi.joker.com/request/cor-verify?key=<authorization key sent by Joker.com>&answer=yes&auth-sid=<your-current-session-id>

query-price-list

Returns

List of domain prices per action and year (separated by tab) in the currency of the reseller account. The prices already include the reseller discount and also vat if it applies.

 Example:

https://dmapi.joker.com/request/query-price-list?auth-sid=<your-current-session-id>

DMAPI

Code-Examples

Perl

List domains of customer

#!/usr/bin/perl
use LWP::UserAgent;
use Data::Dumper;

my $dmapiURL = "https://dmapi.joker.com/request";

my $ua = LWP::UserAgent-> new;

my $req = HTTP::Request-> new(GET => $dmapiURL.'/login?username='.shift().'&password='.shift());
my $res = $ua-> request($req);

unless ($res-> is_success) {
print "Failed: ", $res-> status_line, "n";
exit -1;
}

my $auth=$res-> as_string;
my $output;

if ($auth =~ /Auth-Sid:s*(w+)/ms) {
$req=HTTP::Request-> new(GET => $dmapiURL.'/query-domain-list?auth-sid='.$1);
$res = $ua-> request($req);
if ($res-> is_success) {
$output=$res-> content;
}

else{
print "Failed: ", $res-> status_line, "n";
exit -2;
}
}

else {
print "Failed: Got no auth-id from DMAPI:n";
print $res-> content;
exit -3;
}


my @lines=split ("n",$output);
my $month=now + ("2M");
my %list;

my $p=0;
for my $line(@lines) {
#Skip first line
next unless $p or $line =~ /^s*$/;
unless ($p) { $p=1; next};
my ($fqdn,$exp)=split ("[ t]+",$line);
$list{$fqdn}=$exp;
}

for (sort keys %list) {
print "$_n";
}

List domains to expire next month

Needs:

Class::Date and Date::Parse from CPAN!

#!/usr/bin/perl

use LWP::UserAgent;
use Data::Dumper;
use Class::Date qw(:errors date localdate gmdate now -DateParse);

my $dmapiURL = "https://dmapi.joker.com/request";

my $ua = LWP::UserAgent-> new;
my $req = HTTP::Request-> new(GET => $dmapiURL. '/login?username='.shift().'&password='.shift());
my $res = $ua-> request($req);

unless ($res-> is_success) {
print "Failed: ", $res-> status_line, "n";
exit -1;
}

my $auth=$res-> as_string;
my $output;

if ($auth =~ /Auth-Sid:s*(w+)/ms) {
$req=HTTP::Request-> new(GET => $dmapiURL. '/query-domain-list?auth-sid='.$1);
$res = $ua-> request($req);

if ($res-> is_success) {
$output=$res-> content;
}
else {
print "Failed: ", $res-> status_line, "n";
exit -2;
}
}
else {
print "Failed: Got no auth-id from DMAPI:n";
print $res-> content;
exit -3;
}


my @lines=split ("n",$output);
my $month=now + ("2M");
my %list;

my $p=0;
for my $line(@lines) {
#Skip first line
next unless $p or $line =~ /^s*$/;
unless ($p) { $p=1; next};
my ($fqdn,$exp)=split ("[ t]+",$line);
next unless localdate($exp) < $month;
$list{$fqdn}=$exp;
}

for ( map {$_-> [0]}
sort {
$a-> [1] < => $b-> [1]
||
$a-> [2] cmp $b-> [2]
}
map {[$_, localdate $list{$_},$_]}
keys %list ) {
print "$_:".$list{$_}."n";
} 

Replace admin-c in multiple domains

#
# replace admin-c in multiple domains
#
#!/usr/bin/perl
use LWP::UserAgent;
use Data::Dumper;
my $ua = LWP::UserAgent->new;
my $req = HTTP::Request->new(GET => 'https://dmapi.joker.com/request/login?username='.shift().'&password='.shift());
my $res = $ua->request($req);
#--Admin-C :
my %ADMIN = ( de =>'CODE-12345' , org => 'CORG-12345', com => 'CCOM-12345', 'eu' => 'c12345' );
unless ($res->is_success) {
  print "Failed: ", $res->status_line, "\n";
  exit -1;
}
my $auth=$res->as_string;
my $output;
if ($auth =~ /Auth-Sid:\s*([a-z0-9]+)/m ) {
$auth = $1;
} else {
  print "Failed: Got no auth-id from DMAPI:\n";
  print $res->content;
  exit -3;
}
while ( <DATA> ) {
  chomp;
  my $fqdn = $_;
  ## for 3rd level domains this must be changed!
  my ( $sld, $tld ) = split ( /\./ , $fqdn );
  my $admin = $ADMIN{ $tld };
$req=HTTP::Request->new(GET => 'https://dmapi.joker.com/request/domain-modify?domain='.$fqdn.'&admin-c='.$admin.'&auth-sid='.$auth);
$res = $ua->request($req);
  if ($res->is_success) {
$output=$res->content;
     print $output;
  } else {
     print "Failed: ", $res->status_line, "\n";
     exit -2;
  }
}
__DATA__
domain1.de
domain2.eu
domain3.org
domain4.com
__END__

PHP

Introduction

Please note that there is full DMAPI based interface written in PHP available. It is free to download and modify, and could be downloaded from Sourceforge.
Please read more at section Joker PHP client.
The published examples in PHP are parts of this project and are stripped in terms of functionality and error handling. It is strongly recommended to use the complete code base from Sourceforge.

List domains of a customer


<?php
 
//sends HTTP request using CURL
 
function query_host($conn_server, $params = "", $get_header = false)
{
 
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $conn_server.$params);
    if (preg_match("/^https:\/\//i", $conn_server)) {
        curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0);
        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
    }
 
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
 
    if ($get_header) {
        curl_setopt($ch, CURLOPT_HEADER, 1);
    }
 
    else {
        curl_setopt($ch, CURLOPT_HEADER, 0);
    }
 
    $result = curl_exec($ch);
 
    if (curl_errno($ch)) {
        print "curl error";
    }
 
    else {
        curl_close($ch);
    }
 
    return $result;
}
 
//builds query, sends request and gets the answer back
 
function execute_request($request, $params, &$sessid)
{
    //build the query
    $http_query = "/request/" . $request . "?" . $params   ."&auth-sid=".$sessid."&client-ip=".$_SERVER["REMOTE_ADDR"];
    //send the request
    $raw_res = query_host("https://dmapi.joker.com", $http_query, true);
    $temp_arr = @explode("\r\n\r\n", $raw_res, 2);
    //split the response for further processing
    if (is_array($temp_arr) && 2 == count($temp_arr)) {
        return $temp_arr[1];
    }
 
    else {
        return false;
    }
}
 
//basic parsing of the DMAPI header
 
function parse_response_header($header)
{
    $raw_arr = explode("\n", trim($header));
    $result = array();
    if (is_array($raw_arr)) {
        foreach ($raw_arr as $key => $value)
        {
            $keyval = array();
            if (preg_match("/^([^\s]+):\s+(.+)\s*$/", $value, $keyval)) {
                $arr[strtolower($keyval[1])] = $keyval[2];
            }
 
            else {
                print "Header line not parseable - pattern does not match\nRaw header:\n$value";
            }
        }
    }
 
    else {
        $arr = "";
        print "Unidentified error\nRaw header:\n$header";
    }
 
    return $arr;
}
 
//parses the reply from DMAPI into a header and body
function parse_response($res)
{
    $raw_arr = explode("\n\n", trim($res));
    $arr_elements = count($raw_arr);
    if ($arr_elements > 0) {
        $temp["response_header"] = parse_response_header($raw_arr["0"]);
        $temp["response_body"] = $raw_arr["1"];
    }
 
    else {
        print "Couldn't split the response into response header and response body\nRaw result:\n$res";
        $temp = "";
    }
 
return $temp;
}
 
$response = "";
$authid = "none";
//first obtaining an Auth-ID
$username = "<your username here>";
$password = "<your password here>";
$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

#!/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

#!/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:

C#/.NEt DMAPI Example

Email Gateway

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:

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 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.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.

 

Email Gateway

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
 

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 .us-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.

.de 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 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
 

 

An existing contact (@cncont or @same-as) (.cn only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:COCN-176269
admin-contact-handle:COCN-176229
tech-contact-handle:COCN-176269
billing-contact-handle:COCN-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 .cn-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.

.eu 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>, e.g. C176269.

 

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:C176269
admin-contact-handle:C176229
tech-contact-handle:C176269
billing-contact-handle:C176269

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 .eu-requests the contact handles for (.com/.net/.org/.info/.biz/.de/.us)-contacts are not allowed. If you are referencing to a shortcut like hans@nose.net#1, you will get an error.

.me 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 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

Email Gateway

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

All joker-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

Email Gateway

Domains

Create an order

Introduction

create <tld>-order

Valid values for <tld>: 

 

With this request you can register one or more domains.

You have to provide the following information within the request:


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:

ATTENTION

Please, refer to the table for the corresponding contact handles.

TLD Contact handle
com
CCOM-<number>
net CNET-<number>
org CORG-<number>
info C<number>-LRMS
biz CNEU-<number>
mobi COMO-<number>
name CNAM-<number>
us COUS-<number>
de CODE-<number>
cn COCN-<number>
eu C<number>
me COME-<number>
asia COAS-<number>
xxx CONX-<number>


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 owner-contact-handle admin-contact-handle
tech-contact-handle billing-contact-handle
com @comcont
net @netcont
org @orgcont
info @infocont
biz @decont
mobi @mobicont
name @namecont
us @uscont
de @bizcont
cn @cncont
eu @eucont
me
 @mecont
asia  @asiacon
required yes



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

renew <tld>-domain

Valid values for <tld>:

With this request you can renew up to 500 domains at Joker.com.

You have to provide the following information within the request:

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

renew <tld>-domain

Valid values for <tld>:

With this request you can renew up to 500 domains at Joker.com.

You have to provide the following information within the request:

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>:

With this request you can transfer a domain from 1 registrar to Joker.com.

You have to provide the following information within the request:


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

tld billing-contact-handle
com @comcont
net @netcont
org @orgcont
info @infocont
biz @bizcont
mobi @mobicont
name @namecont
us @uscont
de @decont
cn @cncont
eu @eucont


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:


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:

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:

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:

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:

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 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:

The following parameters are optional:

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


Email Gateway

Contacts

Create a contact

Introduction

create <tld>-order

Valid values for <tld>:


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:

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.



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)

TLD handle
com
CCOM-<number>
net CNET-<number>
org CORG-<number>
info C<number>-LRMS
biz CNEU-<number>
mobi COMO-<number>
name CNAM-<number>
us COUS-<number>
de CODE-<number>
cn COCN-<number>
eu C<number>


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>:


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:


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

An existing contact (@asiacont or @same-as) (.asia only)

This means an existing contact handle in the JOKER-DATABASE.

Examples:

owner-contact-handle:COAS-176269
admin-contact-handle:COAA-176229
tech-contact-handle:COAS-176269
billing-contact-handle:COAS-176269

ASIA-domains require an additional type of contact, the CED contact. This contact has to have its residence in the Asian/Australian area.
The Joker.com Registry Gateways automatically will use your provided tech-contact for the CED contact. 
This means that the request for you remains consistent with the usual requests, you only have to make sure that the country code is correct, otherwise the .asia registry will reject the order. 

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 .asia-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.

Email Gateway

Nameservers

Create a nameserver

Introduction

create <tld>-ns

Valid values for <tld>:

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>:



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

Email Gateway

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-----
Email Gateway

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

Plugins

Joker.com WHMCS Plugin

WHMCS Registrar Module

Joker.com maintains a registrar module for WHMCS, which offers a great load of  features to interface Joker.com seamlessly from within WHMCS:

The following registrar core functionality is provided:

Additionally, also these features are provided:

Installation:

Please extract the contents of the below attached ZIP archive 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: reseller-support@joker.com
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.4

 

New in version 1.3.3

 

New in version 1.3.2

 

New in version 1.3.1

 

New in version 1.3.0

 

New in version 1.2.5

 

New in version 1.2.4

 

New in version 1.2.3

 

New in version 1.2.2

 

New in version 1.2.1

 

New in version 1.2.0

 

New in version 1.1.5

  

New in version 1.1.4

 

New in version 1.1.3

 

New in version 1.1.2

 

New in version 1.1.1

 

New in version 1.1.0

 

New in version 1.0.4:

This version has been tested with WHMCS 6.x, WHMCS 7.10.2 and WHMCS 8.1.3

Simple WHMCS Plugin

This is a very light weight and simple plugin, therefore very easy to install (you will find instructions in the readme of the zip archive below).

However, features are basic, and you have to configure a fixed set of contact handles for each TLD you want to use.

Any TLD of Joker.com should work.

This plugin is provided as an example to show, how easy it is to connect Joker.com to WHMCS using DMAPI. You may also use it as a starting point for your own experiments.

For a full integration of Joker.com into WHMCS, please use our official fully-featured Joker.com WHMCS Registrar Module.

Plugins

Clientexec Registrar Plugin

Clientexec is a popular web hosting and automation solution, which includes billing and support options.2020-02-20 14_23_21-Clientexec - Manage Your Hosting Business.png

If you are using Clientexec for your hosting activities, you may interface Joker.com  with Clientexec domain functionality to easily order and manage domains from within Clientexec. 1)

Joker.com maintains a registrar module for Clientexec, which offers a great load of  features to interface Joker.com seamlessly from within Clientexec:

The following registrar core functionality is provided:- domain availability check

Installation:

The installation is easy, the plugin is already included with each copy of Clientexec, just activate the "Joker.com plugin" from within Clientexec:

Settings => Plugins => Registrars: Select "Joker.com" from the list, and enter your Joker.com API key.

Usage:

Create customers, and register domains with "Packages => Order Domain Services"...

Known Issues:

*) this is a limitation of Clientexec


Please send us your feedback: reseller-support@joker.com
Enjoy!

1) the Clientexec plugin is provided "as-is" without any further obligation or promise of quality or reliability. The normal Joker.com Terms & Conditions apply. 

Version History

Plugins

Hostbill Registrar Plugin

Hostbill is a popular web hosting and automation solution, which includes:

If you are using Hostbill for your hosting activities, you can integrate Joker.com  for the domain management  within Hostbill using the Joker.com plugin. 1)

At Hostbill's Joker.com-plugin page you find an overview of what is provided by our module:

Installation:

The installation is easy, the plugin is already included with Hostbill, just activate the "Joker.com plugin" from within Hostbill:

Select Settings -> Modules -> Domain Modules, choose Joker.com from the list and "activate".

Usage:

Please find an easy step-by-step documentation at Hostbill's Joker.com plugin wiki.

Please send us your feedback: reseller-support@joker.com
Enjoy!

1) the Hostbill plugin is provided without any further obligation or promise of quality or reliability. The normal Joker.com restriction conditions apply.

Tools

Tools

Check Domain Availability

General Information


This is an additional tool which makes it easy to check if a domain is available for registration. All you have to do is to connect to:

Host: whois.joker.com
Port: 4343

 and issue the command 

domain:[sld.tld] [lang=IDN-tag]

Technical Issues

Examples

using telnet: 

telnet whois.joker.com 4343
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]