This article addresses the specific task of verifying domain eligibility for outbound transfers. It focuses on checking the current status of transfer locks and locating the necessary EPP authorization code, using a hypothetical scenario to illustrate the workflow without relying on external statistics or unverified claims.

Scenario: Preparing a Brand Domain for Outbound Transfer

This is an imagined scenario, not a record of a real business or a tested process. A brand operator I'll call Mira handles several domains for a small lifestyle label and has just agreed to move one of them to a new registrar. She opens a plain document and builds a short production list before touching anything in a control panel. Her list has four columns: domain name candidate, current registrar, lock status, and authorization code location. She adds a note at the top stating that she will confirm every value against the registrar's own interface rather than trusting older emails.

Her working inventory uses two made-up records to show the shape of the list. The first row reads "example-brand-home" with the suffix noted as a separate field, current registrar listed as "Registrar A," lock status written as "clientTransferProhibited — to confirm," and the authorization code location written as "secure message in account mailbox, status unknown." The second row reads "example-brand-archive," current registrar "Registrar B," lock status "unknown, request an export of current status," and authorization code location "not yet requested." Neither row is a real domain; they exist only to show how Mira separates what she knows from what she still needs to check.

Before requesting the code, Mira makes one deliberate choice: she sets aside a candidate name that is close in spelling to a term used by an unrelated company, because the spelling similarity could complicate correspondence and she prefers a name whose letters can be read aloud without ambiguity. She writes the reason beside the name rather than deleting it, so the decision is visible later.

She then prepares the outbound request as a form she can reuse for each name. The form's fields are the domain name, the exact suffix, the current registrar, the account holder reference, the confirmed lock status, the date the status was checked, the authorization code request date, the code's storage location, and a final line for confirmation that the destination registrar's instructions were read. For the two fictional records she writes "code request not sent" in both rows, because she has not contacted either registrar and will not claim otherwise. When she does send a request, she plans to direct it only through the support channel named inside the current registrar's own account pages, and she will record where that message went so a reply can be matched to the right domain.

Locating the Transfer Lock Status in the Console

The cited official guide lists a Domain Transfer Lock page within its domain-management documentation, and it describes the page as the place for enabling or disabling the transfer lock on your domains to prevent unauthorized outbound transfers. The same documentation set lists a separate Domain Transfer Out page covering how to initiate an outbound transfer and obtain the transfer authorization code.1

Mira now turns to the console for the same two records. She opens each domain's management page and looks for the status area before touching any transfer request. For the first row, she writes down the lock label exactly as shown, along with the date she read it; for the archived row, she adds one more note: whether the lock state is current or was recorded when that name was last active. This keeps the live check separate from the older name, so she isn't comparing a fresh reading against a stale one.

You can make a small status note of your own with three columns: domain, lock label as displayed, and the date you looked. A filled example might read "example-brand-home — transfer prohibited — 12 March." For an archived entry, you might instead write "example-brand-archive — lock shown as on at last review — no current reading." Both are your own observations, not a claim about what any service guarantees.

Two choices are worth pausing over. You might check the lock for every name in one sitting, which suits a short list, or check only the name you plan to move first, which reduces note-taking. If a console shows no lock field at all, you can record that absence rather than assume the domain is unlocked. Mira chooses the one-sitting check because her list is small, but either path leaves her with the same kind of note.

Before moving on, decide where this note lives — a single page beside your transfer form is usually enough — and whether you'll re-read the lock label right before submitting. Marking a planned re-check as a future step, not a finished one, keeps your record honest about what you have and haven't confirmed.

Requesting and Verifying the EPP Authorization Code

The cited official guide's Domain Transfer Out entry states that initiating an outbound transfer involves obtaining the transfer authorization code, while the domain transfer lock page covers enabling or disabling the lock on domains to prevent unauthorized outbound transfers.1

Check those two documented areas separately for the domain you plan to move. Request the code through the outbound transfer page described in the guide, then complete the process at the receiving registrar, as the guide specifies. The cited official guide does not state the code's format, validity, or how to confirm it at the receiving end.1

You can start with the code request itself, treating it as a separate step with its own record. Consider a simple three-line entry beside each domain you plan to move: the date you asked the current registrar to send the code, who in your team can access the receiving inbox, and the date you expect the code to expire if unused. For an active name, a filled example might read "code requested 12 May, inbox monitored by transfer lead, assume expiry within a few days." For an archived name you are only tidying, the same fields could instead read "code not requested, kept on file, review again next quarter" — a clear signal that no outbound action is underway. The point is that the field means the same thing in both rows, so a later reader can tell active preparation from dormant record-keeping.

You might also add one column for how the code will travel. Some registrars show it in the console; others send it by message. Note which one applies to each name, without judging one as better. That way the code arrives through an expected channel, and you are not searching several places at the last minute.

When the code arrives, consider a quick comparison rather than trusting it blindly: confirm it matches the name and suffix you plan to move, and that no extra spaces were introduced if you copy it into your transfer form. A small worked example: you expected the code for a hyphenated two-word name, but the message references an unhyphenated variant — pause and recheck the name before proceeding.

Finally, treat the code as short-lived. If a verification step stalls, you can mark the date in your note and decide whether to request a fresh code. Keeping that decision visible, rather than implicit, helps the next person understand why a second code exists.

Documenting the Current Configuration Before Action

Use NamesLink to open the transfer lock settings for each domain and record the current lock state before making any change, then review the domain's listed authorization code to confirm what the transfer-out process will require. Document both items in your notes so the configuration you inspected can be compared against later.1

Initiating the Transfer at the Receiving Registrar

The cited official guide lists a Domain Transfer Out page describing how to initiate an outbound domain transfer, obtain the transfer authorization code, and complete the process at the receiving registrar. Those are the three steps the guide names, in that order; it does not state the code's format, how it is delivered, or how long it remains valid.1

A separate Domain Transfer Lock page in the same guide covers enabling or disabling the transfer lock, framed as preventing unauthorized outbound transfers. The guide presents the lock page and the transfer-out page as distinct topics, so the lock action and the code request are each documented on their own.1

At the receiving registrar, you can start the request with a small pre-flight note rather than clicking straight through. Consider writing three short lines for each name you plan to move: the name and suffix exactly as shown, the authorization code you obtained, and the date you requested it. A filled example might read "example-brand-home, .example, code received, 12 March." This gives you a fixed reference to compare against the receiving side's form.

When the receiving registrar asks you to confirm the name and enter the code, pause on the suffix field. If the form displays the suffix separately, check that it matches the one in your note character by character; a name that looks identical beside a different suffix is a different record. You might also confirm the lock has been released before submitting, since a request filed while a lock is still shown as active may simply be refused.

Two choices are worth considering. You could file requests for several names in one session, which saves time but invites copy-paste slips between forms; or file one name, finish it, then start the next. Either is reasonable. If you choose the batch approach, consider reading each form back against your note before you submit it, especially the suffix field.

Keep the code itself in the same note, not in a separate message thread. If a verification step stalls and the code ages out, you can see the request date, decide whether a fresh code is needed, and mark the replacement beside the original rather than replacing it outright. That way your note shows which code was used for which attempt, and you can tell later whether the receiving side rejected a stale code or a mismatched name.

Confirming the Handover Process Completion

The cited official guide names three distinct actions in the outbound process: initiating the outbound domain transfer, obtaining the transfer authorization code, and completing the process at the receiving registrar. It presents these as separate steps rather than a single handover event.1

For handover confirmation, the guide places completion at the receiving registrar, so that is the step to follow when tracking whether the process is finished. The guide also lists a separate page on the transfer lock covering how to enable or disable it to prevent unauthorized outbound transfers.1

The guide's category listing does not state a final status field, confirmation message, or timeline for handover, so those details are not established here. What is documented is the sequence: start the outbound transfer, obtain the authorization code, then complete at the receiving registrar.1

For the completion check, consider working from the name you have already chosen to move first, rather than revisiting every record. You can use your existing note as the place to record what you observe, and treat each entry as provisional until you have seen it yourself.

A practical field set might be: domain, suffix, lock label as displayed, code request date, code received date, and transfer status as you last saw it. A filled example could read "example-brand-home, suffix noted separately, lock shown as active, code requested on a date you record, code received the same day, status awaiting confirmation." You might add a final column for your own remark, such as "suffix matched at receiving form" or "verification pending." Keep the values you actually see, not what you expected.

Before you mark a name as handed over, you can compare the receiving form's displayed name and suffix against your note one more time. If the form shows the suffix separately, check it character by character; if it does not, you might pause and confirm before submitting. You can also note whether a verification step is still outstanding, so a stalled request is not mistaken for a finished one.

Two approaches are worth weighing. You might close out each name immediately after its request is filed, which keeps your note current but spreads the work across several sessions. Or you might wait and reconcile all entries in one pass, which gives a cleaner overview but risks losing the detail of what you saw when. Either choice is reasonable; pick the one that matches how many names you plan to move and how often you return to the note.

Frequently asked questions

What three columns can I use to make a small status note of my own?

You can make a small status note of your own with three columns: domain, lock label as displayed, and the date you looked. A filled example might read "example-brand-home — transfer prohibited — 12 March."

What simple three-line entry can I consider beside each domain I plan to move when recording the code request?

You can start with the code request itself, treating it as a separate step with its own record. Consider a simple three-line entry beside each domain you plan to move: the date you asked the current registrar to send the code, who in your team can access the receiving inbox, and the date you expect the code to expire if unused.

What three short lines can I consider writing for each name I plan to move before starting the request at the receiving registrar?

At the receiving registrar, you can start the request with a small pre-flight note rather than clicking straight through. Consider writing three short lines for each name you plan to move: the name and suffix exactly as shown, the authorization code you obtained, and the date you requested it.