Domain transfers: from authorisation code to final checks

1. Clarify which service the transfer moves

A domain transfer changes the registrar that manages the domain. It does not automatically move website files, mailboxes or the database. If you are also moving your website, manage the hosting migration under a separate plan.

Changing nameservers or DNS records is also different from a transfer. You can point a website to new hosting without moving its domain to another registrar. List which provider hosts each existing service before you begin.

2. Check the domain's transfer conditions

Verify that you own the domain or are its authorised administrator, can access the registered email address, and that the domain has not expired. Some generic extensions impose transfer restrictions after initial registration, a previous transfer or certain changes of registrant. Do not assume every extension uses the same time limits and procedure.

Disputes, payment status, registration locks and special procedures for expired domains can affect a transfer. Ask the relevant registrar about the applicable rules for .tr and other country-code extensions. Do not leave it until the last day, as transfers can take longer than expected.

3. Prepare the lock and authorisation code

Check the domain's transfer lock in your current registrar's panel. Obtain the required EPP/Auth code; protect it like a password because it authorises actions on your domain. Do not include it in a general contact form, public message or screenshot.

Complete any additional verification or approval steps required by the registrar. Use only official channels when identity or authority verification is needed for security. If the domain belongs to your client, obtain written authorisation for the transfer.

4. Track the application and approvals

Enter the domain and requested details correctly in the transfer application. Check the total cost, tax information and whether the transfer extends your domain's term in the order summary. Assuming that every transfer adds a year is not valid for every extension or exceptional situation.

Monitor approval messages at your registered email address and the status in the portal. Check the spam folder too so you do not miss a pending verification. Do not enter account details before inspecting the domain of an approval link.

5. Maintain DNS and email continuity

Existing nameservers may remain unchanged during a transfer; however, if DNS hosting is tied to the old registrar account, confirm its continuation separately. Ending the DNS service can affect web and email access even if the nameserver names do not change.

Copy the existing zone's A, AAAA, CNAME, MX, TXT and any CAA records. If you use DNSSEC, check that the DS record is compatible with the new DNS service. If a DNS change is needed alongside the transfer, plan the timing of each step explicitly.

6. Check registration details after completion

• Does the domain appear in your new customer account?
• Are the registrant and contact addresses correct?
• Are the expiry date and renewal settings as expected?
• Have nameservers and DNS records been preserved?
• Have website, HTTPS and email tests passed?
• Is the transfer lock enabled again for security?

Do not close the old DNS service until these checks are complete. If there is a problem, submit a support request with the domain and the stage where the transfer stopped; share the authorisation code only in the secure area required for the transaction.

Identify the stage if a transfer is not progressing

For status codes, see the Whois / RDAP explanations; for generic extension policies, refer to the ICANN Transfer Policy. Verify the .tr process separately with TRABİS and the authorised registrar; do not apply every generic-extension time limit unchanged to .tr.