Find answers and help fast
This section covers the most common domain transfer related questions and provides instructions on transferring a domain between Registrars.
When you are transferring a .st domain registration from one registrar to another, there are specific steps you will need to take to prepare your domain. Below are the details to prepare your domain for transfer with your current registrar and then submit the transfer request with gaining Registrar (where domain is transferred in).
The management of hosts via REST API Gateway allows for easy checking, creation, deleting, and updating of name servers.
Host management commands can be applied only to the host name objects that have a subordinate relationship to a superordinate domain name, in other words – registrar is able to manage only host name objects related to the domain names within his domain repository in ST Registry.
Using Auth Token received from authentication request(s) client is able to complete set of domain management operations: checking domain(s) availability, creating a domain, updating a domain’s objects, to even deleting a domain. All operations issued to the REST API processed in REAL-TIME.
Authentication in REST API is implemented through Auth Token.
Auth Token – unique string which is generated for limited period of time after successful client authorisation which is required to access any REST API resource by the client except “/auth” resource. One client is able to generate only 1 Auth token, new token is generated only if previous one has expired. This mean that if client will send several authorisation request within short period of time (until auth token expire) – all responses will contain same auth token value. Currently default expire time for token is 60 seconds.
To simplify domain portfolio management for each registrar – ST Registry has implemented “Domains collection” extension. Extension is supposed to simplify synchronisation between Registrar local database and Registry repository.
Purpose for the “Info” command is to simplify querying domains collection by “walking” through it partially. Info command return number of domains in Registrar portfolio.
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <domainsCollection:domainsCollection xmlns:domainsCollection="urn:ietf:params:xml:ns:domainsCollection-1.0"> <domainsCollection:info></domainsCollection:info> </domainsCollection:domainsCollection> <clTRID>53cff4f423159</clTRID> </extension> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <resData> <domainsCollection:infData xmlns:domainsCollection="urn:ietf:params:xml:ns:domainsCollection-1.0"> <domainsCollection:count>3000</domainsCollection:count> </domainsCollection:infData> </resData> <trID> <clTRID>53cff4f423159</clTRID> <svTRID>cdae3f73-ee75-43d2-9fd2-f59dcea9c877</svTRID> </trID> </response> </epp> |
Query command for DomainCollection extension provide possibility to query Registrar domains partially from its collection.
Request should contain 2 attributes:
In example request below we are querying 2 domains with position #101 and #102 in our collection:
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <domainsCollection:domainsCollection xmlns:domainsCollection="urn:ietf:params:xml:ns:domainsCollection-1.0"> <domainsCollection:query limit="2" offset="100"></domainsCollection:query> </domainsCollection:domainsCollection> <clTRID>53cff68f70fca</clTRID> </extension> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <resData> <domainsCollection:queData xmlns:domainsCollection="urn:ietf:params:xml:ns:domainsCollection-1.0"> <domainsCollection:info> <domainsCollection:count>2</domainsCollection:count> <domainsCollection:total>3</domainsCollection:total> <domainsCollection:limit>2</domainsCollection:limit> <domainsCollection:offset>1</domainsCollection:offset> </domainsCollection:info> <domainsCollection:domains> <domainsCollection:domain>example1.st</domainsCollection:domain> <domainsCollection:domain>example2.st</domainsCollection:domain> </domainsCollection:domains> </domainsCollection:queData> </resData> <trID> <clTRID>53cff68f70fca</clTRID> <svTRID>d22c1ef6-6cb6-43c3-b63b-7af4a0442390</svTRID> </trID> </response> </epp> |
Registrar info extension provide possibility to fetch current registrar details in ST Registry system.
Response on request below will provide information:
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <registrar:registrar xmlns:registrar="urn:ietf:params:xml:ns:registrar-1.0"> <registrar:info></registrar:info> </registrar:registrar> <clTRID>53cff79a37869</clTRID> </extension> </epp> |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <resData> <registrar:infData xmlns:registrar="urn:ietf:params:xml:ns:registrar-1.0"> <registrar:clID>ABC123456XYZ</registrar:clID> <registrar:organization>Client organization</registrar:organization> <registrar:publicName>Client public name</registrar:publicName> <registrar:country>US</registrar:country> <registrar:address>Some street</registrar:address> <registrar:url>websiteurl.st</registrar:url> <registrar:whois>whois.nic.st</registrar:whois> <registrar:contact type="admin">ABC111</registrar:contact> <registrar:contact type="tech">ABC112</registrar:contact> <registrar:contact type="billings">ABC113</registrar:contact> <registrar:billingPlan> <registrar:name since="2013-10-08T00:00:00+00:00">LEVEL1</registrar:name> <registrar:records> <registrar:record name="Balance">0</registrar:record> <registrar:record name="BillingPeriod">12</registrar:record> <registrar:record name="ClientState">ACTIVE</registrar:record> <registrar:record name="ContactCreatePrice">0</registrar:record> <registrar:record name="ContactDeletePrice">0</registrar:record> <registrar:record name="ContactUpdatePrice">0</registrar:record> <registrar:record name="CreditLimit">0</registrar:record> <registrar:record name="Currency">EUR</registrar:record> <registrar:record name="DomainCreatePrice">2</registrar:record> <registrar:record name="DomainDeletePrice">0</registrar:record> <registrar:record name="DomainRenewPrice">2</registrar:record> <registrar:record name="DomainTransferFee">0</registrar:record> <registrar:record name="DomainUpdatePrice">0</registrar:record> <registrar:record name="HostCreatePrice">0</registrar:record> <registrar:record name="HostDeletePrice">0</registrar:record> <registrar:record name="HostUpdatePrice">0</registrar:record> <registrar:record name="IDNDomainCreatePrice">0</registrar:record> <registrar:record name="IDNDomainRenewPrice">0</registrar:record> <registrar:record name="MaxBillingPeriod">5</registrar:record> <registrar:record name="MinBillingPeriod">1</registrar:record> <registrar:record name="OneLetterDomainCreateFee">2500</registrar:record> <registrar:record name="OneLetterDomainCreatePrice">2</registrar:record> <registrar:record name="OneLetterDomainRenewFee">0</registrar:record> <registrar:record name="OneLetterDomainRenewPrice">2</registrar:record> <registrar:record name="RedemptionFee">0</registrar:record> <registrar:record name="Status">normal</registrar:record> <registrar:record name="TwoLetterDomainCreateFee">999</registrar:record> <registrar:record name="TwoLetterDomainCreatePrice">2</registrar:record> <registrar:record name="TwoLetterDomainRenewFee">0</registrar:record> <registrar:record name="TwoLetterDomainRenewPrice">2</registrar:record> <registrar:record name="VAT">0</registrar:record> </registrar:records> </registrar:billingPlan> </registrar:infData> </resData> <trID> <clTRID>53cff79a37869</clTRID> <svTRID>b2e3a7e3-8662-4959-a149-680bea2848ad</svTRID> </trID> </response> </epp> |
ST Registry require accurate contact details for every registered domain, this information is used in case a dispute arises about the domain name.This information is often displayed in the WHOIS system which is public and can be viewed by anyone. WHOIS Privacy extension should be used if registrant would like to hide domain contact information from a public view partialy or completely. This function is totally free of charge for every accredited ST Registrar. In other words – WHOIS privacy is used to “mask”/hide domain contact(s) with another contact or set of contacts defined by the current sponsoring domain registrar. Its up to the Registrar if he should use same privacy contact for all contacts and for all domains or if every domain should have own privacy contact or set of contacts.
Since complete domain details can be fetched only by sponsoring registar while other registrar(s) are able to do it only through WHOIS info command (or request(s) to ST Registry WHOIS public servers), this mean that all regisrars except sponsoring registrar will be able to see only privacy contact details if such contact(s) was defined for domain using Whois privacy command.
WHOIS public servers respond identical domain details to WHOIS query command.
Example for Domain info command response for domain with privacy contacts:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <resData> <domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"> <domain:name>example.st</domain:name> <domain:status s="ok"></domain:status> <domain:registrant>ABC111</domain:registrant> <domain:contact type="admin_privacy">PRIVACY222</domain:contact> <domain:contact type="billing_privacy">PRIVACY333</domain:contact> <domain:contact type="tech_privacy">PRIVACY444</domain:contact> <domain:contact type="admin">ABC222</domain:contact> <domain:contact type="billing">ABC333</domain:contact> <domain:contact type="tech">ABC444</domain:contact> <domain:contact type="registrant_privacy">PRIVACY111</domain:contact> <domain:ns> <domain:hostObj>ns1.host.st</domain:hostObj> <domain:hostObj>ns2.host.st</domain:hostObj> </domain:ns> <domain:clID>CliendID1</domain:clID> <domain:crID>ClientID1</domain:crID> <domain:crDate>2014-01-01T00:00:01+00:00</domain:crDate> <domain:exDate>2015-01-01T00:00:01+00:00</domain:exDate> <domain:upID>ClientID1</domain:upID> <domain:upDate>2014-01-02T06:38:03+00:00</domain:upDate> <domain:authInfo> <domain:pw>D0ma1nAuthCode</domain:pw> </domain:authInfo> </domain:infData> </resData> <trID> <clTRID>5412ed81d5a5a</clTRID> <svTRID>09af29c0-2a16-4097-9086-c5ddcc522f27</svTRID> </trID> </response> </epp> |
Command create privacy contact for one or more contact(s) (in this example we assign privacy contacts for all 4 contacts: registrant, admin, billing and tech contacts):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <whoisPrivacy:whoisPrivacy xmlns:whoisPrivacy="urn:ietf:params:xml:ns:whoisPrivacy-1.0"> <whoisPrivacy:create> <whoisPrivacy:domain>example.st</whoisPrivacy:domain> <whoisPrivacy:contact type="registrant">PRIVACY111</whoisPrivacy:contact> <whoisPrivacy:contact type="admin">PRIVACY222</whoisPrivacy:contact> <whoisPrivacy:contact type="tech">PRIVACY333</whoisPrivacy:contact> <whoisPrivacy:contact type="billing">PRIVACY444</whoisPrivacy:contact> </whoisPrivacy:create> </whoisPrivacy:whoisPrivacy> <clTRID>53cff97e49d6c</clTRID> </extension> </epp> |
Successful response:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <trID> <clTRID>53cff97e49d6c</clTRID> <svTRID>742aa2aa-5fcc-45d4-9306-dde9dd9926c5</svTRID> </trID> </response> </epp> |
Command update privacy contact for one or more contact(s):
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <whoisPrivacy:whoisPrivacy xmlns:whoisPrivacy="urn:ietf:params:xml:ns:whoisPrivacy-1.0"> <whoisPrivacy:update> <whoisPrivacy:domain>example.st</whoisPrivacy:domain> <whoisPrivacy:contact type="admin">PRIVACY111</whoisPrivacy:contact> </whoisPrivacy:update> </whoisPrivacy:whoisPrivacy> <clTRID>54131391148cb</clTRID> </extension> </epp> |
Successful response:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <trID> <clTRID>54131391148cb</clTRID> <svTRID>34c4d2f6-ba0b-4d35-ae70-945d2e61b275</svTRID> </trID> </response> </epp> |
Command delete remove all privacy contacts from corresponding domain.
Delete command request example:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <whoisPrivacy:whoisPrivacy xmlns:whoisPrivacy="urn:ietf:params:xml:ns:whoisPrivacy-1.0"> <whoisPrivacy:remove> <whoisPrivacy:domain>example.st</whoisPrivacy:domain> </whoisPrivacy:remove> </whoisPrivacy:whoisPrivacy> <clTRID>5413141c14519</clTRID> </extension> </epp> |
Successful response:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <trID> <clTRID>5413141c14519</clTRID> <svTRID>dc34d4bc-4e7f-4d76-8011-2ec2d86c8031</svTRID> </trID> </response> </epp> |
ST Registry has developed Whois info extension for EPP Gateway to simplify domains management by accredited registrars.
Domain details fetched with Whois info command is completely identical to one that is retrieved from ST Registry WHOIS public servers.
Request example:
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <extension> <whois:whois xmlns:whois="urn:ietf:params:xml:ns:whois-1.0"> <whois:query>example.st</whois:query> </whois:whois> <clTRID>541315bb24f33</clTRID> </extension> </epp> |
Successful response:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="1000"> <msg>Command completed successfully</msg> </result> <resData> <whois:queryData xmlns:whois="urn:ietf:params:xml:ns:whois-1.0"> <whois:name>example.st</whois:name> <whois:registrarName>ST Registry accredited registrar</whois:registrarName> <whois:registrarUrl>accreditedregistrar.st</whois:registrarUrl> <whois:crDate>2014-01-01T00:00:01+00:00</whois:crDate> <whois:exDate>2015-09-11T00:00:01+00:00</whois:exDate> <whois:upDate>2014-01-12T15:41:55+00:00</whois:upDate> <whois:status s="ok"></whois:status> <whois:contactInfo type="registrant"> <whois:id>PRIVACY111</whois:id> <whois:name>Privact contact name</whois:name> <whois:organization></whois:organization> <whois:street></whois:street> <whois:city></whois:city> <whois:state></whois:state> <whois:zip></whois:zip> <whois:country>ST</whois:country> <whois:phone>+1.1234567890</whois:phone> <whois:fax></whois:fax> <whois:email>private@contact.st</whois:email> </whois:contactInfo> <whois:contactInfo type="admin"> <whois:id>ABC222</whois:id> <whois:name>Public contact name</whois:name> <whois:organization></whois:organization> <whois:street></whois:street> <whois:city></whois:city> <whois:state></whois:state> <whois:zip></whois:zip> <whois:country>ST</whois:country> <whois:phone>+1.0987654321</whois:phone> <whois:fax></whois:fax> <whois:email>get@domain.st</whois:email> </whois:contactInfo> <whois:contactInfo type="tech"> <whois:id>ABC222</whois:id> <whois:name>Public contact name</whois:name> <whois:organization></whois:organization> <whois:street></whois:street> <whois:city></whois:city> <whois:state></whois:state> <whois:zip></whois:zip> <whois:country>ST</whois:country> <whois:phone>+1.0987654321</whois:phone> <whois:fax></whois:fax> <whois:email>get@domain.st</whois:email> </whois:contactInfo> <whois:contactInfo type="billing"> <whois:id>ABC222</whois:id> <whois:name>Public contact name</whois:name> <whois:organization></whois:organization> <whois:street></whois:street> <whois:city></whois:city> <whois:state></whois:state> <whois:zip></whois:zip> <whois:country>ST</whois:country> <whois:phone>+1.0987654321</whois:phone> <whois:fax></whois:fax> <whois:email>get@domain.st</whois:email> </whois:contactInfo> <whois:ns> <whois:hostObj>ns1.host.st</whois:hostObj> <whois:hostObj>ns2.host.st</whois:hostObj> </whois:ns> </whois:queryData> </resData> <trID> <clTRID>541315bb24f33</clTRID> <svTRID>7106027c-59b3-4947-b536-5b96df9861fd</svTRID> </trID> </response> </epp> |
Response example if requested domain not found:
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"> <response> <result code="2303"> <msg>Domain object does not exists</msg> </result> <trID> <clTRID>541315bb24f33</clTRID> <svTRID>541318499555b</svTRID> </trID> </response> </epp> |
