Sandbox
 |
 We are partnering with nTLDStats to provide a robust and comprehensive resource on New gTLDs. By integrating their statistics into our site, we are creating a resource that will make the domain name industry more accessible and demystify the world of New gTLDs. The userbox (pictured left) now features statistics such as registrations and parked domains, as well as important dates relating to each TLD. |
|
|
Whether you are a total newcomer or an industry veteran, you should have an article on ICANNWiki. To create your article, follow the Steps below:
- Enter your name as you would like it to appear and submit.
- Publish the template that is populated.
- Click edit and fill in the article
- Save Changes
Domain Locking, sometimes referred to as Registry or Registrar-locking, describes the service provided by registries or registrars to "lock" a domain name so that it cannot be transferred or altered without the explicit permission of the registrant. If a lock is in place, the registrant must request that the name be "unlocked" before such changes can be made.
Domain locking services emerged out of ICANN's Transfer of Registration Policy as a way of ensuring that transfers are intentional before they are completed. Domain locking addresses important security concerns, such as transferring a domain name without the registrant's permission. It is important to note that different registrars and registries may have different locking and unlocking procedures. Some automatically put locks in place while others have an opt-in procedure or a fee-based locking service. Domain locking has also been used by registries or registrars in cases of abuse or suspected abuse as locking the domain keeps the owner from transferring or deleting it. An example of this can be found in ICANN's URS Proceedings, where registry operators, after receiving a URS notice, are required to lock the name in question.