You've logged into your current registrar's panel, clicked the Transfer button, and now you're staring at a page that says "Pending" — or worse, the confirmation email never arrived and you have no idea what state your domain is in. If your domain is stuck somewhere along this path, the problem is almost always one of four things: the domain is locked, there's no EPP code, the email wasn't confirmed, or you're waiting pointlessly for DNS propagation, which isn't even part of the transfer.
A domain transfer means moving the registration ownership of a domain from one Registrar to another. This is different from changing DNS records. If you just want your site up on a new server, you don't need to transfer the domain; just change the A record. Do the transfer when you want renewal, support, and domain management all in one place and one panel.
Before Anything Else: Three Things to Check
There are three prerequisites, and if any one of them isn't met, the transfer request is either rejected immediately or fails silently.
- The Registrar Lock must be off. This lock is on by default and blocks any transfer. In the registrar panel, look for an option like
Transfer LockorClientTransferProhibited. - At least 60 days must have passed since registration or the last transfer. This is an ICANN restriction and there's no way around it. If you registered the domain this month, you have to wait.
- The domain's administrative email must be accessible. The confirmation code goes to the address listed in WHOIS, not to your account's email.
To see whether the lock is on, use the command line:
whois example.com | grep -i "status"If you see clientTransferProhibited in the output, the lock is on. If you see ok or active, the path is clear. One practical note: some registrars turn the lock off in the panel but it doesn't update in WHOIS for several hours. If you submit a request right after turning off the lock, it may be rejected.
How to Get the EPP Code and Why They Sometimes Won't Give It
The EPP code, or Auth Code, is an 8-to-32-character string that proves you own the domain. Without it, the new Registrar can't send the request to the Registry. You can only get this code from your current registrar's panel, and no one else — including ServerNet support — has access to it.
Here's where people go wrong: the user copies the EPP code from the panel, and because the code has a trailing space or hidden character, it gets rejected in the transfer form with an Invalid authorization code message. Paste the code into a plain text editor, remove any extra spaces, then copy it. If the code contains uppercase and lowercase letters, enter it exactly as-is.
Some registrars don't show the code in the panel and say "open a ticket." This is legal but can take several days. If the current registrar doesn't provide the code after 5 business days, follow up via the ICANN complaint form, or for .ir domains, through IRNIC. For Iranian domains, the details of this path are covered in the complete guide to registering and managing .ir domains with an IRNIC ID.
What Happens After You Submit the Request
When you enter the EPP code in the new Registrar's panel, a timeline begins that most people guess wrong.
| Stage | Approximate Time | Who Acts |
|---|---|---|
| Request sent to Registry | A few minutes | New Registrar |
| Confirmation email to administrative email | Immediately to 24 hours | Registry |
| Approval Window | 5 days | Domain owner |
| Transfer completion | 1 to 5 days after approval | Registry |
The confirmation email comes from the Registry, not the new Registrar. If you don't confirm that email, the transfer is automatically cancelled after 5 days and you have to start over. This email usually lands in spam. If nothing arrives after 24 hours, first check your Spam folder, then make sure the email address in WHOIS is the one you think it is.
During these five days, the current registrar can veto the transfer. They have that right and in practice they use it, especially if you have an outstanding invoice. Before starting, clear any balance on the old account.
Domain Transfer Is Confused with Changing DNS
This is the most common misunderstanding. The user transfers the domain, their site goes down, and they think the transfer broke something. In reality, the transfer doesn't touch DNS records. The nameservers stay the same as they were, unless you change them yourself.
If your real goal is to get the site up on a new server, a domain transfer isn't necessary. Just change the A record to the new server's IP. The correct order for this and SSL tips are explained in connecting a domain to a VPS; a complete guide from A record to SSL. After the change, you can use DNS record lookup to see from which point in the world the new record is visible.
One real number that catches many people off guard: if your A record's TTL is set to 86400 seconds (24 hours), the DNS change won't take effect for some users for a full day. Before any move, reduce the TTL to 300 seconds and wait a day. Once things are stable, you can raise it again. The details of this behavior are covered in what is DNS propagation and why does it take time? A complete guide to TTL and caching.
The Cost Nobody Mentions Upfront
In most TLDs, a domain transfer comes with a free one-year renewal, but this "free" isn't without strings. When you start the transfer, the domain's current expiration date is locked, and if the transfer fails, it may stay in a pending state for several days. If your domain is less than two weeks from expiring, don't transfer; renew first, then transfer. Transferring a domain that's fallen into the expiration window is many times more troublesome and sometimes reaches the Redemption stage, whose recovery cost is separate. The exact steps for this situation are described in domain renewal; a complete guide to expiration stages and domain rescue.
The second hidden cost: during the transfer, you can't change the nameservers. If you want to both transfer the domain and move the site to a new server at the same time, do these two things one after the other, not simultaneously. First move the DNS, make sure the site is stable, then start the registration transfer.
Which Should I Choose: Transfer or Just a DNS Change?
If you just want the site up on new infrastructure and you're happy with your current registrar's panel, choose the DNS change. It's faster, lower risk, and your site won't go down for even a minute.
Choose the transfer when you want everything in one place: domain, hosting, and SSL managed in a single panel so renewals don't get forgotten. If you have several domains and management has become scattered, this is a sensible decision. For sites hosted on shared hosting, a Linux host with a domain management panel gives you that same integration, and you won't have to visit multiple panels for every renewal.
Before starting any transfer, read this checklist once:
- Turn off the domain lock and wait 2 hours.
- Get the EPP code and remove any extra spaces.
- Make sure the WHOIS email is accessible and that you're checking Spam.
- Clear any balance owed to the previous registrar.
- If less than 14 days remain until expiration, renew first.
After the transfer is complete, the first thing you should do is compare the DNS records with what they were before. If something has shifted, the practical DNS troubleshooting guide: symptoms and the order to check records shows the correct order of investigation. To register a new domain, you can also start with domain search and registration.
Frequently Asked Questions
How long does a domain transfer take?
Normally between 5 and 7 days. Five of those days are the approval window set by ICANN and can't be shortened, unless the current registrar approves earlier. If you confirm the email quickly, it's usually done by day six or seven.
What happens if I don't see the transfer confirmation email?
After 5 days the transfer is automatically cancelled and the EPP code becomes invalid. You'll have to submit a new request and get a new code. First check your Spam folder and Promotions tab, then make sure the email address registered in WHOIS is one you can access.
Does a domain transfer cause site downtime?
No, as long as you don't change the nameservers at the same time. A registration transfer doesn't change DNS records, and the site keeps running on the same server. Downtime usually happens when the user also moves the DNS at the same time and has a high TTL.
Why is my transfer request rejected with an Invalid authorization code error?
It's almost always due to a space or hidden character in the copied code. Paste the code into a plain text editor, check the beginning and end, and copy it again. If it's still rejected, ask the current registrar for a new code; some invalidate the code after every failed attempt.