

A domain transfer code is a private, domain-specific authorisation code that you give to your new registrar when you move a domain name away from your current one. It is also called an EPP code, auth code or AuthInfo code. You get it from the registrar where your domain is registered today, either in your account dashboard or by asking their support team.
This guide shows you how to get the code, what to do if it never arrives, and why a transfer can still be rejected when the code is correct.
The code proves that the transfer request is authorised. Your new registrar submits it to the registry that runs the domain extension, and the registry checks it. If the code is invalid, the request cannot be verified and the transfer will not go through.
The code is not proof of ownership. Ownership is shown in the registrant details of the domain. Think of the code as a one-time permission slip rather than a title deed. Under ICANN’s rules, every code must be unique to its domain and generated securely.
Yes. They all mean the same code; registrars simply use different names for it. You may see:
In this guide we call it the transfer code.
EPP status codes describe the current state of a domain; they are not another name for the transfer code. Values such as clientTransferProhibited that you see in an RDAP/WHOIS lookup belong to this group. For .com, .net, .org and other generic extensions, registration data is now served through RDAP, which has replaced WHOIS; most lookup tools show both.
| Transfer code (auth code) | EPP status code | |
|---|---|---|
| What it does | Authorises the transfer | Shows the domain’s current state |
| Where you see it | Only in your dashboard or an email sent to you | In any public RDAP/WHOIS lookup |
| Example | A random string of letters, numbers and symbols | ok, clientTransferProhibited, redemptionPeriod |
| Who you share it with | Only your new registrar | Not secret |
No, they are two separate steps. The transfer lock (registrar lock) is a setting that stops anyone moving your domain without permission. In an RDAP/WHOIS lookup it usually appears as clientTransferProhibited.
If the lock is on, the transfer will be blocked even with the correct code. So switch the lock off first, then get your code. Some registrars combine both into a single “Transfer out” button. Locks that apply because of a legal dispute or the 60-day rules are different: you cannot remove those yourself, and we cover them below.
This guide covers moving a domain to a different registrar. That is the change that needs a transfer code; the others follow their own processes.
| Change | What changes | Transfer code needed? |
|---|---|---|
| Domain transfer | The registrar that manages the domain | Yes |
| Account move (push) | The customer account at the same registrar | Usually not; the registrar’s own process applies |
| Change of registrant | The legal holder of the domain | No; it has its own approval process |
| Hosting migration | Website files, databases and mailboxes | No; the domain registration stays where it is |
You get the code from your current registrar; your new registrar cannot create it for you. Menu names vary, but the process usually looks like this:
No such option? Open a support ticket and ask for the code. For ICANN-governed extensions such as .com, .net and .org, a registrar that does not offer self-service must provide the code within five calendar days of your request. It must also give you a way to remove any lock you are entitled to remove within the same period. Locks imposed by the 60-day rules or legal proceedings are outside this rule.
When copying the code: codes are usually case-sensitive, so check for spaces at the start or end. How long a code is, how long it stays valid and whether it can be reused all depend on the registrar and the extension.
Once you have your code, you can start the transfer on Atak Domain’s transfer page in a few minutes.
Moving several domains? Use the bulk transfer box: enter one domain per line, followed by a space and its code.
One common reason is that the email address it was sent to is no longer in use. Check these points in order:
Still nothing? Ask your current registrar for the code in writing and note the date. For an ICANN-governed extension, if you have not received it within five calendar days, you can file a complaint with ICANN. A billing dispute alone is not a valid reason to withhold the code.
Start with the simplest causes: a copying mistake, a code that has since been reset, or a code for a different domain.
A correct code does not help if the domain itself is not eligible to move. The most common blockers and fixes:
| Problem | What it means | What to do |
|---|---|---|
| Transfer lock on (clientTransferProhibited) | The lock has not been switched off | Remove it in your current registrar’s dashboard or ask support |
| Domain registered less than 60 days ago | The 60-day window after first registration has not passed | Add 60 days to the creation date in RDAP/WHOIS and wait |
| Transferred in the last 60 days | The lock after the previous transfer still applies | Add 60 days to the date the last transfer completed |
| Recent change of registrant | A 60-day lock may have been applied after the change | Ask your registrar when the lock ends |
| Required verification not completed | You have not completed a step your new registrar asked for | Find their email and finish the steps. Ignoring the notice from your old registrar does not, on its own, stop the transfer |
| redemptionPeriod | The domain has entered the deletion process | Restore it with your current registrar first, then transfer |
| UDRP, court order or transfer dispute | A legal or policy lock applies | A normal transfer is not possible until that lock is lifted |
| Previous or current term unpaid | The registrar may refuse in this case; unpaid future terms are not a valid reason | Settle the unpaid term and restart the transfer |
If your current registrar rejects the transfer, it must tell you and the new registrar why. Ask for the reason, and the date any lock ends, in writing.
The 60-day lock does not apply to every domain; it is triggered by specific events. The rules below come from ICANN’s Transfer Policy and cover generic extensions such as .com, .net and .org.
| Event | Rule | Exception or note |
|---|---|---|
| First registration | The registrar may refuse a transfer within 60 days of registration | Counted from the creation date in RDAP/WHOIS |
| Previous transfer | The registrar may refuse within 60 days of a transfer to another registrar | May not apply when both registrars agree to move it back |
| Change of registrant | A 60-day lock applies after a change to the name, organisation or email | Your registrar may let you opt out before you make the change |
| Normal renewal | Not a reason for a 60-day lock on its own | Check your registrar’s terms for any extra conditions |
Planning a transfer? Update your registrant details after the transfer completes, not before, so you don’t trigger an avoidable lock.
ICANN is reviewing these rules, and periods and terms may change when new rules take effect. The information in this section reflects the policy published on the date shown at the end of this guide.
It depends on which stage the domain has reached.
Country-code extensions (ccTLDs) set their own rules, and ICANN’s 60-day locks do not automatically apply to them. Three examples:
Not sure how your extension works? Enter the domain on our transfer page; the requirements for that extension are shown before you pay.
Transfers to Atak Domain are usually completed within 5–7 days. For ICANN-governed extensions, if your current registrar does not object within five calendar days, the registry completes the transfer automatically.
Don’t mix this up with the five days your registrar has to give you the code. That period runs before the transfer starts; this one runs after it has started.
What affects the timing most:
Getting the code itself is normally free; you pay the registrar you are moving to. For most generic extensions, the transfer adds a year to your registration, up to a maximum of 10 years in total. Some country-code extensions do not add any time.
You can check current transfer prices for each extension on our Domain Transfer page.
As long as your nameservers and DNS records stay the same, your website and email usually keep working throughout the transfer. A transfer changes who manages the domain; it does not move your hosting or email service.
The risk comes when your DNS records live on your old registrar’s free DNS service, which may stop when the domain leaves. Before you start:
Your transfer code works like a key to your domain, so share it only with the trusted registrar you are moving to.
Before you start:
Got your transfer code? Enter your domain to see the transfer price and terms for your extension, then start the transfer in a few minutes.
Code not arriving, or transfer rejected? Sign in and go to Support › New Support Request, and we’ll look into it with you.
Usually not. Privacy protection does not block a transfer on its own. Some registrars may ask you to switch it off temporarily so their emails reach you. What matters is that you can access the registrant email address.
It depends on the registrar and the extension. Some codes stay valid for a long time; others expire after a set period (30 days for .de, for example) or once a transfer completes. The safest approach is to start the transfer soon after you get the code.
Yes, a normal renewal does not block a transfer. But if the domain was auto-renewed at expiry and you transfer it shortly afterwards, you may lose that renewal year. According to ICANN, when a domain is transferred during the 45-day auto-renew grace period, the auto-renewal year is cancelled and the transfer adds only one year. In other words, you gain one year, not two. This can vary by registry, so check with your current registrar first.
Usually not. Your remaining time is kept, and for most generic extensions a year is added on top, up to 10 years in total. A transfer straight after an auto-renewal is the exception (see the previous question).
No. The transfer code only changes the registrar that manages the domain. To change who owns it, you need a separate change of registrant.
Usually yes, as long as it has not completed. Contact your new registrar’s support, or reject the transfer in the notification email from your current registrar.
You’ll receive a confirmation email when it finishes. You can also run an RDAP/WHOIS lookup and check that the “Registrar” field shows the new registrar.
Last reviewed: 9 October 2026. This guide is based on the rules published on the official ICANN, Nominet, DENIC and TRABİS websites on that date.