How to structure escrow for a .it domain purchase

How to structure escrow for a .it domain purchase. UDRP and ccTLD domain recovery and defense across .it. Email the firm to assess your case.

You have found the .it domain you want. The seller is willing. Now the practical question: how do you pay for a country-code name registered in Italy without losing either the money or the domain? Structuring escrow for a .it domain purchase is not the same as buying a .com. The zone has its own eligibility rules, a distinct registrar-level transfer workflow, and a chain-of-title risk that can follow the name after you acquire it.

To structure escrow for a .it domain purchase, a buyer must verify that the domain meets Italian Registry (Registro.it) eligibility requirements, conduct a chain-of-title and prior-dispute check, appoint a neutral escrow agent to hold funds while the transfer is confirmed at the registry level, and only release payment once the name resolves in the buyer's account. The transfer itself is governed by Registro.it's Reassignment procedure, not by UDRP mechanics. A properly sequenced transaction typically closes in a matter of days once the technical transfer is initiated – but the due-diligence work before that point is where deals go wrong.

This page covers the eligibility check, the due-diligence steps, the escrow mechanics, common deal-breakers, and the cross-zone considerations that arise when a transaction spans .it and other zones.

What makes .it different from a .com purchase?

A .it domain is administered by Registro.it, the Italian national registry operated by the National Research Council (CNR), and its rules sit outside the UDRP ecosystem for direct transfers. Where a .com purchase is a contractual arrangement between private parties enforced through ICANN-accredited registrar procedures, a .it transfer requires the registry to record the new registrant – and that registrant must meet eligibility criteria that do not exist for most gTLDs.

Registro.it currently allows registration by natural persons and legal entities with a presence in the European Union or European Economic Area. That presence requirement matters for a buyer outside that geographic zone. An acquirer who does not meet eligibility cannot complete the transfer at the registry level, regardless of what the sale contract says. This is the first question to answer before any escrow structure is designed.

Beyond eligibility, .it has no native arbitration procedure equivalent to UDRP or the Nominet DRS for .uk. Disputes over .it domains have historically been handled through the Italian courts or, in some cases, through WIPO on a voluntary basis where the holder has consented. That absence of a fast arbitration track means a tainted domain – one with a prior dispute or a questionable chain of title – is harder to unwind after the fact. Pre-acquisition due diligence is therefore not optional. It is the primary risk-control mechanism available to a .it buyer.

A buyer who skips the eligibility and chain-of-title check and closes escrow quickly can find themselves holding a name that the registry cannot formally assign to them, or one that a prior legitimate claimant can contest through national courts with no fast-track arbitration alternative available.

How do you verify eligibility before structuring escrow for a .it domain purchase?

Eligibility verification is the threshold step, and it runs in parallel with – not after – the negotiation. Registro.it publishes its eligibility categories, and the buyer's counsel should confirm before funds are committed that the proposed new registrant fits within them. If the buyer is a non-EU entity, it may need to appoint an EU-established administrative contact or restructure the acquiring entity before the transfer can proceed.

The seller's eligibility at the time of original registration also matters. A domain registered by a holder who did not meet Registro.it's criteria at registration is a domain with a defective chain of title. That defect does not automatically surface in a WHOIS/RDDS lookup, but it does affect the validity of the registration and therefore the marketable title being sold. In our practice, we routinely request the original registration documentation from the seller as part of pre-signing due diligence on any .it transaction.

The WHOIS/RDDS record for a .it domain typically shows registrant name, registrar, creation date, expiry date, and status codes. Status codes indicating a hold, pending transfer, or dispute flag are immediate deal-breakers pending investigation. A name approaching expiry within the transaction window requires escrow terms that account for renewal or the risk that the domain lapses before transfer completes.

What chain-of-title and prior-dispute checks must precede any .it escrow structure?

Chain-of-title for a domain is the sequence of registrant records from the original registration to the current holder. For .it, that history is partially available through historical WHOIS data, registry logs (where accessible), and – critically – through a search of prior dispute records. Unlike .com, where WIPO and the Forum maintain publicly searchable databases of decided UDRP cases, .it dispute history requires a broader search: Italian court records, WIPO's optional voluntary procedure records where applicable, and any domain-specific mentions in trademark databases.

The checks we run on every .it acquisition include:

• Historical registrant records to identify prior ownership chains and any unexplained gaps.
• Italian trademark registry search against the domain string and close variants, to identify third parties with potential claims.
• EU trademark (EUTM) search, since an EUTM owner has rights across the EU and Italy.
• WIPO case database search for any UDRP or voluntary .it proceeding naming this domain.
• Italian court record search (handled with local litigation counsel in the relevant jurisdiction) for any pending or decided action involving the domain.
• Review of domain-specific auction and marketplace history for evidence of prior monetization that could signal bad-faith registration patterns.

A domain that shows a prior UDRP complaint – even one that was denied or withdrawn – signals that a third party believed it had trademark rights over the name. That prior claim does not disappear on transfer. A new buyer takes the name with constructive notice of that history. If the prior claimant's trademark has since matured or its market position has grown, a future challenge becomes more plausible, not less.

In a recent matter (a .it acquisition, spring 2025), we identified through pre-signing due diligence that a domain the client wished to purchase had been the subject of a voluntary WIPO proceeding roughly four years earlier, withdrawn before decision. The underlying trademark owner remained active in the Italian market. We advised the client to seek a written indemnity from the seller covering any future third-party claim arising from the pre-transfer registration period, and to obtain title insurance before closing. The deal completed, but on terms that would not have been negotiated without that prior-dispute discovery.

For a chain-of-title review of a .it domain you are considering purchasing, contact info@cognomenlaw.com.

How should escrow be structured for a .it domain transfer?

The fundamental principle of domain escrow is that neither party bears delivery risk alone. The seller does not transfer until funds are secured; the buyer does not release funds until the domain resolves in their account. For a .it domain, that principle must be implemented against the backdrop of a registry-level Reassignment procedure, not a simple registrar-push as with most gTLDs.

A workable .it escrow structure has four sequenced stages:

1. Escrow account funded. The buyer deposits the agreed purchase price with a neutral third-party escrow agent before any transfer action is initiated. The escrow agent holds, but does not release, the funds.
2. Seller initiates Reassignment at Registro.it. The seller's registrar submits the change-of-registrant request through the registry's Reassignment workflow. Registro.it confirms acceptance of the new registrant's credentials and eligibility.
3. Buyer confirms registry-level completion. The buyer – or the buyer's counsel – verifies through an independent WHOIS/RDDS query that Registro.it has recorded the new registrant name, and that the domain is not subject to any post-transfer hold or status flag.
4. Funds released to seller. Only after Step 3 is confirmed does the escrow agent release payment to the seller.

The escrow agent should be a neutral, regulated entity with a published escrow agreement that specifies the exact conditions for release, the dispute-resolution mechanism if a condition is contested, and the timeline within which each party must act. The escrow period should be long enough to accommodate Registro.it's processing time but short enough to protect the seller from indefinite hold of funds. In our experience, a window of five to ten business days from Step 2 to Step 3 is realistic for a straightforward Registro.it Reassignment, absent any registry hold.

Currency and payment method should be specified in the sale agreement, not left to the escrow provider's default. For .it transactions involving Italian or EU-based sellers, euro-denominated escrow with a SEPA-compatible agent avoids conversion risk and aligns with the seller's expectations. Cross-currency escrow introduces FX risk during the hold period, which both parties should contractually address.

What should the sale agreement cover beyond the escrow mechanics?

The sale agreement is the document that governs the parties' rights if the escrow collapses, the transfer fails at the registry, or a third party challenges the name after closing. For a .it purchase, it should address at minimum:

• Seller's representations and warranties: that the seller is the lawful registrant, that the domain was registered in compliance with Registro.it eligibility rules, that no third-party claim is pending or threatened, and that no prior dispute has been filed and not disclosed.
• Indemnity: seller indemnifies buyer for any claim arising from the domain's pre-transfer registration or use. This is especially important where due diligence has flagged a prior dispute or a third-party trademark.
• Condition precedent: the obligation to pay is conditioned on successful completion of the Registro.it Reassignment and confirmation that no post-transfer hold has been applied.
• Governing law and jurisdiction: for a .it domain, Italian law and Italian jurisdiction is the default that an Italian court will apply. Parties may attempt to agree an alternative jurisdiction, but enforcement of a non-Italian judgment against an Italian asset requires an additional recognition step.
• Escrow release mechanics: the exact trigger for fund release, including who has authority to confirm Step 3 and how a dispute over that confirmation is resolved.
• Domain renewal during the escrow window: who is responsible if the domain approaches expiry during the transaction and must be renewed to preserve the registration.

A short-form term sheet agreed before due diligence is common in faster-moving deals. The full sale agreement should be negotiated in parallel with the due-diligence phase so that the signed documents are ready to execute the moment the buyer is satisfied with the chain-of-title review. Delay between due-diligence completion and execution creates a window in which the seller's situation – or the registry status of the domain – can change.

To review a draft sale agreement for a .it domain acquisition, or to prepare one, email info@cognomenlaw.com.

What are the cross-zone considerations when a .it acquisition is part of a broader portfolio deal?

Many .it acquisitions are not standalone. A brand purchasing its name in Italy is often acquiring or already holds the .com, the .eu, and possibly national ccTLDs in other EU markets. Each zone requires a separate transfer, a separate eligibility check, and – critically – a separate dispute-risk assessment, because a prior claim in one zone does not automatically correspond to a claim in another.

The right route depends on the zone and the goal. If the transaction includes a .com, the escrow can typically be structured as a single agreement with the .com push and the .it Reassignment as parallel deliverables, with fund release conditioned on completion of both. That structure works where the same seller controls both registrations. Where the .com and .it are held by different registrants, the transactions must be structured separately, with independent escrow arrangements and independent due-diligence tracks, because a failure in one does not legally excuse performance on the other.

If the .it acquisition is preceded by or accompanies a dispute – for example, a voluntary WIPO proceeding against the current holder, or Italian court action – the purchase agreement should reflect that procedural posture explicitly. Buying a domain while a dispute is pending raises questions about whether the transfer will be blocked by a registry hold or a court order. Registro.it may place a technical lock on a domain that is subject to active litigation. Timing the commercial transaction around the procedural calendar, rather than ignoring it, is the only reliable way to close cleanly.

For transactions that involve a .eu alongside .it, the comparison between UDRP and national ccTLD procedures provides useful context on how dispute risk differs across zones in the European market. The .eu zone operates under EURid's ADR procedure, and a domain with a prior EURid/ADR.eu finding carries a documented dispute history that a .it due-diligence search should cross-reference.

In a second recent matter (a multi-zone acquisition covering .it and .de, summer 2025), we structured two independent escrow agreements with a coordinating clause: if either registry transfer failed to complete within the agreed window, the buyer had the right to terminate both agreements and recover all escrowed funds. That structure protected the buyer against a partial acquisition – paying for .it but losing .de to a registry hold, or vice versa – without requiring the seller to bear indefinite escrow risk.

How does COGNOMEN approach a .it domain purchase transaction?

We handle .it domain purchase transactions as a sequence of discrete steps, not as a single closing event. The sequence matters because each step reveals information that affects the next one. We do not advise a client to sign a sale agreement before the chain-of-title review is complete, and we do not advise fund release before registry-level confirmation is in hand.

Our standard approach to structuring escrow for a .it domain purchase covers: eligibility verification for the acquiring entity; historical WHOIS and chain-of-title analysis; trademark and prior-dispute search (EU and Italian); coordination with local litigation counsel in Italy for any court-record searches required; drafting or reviewing the sale agreement and escrow terms; supervising the Registro.it Reassignment workflow; and confirming completion before advising escrow release.

Where the deal surfaces a third-party trademark risk that cannot be cleared through contractual indemnity alone, we assess whether the risk warrants a title-insurance product, a price reduction to reflect contingent liability, or – in some cases – a decision not to proceed. No .it domain is worth acquiring if the chain-of-title carries an unresolvable claim from a third party with real trademark rights in the Italian market.

For a broader overview of domain transaction services – including pre-acquisition due diligence across multiple zones and portfolio brand-protection monitoring – see COGNOMEN's domain transaction practice. For guidance on recovering a lapsed domain registration in a related zone, see our page on recovering a lapsed .nl domain.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand-protection monitoring
• How to recover a lapsed domain registration in the .nl zone
• UDRP versus national ccTLD procedures: choosing the right route