Assess my case

Case study: choose between URS and UDRP for a .net domain

Case study: choose between URS and UDRP for a .net domain. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A brand owner discovers a .net registration that mirrors its trademark almost exactly. The registrant has pointed the domain at a pay-per-click parking page. The brand owner wants the domain transferred. The immediate question is whether to file under the Uniform Rapid Suspension system or the Uniform Domain-Name Dispute-Resolution Policy – and for a .net, that choice matters more than it might first appear.

For a .net domain, the UDRP is typically the correct tool when the goal is transfer of ownership. The URS is available for new gTLDs and certain other zones, but .net operates under the UDRP administered by forums including WIPO, where the filing fee for a single-member panel is USD 1,500. The URS remedy is suspension only – not transfer – and carries a higher evidentiary standard. For most brand owners facing a cybersquatting .net registration, UDRP is the faster, more complete path to recovery.

Below is an anonymized account of exactly that situation, the strategic analysis that shaped the filing, and what the outcome turned on.

Situation: a .net typosquat surfaced during a brand audit

In winter 2025, a mid-size technology company retained COGNOMEN after an internal brand audit identified a .net registration that differed from its registered trademark by a single transposed character – a classic typosquat. The domain had been registered roughly eighteen months earlier, well after the company's trademark was registered in multiple jurisdictions. It resolved to a parking page displaying sponsored links in the company's product category.

The registrant had no publicly visible connection to the mark. There was no prior relationship with the company, no licensing arrangement, and no website content suggesting a legitimate business. The RDDS record showed a privacy proxy. Still, the registrant had not approached the company with a sale demand – a fact that prompted the client's initial hesitation about the strength of the bad-faith case.

Passive or near-passive holding of a confusingly similar domain can still support a bad-faith finding. Panels have consistently held that parking a domain on pay-per-click links in the mark owner's sector – even without an explicit sale offer – satisfies the bad-faith use element under Paragraph 4(a)(iii) of the UDRP. The parking revenue itself demonstrates commercial exploitation of the confusion.

Strategy: why UDRP was chosen over URS for this .net

The first analytical step was confirming which procedures actually apply to .net. The URS was designed for new gTLDs introduced after 2013 – zones such as .online, .store, and .tech – not for the legacy gTLDs like .net and .com. ICANN's new gTLD program extended URS coverage to those new extensions. The legacy .net TLD, however, operates under the UDRP, not the URS, as its mandatory dispute policy.

Even if URS had been available, transfer would not have been on the table. The URS remedy is suspension for the remainder of the registration term, not a change of ownership. For a brand that wanted the domain integrated into its portfolio and pointed at its own site, suspension without transfer would have been an incomplete outcome.

The URS also requires a higher evidentiary standard. A complainant must show the infringement is "clear and convincing" – a threshold designed to reflect the speed and limited record of the URS process. The UDRP standard, while rigorous, allows a more developed factual record and gives the respondent 20 days to respond, producing a fuller adjudication. Where the facts are strong, UDRP's fuller process actually suits the complainant better: it produces a transferable, reasoned decision that feeds into the company's trademark enforcement history.

We assessed all three UDRP elements before filing. The confusing similarity element was clear – a single transposed character does not distinguish a domain from the mark it mimics; panels treat minor typographic variations as insufficient to escape confusing similarity. On the second element, the registrant had no evident prior use of the term, no business known by that name, and had made no noncommercial or fair use of the domain. On the third element, the combination of the mark's pre-existing registration, the registrant's lack of connection to the term, and the PPC parking page in the brand's product category provided a coherent bad-faith narrative under Paragraph 4(b)(iv) of the UDRP.

Weighing URS against UDRP for a domain in your portfolio? For a read on which remedy fits your zone and your goal, contact info@cognomenlaw.com.

Outcome: transfer ordered; what decided it

WIPO was selected as the forum. The complaint was filed in winter 2025, a single-member panel was appointed, and a transfer order was issued approximately eight weeks after filing. The registrant did not file a response; the panel nonetheless examined the record on its merits before ordering transfer, as is standard practice on default.

Three evidentiary points carried the decision. First, the company's trademark registrations predated the domain registration by several years, eliminating any plausible argument that the registrant had adopted the term independently. Second, the PPC parking page displayed sponsored links for competing products – direct evidence of commercial exploitation of user confusion. Third, the registrant's use of a privacy proxy, combined with the lack of any plausible legitimate interest, supported an inference of bad faith rather than ordinary registration.

The outcome was a UDRP transfer order, implemented by the registrar within the standard post-decision window. The company now holds the domain, has redirected it to its primary site, and the incident has been documented in its brand-protection file for future enforcement reference.

Had this dispute involved a new-gTLD equivalent – say, a .tech or .store version of the same typosquat – URS would have been a viable fast-track option to suppress the infringing use quickly. The lower fee and compressed timeline can make URS attractive where suspension alone is sufficient and the facts are unambiguous. But for a .net where ownership transfer was the goal, UDRP before WIPO was the only route that delivered the complete result.

If you are deciding whether to pursue UDRP recovery or URS suspension for a domain dispute, email info@cognomenlaw.com for an assessment of the three elements and the right forum.

Related at COGNOMEN

Frequently asked questions

Does URS apply to .net domains?

No. The URS was designed for new gTLDs introduced under ICANN's post-2013 expansion program. The legacy .net TLD is governed by the UDRP, not the URS. A brand owner seeking to address an abusive .net registration must proceed under the UDRP, where the only remedies are transfer or cancellation of the domain.

What is the difference in remedy between URS and UDRP?

A successful URS complaint results in suspension of the domain for the remainder of its registration term – the domain is deactivated but not transferred to the complainant. A successful UDRP complaint can result in transfer of the domain to the complainant. Where ownership is the goal, UDRP is the appropriate route. URS is a faster, lower-cost suppression tool suited to unambiguous cases in new-gTLD zones.

What evidence decides a UDRP case for a .net typosquat?

The key evidence covers all three UDRP elements: a trademark registration predating the domain; proof that the registrant has no legitimate interest (no prior known use, no business connection, no fair-use content); and evidence of bad faith, typically a PPC parking page in the brand's sector, a pattern of similar registrations, or a sale demand. A privacy proxy registration, without more, does not by itself establish bad faith, but combined with the other factors it supports the inference.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Related

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.