This article outlines the specific checks required to ensure a smooth domain transfer-out process, focusing on auth-code validity and security locks.
Preparing for Domain Transfer Out
As a hypothetical illustration, imagine a domain owner who has a short list of names she thinks she may release and a folder of notes she has kept herself. She opens a plain document and writes a heading: “Transfer-out check sheet — one row per name.” Into the sheet she types three column groups that she can fill in without leaving her desk: the authorization code entry, the lock status entry, and the final decision line. The first row is an invented name, harbour-lamp.example, which she records with the code note “requested from the current registrar, stored in the password manager, six-day expiry marked.” Its lock field reads “registrar transfer lock: on — must be lifted before the code is used.” Her decision line says “hold; unlock only after the destination account is confirmed.” The second invented row, cedar-map.example, carries the note “code received once and already expired; request a fresh one” and a lock field that says “client transfer prohibited: on.” Her decision here is “wait,” because she wants the fresh code and the unlock to happen in the same sitting. A third candidate name, quiet-orchard.example, is listed only as a title in a separate “unsure” table, with no code and no lock entry, so it stays out of the action sheet entirely.
She also drafts a short instruction page for herself, titled “What I check before I press anything,” with four lines: whether the domain has been registered or transferred within the last sixty days; whether the registrant contact address in the record still matches the one she can reach; whether the lock is a registrar lock or a registry-level one; and where she saved the code and when it expires. She writes a sample record beneath the page — “example row: name, current registrar, lock type, code date, decision” — and fills nothing else. These notes are her own working examples, written to show how the sheet would be organised rather than to report any completed request. She keeps the sheet open beside the registrar page so that every field she intends to check has a place to land before she acts.
Checking Update Prohibition Locks
Tencent Cloud's domain transfer-out rules list the update prohibition lock as a separate condition: the domain must not have this lock enabled. If it is enabled, the page says to disable it before transferring the domain out. This appears alongside, but distinct from, the transfer prohibition lock, which is also checked and disabled if needed.1
The page frames these as requirements the domain must meet before transfer, and states that all listed requirements must be satisfied. Keep the update prohibition check separate from auth-code and other status checks when reviewing readiness.1
For the update-prohibition check, you can work from your own transfer notes rather than from a live console: list each domain you are considering releasing alongside the lock status you have recorded for it and the date you last confirmed that status. A simple column layout may help, with fields such as domain, recorded lock state, date recorded, and next action. A filled example might read: example-name.test, “update prohibited — confirmed by my registrar note,” date recorded as the day you saved the note, next action “recheck before requesting the code.” You might treat that entry as your baseline and mark it clearly as unverified until you review the page yourself.
The same fields can serve two kinds of entries in your own record. For a current entry, the date recorded and the lock state reflect what you saw most recently, so the next action is usually to confirm the entry still matches before you act. For an archived entry, such as a domain you released last year, the same fields hold the status as it stood then, and the next action becomes “treat as historical; do not reuse for a new request.” Keeping both under one heading with a status label helps you avoid copying an old “unlocked” note into a fresh decision.
You can also keep a short comparison note beside each row, showing the wording you saw on the page and the wording you wrote in your own summary. If those two drift apart, consider revising your summary before you rely on it.
Verifying Auth-Code Validity Period
Tencent Cloud's Auth-Code page states that a domain auth-code is valid for five days. After obtaining the auth-code, the page advises submitting the domain transfer-in at the new registrar within that validity period as soon as possible; otherwise, a new auth-code must be obtained.2
The page does not describe any way to check an auth-code's expiry date before submitting, so under this source the practical check is the date you received the code. The page also says the original registrar usually sends the auth-code by email after verifying the domain identity, and that the code is needed from the original registrar.2
For the auth-code validity step, you can work from the same notes page rather than a live registry view. Add four fields: the code's stated issue date, its stated expiry date, the date you last read the entry, and a one-line note on whether the code is still inside that window. If your notes only recorded “code received” without a date, that gap is the thing to resolve before treating the code as usable.
As a worked example of the format, a current entry might read: stated issue date 3 March, stated expiry 2 April, last read 20 March, note “still inside window as of this reading.” The same four fields applied to an archived entry from an earlier transfer might read: stated issue 14 January, stated expiry 13 February, last read 2 February, note “window closed; code treated as spent.” Keeping both side by side shows whether your habit is to record dates at all, and where you have been relying on memory instead.
You might also mark the source of each date in a fifth short field, since a date you copied from a page and a date you inferred from your own calendar are not the same kind of record. A simple value such as “shown by the code display” or “noted from my own earlier note” is enough. You can then decide which entries need a fresh reading before any transfer request and which are simply historical context.
Confirming Registrar Transfer Restrictions
Verify any 60-day inter-registrar transfer lock before relying on a transfer-out request. The relevant rule states that under ICANN's Transfer Policy, if the 60-day inter-registrar transfer lock is enabled when a domain name's information is modified, that domain name cannot be transferred to another registrar within 60 days. The same page lists domain information modification as the related operation.3
You can take one domain name from your shortlist and write a registrar-restriction note beside it before taking any other step. The note could hold four self-chosen fields: registrar shown on your own record, lock state as you last read it, stated unlock or transfer-prohibition wording, and the date you read it. For a name you still hold, an example entry might read: registrar shown on my note, lock state “client transfer prohibited,” wording “contact us to remove transfer lock,” read 12 May. Treat these as entries you wrote for yourself, not as confirmed facts about the registry.
For a name you are considering releasing, the same fields can describe what you were told rather than a live check. An example might read: lock state “unlocked as stated to me,” wording “transfer can proceed after 60-day hold,” read 3 June. You might also add a fifth field for where each statement came from, since wording quoted from a page and wording you paraphrased from a conversation are not equal evidence.
Consider keeping a short comparison note beside each row: the wording you saw and the wording you wrote yourself. If they differ, mark the row as needing a re-read rather than resolving the difference by assumption. You can choose to leave any row blank until you are ready to fill it; the point is to see clearly which restrictions remain unverified before you act.
Reviewing Email Contact Accuracy
Before requesting an auth-code, the documented transfer-out flow asks you to check the email address shown on the Domain Transfer Out page, read and agree to the Notes for Domain Transfer Out, and then click Get Auth-Code. The same page states that the auth-code is sent to the email address specified in the domain information, so it is worth confirming that address can receive mail normally before getting the code.4
If the email address turns out to be incorrect, the documented remedy is to click Cancel Transfer Out, modify the owner information, and then get a new auth-code. If the confirmation instead shows the auth-code was sent successfully but no message arrives, the page offers a Resend option.4
Take one saved notification from your own transfer folder and mark where the receiving mailbox was recorded, so you can later compare it with what you believe the account holds. You can do this without opening the registrar site: copy the address exactly as it appears in the saved message, note its date, and add a short line saying which mailbox you would expect messages about that domain to reach.
When two versions disagree, you might set them side by side rather than deciding immediately. In a worked example, one note reads "renewal reminder, 14 May, received in the work mailbox" while your newer note says "transfer-out messages should go to the personal mailbox." Choosing which one to trust is your call; if neither settles it, mark the row as unresolved and keep both entries.
You could also add a field for messages you cannot confirm, such as "confirmation email not yet located." Treating that as a gap in your own record, rather than a conclusion about the domain, keeps the check honest.
For a current entry, one filled example might read: expected mailbox, personal; last confirmed from, saved message dated 14 May; status, matches. An archived entry might read: mailbox recorded, work; source, old reminder; status, superseded. The same three fields can describe both, and you can choose which date to show first so the older one does not look current by accident.
Handling Agent Refusals
If a domain was purchased from a registrar agent such as www.net.cn or www.west.cn and that agent refuses to provide an auth-code, the documented path is to complain to the registrar, such as www.net.cn. If the registrar also refuses to cooperate, the next step is to complain to registries such as ICANN and CNNIC.2
The same page notes that under the applicable ICANN Domain Transfer Policy, the original registrar shall not reject, restrict, or charge for domain transfers for any reason. If the original registrar hinders the transfer or charges fees, a complaint can be made to ICANN.2
If an agent declines to release the authorization code, you can treat the refusal as a prompt to record what was said before deciding your next move. In your own notes, write the date of the exchange, the reason given in the agent's own wording, and the exact lock state you had recorded beforehand. For example: refusal date 18 April, reason “account review pending,” lock state “transfer prohibited,” last read 16 April. Keeping the reason in the agent's phrasing helps you spot whether it points to something you can verify yourself, such as an unpaid balance or an unresolved contact detail, rather than a vague delay you cannot act on.
You might also prepare a short question to send back, asking which specific condition must change before the code can be issued, and note the answer beside the refusal. If no clear condition comes back, consider marking the row as open and setting it aside rather than pressing repeatedly. When you revisit your folder later, compare the new wording with the earlier entry; a changed reason is worth recording as a fresh line with its own date, so your own record shows the sequence rather than a single unresolved note.
Frequently asked questions
What heading could I write at the top of a plain document for tracking names I may release?
As a hypothetical illustration, imagine a domain owner who has a short list of names she thinks she may release and a folder of notes she has kept herself. She opens a plain document and writes a heading: “Transfer-out check sheet — one row per name.”
What four fields could I add to my notes page to track an auth code's validity?
For the auth-code validity step, you can work from the same notes page rather than a live registry view. Add four fields: the code's stated issue date, its stated expiry date, the date you last read the entry, and a one-line note on whether the code is still inside that window.
What could I write in a registrar-restriction note beside one name from my shortlist?
You can take one domain name from your shortlist and write a registrar-restriction note beside it before taking any other step. The note could hold four self-chosen fields: registrar shown on your own record, lock state as you last read it, stated unlock or transfer-prohibition wording, and the date you read it.
Domain Transfer-Out Rules . Retrieved 2026-11-19. ↩︎ ↩︎
Rules for 60-Day Inter-Registrar Transfer Lock . Retrieved 2026-11-19. ↩︎
Domain Transfer Out . Retrieved 2026-11-19. ↩︎ ↩︎