When you move a domain to another registrar, the new registrar will ask for one thing: the transfer code. It is called an EPP code, Auth code, authInfo or transfer password, but it is the same thing, a secret string attached to the domain that only the owner is supposed to know. Anyone with the code can start a transfer, so treat it like a bank card PIN rather than a technical detail.
Where the code comes from
Most generic domain zones use EPP (Extensible Provisioning Protocol) between registrars and the registry. When a domain is registered, the registry attaches an authInfo password that only the current registrar can see or change. The new registrar submits this password with the transfer request, and the registry checks it before the transfer starts. Without it, any registrar could claim a domain simply by saying "I am the owner".
How to get the code
Only the registrar currently holding the domain can give you the code. Usually it is a "Get transfer code" button on the domain page; some registrars only email it to the owner. If your domain is managed in the sayt.uz cabinet, request it on the domain page or through support. Under ICANN rules for generic domains, a registrar may not withhold the code without a valid reason. Prepare first, or the transfer will fail even with the correct code:
- Remove the registrar transfer lock.
- Make sure the WHOIS contact email works, since confirmation mail may go there.
- Check the domain has not expired.
- Enter the code only into the new registrar's official transfer form.
Checking that the domain is unlocked
The lock appears in the status field of WHOIS or RDAP. If you see clientTransferProhibited, the domain is still locked:
whois example.com | grep -i "status"
# via RDAP, if jq is installed
curl -s https://rdap.org/domain/example.com | jq '.status'
A serverTransferProhibited status means the registry set the lock, usually because of a dispute or investigation, and it cannot be removed from a registrar panel.
Example: taking a domain back from a web studio
A small hotel in Samarkand ordered a website years ago, and the studio registered example.com in its own account. The owner now wants control. First, check WHOIS: if the hotel or its director is listed as registrant, the owner can ask the studio to unlock the domain and hand over the code. The owner then enters the code at the new registrar and pays. For generic domains the old registrar has a few days to approve or reject, after which the transfer usually completes automatically. Avoid changing name servers or DNS during this time, and generate a new code once the transfer is done.
When the code is rejected
"Invalid auth code" errors are often copy mistakes: a trailing space, changed letter case, or confusing l, 1 and I. Paste the code rather than retyping it. Codes can also expire or be replaced, since some registrars generate a new one each time you request it. If in doubt, get a fresh code and use it immediately.
Keeping the code safe
Never send the code to social media chats, public groups or strangers offering to "check your domain". Scammers often pose as registrar or hosting staff asking for it "for a security check"; a real registrar never needs it from you. If you suspect a leak, regenerate the code and re-enable the transfer lock. Companies should tie domain access to a shared account controlled by management, not to one employee.
A note on .uz and other country-code domains
The EPP process above mainly applies to generic zones such as .com, .net and .org. In country-code zones, including .uz, transfers between registrars follow that registry's own rules and may involve extra confirmation, an application or owner verification. Before moving a .uz domain, ask your current registrar or support for the exact procedure.