Domain Transfer Lock: Why a Domain Won't Transfer and What to Do

Your domain won't transfer and you're getting an error message? See the difference between registry and registrar locks, the 60-day window, and the exact step-by-step fix for each.

7 min Updated 20 Nov 2026

You've clicked the "Transfer Domain" button and the destination registrar's panel rejects it instantly: Domain is locked or Transfer not allowed: clientTransferProhibited. Sometimes there's no error at all and you just get an email saying "transfer request denied." In both cases, the problem is almost always one of three things: the domain transfer lock, the 60-day window imposed by the registry, or an Auth/EPP code that was copied incorrectly. This article opens up exactly those three paths.

First, figure out which lock is on the domain

Two different things with similar names that people constantly confuse: the registry lock and the registrar lock. The first is imposed by ICANN and the TLD registry, the second is enabled by your current registrar. Both show up in WHOIS as the statuses clientTransferProhibited and serverTransferProhibited, and the difference is in the prefix: client means from the registrar side, server means from the registry side.

whois example.ir | grep -i "status"
whois example.com | grep -iE "status|transfer"

If the output has clientTransferProhibited, it's on you: remove the lock from the registrar panel. If you see serverTransferProhibited, the registrar can't do anything on its own and you need to open a ticket. To correctly read the rest of the strange WHOIS codes too, the complete guide to domain status codes in WHOIS lays out the order and meaning of each one.

Why the registry lock is seen more often on .ir domains

On .ir domains the transfer mechanism differs from .com; IRNIC usually handles transfers between registrars through its own panel with ownership verification, not simply with an EPP code. That means even when the lock is removed, if the ownership information in WHOIS doesn't match the registered documents, the request bounces back. I've seen this a lot in practice: the domain isn't locked, but the owner's email has changed and nobody updated it.

The 60-day window: a domain that was recently registered or transferred

ICANN has a strict rule: after a domain is registered, after every successful transfer, and after a change to the owner contact information (in some TLDs), transfer is not possible for 60 days. This window can't be bypassed with a ticket, a phone call, or money. The registry blocks it at the protocol level.

The sign is that WHOIS shows no lock, the EPP code is correct, but the destination registrar says Transfer prohibited: domain is within 60-day lock period. Check the registration date or last transfer date in WHOIS; if it's less than 60 days, the case is closed. The only thing you can do is not miss the expiration date and postpone the transfer until after the window ends.

One point that catches many people off guard: renewing a domain does not reset the 60-day window, but changing the owner information does in some TLDs. If you intend to both renew and transfer, transfer first, then renew; because the destination registrar usually adds a year to the validity and you won't pay twice.

The Auth/EPP code and what's actually being rejected

The EPP code is a case-sensitive string, usually 8 to 16 characters with symbols like ! and #. The biggest mistake I see is someone copying the code from an email and a trailing space comes along with it. The destination registrar doesn't strip that space and the result is Invalid authorization code, even though the code was exactly the right one.

The EPP code has an expiration. With many registrars, each time a new code is requested, the previous one is invalidated. If two people request a code from the panel at the same time, the first one is burned and the transfer request comes back with an authentication error. One person requests the code, uses it, done.

This is where they go wrong

The common mistake is removing the lock from the panel, immediately submitting the transfer request, and getting a lock error. Why? Because the WHOIS status is cached. The registry may return the old status for up to several hours and the destination registrar sees exactly that. The sign is this: the panel says the lock was removed, but whois still shows clientTransferProhibited. The solution isn't to wait; you need to understand TTL and WHOIS caching. The default registry cache value differs for different TLDs and is explained in TTL values in DNS: a guide to choosing the right number, which covers how to figure out where the cache is sitting. In practice, leave at least an hour between removing the lock and submitting the transfer request.

The fix, step by step

  1. Read the status in WHOIS and identify the client or server prefix.
  2. If it's client, turn off the transfer lock from the registrar panel and click the email confirmation.
  3. If it's server, open a ticket and write plainly "request to remove domain transfer lock"; no extra explanation needed.
  4. Check the registration date and last transfer. Less than 60 days? Wait.
  5. Get a fresh EPP code, copy it without spaces, and put it in the destination form right away.
  6. After submitting the request, open the transfer confirmation email from the owner's inbox (not the technical admin) and confirm. This email is usually valid for 5 days and if it's lost, the request is automatically cancelled.

If you're not sure whether the problem is DNS or the transfer, check the current records with DNS record lookup. Sometimes the domain has actually transferred and only the A records weren't set; in that case you don't have a transfer error, you have a resolve error. I've separated the difference between the two in a practical DNS troubleshooting guide: symptoms and the order to check records.

Which approach I choose

If your domain is less than 60 days old and you're in a hurry, my suggestion is: don't transfer. Waiting costs nothing, but a hasty transfer usually leads to renewing again and losing several days of access. The only condition under which I'd go for a transfer is if the current registrar is genuinely unreachable or refuses renewal; in that case the right path is complaining to the TLD registry, not trying again in the panel.

And one cost you should know: a domain transfer usually adds a year to the validity and charges the same amount as a renewal. If your domain is due for renewal this month, transferring means you pay the renewal fee once and move a year forward; if you've already renewed, you've effectively paid twice. Before anything else, look at the expiration date.

After the domain has transferred, move on to connecting it to the server. If you're hosting on Linux hosting, set up the A record and then SSL; I've written the order in connecting a domain to a VPS; a complete guide from A record to SSL. If you have dynamic subdomains, wildcard records and managing dynamic subdomains in DNS will save you a bunch of future headaches.

Frequently asked questions

Why is my domain locked but I don't see any lock in the panel?

Because the lock is on the registry side, not the registrar. Look for serverTransferProhibited in WHOIS. This status can only be removed by the TLD registry and you need to open a ticket through the registrar.

There's another case too: the registrar lock has been removed but the WHOIS cache is still stale. For up to several hours after the change, the previous status is returned.

When does the 60-day domain transfer window start?

From the domain registration date, from the completion date of the last transfer, and in some TLDs from the date the owner information was changed. This window can't be bypassed and no ticket shortens it.

Check the registration date in WHOIS. If it's less than 60 days, the only sensible thing is not to miss the expiration date and postpone the transfer.

Where do I get the EPP code and why is it rejected?

From the current registrar panel, the "Get transfer code" or "Auth Code" section. The code is case-sensitive and with each new request, the previous code is invalidated.

If you get Invalid authorization code, first check for extra spaces, then make sure nobody else requested a code at the same time.

After submitting the transfer request, how long should I wait?

Usually between 5 and 7 days, depending on the TLD and how quickly you open the confirmation email. If you don't open the confirmation email within its validity window, the request is automatically cancelled and you have to start over.

Throughout this time, your site should stay up. If you change DNS before the transfer completes, you may get several hours of downtime. Finish the transfer first, then move the records.

Was this page helpful?