Step-by-step: structure escrow for a .net domain purchase

Step-by-step: structure escrow for a .net domain purchase. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A seller quotes a price for a .net domain you want. The name is clean, the traffic looks real, and the negotiation is almost done. Then the wire clears — and the seller disappears, taking the domain and the money with them.

To structure escrow for a .net domain purchase you need to sequence four things: a pre-acquisition due-diligence check on the domain's dispute history and chain of title, a written purchase agreement that conditions payment on a verified transfer to your registrar account, a neutral escrow hold that releases funds only after ICANN's registrar-to-registrar transfer protocol confirms delivery, and a post-transfer lock to prevent immediate re-transfer. All four steps apply to .net, which is a generic top-level domain governed by ICANN's standard accredited-registrar rules and the UDRP. Miss any one of them and you risk acquiring a tainted domain — or paying for one you never receive.

This guide walks each step in order, flags the trap it hides, and explains what .net's UDRP exposure means for a buyer who skips due diligence.

Why .net escrow differs from a casual domain transfer

A .net domain is a gTLD registration governed by ICANN-accredited registrars, which means the transfer mechanism is standardized — but standardized does not mean safe. The default registrar-to-registrar transfer takes as little as five days once the gaining registrar initiates the request and the losing registrar approves it. That speed is a feature for clean transfers and a hazard when payment and delivery are not formally linked.

The core trap: a direct transfer without escrow puts the buyer in the position of either sending money first or demanding the domain first. Neither party has a reason to trust the other in an arm's-length sale. A neutral escrow intermediary solves the sequencing problem. It holds the buyer's funds until the transfer is confirmed, then releases them to the seller — or returns them if the transfer fails within the agreed window.

There is a second, less obvious risk. A .net domain that has been registered in bad faith, or that has ever been the subject of a UDRP complaint, carries legal exposure for the new owner. If a prior complainant re-files after the transfer, the buyer becomes the respondent. The UDRP does not care that you paid fair value for the name. It asks only whether the registrant — you, now — has rights or legitimate interests and whether the current registration and use is in bad faith.

In our practice, we regularly advise purchasers who discovered a prior WIPO or Forum filing against a domain only after the transaction closed. The due-diligence step described below is the single most effective way to avoid that outcome.

Step 1: Run a pre-acquisition dispute history check — and flag the chain of title

Before any purchase agreement is drafted, the buyer must verify whether the target .net domain has ever been the subject of a UDRP complaint or a court action, and whether the current registration chain of title is clear. This is the step most buyers skip, and it is the most consequential.

UDRP case history is publicly searchable. WIPO and the Forum both publish decision databases. A domain that was previously transferred under a UDRP order, or that was the subject of a complaint that was denied, has a documented dispute history that bears on your risk. A denied complaint does not clear the domain permanently — a new complainant with stronger rights can file again. A transfer order means the domain once changed hands against the prior registrant's will; check whether the complainant in that case still holds trademark rights, because the same party could challenge your use.

Chain-of-title checks go further. You want to know: How many times has the domain changed registrar? Has it ever been in a redemption grace period or deleted? Was it drop-caught? Each of those events can affect whether a future panel would treat the current registration as a new registration or a continuation of an old one — and the answer can shift whether the "registered in bad faith" limb of the UDRP three-element test applies to you.

The trap in Step 1: sellers sometimes describe a domain as "dispute-free" based on nothing more than not having received a complaint letter. That is not the same as a clean UDRP history. Run the check yourself, or instruct counsel to do it, before the purchase agreement is signed.

For a structured pre-acquisition due-diligence review of a .net domain — covering dispute history, registrar lock status, and chain-of-title risk — email info@cognomenlaw.com.

Step 2: Conduct a trademark conflict analysis before you commit

A .net domain that is available and uncontested today can become the subject of a UDRP complaint the week after you acquire it. The Policy does not require that a complaint be filed immediately; a brand owner has no hard deadline to act under the UDRP. That means your exposure as a new owner depends on whether the domain string conflicts with any trademark anywhere in the world that a future complainant might invoke.

The trademark analysis in a .net purchase has a specific structure. First, is the domain string identical or confusingly similar to any registered mark? The similarity test under Paragraph 4(a)(i) of the UDRP ignores the ".net" suffix when assessing identity — panels routinely strip the TLD before comparing. So a domain that looks different from a brand name only because of its extension is still functionally identical under the Policy.

Second, does your planned use of the domain create a "bad faith use" argument? Paragraph 4(b) of the UDRP lists non-exhaustive indicators of bad faith, including using the domain to attract users for commercial gain by creating a likelihood of confusion with a complainant's mark. If you plan to monetize the domain with advertising, that use pattern is exactly what paragraph 4(b)(iv) describes. Generic or descriptive domains monetized with keyword advertising have survived UDRP complaints — but only where the buyer documented the intent and the generic character before acquiring.

What decides whether you survive that challenge is largely what you documented before and at the time of acquisition. We have advised domain investors who purchased a seemingly generic .net only to face a complaint from an international brand owner whose registration predated the acquisition by a decade. The investor's contemporaneous evidence of the generic meaning — search results, dictionary definitions, third-party descriptive uses — was the record that saved the domain.

Step 3: Draft the purchase agreement — the document that controls the deal

The purchase agreement is the legal backbone of the transaction. For a .net domain sale it should address at minimum: the domain name, the agreed purchase price, the escrow mechanics, the transfer procedure, and the representations the seller makes about title and dispute history.

The seller's representations matter enormously. You want the seller to warrant in writing that: (a) the domain is free from any pending or threatened UDRP, URS, or court proceeding; (b) the seller is the sole registrant and has full authority to transfer; (c) the domain is not subject to any registrar lock, hold, or dispute flag that would prevent transfer; and (d) the seller is not aware of any third-party trademark rights that would give rise to a dispute. These are not formalities. If the seller breaches a warranty and you face a UDRP complaint post-transfer, the warranty gives you a contractual claim — though that claim is against the seller, not the UDRP panel. The panel decides on the UDRP merits regardless.

The trap in Step 3: purchase agreements for domain names are often drafted as one-paragraph email exchanges with no representations at all. A seller who skips representations is either unaware or unwilling to stand behind the title. Either way, you are taking on risk you have not priced.

The agreement should also specify the escrow service to be used, the currency, the fee allocation (buyer, seller, or shared), the transfer deadline, and what happens if the transfer does not complete within that window — typically, funds are returned to the buyer and the deal unwinds.

How to structure the escrow mechanics for a .net transfer

This is the operational core of the transaction. A properly structured escrow for a .net domain purchase runs in the following sequence.

1. Both parties confirm the escrow terms in writing through the chosen neutral escrow service. The buyer deposits the full purchase price. The escrow service holds the funds; neither party can access them until the agreed condition is met.
2. The seller initiates the transfer by generating an authorization code (also called an EPP code or auth code) from the registrar where the domain is currently held. This code is the key that allows the gaining registrar to pull the domain.
3. The buyer submits the auth code to their chosen gaining registrar, which initiates the inter-registrar transfer request under ICANN's transfer policy. The losing registrar has five days to approve or deny; silence is treated as approval in most cases.
4. Transfer completion is verified — the buyer confirms that the domain now appears in their registrar account, with the correct WHOIS/RDDS registrant data, before authorizing the escrow release.
5. The buyer authorizes release of funds from escrow to the seller. The escrow service disburses. The transaction is complete.
6. The buyer immediately locks the domain at the gaining registrar — a registrar lock (also called a transfer lock or client transfer prohibited status) prevents any outbound transfer for the lock period, typically 60 days post-transfer under ICANN rules.

The trap in Step 4: some buyers authorize escrow release based on seeing the transfer email notification rather than confirming actual account delivery. Email notifications can be delayed, duplicated, or spoofed. Always verify in the registrar's live control panel before releasing funds.

A second trap: using an informal "escrow" arrangement — a lawyer's trust account, a payment processor, or a payment-on-delivery promise — is not the same as a neutral escrow service. A neutral escrow service has documented procedures for handling failed transfers and disputes between the parties. An informal arrangement may have none of those.

Step 5: Address the UDRP risk window after transfer

Once the .net domain is in your registrar account and the funds have released, you are the registrant. Under the UDRP, that means you are the respondent in any future complaint. The UDRP risk window — the period during which a challenge is most likely — opens immediately after a high-profile acquisition and does not close until your legitimate interest in the domain is established and documented.

Panels have consistently held that a new registrant cannot inherit a prior registrant's bad faith, but they have also held that a new registrant who continues the same bad-faith use can be found independently liable under the Policy. If you acquired the domain to monetize it with advertising, update the advertising feed to reflect your intended use before any complaint is filed. If you acquired it for a project, begin that project — or at minimum, document the intent — promptly.

What evidence decides the outcome of a future UDRP challenge against you? The key record you need to assemble is: the purchase agreement and due-diligence output from Steps 1 and 2; evidence of your own trademark, business name, or personal name interest in the domain string; evidence of a bona fide offering of goods or services under the name, or a demonstrable preparation to launch one; and the contemporaneous record of your intent at the time of acquisition. Paragraph 4(c) of the UDRP lists these as safe harbors — they are defenses, not excuses, and they must be grounded in evidence.

In a matter we handled in autumn 2025, a domain investor acquired a five-letter .net for a mid-five-figure sum and faced a UDRP complaint within three months of the transfer. The purchase documentation — including the prior-dispute-history check, the trademark search, and the contemporaneous project roadmap — established a bona fide legitimate interest. The complaint was denied. The seller's warranty of clean title also preserved a contractual claim for the investor's legal costs.

If you have already completed a .net domain acquisition and are now facing a UDRP complaint, email info@cognomenlaw.com to assess the three elements and build the legitimate-interest record.

Cross-zone considerations: when the same name exists in .com and .net

A .net purchase rarely happens in isolation. The same brand or keyword string often exists as a .com, a .org, and potentially a national ccTLD registration. Each zone is legally independent — a UDRP complaint against a .com does not automatically transfer the .net — but the pattern of registrations matters to the analysis.

Consider two scenarios. In the first, you are acquiring a generic .net domain and the corresponding .com is held by a brand owner who has not yet filed a complaint. The brand owner's trademark rights and the .com registration together suggest a future UDRP filing is plausible. Your due diligence should evaluate the brand owner's trademark status before you complete the .net purchase.

In the second scenario, you already hold the .com and are acquiring the .net to consolidate your brand's namespace. Here the risk runs the other way: a third party holding the .net might assert that your .com registration was itself a bad-faith attempt to disrupt their use. If there is a dispute about who has prior trademark rights, a UDRP complaint on the .net could surface that dispute. We have seen cases where a .net acquisition triggered a counter-complaint on the .com the buyer thought was safe.

Multi-zone acquisitions benefit from a single due-diligence process that maps all zones simultaneously, identifying both the risk to you as the new .net owner and the risk to your existing portfolio. COGNOMEN handles multi-zone due diligence as part of its domain-transaction practice.

The choice of forum, if a dispute does arise, also has a cross-zone dimension. For a .net domain, the UDRP is available at WIPO, the Forum, CAC, and ADNDRC. WIPO and the Forum together account for roughly 97% of all UDRP proceedings. For any ccTLD companion domain — a .uk version at Nominet or a .eu version at ADR.eu — a separate procedure with different rules and fees applies. A .de companion domain sits outside the UDRP system entirely and requires German court proceedings, with a DENIC dispute entry available to block transfer while litigation proceeds.

Avoiding a tainted acquisition: the RDNH angle for buyers

One scenario that buyers rarely anticipate: the seller of the .net domain was previously a respondent in a UDRP proceeding that resulted in a finding of bad faith, but the complainant elected not to pursue transfer and the domain remained with the seller. A new buyer who acquires that domain knowing the dispute history — or without checking it — faces a very difficult UDRP defense. Panels have held that a pattern of bad-faith use by prior registrants can be relevant to whether a new registrant's identical use is in bad faith.

The reverse situation also arises. A seller who has held the domain for years and built genuine value in it may be pressured by a brand owner who files a UDRP complaint not to recover a cybersquatted domain but to take the domain away from a legitimate registrant. That is Reverse Domain Name Hijacking — a finding that the complaint was brought in bad faith to deprive a legitimate registrant. RDNH findings carry no monetary penalty but are publicly recorded and reputationally significant for the complainant.

As a buyer, you inherit neither the seller's bad faith nor the seller's RDNH protection. Your position is assessed on your own conduct and your own rights. That is why the documentation you build at each step of this guide is the only record that will protect you in a future proceeding.

Related at COGNOMEN

• Domain transaction services: purchase, sale, due diligence, and escrow structuring
• Chain-of-title verification before a domain acquisition closes
• Registrar lock escalation: protecting a transferred domain after closing