Verify chain of title for a .it domain: what panels actually decide
A buyer agrees a price for a valuable .it domain. The seller sends screenshots of the original registration and a signed transfer form. The deal looks clean. Six months later the new owner receives a dispute notice alleging the domain was improperly transferred years earlier – and that the current registrant has no valid title at all. The purchase price is now at risk, the domain may be revoked, and the original dispute has never been resolved.
Verifying chain of title for a .it domain means tracing every registrant-to-registrant transfer from the original registration to the present holder and confirming that no link in the chain is tainted by a disputed or unauthorized change. The governing authority is the Registro .it at the IIT-CNR (National Research Council of Italy), and disputes are resolved under the Italian ccTLD dispute rules – not the UDRP. Because .it disputes can result in revocation or reassignment of a domain, a buyer who skips chain-of-title diligence acquires not just a name but also every unresolved claim attached to it.
This analysis covers what .it panels actually decide on chain-of-title questions, which evidence is dispositive, where consensus and contrary views exist, and how to structure an acquisition so the buyer does not inherit someone else's dispute.
What governing rules apply when you verify chain of title for a .it domain?
The .it ccTLD is administered by the Registro .it under Italian law and its own published dispute-resolution rules, which are entirely separate from the UDRP. Unlike .com or .net, .it is not an ICANN-accredited zone, and no WIPO or Forum UDRP complaint can directly compel a .it registrar to transfer or cancel a registration. Instead, the Registro .it operates a dedicated dispute procedure – commonly called the "Reassignment Procedure" – under which a complainant may seek reassignment of a domain to itself, or in some cases deletion, on the basis of rights in an identical or confusingly similar name.
Chain-of-title questions arise in this procedure in two ways. First, a complainant may argue that an intervening transfer was unauthorized – for example that the original registrant never consented to a change of holder – so that the current registrant holds no valid title and the domain should be reassigned to the complainant. Second, a respondent may assert prior title: that the current registration traces to a legitimate original registration that predates the complainant's rights. Both arguments require the panel (the "Expert" in .it procedure) to examine the full transfer history of the domain.
The .it rules require the registrant of record to be domiciled in the European Union or to have an EU-established presence. That eligibility requirement is itself a chain-of-title issue: a transfer to an ineligible holder can render the registration invalid from the moment of transfer, which affects the legitimacy of every subsequent link in the chain. In our practice advising acquirers of Italian ccTLD assets, we routinely check EU-domicile status at every point in the transfer history, not only at the time of the proposed acquisition.
For an assessment of your domain dispute, contact info@cognomenlaw.com.
How do panels reconstruct the transfer history of a .it domain?
The Expert's first task is to establish a reliable timeline of registrant-to-registrant changes. The primary source is the Registro .it's own WHOIS and historical registration data, which records the holder, the administrative contact, and the registrar at each point. However, this record reflects only what the registrar submitted; it does not independently verify that the holder-of-record at any given moment was authorized by the prior registrant to take title.
Panels therefore look beyond the registry record to corroborating transactional documents. The consensus view is that the following categories of evidence are decisive in reconstructing a clean chain:
- Signed transfer-of-holder forms submitted to the registrar, with dates and the transferor's authenticated identity
- Payment records, escrow confirmations, or correspondence evidencing the commercial transaction underlying each transfer
- Domain purchase agreements that expressly represent the transferor's authority to convey
- Prior WHOIS snapshots from third-party archival sources, compared against the registry's own log
- Registrar-side audit trails, where the registrar will produce them in response to a formal information request under the .it rules
Where the registrar's records and the documentary evidence conflict, panels have consistently given greater weight to registrar-side records on the ground that those records reflect actions actually taken within the registry system rather than self-serving post-hoc documentation. A seller who produces a purchase agreement but cannot explain why the WHOIS change log shows the transfer occurring two weeks before the stated contract date faces a credibility problem that no amount of supplemental evidence fully resolves.
There is a minority panel view – one we have seen argued by respondents in contested reassignment proceedings – that the registry record alone is conclusive and that extrinsic documentary evidence is inadmissible to contradict it. The prevailing approach rejects this position. Panels have generally held that the registry record creates a rebuttable presumption of valid title, not an irrebuttable one, and that clear evidence of an unauthorized transfer can displace it.
What makes a transfer "unauthorized" in .it panel decisions?
An unauthorized transfer, in the .it panel consensus, is one in which the registered holder of record at the time of the transfer did not affirmatively consent to the change. Consent is a factual question, and panels approach it the same way a court would approach a contract formation issue: offer, acceptance, and evidence that the party with standing to transfer actually executed the handover.
The most common scenarios in which panels find a transfer unauthorized are:
- Registrar or reseller fraud: A reseller acting as an intermediary transfers the domain to a third party without the registrant's knowledge, typically to satisfy a debt or in the context of a reseller insolvency. Panels treating this as unauthorized have required the complainant to show a) the original registrant's verified identity, b) that the registrant never submitted a transfer instruction, and c) that the receiving party had notice of the registrant's claim.
- Account-compromise transfers: The registrant's account credentials are stolen; the attacker initiates a change-of-holder before the registrant can act. Panels in these cases treat the transfer as a nullity, treating the purported new holder as having acquired no title even if the registry record reflects the change.
- Estate or corporate dissolution disputes: A company dissolves; its domain is transferred by a former director without the authority of the liquidator or the shareholders. The panel's analysis here turns on Italian corporate law as it intersects with the registrant's authority – and a panel applying the .it rules will not simply accept the WHOIS change as evidence of valid succession.
- Unilateral change by a third-party registrar: A domain is moved from one registrar to another as part of a portfolio transfer, and in the process a change-of-holder is recorded without the domain-specific authorization of the registrant. Panels have split on whether a blanket portfolio authorization is sufficient; the safer consensus view requires domain-specific authorization.
In a recent matter (a .it domain dispute, spring 2025), we identified a reseller-level transfer that had occurred without the original registrant's documented consent. The transferee had held the domain for over three years by the time the dispute was filed. The panel ultimately found the transfer unauthorized and ordered reassignment – demonstrating that even a long-standing registry record does not cure a defective transfer.
What does prior dispute history reveal about .it domain title?
Prior dispute history is one of the most significant and most frequently overlooked elements of a .it chain-of-title check. The Registro .it publishes its decisions, and a domain with even one prior reassignment proceeding carries risk that the purchaser must understand before closing.
A prior proceeding can affect title in three ways. First, if the proceeding ended in a reassignment order, the domain's registration was effectively restarted: the prior registrant's rights were extinguished, and the new registrant's title begins from the reassignment date. Any claim grounded in rights that predate the reassignment may be foreclosed, but a claim grounded in rights predating the original registration may not be.
Second, if the proceeding ended in a withdrawal or a settlement, the terms of that settlement may have created private obligations – a non-transfer covenant, a use restriction, a buyback right – that survive in the domain's history even if they are not visible in the registry record. A purchaser with no notice of those obligations is not automatically protected; the .it rules do not have a bona-fide-purchaser-for-value concept that extinguishes prior private claims.
Third, and most practically dangerous, a pending proceeding at the time of transfer may result in a post-transfer reassignment order. The Registro .it imposes a dispute lock once a proceeding commences, which prevents unauthorized transfers during the proceeding. But where a transfer is completed in the window between the dispute being filed and the lock being registered, panels have generally held that the transfer does not insulate the new registrant from the outcome: the proceeding continues against the new holder.
We regularly advise clients who are mid-negotiation on a .it acquisition to run a Registro .it dispute search as a threshold step, before any price is agreed. The few days that search requires can prevent the acquisition of an asset that is already under active challenge.
To weigh a .it acquisition against its dispute history, email info@cognomenlaw.com.
How should escrow and the sale agreement be structured for a .it domain acquisition?
The structure of the sale agreement and any escrow arrangement is the acquirer's primary contractual protection against inheriting a defective chain of title. A bare agreement to pay in exchange for a transfer-of-holder confirmation is insufficient for a domain whose history you have not independently verified.
In transactions involving .it domains, the agreement should contain at minimum:
- A title representation and warranty: the seller warrants that it holds valid, unencumbered title; that no prior dispute proceeding has resulted in an outstanding obligation affecting the domain; that no proceeding is currently pending; and that no third party has asserted a claim to the domain within the prior 36 months.
- A disclosure schedule: the seller lists every prior holder it is aware of, every dispute or legal proceeding involving the domain, and the basis of its own title (original registration, purchase agreement, inheritance, or corporate succession).
- A condition precedent to closing: the purchaser's obligation to pay is conditioned on its satisfactory completion of a chain-of-title diligence review, including a Registro .it dispute search and a review of the seller's transfer documentation.
- A post-closing indemnity: if a dispute is filed within a defined period after closing based on facts that predate the closing, the seller indemnifies the buyer for the cost of the proceeding and any reassignment loss.
- Escrow with a defined release mechanism: funds are held in escrow until the transfer of holder is confirmed in the registry record and the dispute-lock check is clear.
Escrow is particularly important in .it transactions because the Registro .it's transfer confirmation is not instantaneous. The registrar must process the change-of-holder, and in some cases the outgoing administrative contact must also confirm. Releasing funds before registry confirmation exposes the buyer to the risk of non-delivery; holding funds until confirmation is the market standard for professionally handled .it acquisitions.
In a recent matter (a .it portfolio acquisition involving several domains, autumn 2024), we structured the purchase agreement with a tiered escrow release: a portion released on registry confirmation, a further tranche after a 60-day dispute-monitoring period, and the balance on the first anniversary of closing. The seller accepted this structure because the representation and warranty was matched with a proportionate indemnity cap. The result was a transaction where both parties' risks were allocated proportionately to the information asymmetry at closing.
What evidence decides a .it chain-of-title dispute, and what is the realistic next step after an adverse ruling?
Evidence is the center of gravity in any .it reassignment proceeding where chain of title is contested. Panels decide on the balance of probabilities, and the party bearing the burden of proof – typically the complainant asserting an unauthorized transfer – must produce documentary evidence sufficient to displace the registry record's presumption of valid title.
The evidence categories that panels have found decisive are:
- Authenticated identity documents matching the original registrant's contact details at the time of registration
- Registrar-side transaction logs, where obtainable through a formal production request in the proceeding
- Third-party payment records (bank transfers, escrow confirmations, marketplace transaction receipts) that corroborate or contradict the stated transfer date and price
- Communications between the registrant and the registrar or reseller contemporaneous with the disputed transfer
- Domain-archival snapshots from publicly available services, as circumstantial evidence of control at a given date
The evidence categories that panels have consistently found insufficient on their own are: self-authored declarations without corroboration; screenshots of WHOIS as of a single date; and purchase agreements that do not identify the specific domain or that are undated.
What happens after an adverse ruling? The .it procedure does not provide monetary damages. If a panel orders reassignment, the domain transfers to the complainant and the current registrant loses all rights in it. There is no automatic compensation for an acquirer who paid market value and is now stripped of the asset. The acquirer's remedy runs against the seller under the contractual indemnity – which is why the indemnity clause described above is not optional in any professionally structured .it acquisition.
An appeal of a .it expert decision is possible under the Registro .it's rules, but the appeal is heard by the same administrative body. Where a party believes the Expert made a legal error of sufficient weight, Italian court action remains available; this requires local litigation counsel in the relevant jurisdiction and is a substantially longer and more costly path. For most commercial .it domain disputes, the Registro .it's own procedure is the dispositive forum.
How does the .it chain-of-title analysis compare with gTLD and other ccTLD approaches?
The right route depends on the zone, and .it's approach differs in important respects from both the UDRP and the Nominet DRS for .uk domains.
Under the UDRP, which governs .com and other gTLDs, chain-of-title questions arise most often as a bad-faith registration issue: did the original registrant register the domain to exploit someone else's trademark, or did a subsequent transfer to a new registrant cure or create a bad-faith situation? The UDRP test is cumulative – the domain must have been registered and used in bad faith – and the only remedies are transfer or cancellation. There is no monetary award and no mechanism to reconstruct a defective chain of title as such; the UDRP addresses whether the current registrant meets the three-element test, not who should have been the registrant at each historical moment.
Under the Nominet DRS for .uk, the test is "abusive registration" – whether the registration was made or has been used abusively – and the DRS reads this as "registered or used" abusively, a lower bar than the UDRP's cumulative test. The Nominet procedure includes a free mediation stage before any expert decision, and the expert fee is published (GBP 750 + VAT for a full decision, GBP 3,000 + VAT for a three-expert appeal). Chain-of-title issues in .uk proceedings are handled somewhat more flexibly, with panels able to consider the full history of use rather than focusing solely on the registration moment.
The .it procedure occupies a distinct position. It is closer to a civil-law reassignment action than to the UDRP's trademark-based arbitration. The panel's mandate includes examining the validity of transfers as a matter of Italian administrative and contract law, which is why registrar-side records and authenticated identity documents carry the weight they do. A brand owner who has pursued a .com UDRP successfully and then wants to pursue a parallel .it claim cannot simply replicate the UDRP strategy: the elements, the evidence, and the remedy all differ.
For a brand with registrations in both .com and .it, the practical decision is whether to file simultaneously in both forums or to sequence them. Simultaneous proceedings are possible but resource-intensive; a favorable UDRP decision does not bind the .it panel, and vice versa. Sequencing – for instance, using the UDRP result as persuasive (not binding) authority in the .it proceeding – can reduce cost but extends the total timeline. We regularly advise brand owners on which sequence fits their specific timeline and budget.
What are the common myths about .it domain title and what the evidence actually shows?
Several persistent misconceptions affect how acquirers and registrants approach .it chain-of-title questions. The most consequential is the belief that the WHOIS record, as of the date of acquisition, is a conclusive and sufficient title certificate. It is neither. The WHOIS record is an administrative record reflecting what the registrar was instructed to record; it does not represent a legal determination of ownership and does not bar prior claims that were never litigated.
A second misconception is that a long holding period cures a defective title. Panels have generally rejected adverse-possession-style arguments in the .it context. Length of registration is relevant to the balance of equities in some proceedings, but it does not extinguish a claim based on an unauthorized transfer. The party who can demonstrate that a historical transfer was made without consent retains a cognizable claim regardless of how many years have passed – subject, of course, to any limitation period that Italian law may impose on court proceedings.
A third misconception, particularly among brand owners pursuing reassignment, is that holding a registered Italian trademark automatically establishes priority over a prior domain registrant. The .it rules require the complainant to demonstrate rights in a name, and a trademark registration is strong evidence of those rights. But the panel's ultimate question is whether the domain registration is abusive in relation to those rights – and a registrant who registered the domain before the trademark was filed, or who can demonstrate a legitimate use predating the trademark, has a colorable defense even against a registered mark. The trademark registration date matters; it is not the only thing that matters.
Is the UDRP irrelevant to .it, or does it apply at all?
The UDRP does not directly apply to .it domains. WIPO and the Forum have no jurisdiction over .it registrations under the UDRP, and no UDRP transfer order can compel the Registro .it to reassign a .it domain. This is a fundamental distinction that brand owners familiar with gTLD practice sometimes overlook when they expand enforcement to Italian ccTLD registrations.
However, UDRP proceedings can be indirectly relevant to a .it chain-of-title dispute in two scenarios. First, if a respondent in a .it proceeding also holds (or held) a .com version of the same name and a UDRP complaint was filed against that .com registration, the UDRP panel's findings on the respondent's bad faith or legitimate interest may carry persuasive weight in the .it proceeding. Panels in the .it context are not bound by UDRP decisions, but a well-reasoned UDRP decision finding bad faith by the same registrant for the same name in a related zone is relevant documentary evidence of the registrant's conduct pattern.
Second, if the .it domain is part of a portfolio held by a known serial cybersquatter – a registrant with a documented pattern of abusive registrations across multiple zones – a UDRP decision against that registrant in a .com proceeding can support an argument in the .it proceeding that the registrant's acquisition of the .it was similarly abusive. Panels have considered this type of cross-zone conduct evidence, though it is treated as corroborating rather than sufficient on its own.
What this means practically: a brand owner pursuing a .it reassignment should gather and preserve any UDRP decisions, court judgments, or dispute outcomes involving the same registrant across any zone. That cross-zone record can materially strengthen the .it case even though it carries no direct legal weight in the .it procedure.
Related at COGNOMEN
Frequently asked questions
What are the chances to verify chain of title for a .it domain?
A complete chain-of-title verification is achievable for most .it domains if the transfer history is not too long and the registrar retains adequate records. The Registro .it publishes historical WHOIS data and prior dispute decisions; these, combined with the seller's transfer documentation and a registrar-side records request, typically allow a thorough reconstruction. Where transfers were informal – handled between private parties without registrar intermediation – gaps in the documentary record are common, and the verification process involves assessing residual risk rather than achieving certainty.
What evidence do I need to verify chain of title for a .it domain?
The core evidence set for a .it chain-of-title check includes: the Registro .it's WHOIS log and any published dispute decisions involving the domain; the seller's original registration confirmation and each subsequent transfer agreement or transfer-of-holder form; payment records corroborating each transfer; registrar-side transaction logs, requested formally where possible; and archival WHOIS snapshots from third-party sources for the periods between documented transfers. Authenticated identity documents for the original registrant are important where the chain begins with an individual rather than a company.
Can I verify chain of title for a .it domain without going to court?
Yes. Most chain-of-title diligence for .it domains is conducted outside of any formal proceeding: through documentary review, registrar records requests, and a Registro .it dispute history search. If a defect is found during diligence, it can be addressed contractually – through a seller indemnity, a price adjustment, or withdrawal from the transaction – without any court involvement. A formal Registro .it reassignment proceeding, or Italian court action, only becomes necessary if a dispute is actually filed post-acquisition or if the parties cannot resolve a title defect by agreement.
Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.