Human-Audited AI ToolsA Human in the Loop on Every Change

Free first draft. No contract. Nothing is billed until your site is live. Get in Touch (980) 347-9428
Charlotte, NC 28277

Imagine · Design · Forge · Sustain

Vol. I, No. 7 Charlotte, N.C. Anno 2026 Price: One Handshake

Web Design

Domain Transfer Checklist: What to Record First

IDFS AI

Domain Transfer Checklist: What to Record First

Before you transfer a domain to a new registrar, write down the lock on the name, the authorization code, the mailbox that will receive that code and the confirmation mail, any lock a recent contact change already started, and a full export of the DNS and mail records. A registrar move changes which company sponsors the registration. The August 2009 domain mapping for EPP defines that transfer as a request to move sponsorship of the domain object, and the request carries the domain name, an optional registration period, and authorization information, not the name servers [5]. The records visitors and mail actually use live in the zone, and copying a zone is a separate operation [6]. The notes below are a domain transfer checklist for the registrar move. They are not a guide to editing records where the name already lives, and they are not a renewal calendar.

A registrar move is not a nameserver edit

A registrar is the service provider between you and the registry that runs the extension. [6] ICANN's Transfer Policy says registered name holders must be able to transfer registrations between registrars when the gaining registrar's process meets the policy and ICANN or registry rules do not prohibit the move. [1] The Registered Name Holder is the only party with authority to approve or deny a transfer request to the gaining registrar. [1] An agency, a host, or a former developer who pays the invoice is not automatically that person.

Editing name servers leaves the registrar in place. We keep that work on its own list: what to record before you change website nameservers. This post is the move to a new registrar.

Name servers are changed with a separate update, not with the transfer [5]. EPP is still how registries and registrars commonly exchange registration information [6]. A zone transfer is an authoritative server sending a copy of a zone, which an inter-registrar transfer does not do [6]. The parent holds the name server names. The address, mail, and text records are authoritative data in the child zone [6].

Record the lock that is on the name today

Every domain has at least one status code. Client codes are set by the registrar. Server codes are set by the registry, and they take precedence. [4] Write down every status, the date you read it, and whether it came from the panel or from a lookup.

clientTransferProhibited tells the registry to reject a transfer from the current registrar to another. ICANN says that status helps prevent unauthorized transfers from hijacking or fraud, and that you ask the registrar to remove it when you do want to move. [4] Record the label your panel uses, often "registrar lock" or "transfer lock," and whether you can remove it yourself.

If you cannot, the registrar must remove clientTransferProhibited within five calendar days of your initial request [1]. If it also will not let you generate the authorization code, it must provide the code and remove the status within those same five calendar days [1]. That path must not be stricter than the one it already uses for contact or name server changes, and it must not refuse the unlock or the code solely because of a payment dispute with you [1].

serverTransferProhibited is a different lock. ICANN calls it uncommon. It is usually set during legal or other disputes, at your request, or while a redemptionPeriod status is in place. The registrar cannot lift it alone. It has to ask the registry, and removing it can take longer than removing clientTransferProhibited. [4] If that status is present, do not start the move the same day. Record why it is there and how long the registrar says the registry request takes.

pendingTransfer means a transfer to a new registrar has been received and is being processed. If you did not request it, contact the registrar immediately and ask them to deny it. [4] Speed matters because silence is not neutral. If the registrar of record does not respond within five calendar days to the registry's transfer notice, the Transfer Policy treats that as approval. [1]

Note which of clientTransferProhibited, clientDeleteProhibited, and clientUpdateProhibited are on today. Asking for those statuses can help prevent unauthorized transfers, deletions, and updates, and you will want the transfer lock back on after the move [4].

Also record who the registrar actually is. The registrant FAQ says a search at https://lookup.icann.org/ shows it in the Registrar field. [2] Compare that name with the company whose panel you can open. If they differ, find the account that can remove the lock before you start a five-day clock you cannot finish.

Three clocks can stop the move

A domain transfer checklist that skips dates will fail on a name that looks unlocked. For the reasons below, a denial must be explained to you and to the gaining registrar. [1]

The registrar may deny a transfer requested within 60 days of the creation date in the registry record [1]. It may also deny one within 60 days after an earlier inter-registrar transfer, except a transfer back to the original registrar when both registrars agree or a dispute decision directs it [1]. In that rule, "transferred" means an inter-registrar transfer under this policy, not a hosting change and not a name server change [1]. Write down the creation date and the date of the last registrar-to-registrar move. If either falls inside 60 days, ask whether this registrar will use that option before you pay the gaining registrar [1].

The lock that follows a routine contact edit is the Change of Registrant lock. In the Transfer Policy updated on 21 February 2024, a Change of Registrant is a material change to the prior registrant's name, organization, or email address [1]. That includes a name or organization change that is not a mere typo, any such change that arrives with a new address or phone number, and any change to the registrant's email address [1]. After that change, the registrar must impose a 60-day inter-registrar transfer lock unless it let you opt out beforehand and you did [1]. If the lock is on and you did not opt out before the change, the registrar must deny the transfer [1].

The opt-out only counts if you take it before the edit. The policy tells the registrar to warn you: if the goal is a different registrar, request the transfer before the Change of Registrant, unless you were offered the opt-out and took it [1]. The registrant FAQ says you cannot transfer within 60 days of changes to the registrant name, organization, or email address, that the registrar does not have to offer an opt-out, and that you should finish the transfer before changing contact information [2].

Record the current registrant name, organization, and email, the date each last changed, and whether an opt-out was offered and accepted. If the mailbox on the domain is dead, recover that mailbox. Do not correct the registrant email and then start the transfer. That correction is the change that starts the 60-day lock [1].

The registrar must also deny a transfer when it knows of a pending UDRP case, a court order, a pending Transfer Dispute Resolution Policy case, or a URS proceeding or suspension [1].

The auth code and the mailbox that must receive it

ICANN's pages call the same secret an Auth-Code, an authorization code, an Auth-Info code, a transfer code, or an EPP code. The registrar creates it to help identify the holder and to prevent unauthorized transfers. For a generic top-level domain under contract with ICANN, the code is required to transfer the name from one registrar to another. [2][3] Registrar-generated codes must be unique per domain. [1] The code identifies the holder. The forms of authorization still have to authorize or confirm the request. [1]

You either create the code in the control panel, or the registrar provides it within five calendar days of your request [3]. ICANN does not hold these codes and cannot create one [3]. Record the mailbox or screen it arrived in, the date, and the domain. Do not forward it.

The policy text still says the gaining registrar must get express authorization on the form "Initial Authorization for Registrar Transfer," and that the transfer proceeds only if that confirmation is received where the form is required [1]. On 26 January 2020, the ICANN Board deferred enforcement of that gaining-registrar duty until the Transfer Policy review settles it [1]. A missing message from the new registrar is not proof that the move is waiting.

The current registrar's message is not covered by that deferral. When the registry reports a pending transfer, the registrar of record must confirm your intent with the form "Confirmation of Registrar Transfer Request," sent as soon as it can and no later than 24 hours after the registry's notice [1]. If you have not confirmed and the registrar has not explicitly denied the request, the transfer proceeds. No response from the registered name holder is not a valid reason to deny [1]. Five calendar days of silence count as approval [1].

List the registrant email, the login email, and any admin or billing address, and confirm a person can read each one today. A privacy service or a former designer often holds the mailbox that actually gets the approval. Recover that mailbox if you cannot read it. Do not retarget the registrant email unless you already opted out or you accept the lock, because any change to that email is a Change of Registrant [1].

Do not let the name lapse while the request is open. The gaining registrar's authorization expires if the domain name expires before the inter-registrar transfer is completed [1]. The registrant FAQ says a registrar may charge a transfer fee, and that non-payment of that fee is not grounds to deny the transfer [2].

The same form expires if a Change of Registrant is completed while the transfer is still open. [1] Once the request has started, leave the registrant name, organization, and email alone until the new registrar shows the name and the old one does not.

Export the DNS and mail records first

Changing the delegated name servers is an update, not the transfer [5]. The records behind those names are authoritative data in the child zone, and copying that zone is a zone transfer or a panel export, not an inter-registrar transfer [6].

If the current registrar also hosts the zone, it may stop answering after you leave while the delegation still names those servers. DNS Terminology calls that a lame delegation: a server listed in the NS records is not serving the zone, so queries fail [6]. Export while the current host is still answering, and ask in writing whether DNS hosting continues after the registration moves. If it will not, put the same records on a host that will. If that means a new delegation, use the nameserver checklist and do not do both jobs on the same afternoon.

Save this outside the registrar account, with a date on the file:

  • Name server hostnames from the panel and from a lookup. If the lists differ, find out which one is live.
  • The zone export, with full values: A and AAAA, CNAME, MX, TXT, SRV, and CAA, including every TXT record your mail host published. This is a copy. A new DNS host starts empty.
  • Whether DNSSEC is on, and any DS or key data the panel will show. A later name server change has to match it.
  • Who hosts the zone, the login for that host, and the written answer on whether hosting survives the registrar change.

What to watch while the transfer is pending

Start at the gaining registrar after the lock is off and you have the code. Read the registrant mailbox daily. Approve only the transfer you started. If any other confirmation arrives, ask the current registrar to deny it, and do not wait out the five days [1][4].

Leave the registrant name, organization, and email alone while the request is open. That change can impose the 60-day lock and can expire the gaining authorization [1]. Leave name servers alone too, unless the zone is already copied and you meant to change the delegation as its own step.

When a holder-authorized transfer completes, the registry adds one year to the registration, and the total unexpired term cannot exceed ten years [1]. Write down the new expiration. Compare the live name servers, the website address, and the MX record with your export. If the name servers changed, use the nameserver notes. Then confirm clientTransferProhibited is on again, because that status tells the registry to reject a transfer you did not ask for [4]. The new registrar may not set it for you.

If the current registrar denies the request for one of the "may deny" reasons, it must tell you why [1]. Match that reason to your notes: within 60 days of creation, within 60 days of a prior transfer, or inside a Change of Registrant lock [1]. If the reason is off the policy's list, or you disagree, the registrant FAQ says to file a transfer complaint with ICANN, and your dates and status codes belong with that complaint [2].

Practical takeaways

  • Before you remove a lock, record the registrar, the registrant name and email, every status code, the creation date, the last registrar-transfer date, and the last change to registrant name, organization, or email.
  • Remove clientTransferProhibited on purpose. serverTransferProhibited needs the registry. An unexpected pendingTransfer means contact the current registrar now, because five silent days count as approval [1][4].
  • Get the auth code from the panel, or within five calendar days if you cannot, and keep it in a mailbox you control. Ignoring the confirmation mail does not stop the transfer [1][3].
  • Do not change the registrant email to chase a lost message. Any change to that email can start a 60-day lock unless you opted out first [1][2].
  • Export the zone, including MX and TXT records, and store it outside the old account. A registrar transfer does not copy the zone [5][6].
  • Do not let the name expire while the transfer is open, because the gaining authorization expires if the domain expires first [1]. Afterward, compare live records with the export and turn the transfer lock back on.

How we can help

Have more questions or want to get in touch? If you want a second set of eyes before a registrar move, our team can go through the domain transfer checklist with you, including the lock, the mailbox, and the zone export. Reach us on the contact page.

Citations

  1. ICANN, "Transfer Policy" (2024-02-21)
  2. ICANN, "FAQs for Registrants: Transferring Your Domain Name" (2017-10-10)
  3. ICANN, "About Auth-Code" (2013-05-03)
  4. ICANN, "EPP Status Codes | What Do They Mean, and Why Should I Know?" (2014-06-16)
  5. RFC Editor, "Extensible Provisioning Protocol (EPP) Domain Name Mapping" (2009-08)
  6. RFC Editor, "DNS Terminology" (2024-03)
Categories: Web Design

Further Reading