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