How to prove a legitimate interest in your .it domain
A brand owner files a Reassignment complaint against your .it domain. The registrar locks the name. You have a business that predates the complaint, a website with real traffic, and a name you chose for entirely legitimate reasons. So why is the domain suddenly at risk?
To prove a legitimate interest in your .it domain you must demonstrate, under the ICANN Rules applicable through the .it Reassignment procedure, that your use of the domain falls within one of the recognized safe harbors: a bona fide offering of goods or services before notice of the dispute, a common personal or business name that corresponds to the domain, or a legitimate noncommercial or fair use. The procedure is governed by Registro.it and handled by a neutral dispute-resolution provider. Building a strong evidentiary record – before the response deadline – is what decides whether you keep the name or lose it.
This page covers what the .it Reassignment procedure demands, how to structure the legitimate-interest defense, what evidence actually moves panels, and when to seek a finding of Reverse Domain Name Hijacking.
What governs domain disputes over .it – and why Reassignment matters
The .it Reassignment procedure is the primary administrative route for challenging or defending a .it domain. It is separate from the UDRP, which applies to gTLDs such as .com or .net, and it operates under rules published by Registro.it, Italy's national registry. A complainant who wants your .it name files a Reassignment request with an accredited provider; you then have a defined window to respond before a panel rules on whether the domain should be reassigned to the complainant or remain with you.
The core test is functionally similar to the UDRP's three-element framework. The complainant must show rights in a name, that the domain is identical or confusingly similar to that name, and that the registration constitutes an abusive or bad-faith use. For the registrant, the responding party, the practical question is the same one that arises under Paragraph 4(c) of the UDRP: can you establish a legitimate interest that defeats each element the complainant relies on?
Because .it sits outside the UDRP proper, the procedural specifics differ from a standard gTLD complaint. Timelines, evidentiary rules, and the form of the response filing are set by the Registro.it rules, not by ICANN's Supplemental Rules. The substantive analysis of what counts as legitimate interest, however, tracks the well-settled international consensus. Panels worldwide have consistently found that a registrant who can document genuine commercial use, a real connection to the name, or fair noncommercial engagement will defeat a complaint – regardless of the zone.
One distinction worth noting: unlike a German .de dispute, which proceeds primarily through the domestic courts with DENIC offering only a registration block, the .it Reassignment procedure produces a binding administrative decision on ownership. You are not simply stalling a transfer – you are contesting it in a structured proceeding with enforceable consequences. That makes the quality of your response filing directly determinative of whether you keep the domain.
If you have received a Reassignment notice for a .it domain, act immediately. For an assessment of your domain dispute, contact info@cognomenlaw.com.
How do the Paragraph 4(c) safe harbors apply to your .it defense?
The three recognized safe harbors – bona fide commercial use before notice of the dispute, a name by which you are commonly known, and legitimate noncommercial or fair use – are the primary tools for proving a legitimate interest, and they apply in the .it context through the international consensus that Registro.it panels draw on when evaluating Reassignment claims.
Bona fide offering before notice. This is the most commonly invoked safe harbor and the one with the clearest evidentiary path. It requires demonstrating that, before you received any notice of the dispute, you were using the domain in connection with a real commercial offering. The critical markers are timing and authenticity. A domain registered the day after a brand owner's trademark was published, with no content until the complaint arrived, will not satisfy this test. A domain registered years earlier, pointing to a functioning website with genuine customers, transaction records, and verifiable traffic, stands on entirely different ground.
In our practice, the evidence that matters most under this safe harbor includes: the registration date relative to the complainant's trademark filing date; archived website content from the period before the dispute notice (third-party web-archive services are frequently cited); invoices, contracts, or purchase orders connecting the domain name to actual commercial activity; and any third-party references – press, directories, or professional registrations – that associate your business with the domain.
Commonly known by the name. This safe harbor is narrower and fact-specific. It applies where an individual, business, or organization is genuinely identified by the name in the domain, regardless of whether a registered trademark exists. Evidence here typically includes trade name registrations, business registry records, professional profiles, media references, and customer correspondence using the name. It is not sufficient to assert the name; the record must show that third parties independently associate the domain name with you.
Legitimate noncommercial or fair use. The least litigated of the three in commercial disputes, this safe harbor covers commentary, criticism, fan sites, and analogous noncommercial contexts. It rarely applies to purely commercial registrants, but it can be decisive in cases where a domain is used for an informational resource or a cause rather than for revenue. The condition that typically defeats it is any element of commercial gain derived from confusion with the complainant's mark.
What evidence actually decides a legitimate-interest defense?
Panels do not weigh arguments in the abstract. They weigh documents. A persuasively written response without supporting exhibits is far weaker than a well-organized factual record with a concise narrative. In our experience defending .it Reassignment respondents, the cases that hold are the ones where the evidentiary record makes the legitimate interest self-evident before the legal analysis begins.
The categories of evidence that consistently carry weight in legitimate-interest defenses are the following.
- Registration history and intent. The original registration date, the registrant's business activities at that time, and any contemporaneous records showing why the domain was chosen – a business plan, a company formation document, a trade name filing – establish that the registration was not made in anticipation of the complainant's rights.
- Continuous use. Web-archive captures, server logs, analytics records, and customer correspondence demonstrate that the domain was not passively held in bad faith. Even a modest but genuine website, maintained over time, can satisfy the bona fide use threshold.
- Third-party corroboration. Industry directories, press mentions, social media profiles, and customer reviews that use the domain name as an identifier for your business are powerful because they come from outside the registrant's own records. A panel seeing ten independent sources associating your business with the domain name will find legitimate interest far more readily than on self-serving assertions alone.
- Absence of targeting. Evidence that the domain was registered without any knowledge of the complainant's mark – geographic separation, industry distance, a prior domain history predating the complainant's trademark – undercuts the bad-faith element and simultaneously supports legitimate interest.
- Commercial records. Invoices, supplier agreements, banking records showing the domain associated with a trading account, and tax filings that reference the business name all ground the defense in verifiable commercial reality.
What does not work as evidence is equally instructive. A declaratory statement by the registrant alone, website content created after the complaint was filed, or a claimed common-word defense that ignores the complainant's strong secondary meaning in the relevant market – these are patterns that weaken otherwise defensible cases. The record must exist before the dispute notice, not in response to it.
In a recent matter involving a .it domain in the food and beverage sector (spring 2025), a registrant had operated a regional business under a domain-matching trade name for over a decade. The complainant held a trademark registered in the same class but in a different geographic market. The registrant's defense included archived web pages dating to the domain's first year of registration, three separate trade-directory listings, and a decade of customer invoices. The panel declined to reassign the domain, finding the legitimate-interest record compelling on its face.
How should you structure the Reassignment response for a .it domain?
The response is not a brief in the sense of a court pleading. It is a structured submission to a neutral panel, and clarity of organization determines how persuasively the legitimate-interest evidence lands. Panels reviewing multiple cases across multiple zones have developed strong expectations about what a sound response looks like.
Start with a concise statement of the registrant's position: the domain is legitimate, the registration predates or is entirely independent of the complainant's rights, and the evidence demonstrates bona fide use. Do not bury the core claim in a lengthy procedural narrative. Panels will read the response in full, but they form an impression quickly, and the opening paragraphs should give them the answer before the evidence appears.
Then address each element the complainant has raised, in order. Under the similarity element, note any differences between the domain and the trademark – phonetic, visual, or conceptual – that reduce the confusing-similarity finding. Under the legitimate-interest element, present the safe-harbor analysis directly, identifying which of the three applies and attaching the primary evidence. Under the bad-faith element, counter the specific bad-faith factors the complainant cited, and address any that were not cited but could arise from the record.
Exhibits should be organized, paginated, and cross-referenced in the text. A panel that has to search through an exhibit bundle for the document supporting a claim in paragraph twelve of the response will not form a favorable impression. Practical discipline in submission format is part of the defense quality.
Timing matters as much as content. The response window in administrative proceedings is defined and not automatically extended. Filing late, or filing without key exhibits because they were assembled in a rush, is one of the most common and most avoidable ways to weaken a defense that would otherwise succeed.
If you have already received a complaint and need to assess the strength of your response, email info@cognomenlaw.com before the response deadline passes.
When is a Reverse Domain Name Hijacking finding realistic for .it?
Reverse Domain Name Hijacking (RDNH) is a finding that the complainant brought the Reassignment proceeding in bad faith – typically to deprive a legitimate registrant of a domain to which the complainant has no genuine entitlement. The RDNH finding carries no monetary penalty, but it is a reputational sanction with real weight in the domain industry and in subsequent dispute proceedings.
RDNH findings are not granted simply because a complaint fails. Panels look for specific indicators of bad faith on the complainant's side: filing after acquiring knowledge that the registrant's legitimate interest is clear; pursuing a complaint where the trademark postdates the domain registration by years; relying on a trademark that is geographically or industrially remote from the registrant's use; or making factual misrepresentations in the complaint. The consensus view across UDRP and analogous ccTLD proceedings is that a lost complaint alone is insufficient to warrant RDNH – there must be something about the manner or basis of filing that crosses the line into abuse.
In our practice defending respondents, RDNH arguments are most realistic where: the complainant's trademark was filed or registered after the domain; the domain has genuine, documented commercial history that the complainant plainly saw before filing; or the complaint relies on an implausibly broad reading of confusing similarity to capture a common word or descriptive term. Where those conditions exist, a well-built response can achieve both a denial of the complaint and an RDNH finding, putting the complainant on record as having acted abusively.
For a broader analysis of how RDNH operates across different TLDs and why pursuing the finding is sometimes strategically valuable even in clear-cut defenses, see our analysis of RDNH findings in the .tv context, which examines the evidentiary and strategic dimensions in detail.
How does .it Reassignment compare to a UDRP and to a national court?
The right route depends on what the registrant needs and where the threat arises. Understanding the comparison is essential before deciding how to respond – or whether to take a proactive step.
For a .com or other gTLD domain where the complainant has filed a UDRP complaint, the respondent faces the well-known UDRP process before WIPO, the Forum, or another accredited provider. The filing fees begin at USD 1,500 at WIPO for a single-panel case, and a standard case closes in approximately two months. The UDRP's Paragraph 4(c) safe harbors are directly applicable. A UDRP RDNH finding is on the public record.
For a .it domain, the Reassignment procedure is the administrative equivalent. It shares the substantive framework – rights, legitimate interest, abusive registration or use – but it operates under Registro.it's rules, with Italian procedural norms and Italian-language submissions typically expected. A brand owner who loses in Reassignment can still pursue the Italian courts, but the administrative ruling carries significant practical weight and is typically the faster, lower-cost route to resolution for both sides.
The national court path – Italian civil litigation – is a separate and far more resource-intensive option. It is appropriate where damages are sought, where the Reassignment procedure does not cover the specific form of relief needed, or where the complainant has escalated to court after losing administratively. Court proceedings introduce Italian procedural law, expert-evidence requirements, and timelines measured in months to years rather than weeks. For a registrant whose legitimate interest is well-documented and whose commercial use is genuine, the Reassignment defense is almost always the first line, with court action reserved for escalation or for cases where the stakes justify the cost.
If the domain situation involves a stolen or hijacked .it domain rather than a Reassignment complaint, the mechanics differ entirely – see our guidance on recovering a stolen domain for the procedural approach to account compromise and transfer reversal. A Reassignment defense and a theft recovery use different evidentiary tools, even when the underlying goal – keeping or recovering the domain – is the same.
In a second matter from our files – a .it domain in the professional-services sector (autumn 2024) – the complainant filed both a Reassignment claim and a parallel trademark infringement action in the Italian courts. The registrant's response to the Reassignment included a comprehensive commercial record demonstrating bona fide use over more than five years, predating the complainant's trademark registration. The Reassignment panel declined to transfer the domain. The court action was subsequently withdrawn. Maintaining a clean, continuous evidentiary record of legitimate use proved decisive in both forums simultaneously.
What are the practical next steps if you receive a .it Reassignment complaint?
The response deadline is fixed and short. The first practical step is to confirm the exact deadline from the notice of commencement, and then to begin assembling the evidence immediately rather than waiting until the filing date approaches.
The assembly process should follow a defined sequence. First, pull the domain's registration history: the original registration date, any transfers of ownership, and any historical WHOIS records showing continuous registrant identity. Second, gather all evidence of commercial use before the dispute notice: archived web pages, business filings, invoices, and third-party references. Third, review the complainant's trademark: when was it registered, in what classes, and in what jurisdictions? A trademark filed after your domain registration date fundamentally changes the legal landscape of the complaint.
Identify which safe harbor applies to your situation and build the evidentiary record around it specifically. Do not try to invoke all three safe harbors simultaneously if only one genuinely fits; a diffuse response that spreads across multiple weak claims is less persuasive than a focused response that builds one compelling factual narrative.
Consider whether the facts support an RDNH argument. If the complainant's trademark postdates your registration, or if you can document that the complainant had knowledge of your use before filing, note that in the response and support it with the same commercial evidence that proves your legitimate interest.
Finally, consider whether the .it dispute is part of a broader attack across multiple zones. A complainant who files against your .it domain may simultaneously target your .com, .eu, or other ccTLD registrations. A coordinated defense strategy – anticipating all the zones in play – is more efficient and more consistent than responding to each complaint in isolation. Our respondent defense practice handles multi-zone defense matters as a unified engagement. For an overview of the full range of respondent tools available, see our respondent defense and RDNH services page.
Related at COGNOMEN
Frequently asked questions
When should I prove a legitimate interest in your .it domain?
You should build and present your legitimate-interest case as soon as you receive a Reassignment notice for your .it domain – ideally within days of receipt, not at the response deadline. The evidence that matters most (archived web content, invoices, trade-name registrations) must predate the dispute notice. Starting early gives you time to locate, organize, and authenticate that record. Waiting until the final days of the response window increases the risk of a rushed filing that omits key exhibits or misstates a factual sequence that the panel will notice.
What happens if the other side ignores the case?
If the complainant files and then takes no further action, the panel still proceeds to a decision on the record. If you as the registrant fail to respond, the panel decides on the complaint alone – and default is often treated as weakening the registrant's position, even though failure to respond does not automatically result in reassignment. Panels are required to review whether the complaint's three elements are met regardless of a default. That said, a registrant who presents no legitimate-interest evidence gives the panel very little to work with. Filing a substantive response, even a concise one, is almost always better than silence.
How is Reassignment different from a national court for .it?
The .it Reassignment procedure is an administrative dispute mechanism that produces a binding decision on domain ownership, typically faster and at lower cost than Italian court proceedings. Courts are appropriate where monetary damages are sought, where the Reassignment route cannot provide the remedy needed, or where the complexity of the underlying trademark dispute exceeds what an administrative panel can resolve. A court action also allows discovery tools not available in administrative proceedings. For most legitimate registrants facing a straightforward Reassignment claim, the administrative route is the correct first forum; court action is reserved for escalation, parallel proceedings, or situations where the stakes and facts require it.
Author: Anton Grant — Respondent defense and reverse domain name hijacking (RDNH). 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.