Domain/create
apply for domain registration.
Request fields
Fields in this category are optional.
Description of contact data fields
Please note that in this operation it is permissible to use one of two mutually exclusive sets of fields — organization data (if the domain is registered for an organization), or data of an individual (if the domain is registered for an individual). Also, some fields can be multiline.
Common fields for. R U/. S U/
API domain registration in . TJ is not available.
At the moment, all contact details must be filled in in Latin.
Domain Owner Data
At the moment, all contact details must be filled in Latin letters. For domain zones com.ua, kiev.ua, only two types of contacts are used: contacts of the owner (administrator) of the domain and technical contacts. Changing the contact details of the domain owner after registration in automatic mode is not possible.
At the moment, all contact details must be filled in Latin letters. When registering a domain in the pp.ua zone, you must specify the mobile phone number in the contact details of the domain owner. After registering a domain, an SMS will be sent to this number with a domain activation code, which, together with the domain name, must be entered here:
http://www.pp.ua/rus/confirm.html. It is allowed to register no more than three domains per month for one mobile phone. More details about the rules of the pp.ua domain can be found
here. The rest of the rules for registering domains in the pp.ua zone correspond to the rules for registering domains in other zones.
Registration of domains in zones *. kz (all domains of Kazakhstan)
From September 7, 2010, in accordance with the KazNIC Rules, it is necessary to indicate the address of the server equipment on which the domain is located in the contact details of the domain. Domains registered after the specified date must be located on the servers of Kazakhstan. To specify the server hardware address when registering a domain or changing contacts, add the following fields to the contacts hash.
Server hardware address
If you do not plan to immediately link the domain to hosting or parking, you can use the following values for the server hardware address fields:
Registration of domains in the zone
To register a domain . TRAVEL needs to authenticate and obtain an identification number (“TRAVEL UIN”) on the authentication.travel website. If you have already been authenticated and the TRAVEL UIN issued to you has been confirmed (you can check its status on the authentication.travel website), enter your TRAVEL UIN to continue the registration procedure:
In zones . RU. net, . com. RU, . EXNET. SU and geodomains . ABKHAZIA. SU, . ADYGEYA. RU, . ADYGEYA. SU, . AKTYUBINSK. SU, . ARKHANGELSK. SU, . ARMENIA. SU, . ASHGABAD. SU, . AZERBAIJAN. SU, . BALASHOV. SU, . BASHKIRIA. RU, . BASHKIRIA. SU, . BIR. RU, . BRYANSK. SU, . BUKHARA. SU, . CBG. RU, . CHIMKENT. SU, . DAGESTAN. RU, . DAGESTAN. SU, . EAST-KAZAKHSTAN. SU, . EXNET. SU, . GEORGIA. SU, . GROZNY. RU, . GROZNY. SU, . IVANOVO. SU, . JAMBYL. SU, . KALMYKIA. RU, . KALMYKIA. SU, . KALUGA. SU, . KARACOL. SU, . KARAGANDA. SU, . KARELIA. SU, . KHAKASSIA. SU, . KRASNODAR. SU, . Kurgan. SU, . KUSTANAI. RU, . KUSTANAI. SU, . LENUG. SU, . MANGYSHLAK. SU, . MARINE. RU, . MORDOVIA. RU, . MORDOVIA. SU, . MSK. RU, . MSK. SU, . MURMANSK. SU, . MYTIS. RU, . NALCHIK. RU, . NALCHIK. SU, . navoi. SU, . NORTH-KAZAKHSTAN. SU, . NOV. RU, . NOV. SU, . OBNINSK. SU, . PENZA. SU, . POKROVSK. SU, . PYATIGORSK. RU, . RU. net, . SOCHI. SU, . SPB. RU, . SPB. SU, . TASHKENT. SU, . TERMEZ. SU, . TOGLIATTI. SU, . TROITSK. SU, . TSELINOGRAD. SU, . TULA. SU, . TUVA. SU, VLADIKAVKAZ. RU, . VLADIKAVKAZ. SU, . VLADIMIR. RU, . VLADIMIR. SU, . VOLOGDA. SU must specify only the owner of the domain, without the administrator and technical support
Additional fields are filled in only with Cyrillic characters, the data of the administrator and the owner of the domain, contacts of a technical specialist and a billing specialist are indicated.
The contact type is determined by the prefix: a, t, o, b
Set of fields (on the example of an administrative contact)
Domain DNS servers
Note: REG servers can be used free of charge for DNS support. RU. To do this, you must specify the ns1.reg.ru and ns2.reg.ru servers as DNS servers. At the same time, a zone for your domain will be registered on these servers. Subsequently, it will be possible to manage the zone through the web interface of the site reg.ru.
Service list processing support
Only for VIP clients.
Support for unicode domains
In addition to supporting the Russian language in Cyrillic areas. RF, . ENG, . WEBSITE, . ONLINE, . MOSCOW and others, there is support for other languages and characters in the main zones.
Zone . SU supports Armenian, Greek, Georgian and other languages, a complete list of all characters is available on the registry website.
Zones . SITE and . ONLINE supports characters of Ukrainian, Belarusian and Bulgarian languages.
Domain zones . UA support not only the Ukrainian alphabet, but also others. Complete list of majority characters. UA zones are on cctld ua and uanic.
Domain zones supported by the Verisign registry, such as . COM, . NET and others, may have names in many European languages, Cyrillic, Chinese, Korean, Japanese hieroglyphs, Arabic, Thai and others. See the full list here.
Each of the zones maintained by the CentralNic registry, such as . RU. COM, . XYZ, . site, . ONLINE and others, has its own set of supported languages. A complete list can be found on the registry website. Selecting a language will display a list of zones that support it.
Supported zone languages . INFO. ORG and others can be viewed on the IANA website here.
Domain registration requests can be sent in both unicode and punycode. If our system does not accept some character in the domain name, check the registry before writing a request to technical support.
Response fields
an example of ordering one .ru domain using a request in the «PLAIN» format:
Please note that if your library/program does not do full automatic data conversion, then «+» should be passed as «%2B». an example of such a request in JSON format, for clarity, the sent data is first presented as a Perl-e structure with its conversion to JSON format:
and the request itself:
the same, but it is assumed that the contact data is stored in the profile my_like_ru_profile:
first option, but bulk registration:
An example of a request for registration of domains in the zone. M OSKVA i. M OSCOW
example of response to the first request (request in «PLAIN» format):
example of response to the second request (request in JSON format):
example of response to the third request (wholesale request in JSON format):
Possible mistakes
See standard error codes
Domain/update_nss
Changing DNS servers of a domain, setting/removing domain delegation (only for partners)
Also see the service list identification parameters.
REG servers can be used free of charge for DNS support. RU. To do this, you must specify the ns1.reg.ru and ns2.reg.ru servers as DNS servers. In this case, on the servers REG. RU zone for your domain will be registered. You can manage the zone through the web interface of the REG site. RU or via API.
Changing the DNS of one domain
Changing the DNS of the list of domains, one of which contains an error in the name (see the answer for this case below)
Removing a domain from delegation without transferring NS servers
Answer example
Several domains, one of which contains erroneous data:
Successful domain delegation flag change response without NS servers (see request above)
Sample code
See. standard error codes
Domain/get_suggest
selection of a name for a domain by keywords, the function works like the Reg service. Choice
Request for zone information
And Standard Service Identification Parameters, Standard Service List Identification Parameters
See also standard error codes
Domain/register_ns
adding a domain to the NSI-registry, works only for international domains
Accept or reject domains transferred to this account
Examples of a successful response:
Partners with service plan «Partner 2» or higher
Submitting a request to transfer the desired domain names maintained by REG. EN, to your account.
Availability
Removing the domain delegation flag
Get DNS for domains
Full domain transfer to another account
As well as standard service list identification parameters
checking the status of the domain transfer, works only for those zones where REG. RU is a registrar, the status in other zones must be checked via whois
standard service identification parameters, service list identification parameters
missing or standard domain identification parameters
API availability check
checking the existence of a domain and getting its id
apply for a domain transfer from another registrar
Match the fields for the domain/create function. In addition, for domains . EN / . SU / . RF zones data of the domain owner and DNS server can be omitted, i.e. leave contacts and nss hashes empty. This data will be automatically obtained from the registry at the time of acceptance of the domain. Also for domains . EN / . SU / . RF period field can take the value «0» (transfer of domains without renewal). For most international domains (com net org info biz mobi name asia tel in mn bz cc tv us me cn nz co ca, etc.), you must additionally specify authinfo.
Contact details for. R U/. R F domains
Will be used for reconciliation with the data entered into the registry by the current registrar
Data of a private person (only when registering a domain for a private person!)
deleting a domain from the NSI-registry, only supported for international domains
replacement of an incorrect transfer key (authinfo) of a domain, available only until a request is sent to the registry
As well as standard service identification parameters
get a list of free domains with their bids, the list also contains domains for which the bid has been broken
checking availability of domain registration
getting a link to download documents from the Internet for . EN/. su/. RF domains
standard fields for domain identification
returns prices for specified premium domains. The function checks only domains that the registry has determined as premium and allows registration only at an increased cost.
place bids on free domains.
The data is updated around 8:00. At the moment of updating the data, the acceptance of bets is blocked depending on the volume of the update for 10-20 minutes, and at the same time returning the error code CREATION_IS_TEMPORARILY_LOCKED,
See more here
Also partners of REG. RUs can make a preliminary payment in the amount of 225 rubles, and pay the rest of the amount in case of successful completion of the registration application within 10 days after its execution (see the installment parameter below). If you choose this payment method, the domain will be registered on REG. RU, and after paying the full cost, it is automatically re-registered to the data you specified. In case of non-fulfillment of obligations to pay the full cost within the established period, the advance payment will be considered a penalty and will not be refunded. For more details, see the Agreement, paragraphs. 2.16, 2.17, 3.2.9, 6.11.
example of sent data (structure in Perl-e) with its conversion to JSON format:
The same, but using wget for a post request (parameter —post-data) and outputting the response to the console:
result for the above wget request:
Changing the flag Private Person and Total Private Person to hide/display contact details in whois
Changing domain contact details
Single domain query
Request with a list of domains
view domains transferred to the account
Setting the domain delegation flag
Get prices for registration/renewal of domains in all available zones.
get a list of free domains with characteristics, data is updated once every 30 minutes
Getting a list of released domains, the function works like the page Released and free domains
Sending verification emails for GTLD domains and verification of email confirmation for accredited zones
Requesting information about the need to confirm email and sending an email for verification
Requesting information about the need to confirm email without sending a verification email
