FAQ: draft a domain assignment agreement for a .net domain

When can I draft a domain assignment agreement for a .net domain?

You can draft a domain assignment agreement for a .net domain at any point in a voluntary sale or transfer — before or after agreeing on a price, but always before moving the domain at the registrar. Timing matters. Execute the agreement and fund escrow before releasing the authorization code (auth-EPP code). If the domain is subject to a registrar lock or a pending UDRP proceeding, neither party should sign until the lock is lifted or the proceeding resolves, because a mid-dispute transfer does not extinguish the complaint and the incoming registrant may inherit the respondent position.

The agreement should be signed by the legal owner of record — the entity or individual listed as registrant in WHOIS/RDDS — not merely an administrative contact or a broker acting without written authority. Where the registrant is a company, confirm that the signatory holds the authority to dispose of domain assets; a domain registered to a subsidiary cannot be validly transferred by the parent without proper authorization. We regularly advise buyers who have received a signed agreement only to discover the seller's WHOIS record listed a different legal entity.

Is there a hard deadline imposed by any rule? No. The UDRP does not require parties to use a formal agreement, but the UDRP gives a respondent only 20 days to file a response once a complaint commences — so if a dispute arises after a poorly documented transfer, the new registrant may find that window closing before the paperwork is even found.

Who can draft a domain assignment agreement for a .net domain?

Counsel with domain-transactions experience should prepare the agreement, because the drafting decisions — representations on UDRP clean title, dispute-history warranty, indemnification scope — require familiarity with both the UDRP and general contract law. A generic IP assignment template does not address the registrar mechanics, the escrow trigger, or the chain-of-title representations that a .net buyer specifically needs.

The minimum contents of a properly drafted agreement include: identification of the domain by full name and registry (VeriSign for .net); confirmation of registrant-of-record status; a representation that no pending UDRP, URS, or other administrative proceeding is active or threatened; a warranty that the seller has not previously been ordered to transfer or cancel the domain; the escrow structure and release conditions; the mechanism for transmitting the authorization code; confirmation that the domain is not subject to a registrar lock or hold; and the choice-of-law clause governing any contract dispute.

Beyond the agreement itself, a competent draftsperson will run pre-acquisition due diligence: a search of WIPO's online UDRP case database for prior proceedings involving the domain, a check of the Forum's and CAC's case records, a review of WHOIS history where available, and a lien or encumbrance check on the registrant entity. We handle that due-diligence sweep as part of our domain transaction services, because a clean agreement over a tainted name offers no real protection.

What elements decide whether a .net domain transfer is clean?

Three elements determine whether a .net domain transfer is clean: the registrant's chain of title, the absence of prior dispute findings, and the absence of any active or threatened proceeding at the time of transfer. Each requires a specific check, not a representation from the seller alone.

Chain of title means tracing the registered owner from the original registration through every subsequent change. Gaps in WHOIS history — a period of privacy-masked registration, a bulk transfer between registrars, or a name-change on the account without a formal assignment — each create ambiguity about whether the current seller ever held valid title. A seller who acquired the domain through an informal "I'll send you the login credentials" arrangement almost certainly has a defective title to assign.

Prior dispute findings are the higher risk. If a UDRP panel previously ordered transfer or cancellation and that order was not implemented — whether through a court injunction, a registrar error, or an expired registration that was subsequently re-registered — the domain may still carry a cloud. Panels have consistently held that a subsequent registrant who acquires a domain with knowledge of a prior adverse finding cannot cleanse it by re-registration.

Active proceedings are a structural bar. Under UDRP procedure, the registrar locks the domain for 20 days after a decision to allow for court challenge. Any acquisition during that window is procedurally blocked at the registrar level. Confirm the lock status before executing the agreement.

For a detailed examination of how chain-of-title checks work in practice — and the specific WHOIS and dispute-record searches they require — see our analysis of verifying chain of title before a domain acquisition.

If you are buying or selling a .net domain and need the agreement drafted and the due-diligence sweep run concurrently, contact info@cognomenlaw.com for an assessment.

Does WIPO or a court decide a .net dispute?

A .net domain dispute is decided under the UDRP — an administrative arbitration, not a court proceeding — with WIPO and the Forum together handling roughly 97% of all UDRP proceedings. The complainant files before one of the accredited providers; neither a national court nor a government agency decides the outcome. The only remedies available under the UDRP are transfer or cancellation of the domain; no monetary damages are awarded.

This matters for a domain assignment agreement because the contractual disputes between buyer and seller are a completely separate channel. If the seller misrepresented that the domain was UDRP-clean and a complaint subsequently succeeds, the buyer's remedy against the seller runs through the courts — contract or tort — not through WIPO. The assignment agreement should therefore contain an indemnification clause covering the cost of defending a UDRP proceeding (forum fee plus legal fee) and the loss of the domain itself if a transfer order issues.

Can a buyer file a UDRP complaint to recover a domain the seller had no right to transfer? Possibly — but only if the buyer now holds a trademark in the name. The UDRP does not resolve title disputes between private parties; it adjudicates between a trademark holder (complainant) and a registrant (respondent). A buyer defrauded in a domain sale generally has better remedies in a court of competent jurisdiction, and we work with local litigation counsel in the relevant jurisdiction where court action is the appropriate path.

What if the registrant does not respond to a UDRP complaint?

If the registrant fails to file a response within the 20-day response window, the panel proceeds to a decision on the complaint alone. Default is not an automatic transfer — the panel still examines whether the complainant has met all three UDRP elements on the evidence presented. In practice, panels have consistently issued transfer orders in default cases where the complaint is adequately supported, but a thin complaint can still be denied even in the absence of a response.

For a buyer who has just acquired a .net domain and then receives a complaint, the 20-day deadline is the first hard constraint. Missing it means the panel hears only one side. We have defended registrants in exactly this position — incoming owners who were unaware of a pending complaint against their newly acquired domain and discovered the filing only after the response window had nearly closed. In a recent matter (a .net acquisition, spring 2025), we obtained a short procedural extension and assembled the legitimate-interest record in time to secure a denial.

The assignment agreement cannot prevent a complaint from being filed after transfer, but it can allocate responsibility for responding. A buyer who acquires a domain with a full indemnification, a funded escrow, and a chain-of-title warranty from the seller is at least contractually protected even if the panel ultimately orders a transfer. Without that agreement, the loss falls entirely on the acquiring party.

Can a UDRP decision on a .net domain be appealed or challenged?

A UDRP decision is not subject to a formal appellate process within the UDRP system itself. However, either party may seek de novo review in a court of competent jurisdiction — typically in the registrant's jurisdiction or the jurisdiction specified in the registrar's registration agreement — within the 10-business-day implementation window following the decision. If the registrant obtains a court order staying the transfer within that window, the registrar holds the domain pending the court's resolution.

This appellate-via-court route is the only mechanism that can reverse a UDRP transfer order, and it is rarely used in .net cases because the cost of court litigation typically exceeds the value of the domain. The practical implication for a domain buyer is that an assignment agreement should confirm whether the domain is within or past the post-decision window, and whether any court action has been commenced by a prior respondent. A domain transferred by court order to a complainant who then seeks to resell it is a clean title; a domain transferred informally while a court challenge is pending is not.

Reverse Domain Name Hijacking — a panel finding that the complaint was filed in bad faith to deprive a legitimate registrant — is also available within the UDRP but carries no monetary penalty. Its value is reputational. A registrant who succeeds on an RDNH finding does not automatically receive cost recovery; that, again, would require a court action. For respondent-side strategy, including the pursuit of RDNH findings, see our discussion of UDRP recovery and defense.

If you are defending a UDRP complaint over a .net domain you acquired in good faith, or seeking to challenge a decision in court, email info@cognomenlaw.com for an initial read of the position.

What is the deadline once a UDRP case starts?

Once a UDRP case commences — the provider formally notifies the respondent — the respondent has 20 days to file a response. That clock starts from the date of commencement notification, not from the date the complaint was submitted. A standard case is normally decided within approximately two months of filing, absent procedural complications such as a request for a three-member panel or a suspension for settlement discussions.

The timeline has specific implications for domain assignments. A buyer who takes title and then receives a commencement notification must treat the 20-day window as a drop-everything deadline. Domain disputes resolve on the evidence in the file; a response filed on day 21 is almost certainly rejected. Where the assignment agreement is still in negotiation and the commencement notification arrives, parties sometimes seek a brief procedural suspension — but that requires the agreement of both parties to the UDRP proceeding, which includes the complainant.

After a decision, the registrar implements a transfer within roughly 10 business days if no court action is filed. That implementation window is the buyer's last point of intervention via the court route described above. Documenting the post-decision calendar in the assignment agreement — particularly which party bears the cost of any court action during the implementation window — is a detail that standard IP templates routinely omit.