Step-by-step: suspend a .net domain through URS

Step-by-step: suspend a .net domain through URS. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A stranger registers a .net that mirrors your trademark, parks it on a pay-per-click page, and points inbound traffic straight at your competitors. You want it stopped – quickly, and without paying a five-figure buy-back demand. The Uniform Rapid Suspension procedure exists precisely for this situation, and .net domains are fully eligible.

To suspend a .net domain through URS, a complainant must prove all three elements of the URS standard – confusing similarity, no legitimate interest, and bad faith – to a clear-and-convincing evidentiary level, which is a higher bar than the UDRP's preponderance standard. The remedy is suspension for the remaining registration term, not transfer of ownership. Filing fees are lower than the UDRP, but the procedural limitations make it the right tool only in specific circumstances.

This guide walks each step of the URS process for a .net domain, flags the trap concealed in each decision point, and explains when the UDRP is the better path.

What the URS is – and what it is not – for a .net domain

The URS is a mandatory procedure attached to every gTLD registration agreement, including .net, meaning every .net registrant is contractually bound by it. The remedy is suspension: the domain resolves to a holding page for the remainder of the registration term. Ownership does not transfer. That distinction matters enormously.

If your goal is to own the domain permanently, the URS is the wrong instrument. Suspension expires when the registration term ends, and the registrant may then re-register the name. The UDRP is the appropriate vehicle for permanent recovery – it can order transfer or cancellation, and a .net domain filed at WIPO starts at a USD 1,500 filing fee for a single-member panel. The URS, by contrast, carries a meaningfully lower official fee, making it attractive for brand owners who need a fast takedown rather than a title transfer.

In our practice, we encounter brand owners who assume a URS win means they now hold the domain. They do not. We address this misconception early in every URS engagement, because misunderstanding the remedy shapes the decision whether to file at all.

If you are weighing URS suspension against a UDRP transfer for a .net domain, we can assess the three elements and advise on the better route. Contact info@cognomenlaw.com.

Step 1: Confirm the domain is URS-eligible and identify your rights

Before filing, confirm two threshold facts: that the domain is a gTLD subject to the URS and that you hold a trademark right the URS will recognize. .net is a legacy gTLD administered under the ICANN registry agreement, and it is fully subject to the URS. That first question is resolved.

The second is not always clean. The URS requires a trademark right – specifically, a mark registered with a national or regional trademark office, listed in the TMCH (Trademark Clearinghouse), or evidenced through a documented history of common-law use. The trap here is overconfidence: a brand owner with a pending trademark application, an unregistered trade name, or only a business-name registration does not automatically satisfy the rights element. A pending application is not a registered mark.

What to do at this step:

• Identify every trademark registration (national, regional, international) that is identical or confusingly similar to the disputed .net domain string.
• Confirm each registration is current, not expired, and not subject to a pending cancellation or opposition.
• Where you rely on common-law rights, assemble documentary evidence of prior use – advertising materials, sales records, press coverage – dated before the disputed registration date.
• Check whether the mark is in the TMCH; TMCH listing accelerates the rights-evidence submission.

The trap: some brand owners skip the registration date check. If your mark postdates the domain registration, the confusing-similarity element may still hold, but bad faith becomes far more difficult to prove, because the registrant could not have targeted a mark that did not yet exist. Confirm the priority dates before investing in the filing.

Step 2: Conduct a pre-filing investigation of the domain

The clear-and-convincing standard demands better evidence preparation than many complainants anticipate. At this step, you are building the file that will decide the case – not annotating an assertion.

Gather and preserve the following before drafting the complaint:

• A timestamped screenshot of the domain's current resolution – pay-per-click page, redirected website, parking page with competitive advertising, or blank resolution.
• RDDS (WHOIS) data showing the registration date, registrant details, and registrar. Note whether the registrant uses a privacy proxy.
• Historical resolution records from an archive service showing how the domain has resolved since registration. Passive holding since registration is itself a recognized bad-faith indicator in URS proceedings.
• Evidence of any communications, demands, or offers to sell the domain to you or to a competitor. A documented buy-back demand is among the strongest single pieces of bad-faith evidence available.
• Evidence of any confusion events – misdirected emails, customer complaints, social-media references – that link the domain's operation to consumer confusion with your mark.

The trap at this step is filing too early. Complainants who file the same week they discover the domain often submit incomplete evidence. A URS examiner decides on the papers submitted; there is no discovery process, no hearing, and no opportunity to file supplemental evidence after the complaint is submitted unless the examiner requests it. The complaint you file is the case you have.

Step 3: Draft the URS complaint and select the filing platform

The URS is administered through accredited providers. WIPO is the dominant provider and the appropriate choice for most .net disputes. The complaint is filed electronically through the provider's online portal. At WIPO, the URS filing interface is separate from the UDRP filing interface, and the forms are distinct – verify you are in the correct procedure before uploading.

A compliant URS complaint contains five core components:

1. The complainant's identification and contact details.
2. The disputed domain name and the registrar of record.
3. The trademark evidence – registration certificates, TMCH records, or documented common-law use.
4. The factual basis for all three URS elements: confusing similarity, no legitimate interest, and bad faith.
5. The certification that the complaint is complete and accurate, that the mark is currently in use in commerce, and that the complainant agrees to the URS terms.

The trap in drafting is a writing error that defeats even a strong case: asserting rather than proving. "The domain was clearly registered in bad faith" is an assertion. "The domain was registered three days after the complainant's mark received national media coverage, resolves to a page carrying competitive pay-per-click advertising for direct competitors, and the registrant has demanded USD 40,000 from the complainant by email" is proof. The clear-and-convincing standard is not met by characterizations; it is met by documented facts.

Address all three elements in separate, clearly labeled sections. URS examiners work quickly – the procedure is designed for speed – and a complaint that forces the examiner to locate your bad-faith argument in the middle of a paragraph about confusing similarity is a complaint that risks a denial.

Step 4: Understand what happens after you file

Once the complaint is submitted and the filing fee paid, the provider begins the administrative compliance review. This checks that the complaint is formally complete – not that it is meritorious. If there is a deficiency, the provider notifies the complainant and allows a short correction window. Failure to cure within that window means the complaint is terminated without a refund of the filing fee.

After the compliance check, the case commences formally and the registrar locks the domain – meaning the registrant cannot transfer or delete the domain during the proceeding. The registrant then has a defined response period to submit a defense. If no response is filed, the case proceeds as a default.

A default is not an automatic win. The URS rules require the examiner to find the complaint meritorious on its own – the examiner applies the clear-and-convincing standard to the complaint's evidence regardless of whether the registrant has answered. A complaint that would have failed on the merits fails in default.

In a recent matter involving a .net domain (autumn 2025), we filed a URS complaint on behalf of a technology brand against a registrant who had built a near-identical landing page capturing inbound traffic. The registrant defaulted. The examiner still reviewed every element on the evidence we supplied. Suspension was ordered within approximately three weeks of commencement – a timeline that reflects both the procedure's design for speed and the quality of the pre-filing evidence file we assembled.

Step 5: Respond to the examiner's decision – including an adverse one

If suspension is ordered, the registrar implements it within a short window and the domain resolves to a URS suspension notice page for the remainder of the registration term. At that point, consider your next step carefully.

A URS suspension does not bar a subsequent UDRP complaint for the same domain. If permanent recovery matters to you – and for most brand owners it does – a UDRP complaint filed after the URS suspension remains available. The URS suspension decision is not binding on a UDRP panel, though the factual record developed in the URS proceeding can be useful evidence in the UDRP filing.

If the complaint is denied, the denial itself has consequences. A URS denial is not a finding of legitimate interest. The examiner did not conclude the registrant has a right to the name – only that the complainant did not meet the clear-and-convincing threshold on the evidence submitted. A UDRP complaint – with a fuller evidentiary record and the lower preponderance standard – may succeed where the URS did not.

What is the trap if you lose? Filing a second URS complaint on the same facts and evidence is not the answer. The clear-and-convincing bar that blocked the first complaint will block the second. The correct response is to upgrade to the UDRP, reassess the evidence gaps, and address them before filing. In our practice, we have successfully pursued UDRP transfer for clients whose earlier URS attempts on the same domain were denied, precisely because the evidentiary threshold is different.

Step 6: The decision matrix – URS, UDRP, or both?

The right instrument depends on what you need and what the evidence supports. Working through the scenarios helps clarify the choice.

If the domain is a .net, the infringement is clear-cut, and you need a fast takedown but are comfortable forfeiting permanent ownership, URS at WIPO is the fastest and least expensive route – the procedure is designed to run in weeks, not months. That said, the clear-and-convincing threshold means only cases with strong, documentary evidence should go to URS first. A marginal case that fails URS has cost you the filing fee and placed a denial on the record.

If permanent ownership of the .net domain is your objective, UDRP is the direct path. A single-member panel at WIPO costs USD 1,500 in filing fees, and a standard case completes in roughly two months. The preponderance standard is more achievable for cases where bad faith is supported but not immediately obvious from the face of the evidence. The UDRP also carries a full three-element analysis and is the settled mechanism for gTLD recovery at scale.

If the same string is registered across both a .net and a new gTLD – say, a .net and a .cloud – a coordinated filing strategy can address both. A UDRP complaint covers multiple domains if the registrant is the same holder. A URS complaint similarly can target multiple domains in one filing. This approach avoids duplicating costs when the underlying bad faith is the same pattern across both zones.

For situations where the registrant is operating a fraud scheme, impersonating the brand, or where damages are sought beyond mere suspension or transfer, court litigation under applicable anticybersquatting provisions remains an option. That path involves local litigation counsel in the relevant jurisdiction and substantially higher costs, but it is the only route that reaches money damages.

If a prior URS filing produced a denial, or if you are deciding between a URS and a UDRP for your .net domain, email info@cognomenlaw.com to assess the evidence gaps and the better path forward.

Common pitfalls that decide URS outcomes

Evidence quality is the single largest determinant of URS success. The clear-and-convincing standard does not allow examiners to infer bad faith from the circumstantial pattern the way a UDRP panel might on a preponderance reading. Every element must be positively shown.

Complainants in our experience most often fail at the bad-faith element, not the confusing-similarity element. Confusing similarity is a largely mechanical comparison – the domain string against the mark. Bad faith requires positive evidence: documentary proof of intent, commercial exploitation of the mark's goodwill, or a pattern of targeting. A domain that simply sits parked may be passive holding; panels have recognized passive holding as bad faith under the UDRP, but under the URS's higher standard, passive holding alone may be insufficient without corroborating evidence of targeting.

A second common failure is the concurrent trademark. When the registrant holds a trademark registration that arguably covers the domain, the legitimate-interest element is contested. The URS is not the right tool for a contested ownership dispute. If the registrant can point to any documented basis for the name, the case belongs in UDRP – or in court – where full analysis of competing rights is possible.

Should you name all domain registrations in one complaint or file separately? If the same registrant holds a .net and related strings, a single URS complaint covering all registrations is more cost-efficient. The trap is incomplete registrant identification: if the names appear under different registrant aliases, the complaint must target each alias separately, or the provider will question whether the registrant is in fact the same holder.

Related at COGNOMEN

• COGNOMEN's URS and new-gTLD dispute service – how we assess and file
• Analysis: URS strategy for .cloud and new gTLD domains across zones
• FAQ: enforcing a UDRP decision across .it and other ccTLD zones