A domain can be handed over in several different ways, and the right one depends on what actually needs to change. If the domain stays with the same registrar, you may only need to change the registrant or move the domain between accounts. If the new user wants the domain managed by another registrar, that is an inter-registrar transfer. These are separate procedures, so check the rules of the domain zone before you start.
Changing the registrant and transferring a domain are not the same thing
People often use “domain transfer” for almost any handover, but that can cause confusion. First decide what is changing: the registrant, the account that manages the domain, or the registrar itself.
Changing the domain registrant
The registrant is the individual or company under whose name the domain registration is held. If the domain is being passed to another person or business but remains with the same registrar, the relevant procedure is usually a change of registrant.
The registrar may ask both sides to confirm the change, provide new contact details, or submit documents required by the domain zone.
Transferring the domain to another registrar
An inter-registrar transfer moves the domain from one registrar to another. Many international domains require an Auth/EPP code and the transfer lock to be removed first.
The registrant does not necessarily change. A domain can move to another registrar while staying registered to the same person or company.
Moving a domain between accounts at the same registrar
A third situation is an internal account move. The registrar stays the same, while control of the domain is moved to another user account. An Auth/EPP code is normally not involved.
An account move, however, does not always mean that the registrant record has changed as well. Check that separately if ownership of the project is actually changing.
What to check before handing over a domain
Who is listed as the registrant
Make sure the registrant details are current and that the contact email still works. Confirmation messages for a registrant change or transfer may be sent there.
Do not assume that the person who knows the account password is automatically the registrant. Account access and registration data are two different things.
Domain status and transfer restrictions
Check the status in the registrar panel or through RDAP/WHOIS where the zone makes the information available. A clientTransferProhibited status means the domain is currently locked against transfer to another registrar.
Other restrictions may come from registry rules, a dispute, a court order, or a recent change to registration data.
Registration period and email access
Check when the domain expires. A complicated handover is better started before the last few days of the registration period, especially when documents or manual verification may be needed.
Rules of the specific domain zone
The procedure used for .COM should not automatically be applied to .UA, and the rules for a second-level .UA domain do not automatically apply to .COM.UA or other Ukrainian zones.
gTLDs are subject to ICANN policies and registry rules. Ukrainian domains follow the regulations of their particular domain zone.
How to transfer a domain to another RX-NAME user
If you need to hand a domain over to another person who also has an account on the RX-NAME website, in many cases this can be done without moving the domain to another registrar. The domain is transferred from one RX-NAME account to another using the recipient’s user ID.
To do this:
- The recipient creates an RX-NAME account if they do not already have one and provides their user ID.
- The current user opens the relevant domain in their account dashboard.
- In the domain management section, they choose the option to transfer the domain to another user and enter the recipient’s ID.
- Once the operation is confirmed, the domain appears in the new user’s account.
Because this transfer takes place within RX-NAME, an Auth/EPP code is not required. Some domain zones may still have additional requirements related to changing the registrant or confirming the handover. If the transfer option is not available in the account dashboard, it is best to check the procedure for that specific domain.
How to transfer a domain to another registrar
Check whether the transfer is allowed
For many gTLDs, an inter-registrar transfer may be unavailable during the first 60 days after registration or after a previous registrar transfer. A 60-day lock may also follow a change of registrant unless the registrar offered an opt-out before the change and it was used.
Country-code and specialist domains may follow different rules.
Remove the transfer lock
If the domain has the clientTransferProhibited status, it must be unlocked before another registrar can request the transfer. In many control panels this can be done directly; otherwise the registrar has to process the request.
The lock is a useful security feature, so it is normally sensible to enable it again once the relevant transfer work is finished.
Get the Auth/EPP code
Auth code, AuthInfo and EPP code are different names commonly used for the authorization code required to move many domains between registrars.
Treat it as sensitive. It should be provided to the gaining registrar when a genuine transfer is being carried out. It is generally not required simply to change the registrant or move a domain between accounts at the same provider.
Start the transfer with the new registrar
Submit the domain name and the Auth/EPP code if the zone requires one. If the domain is being moved to RX-NAME, the request can be started through the domain transfer page.
There is usually no reason to change DNS simply because the registrar is changing. Decide first where the website will stay and who will continue to provide DNS service.
Confirm the transfer
Depending on the zone and registrar, confirmation may be required by email or through an account panel. When the transfer is complete, make sure the domain appears with the new registrar and still uses the expected name servers.
How to re-register a domain to another person or company
If the registrar is staying the same but the domain is moving to another individual or legal entity, the registrant needs to be changed. This should not be treated as nothing more than editing a name and email field.
The registrar may require confirmation from both sides, updated contact data, identity or company documents, or other evidence required by the relevant zone. For some gTLDs, a registrant change can also trigger a 60-day restriction on a later transfer to another registrar.
If both the registrant and registrar are going to change, check the order before doing either step.
Special rules for .UA domains
Private second-level domains directly under .UA have their own rules. Registration is connected to rights in the corresponding trademark, so handing over an account password or replacing an email address is not enough.
When the registrant changes, the new registrant must meet the .UA requirements related to rights in the mark. The re-delegation procedure involves the current registrar and confirmation from both the current and future registrants; trademark documents may also be required.
These rules concern second-level .UA domains specifically. .COM.UA, .ORG.UA and other Ukrainian zones have their own policies.
What happens to the website, DNS, email and SSL
DNS and the website
Changing the registrant or registrar does not automatically take the website offline. If the name servers and DNS records remain unchanged and the existing DNS service continues to operate, there may be no interruption at all.
Problems usually appear when DNS is changed at the same time, or when the previous registrar’s DNS service ends after the transfer.
Business email
Email depends mainly on MX and related DNS records. If those records remain in place, transferring the domain should not by itself switch email off.
SSL certificate
A registrar transfer does not automatically revoke an SSL certificate. A new setup or certificate issue may be needed if the server, DNS, renewal system, or access to the account managing the certificate changes.
Hosting and website files
A domain and a hosting account are separate services. Moving the domain does not move website files, databases, mailboxes, or the server. If the whole online project is being sold or handed over, those assets need their own transfer plan.
When a domain cannot be transferred
An inter-registrar transfer may be blocked by clientTransferProhibited, the applicable 60-day rules after registration or a previous transfer for certain gTLDs, a Change of Registrant lock, a court order, or an active dispute.
A registrant change can also fail when the new party does not meet the requirements of the domain zone or when the required confirmations cannot be provided.
That is why “a domain cannot be transferred for 60 days” should not be treated as a universal rule for every domain and every kind of handover.
Common mistakes when handing over a domain
The most common mistake is mixing up a registrant change with a registrar transfer. That can lead someone to search for an EPP code when an internal move is enough, or to change registrant details before a planned registrar transfer and trigger an extra lock.
Do not share an Auth/EPP code with a buyer, contractor, or third party just in case. It is an authorization credential for registrar transfers.
Keep access to the contact email until the process is finished. It is also risky to change the registrar, DNS, and hosting at the same time without a migration plan.
When an entire website is being sold, decide separately who receives the hosting account, files, database, mailboxes, analytics, and other connected services.
What to check after the domain has been transferred
Once the process is complete, verify:
- who is now listed as the registrant;
- which account and registrar manage the domain;
- whether the new user has full access;
- which name servers and DNS records are active;
- whether the website and email still work;
- whether the contact email for renewal notices is current;
- whether the previous owner or contractor still has unnecessary access.
Only after these checks is the handover really complete.
Frequently asked questions about domain transfers
Can I transfer a domain to another person?
Yes. Depending on the zone and registrar, this may involve a change of registrant, an internal account move, or more than one procedure.
How do I change the owner of a domain?
Ask the registrar for the change-of-registrant procedure. The confirmations and documents required depend on the domain zone.
What is the difference between a domain handover and a registrar transfer?
A handover may mean changing the registrant or account. A registrar transfer specifically means moving the domain from one registrar to another.
Do I need an EPP code to give a domain to another person?
Not always. An EPP/Auth code is mainly used for transfers between registrars.
How long does a domain transfer take?
There is no single timeframe. It depends on the zone, the type of procedure, required confirmations, and the registrars involved.
Can a domain be transferred immediately after registration?
It depends on the type of transfer. For many gTLDs, moving to another registrar is restricted during the first 60 days after registration.
Will the website stop working after the domain is transferred?
Not necessarily. If DNS and hosting remain unchanged and continue to operate, the website may stay online without interruption.
How do I transfer a .UA domain to another owner?
For a second-level .UA domain, the registrant must be changed in line with the rules governing rights to the corresponding trademark. Ask the current registrar for the required confirmations and documents.
Leave a Reply