Extensible Provisioning Protocol (EPP): An application layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects.This method is used to verify .org, .info, .biz, .us, .cn, .com.cn, .net.cn, .org.cn, .cn, .tw, .jp and .in domains only. This may change at any time depending upon registry requirements.
When an EPP transfer order is created, an â€œauthorization keyâ€ or â€œEPP keyâ€ is required for each domain name to be transferred. Per ICANN regulations, a verification email or fax transfer authorization is also required.
Authorization (or EPP) keys/codes are generated by the current registrar and verified through the global registries for validity.
Although some registrars have begun to implement the EPP security protocol for .com and .net domains, the global registry, (Verisign) does not yet require an EPP/authorization key for registrar transfer of these TLDâ€™s. Until EPP authorization is mandated by the registry,requirements for transferring your .com and .net domains to or away from eNom have not changed.
Until this functionality has been fully employed, you will NOT be asked for an EPP key to transfer your .com or .net domain to or away from eNom. Some EPP enabled registrars may state that they require an EPP/authorization key for registrar transfer. In these cases, the domain owner has to contact the current domain registrar and request for the EPP/authorization key. A EPP/authorization key is a combination of alpha-numeric characters.For Example : A â€ made up â€œ EPP key** would look something like this: X9S03ZQ5490KJ32AM.
NOTE: Authorization (EPP) keys are a security code required by the registry for domain transfer, thus are unique to every domain name. No two EPP/authorization keys are the same, thus if you are transferring more than one EPP domain, you will need to obtain each domainâ€™s specific code.