RegTimeSRS reference

Russian version

(c) RegTime.Net Ltd, 2002-2007


Table of Contents

  1. Introduction
  2. HTTPS-Post Gateway Systems
  3. Submitting HTTPS-Post Requests
  4. Registration and Transfer Operations
  5. Maintenance Operations
  6. Examples

1. Introduction

This reference describes HTTPS-Post Interface to RegTime Shared Registry System (RegTimeSRS), version 0.8.0. The HTTPS-Post gateway is an automated one-step real-time method of sending data to the RegTime Shared Registry System.

In order to offer a one-step process for each operation, all information must be presented to the gateway in a single HTTPS-Post request. The gateway has no notion of state and every request to the URL is expected to be independent of other requests. The HTTPS-Post interface supports operations such as domain name Registration, Redelegation, Check availability of a domain name, Modifying contact details, Transfers. Registrar / Management rights of a domain name and so on. The operations described later in this document.

2. HTTPS-Post Gateway Systems

RegTime.Net offers two HTTPS-Post Gateways that enable Post requests to be processed; these are a Test system and a Live System.

2.1 Live System

To use the live system, HTTPS-Post operations must target the URL

https://www.webnames.ru:81/RegTimeSRS.pl

Typical response times under normal load conditions should be in the order of five to ten seconds. Since the gateway is multi-threaded, requests for multiple names can be made concurrently, however, no more than five connections should be open concurrently, without prior consultation with Regtime.Net.

Warning:
Do not set up a web form for your customers that contain your login details, i.e. your user name and password, as end users can read them. To be secure, the login details must be appended with a server side process.
All posts must adhere to the HTTP/1.0 specifications (HTTP/1.1 is not recommended), as defined in RFC 1945 at the URL:
http://www.ics.uci.edu/pub/ietf/http/rfc1945.html

2.2 Test System

RegTime.Net offers a gateway that interfaces with our test registration system. The test system is identical to the live system with the following exceptions:

To use the test system, HTTPS-Post operations must target the same URL as live system. To access the test system use these login details:

username is test
password is test

2.3 Gateway usage limitations

There are some limitations that should be take into account while communicating with RegTimeSRS gateway.

  1. Request count via gateway should not exceed 60 queries for the period 30 minutes.
  2. Parallel (simultaneous) requests from the same user are disabled.
  3. In case of excessive overload of Registrar servers because of actions of client — client account will be closed. In case of any loss or damages of equipment or software caused by excessive overload of Registrar servers, Registrar should proceed with legal prosecution of person responsible for excessive overload of equipment.


3. Submitting HTTPS-Post Requests

3.1 HTTPS-Post Operations

The HTTPS-Post system allows many operations to be performed. The following tables detail the operations that can be performed using the HTTPS-Post Gateway. Each operation has different field requirements; these have been detailed further on in this document.

Operation (thisPage Value) Explanation Imple-
mented
Registration and Transfer Operations (Further explained in section 4)
pispRegistration Submit domain registration request Yes
pispInitiateTransfer Submit domain transfer request Yes

Maintenance Operations (Further explained in section 5)
pispCheckDomain Check the availability of a domain name. Yes
pispWhois Get WHOIS information for a domain name. Yes
pispRenewDomain Renew an existing domain Yes
pispRedelegation Redelegate an existing domain Yes
pispContactDetails Update contact details for an existing domain Yes
pispCancelDomain Cancel a domain name. No
pispChangeOwnership Change ownership of domain name No
pispregistryKey Obtain registry key for a domain name. No
pispGetDelegation Obtain names of name servers hosting a domain name. No
pispAddNameServer Add a name server (.com, .net, .org) No
pispDeleteNameServer Delete a name server (.com, .net, .org) No
pispCreateNameServer Used to register name servers that are not in the .com, .net .org domain space. No


3.2 Input Format

The input format is a standard HTTPS/1.0 POST packet. The following rules apply:

The following table outlines the Mandatory fields. Every HTTPS-Post request you send MUST contain these fields:

Field Name Max Length Field Description
thisPage 80 Specifies the operation to be performed. e.g., pispCheckDomain
username 80 Specify the exact user name assigned by RegTime.Net for your login to the registration system. It is important to remember that the name is case sensitive.
password 80 Specify the exact password assigned by RegTime.Net for your login to the registration system. It is important to remember that the password is case sensitive.
domain_name 67 Specify the fully qualified domain name to be registered, e.g. example.com. The maximum length is 67 characters (63 + 4). Alphanumeric characters & hyphens are allowed. The domain name cannot start or end with a hyphen. Domain names containing russian characters ("russian domains") must be specified in windows-1251 (CP1251) encoding.


3.3 Common responce messages

The HTTPS-Post system will return the following error messages:

Response Message Description
Error: username/password Incorrect The "username" and "password" fields are either not completed or the data input does not match a valid user. Note: The username and password fields are case sensitive.
Error: Domain Name is invalid The "domain_name" field is either empty or invalid: i.e. domain contains invalid characters, exceeds maximum length etc.
Error: System Unavailable The RegTimeSRS Post gateway is unavailable. The operation has not been processed and should be resubmitted.
Error: Internal error Internal error in the RegTimeSRS. Please, contact RegTime.Net immidiately and report the problem.
Error: The following fields are invalid: <fields list> The data entered in the indicated field is invalid. Enter the correct data in the field and repost the request.

4. Registration Operations

4.1 Registration of .ru and .su Domains

This operation allows you to register .RU and .SU domain names. Following are the field requirements you will need to use in your HTTPS-post script. The thisPage field to perform this operation must be set to pispRegistration.
There are two mulual exclusive sets of contact fields - for organizations and for private persons.
Some fields can be "multiline": lines are separated by "\n" sequence. Example: "+7 3432 811221\n+7 3432 811222\n+7 3432 811223".

Field Name Max Length Field Description
period 2 This is the registration period and is mandatory. The only possible value for .ru and .su domains: 1
descr 255 Domain description in English. Optional.
Organization contacts (only for organizations, do not use for private persons)
org 255
multiline
Organization name in latin letters.
Example: Karla-Marla Uryupinsk State University
org_r 255
multiline
Full organization name in russian language.
Example: Общество с ограниченной ответственностью "Рога и Копыта"
code 10 Organization INN code (for Russian organizations).
Example: 7701107259
kpp 9 Organization KPP code (for Russian organizations).
Пример: 632946014
country 2 2-letter ISO-code of country.
Example: RU
address_r 255
multiline
The legal address of organization in russian language.
Example: 101000, Москва, УЛ.Пупкина, 1, стр. 2
p_addr 255
multiline
The postal address of domain administrator in russian language.
Example: 101000, Москва, ул.Пупкина, 1, стр. 2, отдел мебели, офис 433 (для В. Лоханкина)
phone 255
multiline
The phone numbers of domain administrator.
Example: +7 495 8102233\n+7 3432 811221
fax 255
multiline
The fax numbers of domain administrator.
Example: +7 3432 811221
e_mail 255
multiline
The email addresses of domain administrator.
Example: ncc@test.ru\ntest@test.ru
Private persons contacts (only for private persons, do not use for organizations)
person 80 Private person name in latin letters.
Example: Vassily N Pupkin
private_person 1 Valid values: 0 or 1.
If 1, this allows You to change the domain administrator person name in WHOIS to "Private person".
person_r 80 Private person name in russian language.
Example: Василий Николаевич Пупкин
passport 255
multiline
The serie, number, issuer and issue date of passport.
Example: 32 02 651241 выдан 48 о/м г.Москвы 26.12.1990
residence 255
multiline
Residence address. Must be filled in native language or in English.
Пример: 101000, Москва, ул.Воробьянинова, 15, кв.22
birth_date 10 The birth date of private person in DD.MM.YYYY format.
Example: 07.11.1917
country 2 2-letter ISO-code of country.
Example: RU
p_addr 255
multiline
The postal address of domain administrator in russian language.
Example: 101000, Москва, ул.Пупкина, 1, стр. 2, отдел мебели, офис 433 (для В. Лоханкина)
phone 255
multiline
The phone numbers of domain administrator.
Example: +7 495 8102233\n+7 3432 811221
fax 255
multiline
The fax numbers of domain administrator.
Example: +7 3432 811221
e_mail 255
multiline
The email addresses of domain administrator.
Example: ncc@test.ru\ntest@test.ru
code 12 The INN code of the private businessman.
Only for private businessmen.
Example: 789012345678
Name Servers
ns0 80 Specify the Primary name server hostname. Optional.
ns1 80 Specify the Secondary name server hostname. Optional.
ns2 80 Specify the Secondary1 name server hostname. Optional.
ns3 80 Specify the Secondary2 name server hostname. Optional.
ns0ip 15 Specify the IP-address of Primary name server hostname (only if hostname is based on the domain name). Optional.
ns1ip 15 Specify the IP-address of Secondary name server hostname (only if hostname is based on the domain name). Optional.
ns2ip 15 Specify the IP-address of Secondary1 name server hostname (only if hostname is based on the domain name). Optional.
ns3ip 15 Specify the IP-address of Secondary2 name server hostname (only if hostname is based on the domain name). Optional.

4.2 Registration of .INFO .BIZ .MOBI .ORG .COM .NET Domains

The fields are the same as in 4.4 with the billing contacts included. Unless billing contacts present they are filled in from owner contacts.
The thisPage field to perform this operation must be set to pispRegistration.

Field Name Max Length Field Description
period 2 This is the registration period and is mandatory. Specify as follows: 1 - 10
Domain owner (organization) contacts
o_company 80 Specify the license holder's organization name.
o_first_name 40 Specify the organization's representative given name and surname.
o_last_name 40 Specify the organization's representative surname.
o_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
o_phone 20 Specify the organization's international phone number (example: +7.4952171179).
o_fax 20 Specify the organization's international Fax number (example: +7.4952171179). Optional field.
o_addr 80 Specify the license holder's address.
o_city 80 Specify the license holder's suburb/city.
o_state 40 Specify the license holder's state / area. Optional field.
o_postcode 10 Specify the license holder's post code.
o_country_code 2 Specify the two-letter ISO country code for the license holder. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain administration contacts
a_company 80 Specify the name of the Organization to which the administration contact belongs.
a_first_name 40 Specify the organization's representative given name.
a_last_name 40 Specify the organization's representative surname.
a_email 80 Specify the organization's administration contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
a_phone 20 Specify the organization's administration contact's international phone number (example: +7.4952171179).
a_fax 20 Specify the organization's administration contact's international Fax number (example: +7.4952171179). Optional field.
a_addr 80 Specify the organization's administration contact's address.
a_city 80 Specify the organization's administration contact's suburb/city.
a_state 40 Specify the organization's administration contact's state. Optional field.
a_postcode 10 Specify the organization's administration contact's post code.
a_country_code 2 Specify the two-letter ISO country code for the administrative contact. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain technical contacts
t_company 80 Specify the name of the Organization to which the technical contact belongs.
t_first_name 40 Specify the organization's representative given name.
t_last_name 40 Specify the organization's representative surname.
t_email 80 Specify the organization's technical contact's Email. Specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a `.'; and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de.
t_phone 20 Specify the organization's technical contact's international phone number (example: +7.4952171179).
t_fax 20 Specify the organization's technical contact's international phone Fax (example: +7.4952171179). Optional field.
t_addr 80 Specify the organization's technical contact's address.
t_city 80 Specify the organization's technical contact's suburb/city.
t_state 40 Specify the organization's technical contact's state. Optional field.
t_postcode 10 Specify the organization's technical contact's post code.
t_country_code 2 Specify the organization's technical contact's country code. Specify the two-letter ISO country code. These country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain billing contacts
b_company 80 Specify the name of the Organization to which the billing contact belongs.
b_first_name 40 Specify the organization's representative given name.
b_last_name 40 Specify the organization's representative surname.
b_email 80 Specify the organization's billing contact's Email. Specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a `.'; and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de.
b_phone 20 Specify the organization's billing contact's international phone number (example: +7.4952171179).
b_fax 20 Specify the organization's billing contact's international phone Fax (example: +7.4952171179). Optional field.
b_addr 80 Specify the organization's billing contact's address.
b_city 80 Specify the organization's billing contact's suburb/city.
b_state 40 Specify the organization's billing contact's state. Optional field.
b_postcode 10 Specify the organization's billing contact's post code.
b_country_code 2 Specify the organization's billing contact's country code. Specify the two-letter ISO country code. These country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Name Servers
ns0 80 Specify the Primary name server hostname. Optional.
ns1 80 Specify the Secondary name server hostname. Optional.
ns2 80 Specify the Secondary1 name server hostname. Optional.
ns3 80 Specify the Secondary2 name server hostname. Optional.
ns0ip 15 Specify the IP-address of Primary name server hostname (only if hostname is based on the domain name). Optional.
ns1ip 15 Specify the IP-address of Secondary name server hostname (only if hostname is based on the domain name). Optional.
ns2ip 15 Specify the IP-address of Secondary1 name server hostname (only if hostname is based on the domain name). Optional.
ns3ip 15 Specify the IP-address of Secondary2 name server hostname (only if hostname is based on the domain name). Optional.

4.3. Registration of .asia Domains

Fields are the same as for п.4.2 with CED contact section added, described below. CED contact will be the second domain tech contact.

Field Name Max Length Field Description
CED contact
default_ced 2 If 'on' - use default CED contact. All other fields are not required is this case. Unless default_ced=on you must fill the parameters below.
company 80 Specify the name of the Organization to which the contact belongs.
first_name 40 Specify the organization's representative given name.
last_name 40 Specify the organization's representative surname.
email 90 Specify the organization's contact's Email. Specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a `.'; and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de.
phone 20 Specify the organization's contact's international phone number (example: +7.4952171179).
fax 20 Specify the organization's contact's international phone Fax (example: +7.4952171179).
addr 80 Specify the organization's contact's address.
city 80 Specify the organization's contact's suburb/city.
state 40 Specify the organization's contact's state. Optional field.
postcode 10 Specify the organization's contact's post code.
country_code 2 Specify the organization's contact's country code. Specify the two-letter ISO country code. These country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
cclocality 2 Specify the two-letter ISO country code from Asia-Pacific Region of CED contact
entity_type 13 Type (use one of: naturalPerson|corporation|cooperative|partnership|government|politicalParty|society|institution|other)
ident_form 22 Identification form (use one of: passport|certificate|legislation|societiesRegistry|politicalPartyRegistry|other)
ident_number 255 Identification number

4.4 Registration of .KZ .UZ .TJ Domains

Following are the field requirements you will need to use in your HTTPS-post script. The thisPage field to perform this operation must be set to pispRegistration.

Field Name Max Length Field Description
period 2 This is the registration period and is mandatory. Specify as follows: 1 - 10
Domain owner (organization) contacts
o_name_ru 80 Specify the given name and surname in Russian.
o_name_en 80 Specify the given name and surname in English.
o_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
o_phone 20 Specify the organization's international phone number (example: +7.4952171179).
o_fax 20 Specify the organization's international Fax number (example: +7.4952171179). Optional field.
o_addr_ru 80 Specify the license holder's address in Russian.
o_addr_en 80 Specify the license holder's address in English.
o_city_ru 80 Specify the license holder's suburb/city in Russian.
o_city_en 80 Specify the license holder's suburb/city in English.
o_state_ru 40 Specify the license holder's state / area in Russian.
o_state_en 40 Specify the license holder's state / area in English.
o_postcode 10 Specify the license holder's post code.
o_country_code 2 Specify the two-letter ISO country code for the license holder. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
For organizations only
o_company_ru 80 Specify the license holder's organization name in Russian.
o_company_en 80 Specify the license holder's organization name in English.
o_code 10 INN
o_bank 80 Bank
o_bank_account 40 Bank account
o_mfo 10 MFO (BIK)
o_okonh 10 OKONH
Domain administration contacts
a_name_ru 80 Specify the given name and surname in Russian.
a_name_en 80 Specify the given name and surname in English.
a_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
a_phone 20 Specify the international phone number (example: +7.4952171179).
a_fax 20 Specify the international Fax number (example: +7.4952171179). Optional field.
a_addr_ru 80 Specify the address in Russian.
a_addr_en 80 Specify the address in English.
a_city_ru 80 Specify the suburb/city in Russian.
a_city_en 80 Specify the suburb/city in English.
a_state_ru 40 Specify the state / area in Russian.
a_state_en 40 Specify the state / area in English.
a_postcode 10 Specify the post code.
a_country_code 2 Specify the two-letter ISO country code. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
For organizations only
a_company_ru 80 Specify the organization name in Russian.
a_company_en 80 Specify the organization name in English.
Domain technical contacts
t_name_ru 80 Specify the given name and surname in Russian.
t_name_en 80 Specify the given name and surname in English.
t_email 80 Specify the contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
t_phone 20 Specify the international phone number (example: +7.4952171179).
t_fax 20 Specify the international Fax number (example: +7.4952171179). Optional field.
t_addr_ru 80 Specify the address in Russian.
t_addr_en 80 Specify the address in English.
t_city_ru 80 Specify the suburb/city in Russian.
t_city_en 80 Specify the suburb/city in English.
t_state_ru 40 Specify the state / area in Russian.
t_state_en 40 Specify the state / area in English.
t_postcode 10 Specify the post code.
t_country_code 2 Specify the two-letter ISO country code. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
For organizations only
t_company_ru 80 Specify the organization name in Russian.
t_company_en 80 Specify the organization name in English.
Domain billing contacts
b_name_ru 80 Specify the given name and surname in Russian.
b_name_en 80 Specify the given name and surname in English.
b_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
b_phone 20 Specify the international phone number (example: +7.4952171179).
b_fax 20 Specify the international Fax number (example: +7.4952171179). Optional field.
b_addr_ru 80 Specify the address in Russian.
b_addr_en 80 Specify the address in English.
b_city_ru 80 Specify the suburb/city in Russian.
b_city_en 80 Specify the suburb/city in English.
b_state_ru 40 Specify the state / area in Russian.
b_state_en 40 Specify the state / area in English.
b_postcode 10 Specify the post code.
b_country_code 2 Specify the two-letter ISO country code. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
For organizations only
b_company_ru 80 Specify the organization name in Russian.
b_company_en 80 Specify the organization name in English.
Name Servers
ns0 80 Specify the Primary name server hostname. Optional.
ns1 80 Specify the Secondary name server hostname. Optional.
ns2 80 Specify the Secondary1 name server hostname. Optional.
ns3 80 Specify the Secondary2 name server hostname. Optional.
ns0ip 15 Specify the IP-address of Primary name server hostname (only if hostname is based on the domain name). Optional.
ns1ip 15 Specify the IP-address of Secondary name server hostname (only if hostname is based on the domain name). Optional.
ns2ip 15 Specify the IP-address of Secondary1 name server hostname (only if hostname is based on the domain name). Optional.
ns3ip 15 Specify the IP-address of Secondary2 name server hostname (only if hostname is based on the domain name). Optional.

4.5 Registration of Other (gTLD) Domains

This operation allows you to register .BIZ .INFO .CC .TV .РУ .КОМ .НЕТ .ОРГ domain names. Following are the field requirements you will need to use in your HTTPS-post script. The thisPage field to perform this operation must be set to pispRegistration.

Field Name Max Length Field Description
period 2 This is the registration period and is mandatory. Specify as follows: 1 - 10
Domain owner (organization) contacts
o_company 80 Specify the license holder's organization name.
o_first_name 40 Specify the organization's representative given name.
o_last_name 40 Specify the organization's representative family name.
o_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
o_phone 20 Specify the organization's international phone number (example: +7.4952171179).
o_fax 20 Specify the organization's international Fax number (example: +7.4952171179). Optional field.
o_addr 80 Specify the license holder's address.
o_city 80 Specify the license holder's suburb/city.
o_state 40 Specify the license holder's state / area. Optional field.
o_postcode 10 Specify the license holder's post code.
o_country_code 2 Specify the two-letter ISO country code for the license holder. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain administration contacts
a_company 80 Specify the name of the Organization to which the administration contact belongs.
a_first_name 40 Specify the organization's administration contact's given name.
a_last_name 40 Specify the organization's administration contact's family name.
a_email 80 Specify the organization's administration contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
a_phone 20 Specify the organization's administration contact's international phone number (example: +7.4952171179).
a_fax 20 Specify the organization's administration contact's international Fax number (example: +7.4952171179). Optional field.
a_addr 80 Specify the organization's administration contact's address.
a_city 80 Specify the organization's administration contact's suburb/city.
a_state 40 Specify the organization's administration contact's state. Optional field.
a_postcode 10 Specify the organization's administration contact's post code.
a_country_code 2 Specify the two-letter ISO country code for the administrative contact. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain technical contacts
t_company 80 Specify the name of the Organization to which the technical contact belongs.
t_first_name 40 Specify the organization's technical contact's given name.
t_last_name 40 Specify the organization's technical contact's family name.
t_email 80 Specify the organization's technical contact's Email. Specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a `.'; and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de.
t_phone 20 Specify the organization's technical contact's international phone number (example: +7.4952171179).
t_fax 20 Specify the organization's technical contact's international phone Fax (example: +7.4952171179). Optional field.
t_addr 80 Specify the organization's technical contact's address.
t_city 80 Specify the organization's technical contact's suburb/city.
t_state 40 Specify the organization's technical contact's state. Optional field.
t_postcode 10 Specify the organization's technical contact's post code.
t_country_code 2 Specify the organization's technical contact's country code. Specify the two-letter ISO country code. These country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Name Servers
ns0 80 Specify the Primary name server hostname. Optional.
ns1 80 Specify the Secondary name server hostname. Optional.
ns2 80 Specify the Secondary1 name server hostname. Optional.
ns3 80 Specify the Secondary2 name server hostname. Optional.
ns0ip 15 Specify the IP-address of Primary name server hostname (only if hostname is based on the domain name). Optional.
ns1ip 15 Specify the IP-address of Secondary name server hostname (only if hostname is based on the domain name). Optional.
ns2ip 15 Specify the IP-address of Secondary1 name server hostname (only if hostname is based on the domain name). Optional.
ns3ip 15 Specify the IP-address of Secondary2 name server hostname (only if hostname is based on the domain name). Optional.

4.6. Transfer Domain from another registrar

This operation allows you to submit transfer requests for .COM .NET .ORG .BIZ .INFO .US .RU and .SU domain names. The thisPage field to perform this operation must be set to pispInitiateTransfer.

4.5.1. Transfer of .INFO .BIZ .MOBI .ORG Domains

All fields are mandatory.

Field Name Min length Max length Description
period 1 1 The renewal period: 1 - 9
authinfo 3 40 Domain password (authinfo)

4.5.2. Transfer of other Domains

All other fields are the same as for domain registration operations (see sections 4.1, and 4.2 and 4.4). The only exception: for .ru and .su domains "period" field can accept value "0" (transfer without renewal).

4.7 Registration Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Success: Registered <domain name> for <years> years This response indicates a successful registration
Success: Transfer request accepted for <domain name> Transfer request was successfully accepted
Error: Unavailable Domain Name This response results from a registration request. The domain name is already registered, or it fails to meet the criteria for a legitimate domain name.
Error: Invalid name servers Name servers are not specified or they are invalid.

5. Maintenance Operations

Following are the different maintenance operations that can be performed via the HTTPS-Post interface:


5.1 Check the Availability of a Domain Name

This operation allows you to check the availability of a domain names.
The thisPage field to perform this operation must be set to pispCheckDomain.
There are no additional fields besides common mandatory fields for this operation.

5.1.1 Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Success: <domain name> is Available This indicates that the domain name is available for registration.
Success: <domain name> is Unavailable This indicates that the domain name is already registered

Sell also: Common responce messages


5.2 Obtain WHOIS Information of Domain

This operation allows you to obtain WHOIS information of a domains.
The thisPage field to perform this operation must be set to pispWhois.
There are no additional fields besides common mandatory fields for this operation.

5.2.1 Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Error: <domain name> not found The domain name is either not existing or it's WHOIS data is not at the WHOIS database yet.
<raw whois data> Whois information returned in human-readable form in HTML format. This data can be directly embedded to any web page without risk of page layout corruption.

Sell also: Common responce messages


5.3 Renew an existing domain

This operation allows you to renew one or more domain names.
The thisPage field to perform this operation must be set to pispRenewDomain.
See field description in the table below for details.

Field Name Max Length Field Description
period 2 This is the renewal period and is mandatory. Specify as follows: 1 - 10

5.3.1 Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Success: Renewed <domain name> for <years> years This response indicates a successful renewal

Sell also: Common responce messages


5.4 Redelegate Domain Name

This operation allows you to redelegate domain name to new name servers. It is to be noted that only domain names under your account can be redelegated.
The thisPage field to perform this operation must be set to pispRedelegation.

IMPORTANT: A minimum of 2 name servers must be specified. The maximum is 4. The name server and its IP address must be specified for each name server that does not exist at the registry. This will enable the name server to be created at the registry.

Following are the fields to be completed and submitted via the HTTPS-Post interface.

Field Name Max Length Field Description
ns0 80 Specify the Primary name server hostname.
ns1 80 Specify the Secondary name server hostname.
ns2 80 Specify the Secondary1 name server hostname. Optional.
ns3 80 Specify the Secondary2 name server hostname. Optional.
ns0ip 15 Specify the IP-address of Primary name server hostname (only if hostname is based on the domain name). Optional.
ns1ip 15 Specify the IP-address of Secondary name server hostname (only if hostname is based on the domain name). Optional.
ns2ip 15 Specify the IP-address of Secondary1 name server hostname (only if hostname is based on the domain name). Optional.
ns3ip 15 Specify the IP-address of Secondary2 name server hostname (only if hostname is based on the domain name). Optional.

5.4.1 Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Success: Redelegated <domain name> to <name server list> This indicates a successful redelegation
Error: Invalid name servers Name servers are not specified or they are invalid.

Sell also: Common responce messages


5.5 Update Contact Details for an Existing Domain Name

This operation allows you to update contact details for domain name. The thisPage field to perform this operation must be set to pispContactDetails.

5.5.1. Update Contact Details for .ru and .su domains

After manual chack of registrant data any changes of "org", "org_r", "code", "address_r", "person", "person_r", "passport", "birth_date" fields will be disabled. All changes made by this operation for given fields will be ignored.
Following are the field requirements needed to use the HTTPS-Post interface.

Field Name Max Length Field Description
descr 255 Domain description in English. Optional.
Organization contacts (only for organizations, do not use for private persons)
org 255
multiline
Organization name in latin letters.
Example: Karla-Marla Uryupinsk State University
org_r 255
multiline
Full organization name in russian language.
Example: Общество с ограниченной ответственностью "Рога и Копыта"
code 10 Organization INN code (for Russian organizations).
Example: 7701107259
kpp 9 Organization KPP code (for Russian organizations).
Пример: 632946014
country 2 2-letter ISO-code of country.
Example: RU
address_r 255
multiline
The legal address of organization in russian language.
Example: 101000, Москва, УЛ.Пупкина, 1, стр. 2
p_addr 255
multiline
The postal address of domain administrator in russian language.
Example: 101000, Москва, ул.Пупкина, 1, стр. 2, отдел мебели, офис 433 (для В. Лоханкина)
phone 255
multiline
The phone numbers of domain administrator.
Example: +7 495 8102233\n+7 3432 811221
fax 255
multiline
The fax numbers of domain administrator.
Example: +7 3432 811221
e_mail 255
multiline
The email addresses of domain administrator.
Example: ncc@test.ru\ntest@test.ru
Private persons contacts (only for private persons, do not use for organizations)
person 80 Private person name in latin letters.
Example: Vassily N Pupkin
private_person 1 Valid values: 0 or 1.
If 1, this allows You to change the domain administrator person name in WHOIS to "Private person".
person_r 80 Private person name in russian language.
Example: Василий Николаевич Пупкин
passport 255
multiline
The serie, number, issuer and issue date of passport.
Example: 32 02 651241 выдан 48 о/м г.Москвы 26.12.1990
residence 255
multiline
Residence address. Must be filled in native language or in English.
Пример: 101000, Москва, ул.Воробьянинова, 15, кв.22
birth_date 10 The birth date of private person in DD.MM.YYYY format.
Example: 07.11.1917
country 2 2-letter ISO-code of country.
Example: RU
p_addr 255
multiline
The postal address of domain administrator in russian language.
Example: 101000, Москва, ул.Пупкина, 1, стр. 2, отдел мебели, офис 433 (для В. Лоханкина)
phone 255
multiline
The phone numbers of domain administrator.
Example: +7 495 8102233\n+7 3432 811221
fax 255
multiline
The fax numbers of domain administrator.
Example: +7 3432 811221
e_mail 255
multiline
The email addresses of domain administrator.
Example: ncc@test.ru\ntest@test.ru
code 12 The INN code of the private businessman.
Only for private businessmen.
Example: 789012345678


5.5.2. Update Contact Details for .INFO .BIZ .MOBI Domains

Fields list

5.5.3. Update Contact Details for .KZ .UZ .TJ Domains

Fields list

5.5.4. Update Contact Details for other (gTLD) domains

You will not be able to change the organization name (o_company) through this operation. Changing the organization name would effectively be a transfer of ownership.
Following are the field requirements needed to use the HTTPS-Post interface.

Field Name Max Length Field Description
Domain owner (organization) contacts
o_company 80 Specify the license holder's organization name.
o_first_name 40 Specify the organization's representative given name.
o_last_name 40 Specify the organization's representative family name.
o_email 80 Specify the organization's representative contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
o_phone 20 Specify the organization's international phone number (example: +7.4952171179).
o_fax 20 Specify the organization's international Fax number (example: +7.4952171179). Optional field.
o_addr 80 Specify the license holder's address.
o_city 80 Specify the license holder's suburb/city.
o_state 40 Specify the license holder's state / area. Optional field.
o_postcode 10 Specify the license holder's post code.
o_country_code 2 Specify the two-letter ISO country code for the license holder. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain administration contacts
a_company 80 Specify the name of the Organization to which the administration contact belongs.
a_first_name 40 Specify the organization's administration contact's given name.
a_last_name 40 Specify the organization's administration contact's family name.
a_email 80 Specify the organization's administration contact's Email. You must specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a., and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de
a_phone 20 Specify the organization's administration contact's international phone number (example: +7.4952171179).
a_fax 20 Specify the organization's administration contact's international Fax number (example: +7.4952171179). Optional field.
a_addr 80 Specify the organization's administration contact's address.
a_city 80 Specify the organization's administration contact's suburb/city.
a_state 40 Specify the organization's administration contact's state. Optional field.
a_postcode 10 Specify the organization's administration contact's post code.
a_country_code 2 Specify the two-letter ISO country code for the administrative contact. A list of these country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Domain technical contacts
t_company 80 Specify the name of the Organization to which the technical contact belongs.
t_first_name 40 Specify the organization's technical contact's given name.
t_last_name 40 Specify the organization's technical contact's family name.
t_email 80 Specify the organization's technical contact's Email. Specify a string of at least one character, followed by @, followed by a string of at least two characters, followed by a `.'; and followed by a string of at least two characters. An example of the minimum allowable is a@bc.de.
t_phone 20 Specify the organization's technical contact's international phone number (example: +7.4952171179).
t_fax 20 Specify the organization's technical contact's international phone Fax (example: +7.4952171179). Optional field.
t_addr 80 Specify the organization's technical contact's address.
t_city 80 Specify the organization's technical contact's suburb/city.
t_state 40 Specify the organization's technical contact's state. Optional field.
t_postcode 10 Specify the organization's technical contact's post code.
t_country_code 2 Specify the organization's technical contact's country code. Specify the two-letter ISO country code. These country codes can be found at http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html

5.5.3. Response Messages

The HTTPS-Post system will return the following messages:

Response Message Description
Success: Modified contact details for <domain name> This indicates a successful update

Sell also: Common responce messages


6. Examples

Examples of HTML-forms for making HTTPS-requests to RegtimeSRS can be downloaded from http://www.webnames.ru/downloads/RegTimeSRS-examlpes.zip