A buyer's checklist for closing cleanly.

Most domain acquisitions that go sideways do so after the price is agreed, not before. The negotiation is the visible part of the process. The closing, due diligence, escrow setup, authorization codes, registrar coordination, post-transfer hygiene, is where money actually moves and where the buyer either ends up with a working asset or with a problem.

This essay is the buyer's side of that closing process, written as a checklist. It assumes you have agreed a number with the owner of a premium or geographic domain through direct correspondence. The previous essay in this series covered the discovery and outreach steps. What follows is the work between the handshake and the keys.

Phase one: pre-payment due diligence

Before money moves, the buyer should confirm a short list of facts about the asset. None of this is unusual; all of it is standard. Five checks cover most of what matters.

One. Confirm the seller controls the domain. A current WHOIS record (via lookup.icann.org) shows the registrar, the registrant organization, and the dates. If the seller's email signature, business letterhead, or registrar account aligns with the WHOIS record, that is a positive signal. If you cannot reconcile the seller to the WHOIS record, ask the seller to log into the registrar and screen-share a view of the domain in their account. Reputable sellers do this without hesitation. A refusal here is the most important red flag in the entire process.

Two. Confirm the domain is currently unlocked or that the seller can unlock it. Most premium domains sit in "registrar lock" status by default to prevent unauthorized transfers. Unlocking is the seller's job, not yours, and a one-click operation in the registrar dashboard. If the seller does not know how to do this, that is informative; it does not mean the deal cannot close, but it slows the timeline.

Three. Verify the renewal date is far enough out. A domain that is set to expire in three weeks is fine to acquire, but the transfer process itself can take seven to ten days, and a transfer in the last few days before expiration introduces avoidable risk. If the renewal date is close, ask the seller to renew before initiating transfer. The cost is trivial and it removes a category of timing problem.

Four. Check the registrar's transfer-out policy. Most major registrars allow outbound transfers freely after the 60-day post-registration lock has cleared. A handful of niche registrars have additional friction, fees, or holds. A quick look at the registrar's documentation tells you whether anything unusual applies. The registrar's name is in the WHOIS record.

Five. Run the asset history. The Wayback Machine at web.archive.org shows snapshots of every public version of the site. Look for periods where the domain may have served content you would not want your new property associated with. This is uncommon on long-tenured premium names, but it is a five-minute check that occasionally surfaces something worth knowing before you commit.

Phase two: structure the deal

For any transaction above a few thousand dollars, the structure should be a written agreement plus an escrow service. The agreement does not have to be elaborate. A short letter that captures the buyer, the seller, the asset, the price, the payment method, the escrow service, the transfer timeline, and the closing conditions is enough for most private deals.

Minimum elements of a clean offer letter.

Buyer's full name and entity. Seller's name as it appears in the WHOIS record. The exact domain (including correct extension). The agreed price in a specific currency. Payment method (wire, ACH, or other). Escrow service name. Target close date. Confirmation that both parties will execute the transfer through the escrow's standard process. Signature lines for both parties.

A two-page offer letter signed by both parties is far better than a fifty-page contract that takes a month to negotiate. The escrow service handles the actual movement of money and the verification of transfer. The letter just records what both sides agreed to.

Phase three: open escrow

Escrow.com is the standard third-party escrow service for domain transactions and has been since the late 1990s. It is licensed in California and a number of other US jurisdictions, holds an audited trust account, and processes domain transactions specifically as a category. There are other escrow services in the industry, but Escrow.com is by far the most common, and a seller who refuses to use it should be asked why.

The buyer initiates the transaction on Escrow.com, names the seller, names the asset, names the price, and selects "domain name" as the asset type. The platform then sends the seller an invitation to confirm. Both parties verify their identity, the buyer wires (or ACHs, depending on amount) the full price into the escrow trust account, and the platform notifies the seller that funds are confirmed. Only at that point does the seller initiate the transfer of the domain.

Escrow.com charges a fee, typically split between the parties or paid by whichever side negotiated the split. The fee is small as a percentage of any meaningful transaction. It is the single best dollar a buyer can spend on a six-figure deal.

Three things to confirm at this stage:

• The asset name in the escrow record is the exact domain including the extension, with no typos.
• The buyer's registrar account at the receiving registrar is open and verified before the seller starts the transfer.
• The inspection period (the time the buyer has to confirm receipt of the asset before funds release) is set to a reasonable length, typically three to five business days for a clean domain transfer.

Phase four: the EPP authorization code

The transfer mechanism itself is a protocol called EPP (Extensible Provisioning Protocol). The seller's registrar issues an authorization code, sometimes called an EPP code, an auth code, or a transfer key. It is a short alphanumeric string that proves the seller authorizes the transfer.

The seller's job is to log into their registrar, find the domain, request the auth code, copy it, and send it to the buyer through the escrow message system (or a separate secure channel). The seller also unlocks the domain in the same dashboard. Both of these are dashboard operations that take less than two minutes at most modern registrars.

The buyer's job is to log into the receiving registrar, paste in the auth code, and initiate an inbound transfer. The receiving registrar takes the code, verifies it with the losing registrar, and begins the transfer process. ICANN policy requires the losing registrar to send an email confirmation to the registered owner; the seller approves it, and the transfer completes.

Standard timing: typically five to seven days from initiation to completion. Some registrars offer expedited transfer paths that complete in 24 to 48 hours when both sides act quickly. Cloudflare, Namecheap, and Porkbun are commonly recommended receiving registrars for premium domains because of their low renewal fees and good security posture. GoDaddy and Network Solutions are more expensive at renewal but are common receiving registrars when the buyer's broader infrastructure is already there.

Phase five: confirm receipt and release funds

When the transfer completes, the buyer sees the domain in their new registrar account. Standard hygiene at this point:

• Verify the WHOIS record updates to show the buyer's account or organization as the new registrant. WHOIS propagation can take a few hours; do not panic if it lags briefly.
• Lock the domain at the new registrar. Most registrars auto-lock after a successful transfer, but confirm.
• Enable two-factor authentication on the receiving registrar account. A premium domain is now an asset worth protecting; account security is the new perimeter.
• Set the auto-renewal to "on." Premium domains that lapse accidentally are an industry-wide horror story; the renewal fee is trivial compared to the loss.
• Update DNS if you have hosting ready to go. If not, point the domain at a holding page or a parking nameserver for now. An idle premium domain pointing at a 404 is a small but persistent leak of credibility.

Once the buyer is satisfied that the domain is fully in their control and the registrar account shows clean ownership, the buyer releases funds in the Escrow.com dashboard. The platform pays the seller. The transaction is done.

Phase six: post-close housekeeping

A few hours of work in the week after close pays back many times over.

Document the transaction. Save the signed offer letter, the Escrow.com receipt, the WHOIS records before and after, the auth code transcript, and the registrar transfer confirmation in one folder. If the domain ever becomes part of a corporate transaction, due diligence on a clean acquisition record is much faster than reconstructing what happened from memory.

Set calendar reminders. One for sixty days post-transfer (when ICANN's post-transfer lock expires and you can move the domain again if needed). One for one year post-transfer (renewal). One for any DNS or security configuration that has an expiration date attached.

Consider domain privacy. Most modern registrars offer WHOIS privacy as a free or low-cost add-on. For a premium domain that will sit while you build, privacy reduces the volume of unsolicited inquiries you will receive over the next several years.

Set up a holding page. Even a single static page that says "coming soon" or that describes the project briefly is better than a parked-domain advertising lander or a server error. Cloudflare Pages, Vercel, and Netlify all host static pages free; the configuration takes an hour.

Common failure modes and how to avoid them

Wiring funds directly to the seller without escrow. Almost every serious loss in this industry involves a buyer who skipped escrow on the seller's request. There is no reasonable reason to skip escrow on a meaningful transaction. The fee is small. The protection is large. If a seller refuses escrow, walk.

Using personal email and personal accounts for the acquisition. A premium domain held in a personal Gmail-tied registrar account is exposed to one bad password reset away from loss. If the asset matters, set up a dedicated business email at a separate provider and use that account for the registrar and the escrow.

Failing to confirm the receiving registrar before the seller starts the transfer. Some registrars require additional verification or have weekend processing pauses. A small amount of homework up front avoids a five-day wait at the worst possible moment.

Releasing funds early. Escrow's inspection period exists for a reason. Use the full window. Verify the domain works under your control. Send a test email if email service is configured. Confirm DNS responds. Only then release.

How geographic and country-keyword domains differ

The closing mechanics above apply to any domain. Country-keyword and geographic-keyword domains add a few small wrinkles worth knowing.

Some country-code top-level domain registries (ccTLDs) have additional transfer policies, in-country contact requirements, or registrar restrictions. Common ones (.tv, .me, .io, .co, .ai) operate similar to gTLDs and use standard EPP transfers. Less common ccTLDs sometimes require a local contact or a specific registrar. The receiving registrar's documentation usually says so up front.

The other practical difference is that geographic-keyword domains tend to be older. A domain registered in 1996 has thirty years of historical data attached to it: redirects, old name-server changes, owner moves, and Wayback snapshots that may surprise you. None of it is necessarily a problem. All of it is a few extra minutes of due diligence work.

If the asset is the right address for an operating business that will route a category of attention, the closing work above is the same closing work that any serious buyer would do. The point of the checklist is not novelty; it is making sure that nothing in the standard playbook gets skipped because the deal felt straightforward.

The next essay looks at one of the most underestimated reasons short, memorable geographic domains accrue value over time: direct-navigation traffic.