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

What does it mean to draft a domain assignment agreement for a .it domain?

Drafting a domain assignment agreement for a .it domain means preparing a written contract that conveys legal and administrative title from the current registrant to the buyer, and that the Italian registry – Registro .it – will accept as the basis for updating its WHOIS record. The agreement is not simply a sale-of-goods contract; it must identify both parties precisely, recite the domain in full, state the consideration (even where nominal), include representations that the seller holds the name without encumbrance, and authorize the buyer to instruct the registrar to execute the reassignment. Under .it rules, the reassignment procedure requires the registrant to initiate a change-holder request through the accredited registrar, and the agreement is the foundational document supporting that request. Without a valid written instrument, the registrar has no authority to process the transfer and the registry has no record of the chain of title. Eligibility matters too: the buyer must satisfy Registro .it's current registrant eligibility criteria, which generally require an EU nexus or an Italian address of record. Confirming eligibility before drafting saves a failed transfer later.

What evidence is needed to draft a domain assignment agreement for a .it domain?

The evidence needed falls into three categories: seller identity, domain status, and dispute history. On seller identity, the agreement must match the registrant of record in the WHOIS/RDDS at the time of execution; any discrepancy between the contracting party and the listed registrant creates a chain-of-title defect. Domain status evidence means a current WHOIS printout showing the domain is active, not in redemption grace period, and not subject to a registrar lock or hold. Dispute history is the category most buyers overlook. A .it domain may have been the subject of a prior Italian or EU dispute, a UDRP complaint if it was at some point registered under a gTLD equivalent, or a court proceeding in the Italian courts; the seller's warranty in the agreement must cover all of these, and a prudent buyer will conduct independent pre-acquisition diligence to verify the warranty before completion. We regularly advise buyers who discover prior proceedings only after funds have moved. Additional evidence useful in drafting includes proof of registrar authorization codes (the authInfo or equivalent), any correspondence establishing the agreed price, and, where the seller is a corporate entity, a board or officer authorization showing the signatory's authority to convey.

How long does it take to draft a domain assignment agreement for a .it domain?

Drafting the agreement itself typically takes a matter of days once the parties have agreed on commercial terms and the due-diligence review is complete. The registry reassignment procedure at Registro .it adds time: after the registrar submits the change-holder request, the registry processes it within a window that varies by registrar and load, but is generally measured in days rather than weeks for a straightforward uncomplicated transfer. Total elapsed time from instruction to completed WHOIS update is commonly in the range of one to three weeks, assuming no eligibility issues, no outstanding registry holds, and prompt execution by both parties. Where escrow is used – and we recommend it for any transaction above a nominal value – the escrow provider's settlement cycle adds a further two to five business days depending on the provider and the payment method. If due diligence uncovers a prior dispute or a registrar lock, resolution of those issues can extend the timetable materially. The short version: a clean transaction with a cooperative seller and no eligibility problems closes faster than most clients expect.

For an assessment of your domain transaction, contact info@cognomenlaw.com.

What does it cost to draft a domain assignment agreement for a .it domain at Reassignment?

Cost has two components: legal fees for drafting and due diligence, and registry or registrar fees for the reassignment procedure itself. On the legal side, market rates for a straightforward domain assignment agreement – one domain, no dispute history, clean WHOIS – fall in a range that reflects the complexity of the transaction rather than a fixed tariff; a simple instrument with a short due-diligence review is materially less expensive than a multi-domain transfer with warranty negotiations and escrow coordination. For registry and registrar fees, Registro .it does not publish a separate reassignment fee distinct from the standard annual registration renewal; the registrar may charge an administrative fee for processing the change-holder request, and that fee varies by registrar. Escrow services charge a percentage of the transaction value or a flat fee, depending on the provider and the amount. For very-low-value .it transfers – where the domain's market value does not justify a full escrow structure – the parties sometimes rely solely on the assignment agreement, with the seller initiating the reassignment before receiving payment or both steps occurring simultaneously through registrar coordination. We advise clients on which structure fits their risk profile before any agreement is signed.

Can I draft a domain assignment agreement for a .it domain for more than one domain at once?

Yes. A single assignment agreement can cover multiple .it domains, and a well-drafted instrument typically schedules all domains in an annex rather than creating separate contracts for each name. This approach simplifies execution, consolidates the consideration into a single payment mechanism, and produces one chain-of-title document covering the entire portfolio. However, each domain still requires its own change-holder request at the registrar level; the registry processes reassignments per domain, not per contract. This means the agreement's completion mechanics must account for the possibility that one domain in a batch encounters an eligibility or hold issue while others clear without difficulty. In our practice, we draft multi-domain schedules with domain-by-domain closing conditions so that a problem with one name does not prevent completion on the others. For portfolios spanning .it and other ccTLDs – for example, a brand acquiring both .it and .de simultaneously – we prepare a master assignment agreement with jurisdiction-specific annexes and direct each annexe to the applicable registrar process, coordinating through a single escrow release trigger where feasible.

What are the possible outcomes when you draft a domain assignment agreement for a .it domain?

The realistic outcomes run from clean completion to partial or failed transfer, and the agreement's drafting determines which path the transaction takes. Full completion – both parties execute, the registrar processes the change-holder request, and the buyer's details appear in the WHOIS – is the expected outcome for a properly prepared transaction with verified eligibility and no outstanding holds. Partial completion occurs when a portfolio covers multiple domains and one or more fail for eligibility or technical reasons; a well-drafted agreement anticipates this and sets out the price adjustment mechanism. Failed transfer can result from several causes: the seller is not the true registrant of record (a chain-of-title defect), the buyer lacks the required EU/Italian nexus for eligibility, the domain is under a registrar lock from a prior dispute or registrar hold, or the agreement is contested by a third party with a prior claim. Where the transfer fails after payment, the contractual allocation of risk and escrow structure determines whether the buyer recovers funds. RDNH-adjacent risk can also arise: if the seller is the subject of a prior domain dispute and the assignment is challenged by a brand owner, the buyer may acquire a name already under challenge. Pre-acquisition due diligence – checking prior UDRP and Italian dispute history, reviewing the WHOIS chain, and confirming no active proceedings – is the primary tool for avoiding that outcome. We assess each of these risk vectors before advising a client to sign.

How does the .it Reassignment procedure differ from a standard UDRP transfer?

The .it Reassignment procedure is a consensual, contract-driven process initiated by the current registrant through the registrar; it requires the existing holder's cooperation and produces a voluntary change of title. A UDRP transfer, by contrast, is a mandatory remedy ordered by a panel following a dispute proceeding: the registrant need not cooperate, and the registrar implements the order under ICANN rules. The two processes serve entirely different situations. Reassignment is for an agreed sale or gift. UDRP – or, for .it specifically, the applicable Italian dispute procedure or court route – is for contested recovery where the registrant refuses to transfer. For .it domains, there is no UDRP in the conventional gTLD sense; the governing dispute procedure is administered through the Italian registry's own dispute rules, and contested recovery may require a proceeding before the competent Italian authority or the Italian courts. When a client needs both – a negotiated assignment if the seller agrees, and a dispute filing if they do not – we assess the viability of both routes in parallel before committing the client to either. This dual-track approach preserves negotiating leverage while the dispute window remains open.