Before moving a domain to a new provider, you must confirm its status is unlocked and eligible. This checklist helps you verify WHOIS details and secure the necessary authentication code to prevent transfer failures.
Preparing Your Domain for Transfer
This is a hypothetical situation: an independent site owner is preparing a modest informational site and wants to move the domain record between registrars. On the desk are a registration receipt, a provider dashboard printout, and a short transfer worksheet the owner made for this exercise.
The worksheet has three columns: Item, Where to Confirm, and Ready When. The owner fills them with made-up entries to see how they fit. First row: “Registrant contact email,” checked in the account profile and the public contact record, ready when both show the same working address the owner can open. Second row: “Transfer lock state,” checked in the control panel’s domain settings, ready when the lock is shown as off and the change is saved. Third row: “Authorization code,” requested from the losing provider’s transfer section, ready when a code appears and its expiry note is copied beside it. A fourth row covers “Public contact record,” ready when the organization name, country, and postal code match the receipt rather than an old address.
The owner drafts a small form for the move itself, with fields for domain name, current registrar, account email, unlock confirmation time, authorization code receipt time, and code expiry. Two invented records show the shape. One reads “garden-notes-example” with the current registrar listed as a mailbox provider, unlock confirmed and code received on the same afternoon, and an expiry noted two weeks later. The other reads “harbor-list-example” with unlock confirmed but no code yet, so the status column stays open and no transfer request is placed. These are labels the owner chose for practice, not names taken from a live account.
One choice needs a reason: the owner sets the public contact record to a role address rather than a personal inbox, because the transfer messages and the public record should point to the same place that will still exist after the move; a personal address that changes with a job would split those two threads. Another choice is to write the code’s issue time and expiry on the worksheet instead of relying on memory, since the code is time-limited. The point of the sheet is to make each item’s state visible before any request is sent.
Verifying Eligibility via WHOIS Status
Before transferring a domain to Alibaba Cloud, its status must be ok or active. A WHOIS lookup is the stated way to confirm this, and the domain must not be in a restricted state such as clientTransferProhibited (registrar transfer lock) or serverTransferProhibited (registry transfer lock).1
The same WHOIS check covers timing: the registration date must be more than 60 days earlier, and the expiry date must be more than 15 days away but under 10 years. For .hk domains, the expiry date must be more than 90 days away.1
You can take your transfer worksheet and add one row for each WHOIS status field you intend to read, because status codes are the first place a mismatch between your receipt and the live record tends to show. For a working example, the owner might write “Domain Status” in the Item column, “registrar WHOIS lookup” in Where to Confirm, and “shows ok or active with no clientHold or pendingTransfer flags” in Ready When. That filled row is a demonstration only; your own entries can name whichever statuses you decide matter for your case.
When the same worksheet has to serve both a current announcement and an archived one, the fields stay put while the values change. Suppose the owner adds a “Record State” column: for a live notice the value might read “current, verified this week,” and for an older archived notice “superseded, kept for reference.” The status row follows the same split, so a present entry notes an unlocked state and a historical entry notes what the record showed at that time without implying it still holds.
A second choice worth recording is which status flag would make you pause. The owner might note “pendingTransfer seen” beside a row and decide to wait rather than proceed, then write the reason in a short note column. Keeping that reason next to the item lets you revisit the decision later instead of relying on memory.
You might also compare the registrant fields in the dashboard printout against the public record and mark any difference as “needs correction” before moving on. The point is to leave yourself a clear record of what you checked and what you chose, so the next step in the transfer follows from written evidence rather than assumption.
Checking Registration Age and Expiration Limits
The registration age limit is stated directly: a domain must have been registered for more than 60 days before a registrar transfer can be submitted; if it was registered less than 60 days ago, you wait until the 60-day mark.2
The expiration window is equally specific. The source says the time remaining before the domain's expiry date must be greater than 15 days and less than 10 years. It also applies a renewal ceiling: a domain whose renewal term has already reached the maximum of 10 years is not supported for transfer.2
Separately, the source notes that a domain renewed recently at the original registrar should be transferred only after 45 days have passed since that renewal succeeded; otherwise, under registry rules, the original registrar's renewal fee is refunded and the renewal year is not added.2
You can take your transfer worksheet and add a registration-age line and an expiration line, then fill them from your own receipt and dashboard printout rather than from memory. For a made-up example, the owner writes “age: created two years ago this month” and “expiry: eleven months out” beside the domain name. The point is to see whether the two sources agree and to leave yourself a note about which date you would trust if they do not.
If your transfer window feels tight against the expiry date, you might note the gap in plain words instead of calculating anything exact: “about three weeks between my planned move and renewal.” That note belongs in the same row as the expiry date, so the reader of your worksheet sees why the timing matters. You can then decide whether to renew first or move first; either is a legitimate choice, and recording the reason keeps the decision visible.
You might also add a short “limits” question to the worksheet: would any status or date stop the move in your view? Write your own answer, such as “renewal due within thirty days puts the move on hold,” and treat it as a personal threshold rather than a rule. This gives you a record of the reasoning you can revisit when the dates change.
Disabling Locks and DNSSEC Before Transfer
For the transfer-lock check, the source describes opening the domain list in the console, clicking Manage for the target domain, and entering the domain security page. There you confirm that clientTransferProhibited is turned off.3
The eligibility check also excludes certain registrar- or registry-level statuses. A domain must not be in serverTransferProhibited (registry lock) or clientHold (registrar suspension of resolution), nor in clientHold or serverHold, which the source directs you to troubleshoot through its lock-removal guidance first. Disputes, arbitration, or court restrictions must likewise be cleared before transfer.3
The source does not describe a DNSSEC step for this transfer. Its only related note is optional: if you plan to migrate resolution records, change the DNS settings to the new provider's servers before transferring.3
You can extend your own transfer worksheet with a short “lock and security” block before you request the authorization code. Add rows for the transfer lock state, the registrar lock setting, and whether DNSSEC is enabled, and fill each from the dashboard printout you already have. For example, a hypothetical entry might read “Transfer lock: on per dashboard, date noted; action: switch off, then note off.” The point is to see your own record of lock state side by side rather than rely on memory.
If your printout also shows a DNSSEC indicator, you might decide whether to leave it on or turn it off during the move. A hypothetical owner with no signed zone could write “DNSSEC: not in use, nothing to remove,” while another who sees it active might note “DNSSEC active, decide before code request.” Either result is a valid personal choice; record which you picked and why in one plain line.
You can also choose the order of steps in your own notes: unlock first, then confirm the code request, or reverse the sequence if it suits you better. As a before-and-after example, “Draft: unlock and transfer” might become “Draft: note lock state, then request code after lock is off.” Which phrasing you keep is up to you.
Obtaining the Authorization Code Securely
In Cloudflare 's dashboard, open the Manage Domains page, find the domain to be transferred, and select Manage. Under Configuration, choose Unlock and then Confirm and Unlock. After unlocking, copy the auth code that Cloudflare generates and use it at the new registrar; Cloudflare notes the same code may be called EPP in some systems. If the code is lost, Cloudflare says it can be regenerated with the Regenerate button, or by locking the domain and repeating the steps.4
Cloudflare also warns that anyone with super-admin or admin permissions for a zone can manage its domains, including unlocking domains and obtaining authorization codes for transfers to other registrars, so account roles should be assigned carefully.4
You can take your transfer worksheet and add an authorization-code row that records two things: the channel you used to request the code and the date it arrived. A hypothetical owner writes “requested through account dashboard, code received same day” as a made-up entry, then leaves the value column blank until the code actually appears. This keeps the code itself out of the worksheet while still showing whether the request is pending.
You might also decide where the code should live once it arrives. One option is to store it in a password manager entry tied to the domain name; another is to print it and keep the page with the registration receipt. The owner in this example chooses the password manager, reasoning that a printed page could be misplaced near the desk. Either choice is yours to make, and noting the reason beside the row helps you remember it later.
Consider writing a short note for the handoff moment: who requested the code, when, and where it was placed. A sample entry reads “code requested by site owner, 14 March, stored in password manager.” If you request a fresh code later, add a second line rather than overwriting the first, so the worksheet shows the sequence of requests. This is a record you keep for yourself, not a step you owe anyone else.
Submitting the Transfer Request at New Registrar
At the new registrar, log in to the official website and locate the domain transfer or "Transfer Domain" entry point. Follow that registrar's instructions to enter the domain name you want to transfer and the authorization code obtained from the losing registrar, then complete payment; the original text notes this step usually involves paying a one-year domain renewal fee. Afterward, check your email for a confirmation message from the receiving registrar. This describes the documented submission step at the new provider, not a guarantee that every transfer will proceed the same way.3
Once your authorization code has arrived and your lock notes are settled, you can prepare the new registrar's request as the last local step rather than as something already sent. Reopen your transfer worksheet and add a short “request draft” block beneath the code row. Separate fields work better than one blob: domain name, current registrar, account email at the gaining side, unlock confirmation time, code received date, and a free-text note. Fill each with your own values, for example: domain name written exactly as it appears on your receipt; current registrar as the name on your dashboard printout; account email as the address you control and can open today; unlock time as the moment you recorded; code received date as the day it landed; note reading “decide whether to draft the request now or after the expiry buffer is checked.”
You might then write the request text in plain words before touching any form, so the sentences you will paste are yours. A sample draft could read: “I would like to move the domain record listed above to this account. The name is unlocked, and I have the authorization code in hand. Please tell me if any field is missing.” Keep the draft beside the worksheet and mark it “not yet sent” until you choose otherwise.
Consider a second check before submitting: read the gaining account email aloud from your printout and compare it with the worksheet entry, marking “match” or “differs” in your own words. This stays a personal note, not a claim about what any provider requires.
Frequently asked questions
What can I add to my transfer worksheet for each WHOIS status field I plan to read?
You can take your transfer worksheet and add one row for each WHOIS status field you intend to read, because status codes are the first place a mismatch between your receipt and the live record tends to show. For a working example, the owner might write “Domain Status” in the Item column, “registrar WHOIS lookup” in Where to Confirm, and “shows ok or active with no clientHold or pendingTransfer flags” in Ready When.
What lines can I add to my transfer worksheet and fill from my own receipt and dashboard printout?
You can take your transfer worksheet and add a registration-age line and an expiration line, then fill them from your own receipt and dashboard printout rather than from memory. For a made-up example, the owner writes “age: created two years ago this month” and “expiry: eleven months out” beside the domain name.
What can I extend my transfer worksheet with before requesting the authorization code?
You can extend your own transfer worksheet with a short “lock and security” block before you request the authorization code. Add rows for the transfer lock state, the registrar lock setting, and whether DNSSEC is enabled, and fill each from the dashboard printout you already have.
域名转入阿里云-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎
域名转入和转出相关FAQ-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎
阿里云域名转出-域名(Domain)-阿里云帮助中心 . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎ ↩︎
Transfer domain from Cloudflare to another registrar · Cloudflare Registrar docs . Retrieved 2026-11-19. ↩︎ ↩︎