Bunge Limited, Bunge SA, and Bunge Deutschland GmbH v. IsmailovIskandar
Claim Number: FA2208002008945
Complainant is Bunge Limited, Bunge SA, and Bunge Deutschland GmbH (“Complainant”), represented by Renee Reuter, Missouri, USA. Respondent is IsmailovIskandar (“Respondent”), Uzbekistan.
REGISTRAR AND DISPUTED DOMAIN NAME
The domain name at issue is <bunge.group>, registered with Eranet International Limited.
The undersigned certifies that he has acted independently and impartially and to the best of his knowledge has no known conflict in serving as Panelist in this proceeding.
Paul M. DeCicco, as Panelist.
Complainant submitted a Complaint to the Forum electronically on August 18, 2022; the Forum received payment on August 18, 2022.
On August 19, 2022, Eranet International Limited confirmed by e-mail to the Forum that the <bunge.group> domain name is registered with Eranet International Limited and that Respondent is the current registrant of the name. Eranet International Limited has verified that Respondent is bound by the Eranet International Limited registration agreement and has thereby agreed to resolve domain disputes brought by third parties in accordance with ICANN’s Uniform Domain Name Dispute Resolution Policy (the “Policy”).
On August 24, 2022, the Forum served the Complaint and all Annexes, including a Written Notice of the Complaint, setting a deadline of September 13, 2022 by which Respondent could file a Response to the Complaint, via e-mail to all entities and persons listed on Respondent’s registration as technical, administrative, and billing contacts, and to postmaster@bunge.group. Also on August 24, 2022, the Written Notice of the Complaint, notifying Respondent of the e-mail addresses served and the deadline for a Response, was transmitted to Respondent via post and fax, to all entities and persons listed on Respondent’s registration as technical, administrative and billing contacts.
Having received no response from Respondent, the Forum transmitted to the parties a Notification of Respondent Default.
On September 21, 2022, pursuant to Complainant's request to have the dispute decided by a single-member Panel, the Forum appointed Paul M. DeCicco as Panelist.
Having reviewed the communications records, the Administrative Panel (the "Panel") finds that the Forum has discharged its responsibility under Paragraph 2(a) of the Rules for Uniform Domain Name Dispute Resolution Policy (the "Rules") "to employ reasonably available means calculated to achieve actual notice to Respondent" through submission of Electronic and Written Notices, as defined in Rule 1 and Rule 2. Therefore, the Panel may issue its decision based on the documents submitted and in accordance with the ICANN Policy, ICANN Rules, the Forum's Supplemental Rules and any rules and principles of law that the Panel deems applicable, without the benefit of any response from Respondent.
Complainant requests that the domain name be transferred from Respondent to Complainant.
PRELIMINARY ISSUE: MULTIPLE COMPLAINANTS
Paragraph 3(a) of the Rules for Uniform Domain Name Dispute Resolution Policy (the “Rules”) provides that “[a]ny person or entity may initiate an administrative proceeding by submitting a complaint.” The Forum’s Supplemental Rule 1(e) defines “The Party Initiating a Complaint Concerning a Domain Name Registration” as a “single person or entity claiming to have rights in the domain name, or multiple persons or entities who have a sufficient nexus who can each claim to have rights to all domain names listed in the Complaint.”
There are three nominal complainants in this matter: Bunge Limited, Bunge SA, and Bunge Deutschland GmbH. Complainant contends that Bunge Limited, Bunge SA, and Bunge Deutschland GmbH are all related companies and that Bunge Limited is the parent of the various Bunge subsidiary company. Furthermore, Bunge SA and Bunge Deutschland GmbH are wholly indirectly owned by Bunge Limited. The Panel therefore finds that the three nominal complainants (herein referred to collectively as Complainant) have a sufficient nexus to one another and to the matters complained of herein such that they may be treated as if a single entity. See Tasty Baking, Co. & Tastykake Invs., Inc. v. Quality Hosting, FA 208854 (Forum Dec. 28, 2003) (treating the two complainants as a single entity where both parties held rights in trademarks contained within the disputed domain names); see also, Am. Family Health Srvs. Group, LLC v. Logan, FA 220049 (Forum Feb. 6, 2004) (finding a sufficient link between the complainants where there was a license between the parties regarding use of the TOUGHLOVE mark).
A. Complainant
Complainant contends as follows:
Complainant is a supplier of oil for business customers, manufacturers, bakeries, restaurants, and foodservice operators.
Complainant has rights in the BUNGE mark through its registration with the United States Patent and Trademark Office (“USPTO”).
Respondent’s <bunge.group> domain name is identical or confusingly similar to Complainant’s BUNGE mark as it incorporates the mark in its entirety while merely adding the “.group” generic top-level domain (“gTLD”).
Respondent lacks rights and legitimate interests in the <bunge.group> domain name. Respondent is not commonly known by the at-issue domain name, nor has Complainant authorized or licensed Respondent to use its BUNGE mark in the at-issue domain name. Respondent does not use the domain name for any bona fide offering of goods or services, nor a legitimate noncommercial or fair use, but instead passes off as Complainant while potentially phishing for internet users’ private information.
Respondent registered and uses the <bunge.group> domain name in bad faith. Respondent disrupts Complainant’s business while passing itself off as Complainant. Additionally, Respondent registered the at-issue domain name with constructive and/or actual knowledge of Complainant’s rights in the BUNGE mark.
B. Respondent
Respondent failed to submit a Response in this proceeding.
Complainant has trademark rights in BUNGE.
Respondent is not affiliated with Complainant and had not been authorized to use Complainant’s trademark in any capacity.
Respondent registered the at‑issue domain names after Complainant acquired rights in the BUNGE trademark.
Respondent uses the at-issue domain name to addresses a website mimicking Complainant’s genuine website.
Paragraph 15(a) of the Rules instructs this Panel to "decide a complaint on the basis of the statements and documents submitted in accordance with the Policy, these Rules and any rules and principles of law that it deems applicable."
Paragraph 4(a) of the Policy requires that Complainant must prove each of the following three elements to obtain an order that a domain name should be cancelled or transferred:
(1) the domain name registered by Respondent is identical or confusingly similar to a trademark or service mark in which Complainant has rights; and
(2) Respondent has no rights or legitimate interests in respect of the domain name; and
(3) the domain name has been registered and is being used in bad faith.
In view of Respondent's failure to submit a response, the Panel shall decide this administrative proceeding on the basis of Complainant's undisputed representations pursuant to paragraphs 5(f), 14(a) and 15(a) of the Rules and draw such inferences it considers appropriate pursuant to paragraph 14(b) of the Rules. The Panel is entitled to accept all reasonable allegations set forth in a complaint; however, the Panel may deny relief where a complaint contains mere conclusory or unsubstantiated arguments. See WIPO Jurisprudential Overview 3.0 at ¶ 4.3; see also eGalaxy Multimedia Inc. v. ON HOLD By Owner Ready To Expire, FA 157287 (Forum June 26, 2003) (“Because Complainant did not produce clear evidence to support its subjective allegations [. . .] the Panel finds it appropriate to dismiss the Complaint”).
The at-issue domain is confusingly similar to a trademark in which Complainant has rights.
Complainant’s USPTO registration for BUNGE, as well as any of its many national registrations for such mark worldwide, establishes Complainant’s rights in BUNGE for the purposes of Policy 4(a)(i). See Haas Automation, Inc. v. Jim Fraser, FA 1627211 (Forum Aug. 4, 2015) (finding that Complainant’s USPTO registrations for the HAAS mark sufficiently demonstrate its rights in the mark under Policy ¶ 4(a)(i)).
The at-issue domain name contains Complainant’s BUNGE trademark followed by the “.group” top level domain name. The differences between Respondent’s domain name and Complainant’s trademark are insufficient to distinguish the <bunge.group> domain name from Complainant’s trademark under Policy ¶ 4(a)(i). Therefore, the Panel finds that Respondent’s <bunge.group> domain name is confusingly similar to Complainant’s BUNGE trademark. See Tupelo Honey Hospitality Corporation v. King, Reggie, FA 1732247 (Forum July 19, 2017) (“Addition of a gTLD is irrelevant where a mark has been fully incorporated into a domain name and the gTLD is the sole difference.”).
Under Policy ¶ 4(a)(ii), Complainant must first make out a prima facie case showing that Respondent lacks rights and legitimate interests in respect of an at-issue domain name and then the burden, in effect, shifts to Respondent to come forward with evidence of its rights or legitimate interests. See Hanna-Barbera Prods., Inc. v. Entm’t Commentaries, FA 741828 (Forum Aug. 18, 2006). Since Respondent failed to respond, absent evidence of Policy ¶4(c) circumstances Complainant’s prima facie showing acts conclusively.
Respondent lacks both rights and legitimate interests in respect of the at-issue domain name. Respondent is not authorized to use Complainant’s trademark in any capacity and, as discussed below, there are no Policy ¶ 4(c) circumstances from which the Panel might find that Respondent has rights or interests in respect of the at-issue domain name.
The WHOIS information for <bunge.group> indicates that “IsmailovIskandar” is the domain name’s registrant and there is nothing in the record indicating that Respondent is otherwise known by the at-issue domain name. Therefore, the Panel finds that Respondent is not commonly known by <bunge.group> under Policy ¶ 4(c)(ii). See Coppertown Drive-Thru Sys., LLC v. Snowden, FA 715089 (Forum July 17, 2006) (concluding that the respondent was not commonly known by the <coppertown.com> domain name where there was no evidence in the record, including the WHOIS information, suggesting that the respondent was commonly known by the disputed domain name).
Respondent uses the <bunge.group> domain name to pass itself off as Complainant and address a website with the look and feel of Complainant’s genuine website. Such use of the domain name is not indicative of a bona fide offering of goods or services under Policy ¶ 4(c)(i), nor of a non-commercial or fair use under Policy ¶ 4(c)(iii). See Ripple Labs Inc. v. Jessie McKoy / Ripple Reserve Fund, FA 1790949 (Forum July 9, 2018) (finding the respondent did not use the domain name to make a bona fide offering of goods or services per Policy ¶ 4(c)(i) or for a legitimate noncommercial or fair use per Policy ¶ 4(c)(iii) where the website resolving from the disputed domain name featured the complainant’s mark and various photographs related to the complainant’s business).
Given the forgoing, Complainant satisfies its initial burden under Policy ¶ 4(a)(ii) and conclusively demonstrates Respondent’s lack of rights and lack of interests in respect of the at-issue domain name.
As discussed below without limitation, bad faith circumstances are present which compel the Panel to conclude that Respondent acted in bad faith pursuant to paragraph 4(a)(iii) of the Policy.
First, Respondent uses the at-issue <bunge.group> domain name pass itself off as Complainant. Notably, the <bunge.group> website mimics Complainant’s genuine website in form and content. Such use of the domain name is disruptive to Complainant’s business and demonstrates bad faith pursuant to Policy ¶¶ 4(b)(iii) and (iv). See Artistic Pursuit LLC v. calcuttawebdevelopers.com, FA 894477 (Forum Mar. 8, 2007) (finding that the respondent’s registration and use of the disputed domain name, which displayed a website virtually identical to the complainant’s website, constituted bad faith pursuant to Policy ¶ 4(b)(iii)); see also, Bittrex, Inc. v. Caroline Alves Maia, FA 1796113 (Forum Aug. 6, 2018) (finding the respondent registered and used the domain name in bad faith per Policy ¶ 4(b)(iv) because the respondent used the disputed domain name to present users with a website that was “virtually identical, with the same color scheme, the same layout and the same substantive content” and used the website to gain access to users’ cryptocurrency accounts).
Moreover, Respondent had actual knowledge of Complainant’s rights in the BUNGE mark when it registered <bunge.group> as a domain name. Respondent’s actual knowledge is evident from the notoriety of the BUNGE trademark and from Respondent’s use of <bunge.group> to address a website that mimics Complainant’s genuine website. Respondent’s registration and use of the <bunge.group> domain names with knowledge of Complainant’s rights in such domain name further shows Respondent’s bad faith pursuant to Policy ¶ 4(a)(iii). See Minicards Vennootschap Onder FIrma Amsterdam v. Moscow Studios, FA 1031703 (Forum Sept. 5, 2007) (holding that respondent registered a domain name in bad faith under Policy ¶ 4(a)(iii) after concluding that respondent had actual knowledge of Complainant's mark when registering the disputed domain name); see also, Univision Comm'cns Inc. v. Norte, FA 1000079 (Forum Aug. 16, 2007) (rejecting the respondent's contention that it did not register the disputed domain name in bad faith since the panel found that the respondent had knowledge of the complainant's rights in the UNIVISION mark when registering the disputed domain name).
Having established all three elements required under the ICANN Policy, the Panel concludes that relief shall be GRANTED.
Accordingly, it is Ordered that the <bunge.group> domain name be TRANSFERRED from Respondent to Complainant.
Paul M. DeCicco, Panelist
Dated: September 22, 2022
Click Here to return to the main Domain Decisions Page.
Click Here to return to our Home Page