Assume you plan to move a domain from one registrar to another. This guide covers the essential pre-transfer checks: ensuring the domain is unlocked, securing the authorization code, and reviewing current DNS settings to prevent service interruption.
Scenario: Preparing a Domain for Registrar Change
Suppose a small studio is moving its project domain, written in its own notes as studio-index.example, to a different registrar before a site launch. The owner drafts a one-page handoff sheet with three sections: Lock status, Authorization code handling, and DNS records. Under Lock status the fields are “Registrar lock state,” “Who can unlock,” and “Date unlocked.” Two fictional entries show the intent: “Registrar lock state: locked, pending owner approval” and “Who can unlock: account owner only.” These are invented examples to show how fields work, not records of a real move.
For the authorization code, the sheet asks for “Code requested by,” “Storage location,” and “Expiry noted.” The owner writes two dummy rows: “Code requested by: primary contact” and “Storage location: password manager entry labeled transfer-2025.” The name transfer-2025 is just the author’s own labeling choice; whether any external form accepts such a label is not established here. A separate line records that the code travels out of band, with the recipient fixed as the registrar account holder, not a generic support address.
The DNS section lists record type, host, value, and purpose. Two fictional rows demonstrate grouping: “A | www | 203.0.113.10 | main site” and “TXT | _verify | sample-value-01 | launch verification placeholder.” The address and token are deliberately arbitrary. The owner also notes whether the zone is hosted at the losing registrar or elsewhere, since that determines whether nameservers need to be re-entered or merely kept.
A short choices block captures a single trade-off: the owner decides to lower the TTL on the main A record a day before the move, accepting a slightly slower first day of updates in exchange for faster propagation afterward. The reason is written beside the choice so the next reader understands it. Each item in the sheet is labeled as an author-made illustration for explaining the problem, not a tested procedure or a report of an actual transfer.
Verifying Contact Info and Unlock Status
Before moving a domain, confirm its contact information is current with both the current and new registrar. The source explains that both registrars contact the registrant during transfer, and an outdated email address could send an authorization code to the wrong place, letting someone else use it to move the domain. It also warns that changing contact details can cause the registrar to lock the domain for 60 days; domains are also locked for 60 days after registration and must have been registered at least that long to be eligible.1
The domain must then be unlocked, since locked domains cannot be transferred or modified. Registrars usually provide an option in their dashboard to release a registrar lock, which many apply by default using the REGISTRAR-LOCK status code. Removing a registry lock, indicated by a serverUpdateProhibited status code, requires the registrar to contact the registry on the registrant's behalf, with extra authentication steps, so a domain locked at both levels may take longer to transfer.1
You can compare the contact details in your registrar account against the contact record attached to the domain before deciding whether to proceed. Open the domain's contact record and read the registrant name, organization, email, and phone one field at a time, then set them beside the details in your account profile. If the email on the record is an old address you no longer control, that is a decision point: update it and wait for the change to settle, or accept that transfer messages may not reach you. Either choice is yours; the point is to know which address will receive the confirmation.
The unlock status is a separate switch, so treat it separately. Look for a lock indicator on the domain's management page and note its current state in your working notes, for example "Lock: on, seen 14 March" or "Lock: off, seen 14 March." If it reads locked, you can decide when to switch it off rather than doing so immediately; some people prefer to unlock only after their contact details are confirmed. A small studio moving studio-index.example might record the lock state first, then correct an outdated registrant email, then revisit the lock — the order follows what each check depends on.
For each item you verify, you can keep a short line noting what you saw and when, so a second person reviewing your notes can tell a confirmed field from an assumption. Nothing here requires a particular tool or format; a sentence per field is enough. If a detail looks wrong, write down the discrepancy rather than fixing it on the spot, and decide afterward whether to correct or leave it.
Obtaining the Authorization Code Securely
In the NamesLink console, open the Domain Transfer Out page to initiate the outbound transfer and obtain the transfer authorization code. Before you start, check that the transfer lock is disabled on the domain.2
Reviewing Current DNS Records Before Migration
You can take your current DNS record set and turn it into a short working inventory before you commit to a migration date. Start by opening the DNS management view for the domain and copying each row into your own notes: the record type, the host or name, the value, and a plain-language note about what depends on it. For example, a row might read “A | www | 203.0.113.10 | main site” and another “MX | @ | mail route | team email.” You might group records by purpose rather than by type, since that makes it easier to spot which ones the site launch actually needs and which ones can wait.
Once the list exists, you can mark each record with one of three labels of your own choosing: keep as is, confirm with whoever owns the service, or leave for later. A record you do not recognize is a reasonable candidate for the middle label rather than a reason to delete it. If a value points to a hostname you no longer use, note that suspicion next to the row instead of changing it, and decide later whether the migration is the right moment to touch it.
You can also record the time-to-live value for the records that matter most to the launch, because that number shapes how long a change takes to settle. A useful author demonstration: before a planned move, lower the TTL on the main site record a day ahead and accept slightly slower lookups in exchange for a faster rollback if something goes wrong. That is one trade-off you can choose; keeping the existing TTL is an equally valid option if the launch window is not tight.
Finally, you might compare this inventory against the records you expect the new setup to need, and write the gap as a question rather than a task. For instance, “Does the new host require a different verification TXT record?” is easier to answer than a vague instruction to fix DNS. Keep the sheet with your authorization code notes so the whole pre-transfer picture sits in one place, and let the record list stay a snapshot rather than a live copy you feel obliged to maintain.
Checking Nameserver Configuration in Console
The cited official guide links nameserver work to a batch DNS settings page, described as the place to batch modify name servers and batch add DNS records for multiple domains. It presents this as a separate capability of the console rather than part of a single domain's page.2
A separate item in the same guide covers the transfer lock, describing how to enable or disable it to prevent unauthorized outbound transfers. That keeps the nameserver configuration step distinct from the lock setting, so each can be checked on its own.2
You can turn the nameserver view in your registrar console into a short comparison note before you commit to a transfer date. Open the domain’s nameserver section and write down the hostnames exactly as shown, then put beside them the nameservers you believe the destination setup will use. Treat any mismatch as a question to resolve rather than a fault to fix on the spot.
A fictional example helps show the shape of the note. For a domain recorded in your notes as studio-index.example, the console might show two hostnames under the old provider, while your launch notes name two different hostnames from the new setup. You could write “Old: two hostnames from current provider; Expected: two hostnames from new setup; Question: which pair should be authoritative at cutover?” Another owner might find that only one hostname differs and mark that single line for a closer look.
You can also record how the nameserver setting is presented: whether it is an editable field, a read-only display, or a preset choice offered by the console. This observation helps you decide whether the change belongs in your own hands or with whoever manages the account. Consider noting the date and time you looked, so the entry reads as a snapshot rather than a permanent claim.
When you review the note later, you might sort entries into three groups of your own: confirmed, still unclear, and deferred until after the move. The confirmed group needs no further action; the unclear group becomes questions for the account holder or the person running the destination setup; the deferred group can wait until the site is live. Leave a blank line under each group for new observations, so the note grows without losing earlier entries.
Final Validation of Transfer Eligibility
Before starting, check that the domain has been registered with its current registrar for at least 60 days. The source states a domain registered for less than 60 days is likely locked until that period ends, so it is not yet eligible to move to a new registrar.3
Also confirm the registrant contact information is current, since both the current and new registrar contact the registrant during transfer, and the authorization code is sent to that contact by email. The source warns that changed contact details can trigger a new 60-day lock, so note that trade-off when deciding whether to proceed.3
You can now take the working inventory you built—unlock state, authorization code status, DNS record list, and nameserver comparison—and read it as a single eligibility decision rather than four separate notes. Set the four columns side by side in whatever order you noted them, then scan each row once without adding anything new. The question is not whether every line is complete, but whether any line still says "unclear" in a way that would block a transfer request.
Consider marking each row with a simple verdict of your own: ready, waiting on someone, or deliberately deferred until after the move. A fictional row might read "Code storage—confirmed with the person who requested it—ready," while another reads "Second nameserver hostname—differs from console display—waiting on the service owner." The verdict is yours to phrase; what matters is that the row no longer mixes a fact with a hope.
You might then reread the same rows as if a second person had written them. If a line says "looks fine" or "should be okay," that is a sign to replace it with what you actually saw and when. A useful rewrite is to turn "DNS seems normal" into "Four A and TXT records listed; TTL noted on the main record; no gaps found against the expected set." This is an author demonstration of tightening your own wording, not a report of any check you have run.
For entries you deferred, you can leave them visible rather than delete them, so the decision record shows what you chose to postpone and why. If the only blockers are deferred items you have already reasoned about, you might decide the eligibility question is settled enough to pick a transfer date. If a blocker is still "waiting on someone," you can hold the decision and revisit that row first, then compare the whole sheet once more before committing.
Frequently asked questions
How can I turn the DNS records I currently have into a short working inventory before choosing a migration date?
You can take your current DNS record set and turn it into a short working inventory before you commit to a migration date. Start by opening the DNS management view for the domain and copying each row into your own notes: the record type, the host or name, the value, and a plain-language note about what depends on it.
How might I sort the entries in my review note later?
When you review the note later, you might sort entries into three groups of your own: confirmed, still unclear, and deferred until after the move. The confirmed group needs no further action; the unclear group becomes questions for the account holder or the person running the destination setup; the deferred group can wait until the site is live.
What labels can I use to mark each record once my list exists?
Once the list exists, you can mark each record with one of three labels of your own choosing: keep as is, confirm with whoever owns the service, or leave for later. A record you do not recognize is a reasonable candidate for the middle label rather than a reason to delete it.
How to transfer a domain name . Retrieved 2026-11-19. ↩︎ ↩︎
Domain Management | NamesLink . Retrieved 2026-11-19. ↩︎ ↩︎ ↩︎
如何將網域名稱轉移到其他網域名稱註冊商 | Cloudflare . Retrieved 2026-11-19. ↩︎ ↩︎