This article describes the procedures and requirements of .sg domain names.
Click on the subject below to open the dropdown for more information.
- for legal entities:
- company registration number in owner's handle
Successful domain transfer requires:
- authorisation code
- up to 7 days of processing time
|Authorization code required||yes|
|Method of confirmation||authcode|
|Registration period after transfer||extends|
|Average transfer time||Max 7 days|
|Advanced and simple transfers available||Contact our Sales department to check if easy transfer of 100 or more .sg domains is available.|
- Authorization code in RCP can be used for internal transfer only.
- Authorization code for external transfers can only be requested if domain's admin contact has local presence in Singapore and is not using our local presence service anymore.
If the above criteria is met - please contact email@example.com for assistance in retrieving the code. If you have updated the admin contact to a new contact person in Singapore, please sent the SingPassID or SGNICID number from this contact in the email.
SingPassID format: X1234567X - where X is an upper case letter at the beginning and end of a seven digit string
SGNICID format: SGNICID-X12-345678
Owner change (trade)
trade - processed via contact handle change in RCP
After submission, the current registrant will receive an email by NIC.SG which must be approved for the changes to take effect. A change of registrant is not real time and will need 7 days to complete. This domain will not be renewed after the trade and keep it's expiration date.
domain update - by updating associated handles
deletion - manual via RCP
Restore / reactivate
Manual by contacting firstname.lastname@example.org
|Registration agreement||The registry requires that a registration agreement is in place between the provider and the domain holder. The text of this registration agreement and any required supplements is the following:
Due to the regular changes in registry rules and configuration or missing information from registry side, and despite our effort to keep our knowledge base up-to-date, information in the knowledge base may be outdated or incorrect. If you encounter some issue, please report it through the "HotJar" feedback collector on the bottom right, or (if it is blocked by your browser) by clicking the "Submit a request" link below. No rights can be derived from the information in this knowledge base. If there is discrepancy between the knowledge base and the process in Openprovider, the process in Openprovider is leading.