Breaking news: NiceNIC discovers the Report button

After Nicenic got mad at the site, instead of trying to contact me first. They went straight to the registrar and registry claiming defamation, which is ironic because in their own blog they say that its not the registrars responsibility to police the content of the site. So after that failed, they went running to WIPO like a crying child runs to his mom after being told 'no' by a registrar.

According to the Decision, the UDRP Complaint was filed at WIPO on February 15, 2026, which is the day NiceNIC decided that the internet had become dangerously confusing and something had to be done immediately. The next day, on February 16, 2026, WIPO asked the Registrar (Spaceship, Inc.) to verify the registration details for <nicenic.blog>, <nicenic.support>, <nicenic.top>, and <nicenic.xyz>, and the Registrar responded the same day with the underlying registrant and contact information. The Decision notes that this registrant information differed from the respondent details originally shown in the Complaint (which referenced an “unknown”/privacy-masked registrant at filing time).

On February 17, 2026, WIPO emailed the Complainant to provide the registrar-disclosed registrant details and invited the Complainant to amend the Complaint, because the “unknown” villain needed a real name for the paperwork. That same day, the Complainant submitted an amended Complaint. Also on February 17, 2026, I contacted Spaceship’s live support because I had received an email from domain.disputes@wipo.int that included my personal registrant information and I wanted to understand who it had been disclosed to, under what process, and why I was not separately notified by the Registrar.

WIPO formally notified me of the Complaint and the proceeding commenced on February 18, 2026. The Decision records that my formal Response deadline would have been March 10, 2026, and that I filed a full Response earlier, on February 23, 2026.

The Decision also records that there were unsolicited supplemental filings: the Complainant filed a supplemental submission on February 28, 2026, I filed a reply supplemental submission on March 2, 2026, and the Complainant filed a second supplemental submission on March 7, 2026. The Panel declined to admit those supplemental filings, noting that nothing turned on the new information for the issues that needed to be decided in this particular proceeding, which is a polite judicial way of saying “thanks, but no thanks”.

WIPO appointed Andrew D. S. Lothian as the sole panelist on March 2, 2026. The Decision was issued on March 16, 2026 and ordered that all four disputed domain names be transferred to the Complainant.

The Decision describes nicenic.blog as hosting a site titled “How Nicenic is Helping Cyber Criminals” with critical content about how abuse reports are handled. It also notes that nicenic.support and nicenic.xyz forwarded to nicenic.blog (and that nicenic.top was intended to do the same).

The disputed domains in this case were <nicenic.blog>, <nicenic.xyz>, <nicenic.support>, and <nicenic.top>, and the Registrar was Spaceship, Inc.. The Complainants were Nicenic International Group co., Limited (Hong Kong, China) and Nicenic LLC (United States), and the Decision treats them together as “the Complainant” for most of the analysis.

Translation: one site had criticism, the other three were basically signposts pointing to it, and everyone involved understood that the content was criticism. The controversy was not “what is this site about?”, it was “should the URL be allowed to be this obvious?”.

The Complaint alleged that the domains were identical to the NICENIC trademark, that I had no legitimate interest in registering exact-match domains, and that registration/use was in bad faith.

On the first UDRP element, the Complaint relied on a United States trademark registration for NICENIC (the Decision references United States Registered Trademark Number 7843916, registered June 24, 2025, in Class 45) and argued that the disputed domains incorporated the mark in its entirety, and that changing only the TLD (such as “.blog” or “.support”) does not avoid confusing similarity. On the second element, the Complaint argued that I was not authorized to use the mark, that I was not commonly known by “nicenic”, and that registering exact-match domains without any critical qualifier (for example, without adding a term like “review” or “criticism” in the domain itself) created a false impression of official association, which is a fancy way of saying “we’d like the address bar to be a restricted resource”. On the third element, the Complaint argued that the timing and pattern of registrations targeted the mark and that the redirections to <nicenic.blog> showed coordinated use intended to disrupt the Complainant’s business and mislead users.

In plainer English, the Complaint’s theme is: “you criticized us, and you used our name to do it, therefore you must be acting in bad faith”. Whether you agree with that framing or not, that is the posture the case takes from the first page onward.

My opinion is that it reads like a company discovering, with genuine surprise, that the internet can contain negative information about them. Rather than respond to the substance, the Complaint tries to turn the URL itself into the villain, because you can’t cross-examine a URL.

Before the WIPO email turned up, NiceNIC’s submissions include evidence of the “let’s ask the registrar-abuse team to fix it” approach since they probably didnt want to spend $1500 on a UDRP filing. The screenshots show an urgent abuse report sent to Spaceship’s abuse address pointing at the nicenic domain cluster, framed as trademark infringement and “false affiliation”. In other words, step one was: ask the platform that can actually take domains down.

Also, I find it ironic that nicenic says themself on 90% of abuse cases its only the registrars ability to address dns abuse and registrars dont control websites here and many other pages. But i guess that only applies when they want it to.

After Spaceship did the same as NiceNIC does to people who report abuse which is ghosting them, NiceNIC then tried the gentler route and tried to contact me. Their materials include a “clarification request” email addressed to contact@nicenic.blog, telling me their business is under “confusing” inquiry and inviting clarification, sadly i didn’t receive the email. So the “please respond, we just want clarity” strategy didn’t actually create a conversation, it just became more ammunition for a later narrative.

NiceNIC also attached ticket-style screenshots showing people contacting them with questions about the sites. Those same “people asking questions” screenshots are later packaged in the UDRP Complaint as proof of “actual consumer confusion”. The funny part is that if asking for clarification counts as confusion, then congratulations: every careful reader is “confused” on NiceNIC’s paperwork-approved definition.

In the UDRP submission, NiceNIC explicitly ties the case to what the sites say and publish, arguing that “The Respondent has used the disputed domain names to publish allegations and accusations targeting the Complainants’ business.” NiceNIC then adds that “Importantly, actual consumer confusion has already occurred” and that, as evidenced by “Annex 6 - Customer Confusion Evidence.pdf”, customers contacted the Complainants asking whether the websites nicenic.xyz and nicenic.support were affiliated and whether the content was legitimate. To translate that into normal human English: do you see how everyone who asked was “so confused”? No? Yeah, that’s because they weren’t confused, they were verifying.

My Response identifies me as the Respondent and states that I am self-represented. It explains that I registered and used the disputed domains for independent journalistic reporting, cybersecurity research, and public-interest critical commentary about NiceNIC’s business practices, and that the sites were non-commercial, with no advertising or monetization, and no intent to impersonate or defraud the Complainant. I emphasized that all the domains either hosted the critical reporting or redirected to it, and that the purpose was informational and educational rather than commercial.

A key part of the Response is the claim that the website(s) contained a clear disclaimer indicating that the site is not affiliated with NiceNIC and providing a contact email address. The Response argues that this disclaimer eliminates any meaningful likelihood of confusion in practice and that inquiries cited by the Complainant did not prove that users truly believed the site was official, but rather that readers were discussing or questioning the reporting.

“The Respondent operates the disputed domains solely for independent journalistic reporting, cybersecurity research, and public-interest critical commentary… The websites are strictly non-commercial…”

— Response, Case No. D2026-0653

The Response also addresses one of the factual points raised by the Complainant about registry status, noting that <nicenic.top> had been placed on “serverHold” and stating that, after contacting the registry, it was described as a temporary administrative suspension on an alleged rights basis and was later reinstated. The Response argues that such administrative holds are not a substantive adjudication of UDRP criteria and therefore should not be treated as evidence of bad faith.

On the legal framing, the Response argues that the use falls within UDRP paragraph 4(c)(iii) (legitimate noncommercial/fair use without intent for commercial gain or misleading diversion) and cites a number of prior WIPO decisions as support for criticism and free-speech use cases. It concludes by asking the Panel to deny the Complaint and to make a finding of Reverse Domain Name Hijacking (RDNH) on the theory that the proceeding was brought to silence legitimate speech despite the noncommercial and critical nature of the site.

In other words, my position was that criticism is exactly what the Internet is for, and that “I don’t like what you wrote about me” is not a magic incantation that turns noncommercial reporting into “bad faith”.

The Decision begins by treating the two named complainant entities together as “the Complainant” and records that they requested consolidation because they are affiliated and share a common legal interest in the NICENIC trademark. The Panel allowed consolidation, noting it was equitable and procedurally efficient, and that the affiliated entities’ rights were affected in a similar way by the same set of domain registrations.

The Decision’s factual background records the Complainant’s official domains <nicenic.net> and <nicenic.com>, and references the NICENIC trademark registration (United States Registered Trademark Number 7843916) dated June 24, 2025. It then lists the registration dates for the disputed domains and notes that the Respondent is a private individual in Finland. Those domain registration dates are recorded as follows: <nicenic.support> and <nicenic.xyz> on October 11, 2025, and <nicenic.blog> and <nicenic.top> on October 19, 2025.

The Panel also describes the actual use pattern that mattered for the case: <nicenic.blog> was used for a critical site (titled “How Nicenic is Helping Cyber Criminals”), while the other disputed domains forwarded traffic to that site. The Decision mentions the Complainant’s allegation that <nicenic.top> had been subject to “serverHold” and the Respondent’s position that it had been reinstated, but it states that nothing turned on that detail for the outcome.

On the first UDRP element, the Panel found that the NICENIC mark is recognizable within each disputed domain name and that the second-level portion of each disputed domain is alphanumerically identical to the trademark. It therefore found the first element satisfied, noting that the TLD is ignored for the similarity test.

The second element is where the Decision’s key reasoning appears. The Panel acknowledged that UDRP jurisprudence recognizes fair use and noncommercial free speech in principle, and it expressly accepted that my criticism motivation was genuine and not a pretext for commercial cybersquatting. Nevertheless, the Panel applied the approach summarized in WIPO Overview 3.1 section 2.6.2 and held that registering a domain name identical to a trademark, even for genuine criticism, tends to create an impermissible risk of user confusion through impersonation. The Decision emphasizes that each disputed domain here is an exact match for NICENIC without additional wording that would signal “criticism” in the domain itself, and it calls out the choice of certain TLDs (including “.support”) as part of the overall impression.

“Panels… have increasingly found that even a general right to legitimate criticism does not necessarily extend to registering or using a domain name identical to a trademark… panels tend to find that such a domain name creates an impermissible risk of user confusion through impersonation.”

— Decision, Section 6.3(B)

The Panel then addressed the disclaimer argument directly and rejected the idea that a disclaimer “fixes” the initial deception created by the domain name itself, quoting a prior case to the effect that it is not enough to catch users with an official-looking entrance and only then reveal the true identity and intent. The Decision uses a physical-world analogy: it compares using an identical trademark domain for criticism not to “standing outside with a placard”, but to “constructing a confusingly similar entrance” to the trademark owner’s premises and capturing visitors who were looking for the official site.

If you’re wondering how much the content itself mattered, the answer (in this Decision) is: not much. The Panel explicitly says it is not judging whether the criticism is true or “defamatory”; it is judging whether the domain name string creates what it considers an unacceptable impersonation risk. So the fight is less “are the allegations correct?” and more “does the Complainant get to control the most obvious domain string forever, even when it points to criticism?”.

Based on that framework, the Panel concluded that I did not have rights or legitimate interests in the disputed domains under the Policy. The third element analysis largely mirrors the second: because the Panel treated the domains as inherently deceptive impersonation, it found that the domains were registered with the Complainant in mind and were used to divert Internet users expecting an official site to a site containing criticism they did not expect to see.

“The disputed domain names are being used to divert Internet users expecting to find an official site of the Complainant to the Respondent’s website… The adoption of such deceptive domain names… constitutes registration and use in bad faith…”

— Decision, Section 6.3(C)

Finally, because the Panel ruled for the Complainant, it stated that it did not need to address my request for a Reverse Domain Name Hijacking finding. The Decision therefore ends with the transfer order for <nicenic.blog>, <nicenic.support>, <nicenic.top>, and <nicenic.xyz>.

In my opinion, this is the core irony of the whole thing: a registrar accused of enabling online abuse got to frame itself as a helpless victim of “confusion”, while the remedy functionally helps remove a critical site from the most memorable address.

The Decision’s procedural history records that the Registrar disclosed underlying registrant data to WIPO on February 16, 2026, and WIPO invited the Complainant to amend on February 17, 2026. On February 17, 2026, I also contacted Spaceship support after receiving email that contained my registrant information.

My opinion is that this is the part where the “confusion” narrative becomes especially rich. The case is framed as protecting internet users from being misled, while the practical machinery of the dispute involves quietly swapping masked registrant data for a real person’s details so the paperwork can move forward.

“I’m more concerned about why spaceship gave my information… which party did you give my information to and why was i not notified…”

Spaceship chat transcript