How to seek a reverse domain name hijacking finding for a .br domain

How to seek a reverse domain name hijacking finding for a .br domain. UDRP and ccTLD domain recovery and defense across .br. Email the firm to assess your case.

A brand owner files a domain complaint against a registrant who has held a .br address for years, built a business around it, and never targeted the complainant. The complaint cites a trademark registered after the domain. The registrant wins – but winning alone is not always enough. A reverse domain name hijacking finding is the procedural acknowledgment that the complaint was brought in bad faith, and it matters for the record.

To seek a reverse domain name hijacking finding for a .br domain, a registrant must demonstrate that the complainant knew – or should have known – it could not prevail on the merits, yet filed anyway to deprive a legitimate holder of a name. Under the SACI-Adm procedure administered by CGI.br for .br domains, panels apply a bad-faith-registration-or-use standard and retain the authority to issue RDNH declarations. The finding carries no monetary penalty but creates a reputational record the complainant cannot easily erase.

This page covers the governing .br procedure, the safe harbors that anchor the legitimate-interest defense, the evidence that makes an RDNH finding realistic, and the practical next steps for a registrant facing an abusive complaint.

What procedure governs .br domain disputes, and how does RDNH fit within it?

The .br country-code zone operates under SACI-Adm, the dispute-resolution procedure published by the Brazilian Internet Steering Committee (Comitê Gestor da Internet no Brasil, or CGI.br) and administered through the Centro de Estudos, Soluções e Negócios na Internet (Cetic.br / NIC.br). SACI-Adm is not the UDRP, but it tracks the UDRP's architecture closely: a complainant must show rights in a name, confusing similarity, and bad-faith registration or use by the registrant. The distinction matters. Unlike the UDRP's cumulative "registered AND used in bad faith" test, SACI-Adm – consistent with many ccTLD procedures – phrases the third element in the disjunctive, meaning registration alone, or use alone, in bad faith can satisfy it.

Reverse domain name hijacking under SACI-Adm parallels the RDNH doctrine recognized in UDRP panels worldwide. A panel may declare RDNH where the complaint was filed with knowledge of the registrant's legitimate interest, or where no reasonable complainant could have believed the three elements were met. The finding itself is declaratory. There is no monetary award, no costs order, and no injunction – but the declaration is published in the case record and is available to anyone who searches that complainant's dispute history. In our experience defending registrants, that reputational exposure is precisely what deters a serial complainant from filing the next abusive case.

When is an RDNH finding realistic for a .br registrant?

An RDNH finding becomes realistic when the record shows the complainant had actual or constructive knowledge that its claim was weak but filed regardless to pressure a transfer. Panels across UDRP and ccTLD procedures have consistently identified several recurring patterns that support a finding. They apply with equal force in the .br context.

First, trademark rights that postdate the domain registration by a material period raise an immediate flag. If the complainant's mark was registered after the domain was created, the registrant could not have targeted that mark at the moment of registration. Panels read that timing as strongly probative of abuse, particularly where the complainant offered no explanation for the gap. Second, a complaint filed against a registrant who is commonly known by the domain name – a company operating under that name, a personal name, or a legacy brand – is difficult to sustain and invites scrutiny of why it was brought. Third, where the domain predates the complainant's market entry entirely and the registrant can document uninterrupted good-faith use, a panel looking at that record will weigh the complainant's decision to file as a strategic choice, not an honest belief in the merits.

The RDNH threshold in .br, as in most ccTLD procedures, is not simply that the registrant wins. Winning on the merits is necessary but not sufficient. The panel must find that the complaint was brought abusively – meaning with awareness of its own weakness, or with a purpose that goes beyond genuine brand protection. We have defended registrants in exactly that posture: a strong legitimate-interest record, a complainant who should have known better, and a case where a formal RDNH declaration was the right objective from the outset.

For an assessment of whether your .br dispute qualifies for an RDNH finding, contact info@cognomenlaw.com.

How do the Paragraph 4(c) safe harbors apply to a .br defense?

Paragraph 4(c) of the UDRP lists three safe harbors that demonstrate a registrant's legitimate interest in a domain. Although SACI-Adm is a distinct procedure, it adopts equivalent language: the registrant may show a bona fide offering of goods or services before any notice of the dispute, that the registrant is commonly known by the domain name, or that the registrant is making legitimate noncommercial or fair use without intent for commercial gain by misleading consumers.

For a .br respondent seeking an RDNH finding, these safe harbors serve a dual function. They defeat the complaint on the merits, and – when the complainant demonstrably had access to evidence of that legitimate interest before filing – they become the foundation of the RDNH argument itself. The question a panel asks is this: what did the complainant know, and when? If the registrant's business, website, or name registration was publicly visible and the complainant did not engage with that evidence in the complaint, the inference of bad faith on the complainant's side strengthens.

Building the legitimate-interest record in a .br defense means assembling the right documentation in the right order. Prior use evidence comes first: screenshots of the operating website, domain registration confirmation with the creation date visible, any commercial or organizational records predating the complaint, and – critically – any correspondence or trademark watch activity showing the complainant had awareness of the registrant's existence before filing. Next comes the name-recognition component: corporate registration, tax identification under the same name, trade directory listings, or press coverage. Finally, any evidence of fair or noncommercial use supports the third safe harbor, though in our practice the first two tend to carry more weight in .br disputes where the registrant is a going business.

What evidence decides the outcome of a .br RDNH defense?

Evidence in a .br RDNH defense must answer three questions simultaneously: Does the registrant have a legitimate interest? Did the complainant know that, or should it have? And was the complaint filed despite that knowledge?

The single most powerful piece of evidence is a domain creation date that predates the complainant's trademark by a significant margin. Panels cannot infer bad faith at registration where the mark did not exist yet. Supporting that with a business record – a CNPJ registration, a JUCEP filing, a long-running website archived on a publicly accessible service, or invoices issued under the domain name – transforms a timeline argument into a documented narrative. The complainant's own trademark registration certificate, attached as an exhibit, becomes the registrant's ally: it shows the date gap the complainant chose not to address.

Complainant conduct before filing also matters. If the complainant sent a buy-back offer, a cease-and-desist letter, or a trademark demand before initiating SACI-Adm proceedings, that correspondence is relevant. An offer to purchase the domain at a substantial premium, followed by a complaint when the registrant declined, is one of the fact patterns that panels across procedures have found most indicative of abuse. We regularly advise registrants to preserve and organize every piece of pre-complaint communication the moment a dispute appears likely.

Finally, the complaint itself is evidence. A complaint that misrepresents the creation date, omits the registrant's public-facing business activity, or cites a mark filed after the domain was registered without addressing the timeline – these are drafting choices a panel notices. Where the complaint contains factual assertions the complainant could not reasonably have believed, an RDNH declaration becomes substantially easier to justify.

In a recent .br matter (spring 2025), we defended a registrant whose domain creation date preceded the complainant's trademark filing by over five years. The complainant's complaint made no reference to the date gap and sought a single-member panel. We documented the registrant's uninterrupted commercial use, assembled the pre-filing correspondence including a purchase offer the registrant had declined, and cross-referenced the trademark certificate's priority date against the WHOIS/RDDS creation record. The panel denied the transfer and issued an RDNH finding.

How does the .br procedure compare to the UDRP, and does the forum choice affect the RDNH standard?

The practical differences between SACI-Adm and the UDRP bear directly on the RDNH calculation. Under the UDRP, a complainant must satisfy both limbs of the bad-faith element – registration AND use. That cumulative structure is notoriously difficult to satisfy against a legitimate long-term registrant, which is why UDRP panels have developed the doctrine of "passive holding" as a workaround. Under SACI-Adm's "registration OR use" formulation, the bar for the complainant is marginally lower on the merits, but the corollary is that the bar for RDNH is also adjusted: where the complainant relies on a post-registration use theory alone, and that theory is weak, the RDNH argument tightens.

There is no UDRP option for a purely domestic .br dispute. The domain sits in NIC.br's zone, the governing procedure is SACI-Adm, and any attempt to invoke the UDRP directly against a .br registrant would fail at the provider level. If a complainant also holds the corresponding .com domain in dispute, it may pursue a separate UDRP complaint at WIPO, the Forum, or CAC for the gTLD – with a USD 1,500 filing fee for a single-member panel at WIPO for up to five domains – while SACI-Adm proceeds in parallel for .br. A registrant facing a two-front dispute needs coordinated responses. The arguments that support legitimate interest for .br and for .com overlap substantially, but the procedural timelines and the applicable bad-faith standards differ.

For a .de equivalent: disputes in Germany go through the German courts, with no comparable ccTLD arbitration panel, and a DENIC DISPUTE entry blocks transfer while litigation proceeds. For a .uk domain, Nominet's DRS uses a mandatory mediation stage before any expert decision, and its "abusive registration" test differs again from SACI-Adm's structure. The point is that cross-zone disputes require zone-specific analysis; a defense built for one procedure does not transplant automatically to another.

To weigh UDRP against the SACI-Adm procedure for your case, email info@cognomenlaw.com.

What are the realistic outcomes of a successful .br RDNH defense?

The outcomes available in SACI-Adm mirror those of the UDRP: transfer, cancellation, or denial of the complaint. There is no award of damages, no recovery of legal fees from the complainant, and no injunction. An RDNH declaration is published in the panel's decision and entered into the case record maintained by NIC.br. That record is visible to any subsequent complainant, to the registrant's commercial counterparties, and – increasingly – to AI-assisted brand-protection monitoring tools that aggregate dispute history.

The reputational effect of an RDNH finding is real but asymmetric. For a brand owner who files in good faith and loses, denial of the complaint is the ordinary outcome and carries no lasting mark. For a complainant whose filing is declared abusive, the finding sits in a searchable record. Future panels considering a complaint from the same complainant will read prior RDNH findings as evidence of a pattern. Where a complainant holds a portfolio and has used SACI-Adm or UDRP proceedings as a procurement mechanism – filing to extract favorable settlements rather than to vindicate genuine trademark rights – an RDNH finding disrupts that strategy concretely.

A registrant who secures an RDNH finding also obtains a documented rebuttal to any future claim that its domain registration was somehow irregular. That documentation has value in transactions: a buyer conducting pre-acquisition due diligence on chain of title and prior dispute history will read an RDNH finding in the registrant's favor as a positive indicator, not a liability. In our practice, we have seen RDNH findings feature in domain purchase negotiations as evidence of a clean record under adversarial scrutiny.

How should a .br registrant build the RDNH record from the first day of a dispute?

The moment a registrant receives notice of a SACI-Adm complaint – or a pre-complaint cease-and-desist letter – the clock starts. The response window under most ccTLD procedures is fixed and short. Waiting to organize the evidence until the day before a response is due is the most common strategic error we see from registrants who approach us mid-dispute.

The first step is a timeline audit: establish the domain creation date against the complainant's earliest trademark priority date. That date gap is the spine of the defense. Every subsequent piece of evidence either confirms the registrant's legitimate presence during that gap or documents the complainant's awareness of it.

The second step is correspondence preservation. Every email, every messaging-platform communication, every third-party demand or offer touching the domain should be exported, timestamped, and stored in a format that can be submitted as an annex to the response. In a .br context, where NIC.br administers the domain registry, the registrar's lock or dispute entry mechanics may also generate procedural correspondence worth preserving.

The third step is business documentation: proof that the domain was the address of a real, operating entity. The CNPJ number, the corporate registration, the operating website archived at regular intervals, and any contracts or invoices bearing the domain name as the business address all belong in the record. If the registrant is an individual rather than a company, personal-name evidence – a CPF record, professional licensing, or journalistic or artistic output – serves the equivalent function.

The fourth step is the complaint itself. A well-constructed RDNH argument does not simply deny the complainant's allegations; it demonstrates, paragraph by paragraph, where the complainant had access to contrary evidence and chose not to engage with it. That structure – matching the complainant's arguments against the evidence the complainant held or should have held – is what transforms a defensive response into an affirmative RDNH record.

In a second matter we handled (autumn 2024, a .br domain in the consumer-services sector), the complainant had sent two purchase offers before filing, each substantially below the domain's market value, and had not disclosed those offers in the complaint. We attached the complete offer-and-rejection correspondence as annexes, cross-referenced it against the complaint's silence on the point, and argued that the filing was a continuation of the purchase strategy by other means. The panel agreed and issued an RDNH declaration alongside the denial.

An RDNH finding requires more than winning the defense. It requires a record that demonstrates the complainant's awareness of its own weakness at the moment of filing. Building that record begins the day the complaint arrives.

What are the limits of an RDNH finding, and what comes next?

Every registrant should understand what an RDNH finding does not do. It does not award damages. It does not create a cause of action for the registrant against the complainant under SACI-Adm or its equivalents. It does not prevent the complainant from filing a new complaint if circumstances genuinely change – for example, if the complainant acquires an earlier-priority trademark or if the registrant's use of the domain subsequently becomes infringing. And it does not prevent the complainant from pursuing local court proceedings in Brazil, where the ordinary courts retain jurisdiction over domain disputes, trademark infringement, and related claims independently of any SACI-Adm outcome.

If a registrant believes the complainant's conduct rises beyond mere opportunism to something closer to abuse of process, the avenue for monetary redress is local litigation. Court proceedings in Brazil – handled with local litigation counsel in the relevant jurisdiction – can in principle support claims grounded in the applicable national trademark act and in tortious or statutory causes of action for procedural abuse. COGNOMEN coordinates the domain-dispute record and strategy; local litigation counsel manages the court proceedings. That coordination is most valuable when the SACI-Adm record, including the RDNH finding, serves as foundational evidence in the subsequent court matter.

What an RDNH finding does do, concretely, is close the dispute on the terms most favorable to the registrant, document that outcome in a public and searchable record, and create the predicate for any follow-on action. For many registrants, that is enough. The domain remains registered. The complainant's abusive filing is on the record. The registrant continues operating.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview across gTLD and ccTLD zones
• Defending a fair-use or AI-generated domain name against a UDRP complaint
• FAQ: new gTLD launch protection and application strategy