Successful domain registration via RCP or API requires:

• the domain's contact handles including:
  
  • For private person
    • Name of the registrant must be correct, abbreviations are not allowed.
  • For companies
    • Correct and valid company registration number required
• two or more pre-configured nameservers or a nameserver group
  
  

The registry regularly checks on correctness of registration data!
Correct and valid company registration number is required, the number can be verified via this database.
Name of the registrant must be written fully and correct, abbreviations (John D.) are not allowed.

Please note that:

• Incomplete information (e.g. a typing error in the name) can only be corrected by doing a trade
• Fake data in the handles can lead to deletion of the domain name by the Registry.

REGISTRATION OF A RESERVED .lt DOMAIN NAME

• Currently, it is not possible to directly register a reserved .lt domain via RCP.
• If you want to do so, send an email to support@openprovider.com with all the details of the domain name (Contact Handles, Nameserver Records)
• Correct and valid company registration number is required, the number can be verified via this database as the registry will check for the sanity of the data.
• If the domain is to be registered in the name of an individual, Passport Number must be specified in the Owner Contact Handle.
• Openprovider will check with the registry, if it meets all the requirements and will revert you back.
• Upon the reseller's confirmation, we will register the domain name and add it to your portfolio.

Successful domain transfer requires:

• the domain's contact handles including:
  • For companies
    • Company registration number required
• two or more pre-configured nameservers or a nameserver group

The domain holder may not change during the transfer request. Please review the whois and your handle before initiating the transfer.

Procedure

1. Request for a transfer auth code at current registrar. 

2. The transfer authorization code is valid for 7 calendar days from its creation.

3. Submit a transfer request at Openprovider via API or RCP using the auth code. 

4. During the transfer procedure with a transfer authorization code, the verification of the registrant's name remains (i.e., ensuring that the natural person's name or legal entity's name matches the existing one).

5. During the validity period of the generated transfer authorization code, it is only possible to generate a new transfer authorization code (replace it) for the same domain by revoking the current transfer authorization code.

6. The domain transfer procedure can be initiated by the registrar, registrant, or .lt administrator.

   • Three domain transfer authorization codes are possible, respectively generated by the registrar, the registrant (registrant.domreg.lt), and the .lt administrator.

   • Accordingly, the registrar and the registrant can only revoke their own generated transfer authorization codes.

7. Transfer authorization code format: AAAA-AAAA-AAAA-AAAA
   A - randomly generated number or uppercase letter.

Additional notes on a .lt transfer

Details about selecting a registrar are listed on the registry's website.

In case your current provider is not aware about the .LT transfer process and is not familiar with the transfer auth code which you need, please refer them to this information page from the .LT Registry:

How to transfer servicing registrar 

You may request transfer auth code via RCP (Reseller Control Panel) or API. 

PLEASE NOTE, that if the domain transfer procedure was not completed within 7 calendar days since code was generated, the transfer authorization code for domain should be generated anew.

Owner change (trade)

Trade requests are initiated at the registry's website domreg.lt
(NOTE: a transfer and trade at the same time are not supported! First transfer the domain with keeping the same registrant, once the transfer is finished, you can submit a trade)

Procedure

1. Make a trade agreement with the gaining registrant.
2. The current registrant logs in to http://www.domreg.lt/registrant, and starts a trade request.
   1. Indicate the domain gaining registrant’s data in the opened window:
   2. Select whether gaining registrant type is a natural person or legal entity in the drop box;
   3. Enter gaining registrant full name, surname or legal entity’s name (when completing the trade procedure, these data have to coincide with the data provided by the gaining registrant’s servicing registrar);
   4. Enter gaining registrant’s full email address;
3. Once the registrant has initiated this trade, the reseller orders the trade in Openprovider within 7 days, ensuring that the name and e-mail address match the provided data. When procedure is completed, a new domain holder (registrant) is displayed in WHOIS database.

If trade procedure is not completed within the specified period, you can initiate it again, as previously specified.

It is now possible to request registrant ID, i.e. RN[number] via Openprovider API, please use 'auth_code_type' 'rncode' for REST API requests and 'authCodeType' 'rncode' for XML API requests.

Notes: Trade is not allowed within the period of 30 calendar days from the domain’s creation, or from the last trade, or from the domain’s creating during “quarantine”. In such case, you have to wait until the end of the specified period or apply to .lt registry with a request to quicken the procedure’s admissibility due to essential reasons, and state these reasons. In case a domain name is on the list of the reserved labels, the acquirer has to submit a permission to use the reserved label to .lt registry before the trade procedure.

Other update

• domain update - by updating associated handles
• processed in realtime

Delete

• deletion - processed in realtime
• deletion leads to 30 day quarantine

During the quarantine the domain can be re-registered by its original owner. After these 30 days the registry will keep the domain reserved for up to 24 hours (random interval) before releasing it for registration again.

Restore / reactivate

A restore can be done via the restore queue in the control panel or by API.