Before moving a domain to a new registrar, you need to ensure that all status locks are disabled and that the contact email matches your current access. This article outlines the specific checks required to avoid transfer failures.
Assuming a Domain Transfer Request is Pending
Assume a web author has drafted a transfer checklist but the request itself is still only pending, with no registrar action taken. The working folder holds an export named contact-audit.csv, a screenshot of the registry record, and a short page stub called info-consistency.md.
The first concrete item is a table of status fields. The author lists three columns—field name, current value, and where that value was last observed—and fills in two clearly invented rows. Row one reads clientTransferProhibited, "set", "registry record viewed 12 March". Row two reads redemptionPeriod, "not present", "same registry record". A third candidate field, pendingTransfer, is deliberately left out because the pending request has no confirmed registry entry to point to; the author notes it as an open question rather than inventing a value. That is the example trade-off: a longer table looks thorough, but a field with no observed source would blur the audit.
The second item is a four-part heading list for the info page, each paired with what it must match: registrant organization against the contact export; registrant email against the same export; nameserver hostnames against the registry record; and the domain's own spelling and suffix against the wording used on the site. Two invented records show how the author sorts them. One line, under the nameserver heading, gives ns1.example-hosting.test and ns2.example-hosting.test as a matched pair. Another, under registrant email, gives a placeholder mailbox name ending in a test domain and marks it "needs confirmation"—not because it is verified, but because it is the one entry the author cannot reconcile locally.
The third item is a naming worksheet for the checklist file itself, with candidates such as transfer-precheck-2025, status-field-log, and info-parity-notes. The author keeps the first and drops the second because "log" suggests an event history that this file does not contain; the third survives as the page stub name. These are self-invented labels for illustrating the sorting decision, not real records.
Links in the draft are each fixed to one destination and one channel: the registry record view is cited through the registry's own record lookup, and the contact export is cited only as a local file. The pending request is described as the reason for the audit, not as evidence that any check has passed.
Checking Active Status Fields in the Registry Database
In the registry database record shown in WHOIS, the Status column can list one or several values. The source page distinguishes statuses beginning with client, which it says are initiated by the registrar, from those beginning with server, initiated by the registry. It describes ACTIVE (OK) as the normal status requiring no action and no protection measure; when other statuses appear, OK is not displayed, though that alone does not establish an abnormality.1
For transfer-related fields, the page says clientTransferProhibited prohibits transfer by the registrar and serverTransferProhibited prohibits transfer by the registry. It states that some newly registered or newly transferred domains receive serverTransferProhibited for 60 days, released automatically, while some are set for arbitration or litigation and released when that ends.1
You can treat the registry record screenshot as the source of truth for this pass, but read it as an observation snapshot rather than a live feed. Before comparing anything, note when the capture was taken and which fields it shows. If the screenshot is older than your pending transfer request, consider whether it still reflects what you want to check, and whether a fresh lookup belongs on your own to-do list rather than in the checklist as a confirmed result.
For the active status fields themselves, a simple three-column table works: field name, value as seen, and your reading of it. A filled example might read "domain status: clientTransferProhibited; reading: a lock currently shown, needs confirmation before any request is filed." Another row could read "domain status: ok; reading: no hold shown in this capture." Keep the reading column as your interpretation, clearly separated from the copied value, so a later reader can tell observation from judgment.
You might then mark each row as either "current" or "to recheck" depending on the capture date, and move the to-recheck rows into your pending notes rather than the checklist body. This keeps the checklist from implying that locks are already cleared when no registrar action has occurred.
If the screenshot shows a field you cannot interpret, consider leaving the value copied and the reading blank, with a short note that it awaits a second look. That is more honest than guessing. The goal of this pass is a status table you can trust as a record of what you observed and what still needs confirmation, not a claim that the transfer is ready.
Verifying Registrant Email Accuracy Before Code Release
Use NamesLink to check whether the registrant email on file matches the address you intend to use before releasing the transfer code. Cross-check that address against the registry record screenshot and the entries in contact-audit.csv, and note any mismatch in info-consistency.md so the discrepancy is visible before you proceed.2
Disabling Client-Side Transfer Prohibition Locks
Before a transfer-out can proceed, the documented transfer-out directions say to check whether Transfer Prohibition Lock is enabled. If it is enabled, the domain cannot be transferred out, and that option must be disabled before the transfer can go ahead.3
The same account's directions point to separate guidance for enabling domain security protection for the detailed steps, rather than describing the disabling procedure on the transfer-out page itself.3
These checks sit alongside the rule that domains in the serverTransferProhibited status cannot be transferred out, and the note that selecting the 60-day registrar transfer lock period when modifying domain information also requires waiting 60 days before transfer-out.3
You can turn the pending transfer checklist into a small lock-reading exercise before any request leaves your drafts folder. Using the registry record screenshot you already saved, read the client-side prohibition lock as a separate field from the other status entries, note its current value in plain words, and record the date you observed it. Then compare that reading against the wording you intend to use in the checklist, so the lock is described as either absent or present rather than assumed unlocked.
For the info page stub, add one line that pairs the lock reading with your next action. A filled example might read: field—client transfer prohibition; value as seen—present; reading—needs removal before a request; planned action—follow the registry-listed route when ready. Keep the action as a plan, not as a completed step, and note that the screenshot is a snapshot whose freshness you will recheck before submitting anything.
Consider labeling each lock-related row in your status table as current, stale, or unread based on the screenshot date. Move the stale rows into pending notes instead of deleting them, so the earlier reading stays visible alongside the newer one. If the lock wording is unfamiliar, you can copy the value verbatim and leave your interpretation blank until a second look, which keeps the checklist honest about what remains unresolved.
You might also add a short author-facing line to the info page explaining why the lock matters for consistency: it is one field among several that must agree across the registry record, the contact export, and your own notes. This is your explanatory sentence, not a quoted rule, and you can word it in whatever form suits the page.
Reviewing Server-Side Restrictions and Recent Changes
Tencent Cloud's registry guidance ties one server-side restriction to a specific trigger: when a 60-day inter-registrar transfer lock is enabled while modifying domain information, the domain cannot be transferred to another registrar within those 60 days. The rule cites ICANN's Transfer Policy as its basis and applies to the operation of modifying domain information.4
For a review pass, this means the restriction belongs with the information modification, not with the transfer request itself, and its window is stated as 60 days from that point. The page does not describe how to check whether the lock is currently on, so it supports recording the restriction and its 60-day condition rather than confirming live lock state.4
For this pass, focus on the status row that reads client transfer prohibition. You can keep the registry screenshot as your observation snapshot and treat its date as the cutoff for what counts as recent. Add a fourth column to your three-column table labeled "last changed, if visible," and leave the cell blank when the screenshot gives no date rather than guessing one. A filled example might read: field—client transfer prohibition; value as seen—present; reading—must be lifted before any request; last changed—not shown.
If the same lock appears in both the screenshot and your pending checklist, you might decide which one to trust by date alone and mark the older entry stale. Move stale rows into a pending-notes file instead of deleting them, so the record of what you believed at each point stays readable. That choice is yours; the aim is simply that no two copies of the same field disagree without a visible reason.
You could also annotate the info page stub with one line per lock naming the action you plan: "awaiting confirmation that the prohibition is lifted" is a fine entry while nothing has been requested. Keep that line separate from any value you copied from the screenshot, so a reader can tell observed text from your intention.
Confirming Auth-Code Delivery Path and Timing
For this step, the documented path is to contact the original registrar to obtain the domain auth-code. According to the page, that registrar usually sends the auth-code by email after verifying the domain identity.5
You can also submit a domain transfer-out application to the original registrar to get the auth-code. Generally, the auth-code can be sent quickly to the email address of the domain owner in the original registrar's system. If that does not work, the page says to contact the original registrar or its agent to manually request an auth-code or domain transfer-out, and the registrar will provide instructions.5
On timing, the page states that the auth-code is valid for five days. After getting it, submit domain transfer-in at the new registrar within that validity period as soon as possible; otherwise, a new auth-code is needed. The page also indicates that transfer-in completes within 3–7 days after obtaining the code.5
You can take the draft checklist and add one more small section to it: a delivery-path note. The point is not to request the auth code yet, but to write down, in ordinary text, how you expect it to reach you and when you would begin watching for it. A filled example might read: field—auth-code delivery; expected path—email to the registrant contact; earliest reasonable check—next working day; fallback—look again in the registrar's own message area. Keep each line phrased as a plan, since nothing has been sent.
Two other details belong beside that note. First, the contact address you would expect the code to arrive at, copied from contact-audit.csv rather than retyped from memory, so you can compare the two later. Second, a short line on where you would look if the message does not appear, such as a spam folder or the message list attached to the account. You might also add a dated line saying "awaiting confirmation that the code has been issued" — that marks the item as pending rather than done.
The info page stub can carry the same idea in one sentence chosen by you. A working version is: "The auth code is expected by email to the registrant contact; timing is unconfirmed until the request is submitted." If you prefer a more cautious wording, try: "Delivery path for the auth code is still a plan, not an observation." Either version keeps the page honest about what you actually know.
Finally, consider pairing the delivery note with the lock rows in the same table so the reader of your draft can see the sequence: locks read, contacts matched, then delivery path stated. You decide the order that suits your own review.
Frequently asked questions
What three columns should I use in my table for the status fields, and how should I fill in sample rows?
The first concrete item is a table of status fields. The author lists three columns—field name, current value, and where that value was last observed—and fills in two clearly invented rows.
How can I organize the lock-related rows in my status table based on the screenshot date?
Consider labeling each lock-related row in your status table as current, stale, or unread based on the screenshot date. Move the stale rows into pending notes instead of deleting them, so the earlier reading stays visible alongside the newer one.
How should I record a field I cannot interpret in the screenshot?
If the screenshot shows a field you cannot interpret, consider leaving the value copied and the reading blank, with a short note that it awaits a second look. That is more honest than guessing.
Domain Status . Retrieved 2026-11-19. ↩︎ ↩︎
Domain Management | NamesLink . Retrieved 2026-11-19. ↩︎
Domain Transfer Out . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎
Rules for 60-Day Inter-Registrar Transfer Lock . Retrieved 2026-11-19. ↩︎ ↩︎