I believe the transfer authorisation code for .info and .biz names, is the so-called lock.
If you are new to domains and looking to buy, sell and learn about domains then you have come to the right place. DNForum is the largest domain name community on the internet and continues to grow every day. There are over 105,000 domainers on DNForum doing everything from buying domains, selling domains, learning about domains and discussing domains. Take a minute and Register.
Register Today on DNForum IT'S FREE!When will a registry lock be available for .INFO names?
Anyone have any news on this?
I believe the transfer authorisation code for .info and .biz names, is the so-called lock.
If a man will begin with certainties, he shall end in doubts; but if he will be content to begin with doubts he shall end in certainties. Sir Francis Bacon
When will a registry lock be available for .INFO names?
-----------------------------------------
A CLIENT LOCK is currently available.
(See my seniorhealth.info). I did a test to confirm its effect: Am able to alter owner on dot info domains I haven't locked but couldn't do so to seniorhealth.info.
Just a reminder/tip: if you had many dot info names during the recent landrushes and are now moving them to other registrars, remember (for security reasons) to request that the authorization numbers be changed by the new registrar after the transfer has been completed.
Skylark
Thanks, mole and skylark!
Much appreciated!
Is the CLIENT LOCK available to names which have been transferred to an Enom.com account, or an Enom reseller account?
Is the CLIENT LOCK available to names which have been transferred to an Enom.com account, or an Enom reseller account?
I don't know if Enom supports the client lock. I would ask them. If it helps you might forward to them the below which is a quote from a e-mail afilias sent to dd24.net re my seniorhealth.info lock inquiry:
11/1/2001 - An xml example of client lock imposed with the domain update command:
<epp xmlns="urn.iana:xml:ns:epp"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xsi:schemaLocation="urn.iana:xml:ns:epp
epp.xsd"><command><update><domain:update xmlns:domain="urn:iana:xml:ns:domain"
xsi:schemaLocation="urn:iana:xml:ns:host
domain.xsd"><domain:name><infodomain.info</domain:name><domain:add><domain:status="ClientLock "/>
<domain:add></domain:update></update><unspec/><clTRID>ABC-12345</clTRID></command></epp>
Good Luck
Skylark
Thanks very much for that, Skylark!
If that will work with Enom, I will sleep much easier!
I'll post here when I find out anything...
Bookmarks