How to draft a domain assignment agreement for a .it domain

How to draft a domain assignment agreement for a .it domain. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your case.

A brand owner locates the .it domain matching its registered mark. The current registrant is willing to sell. Both sides want the transaction closed quickly and cleanly – but neither wants to discover, six months later, that the domain carried a prior dispute, a disputed chain of title, or a registration defect that voids the transfer under Italian rules. Drafting the assignment agreement correctly is where the deal either holds or unravels.

To draft a domain assignment agreement for a .it domain, the document must address Registro.it's specific Reassignment procedure, confirm clean chain of title, structure payment through escrow, and bind both parties on representations about prior disputes and encumbrances. There is no standard UDRP transfer mechanism for .it; the governing national procedure applies, and the agreement must be built around it. A sound assignment agreement also documents the consideration, the warranties, and the post-transfer notification steps required by Registro.it.

This page covers the governing procedure, the chain-of-title checks that protect the buyer, the escrow structure that protects both sides, and the specific provisions your agreement should carry.

Why .it domain transfers follow a different path than .com

The .it zone is administered by Registro.it, Italy's national registry, and it operates under rules that differ materially from the UDRP that governs .com, .net, and most new gTLDs. There is no UDRP for .it. Disputed .it domains are handled either through the Registro.it Dispute Resolution Service – a national procedure with its own eligibility and timing rules – or through Italian courts. Consensual transfers follow Registro.it's published Reassignment procedure, not a UDRP-style transfer order.

That distinction matters for the assignment agreement. A .com assignment can be drafted on largely generic terms and executed through a registrar-level domain push or auth-code transfer. A .it assignment must be structured around the Registro.it Reassignment process: the outgoing registrant (the "assignor") and the incoming party (the "assignee") each take steps through their respective registrar agents. The agreement must name those steps, allocate responsibility for completing them, and set a deadline by which the Reassignment must be confirmed. If the Reassignment is not completed within the window that Registro.it allows, the transaction stalls – and the buyer needs a remedy clause in the agreement for precisely that scenario.

The eligibility question is also zone-specific. Registro.it imposes residency and entity requirements on .it registrants. Any assignee must confirm they meet those requirements before the agreement is signed, not after. An agreement that closes before eligibility is confirmed may be unenforceable at the registry level, leaving the buyer with a contractual right but no domain.

For an assessment of your domain transaction and the specific provisions your .it assignment agreement needs, contact info@cognomenlaw.com.

What does the Registro.it Reassignment procedure require?

Registro.it's Reassignment process is the technical mechanism by which a .it domain changes hands between two consenting parties. Both the outgoing and incoming registrant must have a registrar agent that is accredited with Registro.it. The procedure is initiated by the assignor's registrar and must be accepted by the assignee's registrar within the period Registro.it prescribes. Failure to act within that window cancels the operation; the domain remains with the assignor.

The assignment agreement should set out the precise sequence: which party initiates, which party accepts, and what happens if either registrar fails to act in time. It should also address the WHOIS/RDDS update – Registro.it's public registration data will reflect the change once the Reassignment completes, and the agreement should confirm that both parties will cooperate with any post-transfer validation steps the registry requires.

One procedural wrinkle that regularly surprises buyers: Registro.it distinguishes between a Reassignment (consensual transfer between living entities) and a succession or corporate acquisition. If the .it domain is held by a company that is itself being acquired, the domain may move as part of that corporate transaction without a separate Reassignment – but Registro.it still needs to be notified. The assignment agreement should specify which mechanism applies to avoid a mismatch between the legal structure of the deal and the registry's expectations.

In our practice, we advise buyers to build a 10-business-day Reassignment window into the payment-release mechanics of the escrow. That buffer accommodates minor registrar delays without giving either party grounds to terminate prematurely. We regularly advise registrants and brand owners on exactly how that sequencing should be documented.

How should chain-of-title checks protect the buyer before signing?

Buying a .it domain without a chain-of-title check is roughly equivalent to buying real property without a title search. The domain may carry a prior dispute, a prior transfer that was itself contested, or a registration that was obtained in violation of the previous holder's rights. Discovering any of those facts after the assignment completes leaves the buyer with a domain they paid for but may not be able to hold.

The minimum chain-of-title inquiry for a .it domain before signing an assignment agreement covers four areas. First, the current RDDS (WHOIS equivalent) record: who is the registrant of record, who is the registrar of record, and when does the registration expire. Second, the prior-dispute history: has this domain been the subject of a Registro.it dispute procedure or Italian court proceedings. Third, the registration history: how many times has this domain changed hands, and were those transfers properly executed under Registro.it rules. Fourth, any encumbrances: has the domain been pledged, attached, or listed as an asset in insolvency proceedings.

The assignment agreement should require the assignor to represent and warrant, as of the date of signing and as of the transfer completion date, that: the domain is free from any pending or threatened dispute; no prior transfer was made in violation of any third-party rights; no court order, attachment, or insolvency proceeding encumbers the domain; and the assignor has full legal capacity and authority to assign. A breach of those representations should give the buyer a right to unwind the transaction and recover the purchase price from escrow.

In a recent matter – a .it domain transaction, early 2025 – a pre-signing chain-of-title check revealed that the domain had been subject to an earlier Registro.it dispute in which the prior registrant had been found to have registered abusively. The domain had subsequently been transferred consensually, but the acquirer in that earlier transfer had never fully resolved the question of whether its own registration was clean. Our due-diligence review surfaced that history; the buyer renegotiated the price and obtained additional indemnification before closing.

See our related page on verifying chain of title for domain acquisitions for the full due-diligence framework we apply across gTLD and ccTLD transactions.

How should the escrow structure be designed to protect both sides?

A domain assignment agreement that relies on simultaneous exchange – payment against domain delivery, with no intermediary – exposes both parties. The buyer risks paying for a domain that never transfers. The seller risks completing the Reassignment before receiving cleared funds. A properly structured escrow eliminates both risks by holding funds and domain delivery instructions in the custody of a neutral intermediary until both legs of the transaction are confirmed.

For a .it assignment, the escrow mechanics work as follows. The buyer deposits the agreed consideration with the escrow provider before the Reassignment is initiated. The escrow provider confirms receipt of funds to both parties and to the registrars. The Reassignment is then initiated by the assignor's registrar and accepted by the assignee's registrar. Once Registro.it confirms the domain is now registered in the assignee's name, the escrow provider releases the funds to the seller.

The assignment agreement should specify the escrow provider by name, define what constitutes "confirmation of transfer" (typically a written confirmation from Registro.it or from the assignee's registrar that the RDDS record has been updated), and set a longstop date beyond which either party may cancel if the Reassignment has not completed. The longstop date should be realistic – allowing for registrar processing times and any technical review Registro.it may require – but not so long that it gives a bad-faith seller an extended window to manipulate the process.

Currency and tax mechanics also belong in the agreement. If the buyer and seller are in different jurisdictions – for example, an EU entity buying from a non-EU seller – VAT treatment, withholding obligations, and currency of payment must all be addressed. An agreement silent on those terms creates disputes at the point of payment release.

To weigh UDRP against a court action for your case, or to structure an escrow for a .it domain acquisition, email info@cognomenlaw.com.

What provisions must the assignment agreement contain?

A .it domain assignment agreement is a contract. Its enforceability depends on the same formation requirements as any commercial contract under the applicable law – offer, acceptance, consideration, and the legal capacity of both parties. Beyond those basics, several provisions are specific to domain assignments and especially to .it.

The agreement must identify the domain with precision: the full domain name, the Registro.it registration number if available, the name of the registrant of record, and the registrar of record as of the signing date. A domain identification clause that relies only on the domain string itself creates ambiguity if the registrar or registrant record changes between signing and closing.

The consideration clause should state the purchase price, the currency, the escrow mechanics, and the conditions for release. It should also address what happens if the Reassignment fails through no fault of either party – for example, a technical freeze imposed by Registro.it – and how costs are allocated in that scenario.

The representations and warranties clause, described above under chain-of-title checks, is the buyer's main protection. The seller's main protection is a limitation on those warranties: reasonable time limits on claims and a cap on liability are standard in domain transactions and should be negotiated explicitly.

The governing law and jurisdiction clause matters more in .it transactions than in generic .com deals, because the Reassignment procedure is governed by Italian registry rules even if the parties choose a different governing law for the contract itself. The agreement should acknowledge that registry-level mechanics follow Registro.it rules regardless of the contractual governing law, to avoid a later argument that the contract requires steps the registry will not recognize.

Post-transfer obligations should also be covered: who notifies Registro.it of any required documentation, who updates the administrative contact, and how the seller cooperates if the buyer later needs to demonstrate chain of title to a third party or a future buyer.

How does a .it dispute procedure differ from a court action?

When a .it domain cannot be acquired consensually – because the registrant refuses to sell, is unreachable, or is using the domain in a way that infringes established rights – the buyer's options split between the Registro.it dispute procedure and Italian court proceedings. Understanding that split is essential context even for a consensual transaction, because the viability of those alternatives affects negotiating leverage.

The Registro.it dispute procedure is an administrative mechanism. It allows a rights-holder to challenge a .it registration on grounds broadly similar to those in the UDRP – that the domain was registered in bad faith and infringes established rights – but the specific test and the procedure differ from the UDRP. The remedy, if the complaint succeeds, is reassignment of the domain to the complainant or cancellation. The procedure is substantially faster than litigation and less expensive, but it is not available to parties who simply want a domain the current registrant is legitimately holding.

Italian court proceedings provide a broader range of remedies, including injunctive relief, damages, and orders against third parties such as hosting providers. They take longer and cost more than administrative procedures. They are appropriate where the facts are complex, where damages are significant, or where the domain is being used as part of a wider infringement scheme that court discovery could expose.

For a buyer in a consensual transaction, the practical point is this: if the seller knows that the buyer has a realistic path to the domain through dispute or litigation, the negotiation dynamics change. We regularly advise clients on whether those alternative routes are available – and we use that assessment to calibrate the transaction strategy, not just the dispute strategy.

In a recent matter – a .it dispute assessment, autumn 2024 – we advised a European brand owner that its rights position was strong enough to support a Registro.it complaint, but that the domain had commercial value to the current registrant for legitimate reasons. The brand owner used that assessment to make a market-rate offer that settled the matter without a formal procedure. The assignment agreement was structured and executed within three weeks of the assessment.

What cross-zone considerations arise when the brand also holds .com or .eu?

Brand owners rarely operate in a single zone. A brand that holds a .it domain is typically also registered – or interested – in .com, .eu, and one or more other ccTLDs. A domain transaction that addresses only the .it creates gaps.

The right approach depends on the situation. If the brand already holds the .com and is acquiring the .it to consolidate control, the assignment agreement can be drafted as a standalone .it transaction. If the brand is acquiring both the .it and the .eu from the same seller, a single agreement can cover both domains – but it must acknowledge that the two zones have different registries, different eligibility rules, and different Reassignment mechanics. The EURid procedure for .eu differs from Registro.it's procedure for .it; an agreement that treats them identically will create operational problems at the transfer stage.

If the brand has not yet secured the .com, any .it acquisition should be paired with a priority assessment of the .com availability. A brand that holds .it but not .com is exposed to a .com cybersquatting registration by a third party who observes the .it activity. The UDRP is available for .com, and a well-documented .it registration can support the trademark-rights element of a later UDRP complaint – but prevention is faster and less expensive than recovery.

We have defended and prosecuted UDRP complaints involving brands with .it registrations. See our page on UDRP recovery in the finance sector for the kind of cross-zone brand-protection work that commonly accompanies a .it acquisition. For a broader view of our transaction services, see our domain transactions practice overview.

What myths stop buyers from protecting themselves in a .it acquisition?

The most common misconception we encounter is that a domain assignment is a simple bilateral agreement requiring no more than a purchase price and a transfer instruction to the registrar. That view may hold for some .com transactions between experienced domainers. It does not hold for .it. The Registro.it Reassignment procedure has its own steps, its own timing, and its own failure modes – and an agreement that ignores them gives neither party a reliable path to completion.

A second misconception is that the seller's warranty is sufficient protection. Warranties are only as good as the warrantor's ability to perform or pay. If the seller is a thin-capitalized entity, an insolvent individual, or a foreign registrant with no assets in the relevant jurisdiction, a contractual warranty provides theoretical protection but no practical recovery. The chain-of-title check and the escrow structure are the practical protections; the warranty supplements them.

A third misconception – less common but potentially costly – is that a .it domain acquired without a dispute history check is necessarily clean. Registro.it's public records do not always surface every prior dispute or every contested transfer. A thorough due-diligence inquiry requires going beyond public records: reviewing any litigation involving the domain, checking the registration history against known dispute patterns, and, where the domain has high commercial value, instructing counsel to obtain a written legal opinion on title.

The answer to all three misconceptions is the same: treat a .it domain acquisition as a structured transaction, not an informal exchange. The additional time and cost of proper documentation are modest compared to the cost of unraveling a flawed transfer.

Related at COGNOMEN

• Domain Transactions Practice – purchase, sale, escrow, and pre-acquisition due diligence across gTLD and ccTLD zones
• Verify Chain of Title – the full due-diligence framework for domain acquisitions
• UDRP Recovery in Finance – cross-zone brand protection and gTLD dispute strategy