Protecting the Petrossian Brand from Passive Holding and Email Fraud

UDRP Cases

In case D2026-4541, CAVIAR PETROSSIAN successfully moved to transfer the domain petrossian.store. The panel found that the Respondent used the domain for passive holding with suspicious email configurations, meeting the criteria for bad faith registration.

Case Snapshot

Case Number D2026-4541
Complainant CAVIAR PETROSSIAN
Respondent Charly Bilzerian
Disputed Domain
petrossian.store
Threat Tactic Passive Holding
Decision Date 2026-11-12
Panelist Alexandre Nappey
OutcomeTransfer
Official Source https://www.wipo.int/amc/en/domains/search/text.jsp?case=D2026-4541
UDRP Legal Assistance

Facing Unauthorized Domain Registrations or Brand Abuse?

Our domain dispute attorneys represent trademark owners and businesses worldwide before WIPO, Forum (NAF), and CAC. Explore our Domain Name Disputes and Enforcement & Takedowns services, or request a free case evaluation.

Request Case Evaluation

Business Risk: Email-Based Impersonation and Passive Domain Holding

The registration of ‘petrossian.store’ represents a clear risk of brand impersonation, notwithstanding the absence of an active website. Although the domain currently directs to a registrar landing page, the presence of Mail Exchange (MX) and Sender Policy Framework (SPF) records indicates the domain was likely configured to send and receive emails. Given the Complainant’s history of facing retail phishing campaigns, these technical configurations suggest a high probability that the domain was intended to facilitate deceptive business email compromise or fraudulent customer correspondence. Such activities can severely compromise customer trust and operational security by mimicking the brand’s official communication channels.

Furthermore, the discovery of contact information during the registrar verification process that differed from the initial complaint details highlights the challenges of identity obfuscation in domain registration. This tactic, combined with the passive holding of a high-value trademark domain, forces brand owners into reactive legal enforcement cycles. For organizations like CAVIAR PETROSSIAN, these registrations necessitate constant vigilance against supply chain fraud, as bad actors often exploit the perceived legitimacy of a domain name to conduct secondary attacks. Proactive monitoring for trademark-matching registrations in new gTLDs remains an essential defensive measure to mitigate the risk of such infrastructure being weaponized against customers and partners.

Strategic Application of Passive Holding and Technical Indicators in UDRP

The Complainant successfully navigated the burden of proof in this case by linking the lack of an active website to a broader pattern of potential brand abuse. Rather than relying solely on the domain’s inactivity, the Complainant provided technical evidence in the form of MX and SPF records, which served to substantiate a claim of bad faith under the doctrine of passive holding. By documenting these configurations, the Complainant demonstrated that the domain was likely prepared for unauthorized email communication or phishing, even before an active landing page or consumer-facing website was established. This approach effectively anticipated potential defense arguments, positioning the domain’s registration as a preparatory step for fraudulent activity rather than an benign acquisition.

Furthermore, the Complainant’s evidence-gathering strategy was strengthened by highlighting past retail phishing incidents associated with their brand. By framing the petrossian.store registration within the context of previous external threats, the Complainant established a compelling narrative of risk that enabled the Panel to conclude bad faith usage. The Registrar verification process also played a critical role; by identifying discrepancies between the registrant’s contact information and the data provided in the initial complaint, the Complainant cast doubt on the Respondent’s legitimacy. This multi-layered approach—combining forensic technical data with historical threat intelligence—proved persuasive in securing a transfer without requiring the Respondent to initiate a live fraudulent campaign.

Practical Recommendations

  • Perform active technical monitoring for new domain registrations containing your brand; specifically, query DNS records for MX and SPF configurations to identify domains primed for email-based impersonation, even when no website is active.
  • Document and archive all instances of non-public technical domain configurations (like mail server records) early in your investigation, as these serve as critical evidence of bad-faith intent in ‘passive holding’ UDRP cases.
  • Utilize domain registrar verification requests early in the dispute process to identify discrepancies between WHOIS data and actual registrant details, which strengthens the argument of respondent anonymity or bad faith.
  • Maintain a proactive defensive registration strategy across high-risk gTLDs (such as .store or .shop) that align with your retail business model to minimize the surface area for impersonation attacks.
  • When filing UDRP complaints for inactive domains, explicitly link the domain’s passive status to historical brand-specific fraud patterns to help the panel establish a broader pattern of bad faith.

Frequently Asked Questions (FAQ)

Why was the domain petrossian.store considered confusingly similar to the Complainant’s brand?

The Panel determined that the disputed domain petrossian.store is identical to the PETROSSIAN word mark, as it reproduces the trademark in its entirety, thereby meeting the standing requirement for confusing similarity.

How did the absence of an active website impact the finding of bad faith?

Under the doctrine of passive holding, the lack of an active website does not preclude a finding of bad faith. In this case, the Panel noted that the presence of MX and SPF records—which facilitate email communication—strongly suggested the domain was intended for malicious use such as phishing, especially given the Complainant’s history with retail impersonation schemes.

What evidence proved the Respondent lacked rights or legitimate interests in the domain?

The Respondent failed to file a response to the complaint and was not commonly known by the name PETROSSIAN. Additionally, there was no evidence of any authorization, license, or affiliation between the Respondent and the Complainant, confirming the absence of any legitimate interests.

What is the primary business risk identified in this UDRP case?

The case highlights the risk of domain-based technical configurations (MX/SPF) being used to facilitate email fraud and supply chain impersonation, even when no visible website is active. Monitoring for these specific DNS configurations is a critical component of defensive brand protection.

Is someone blocking a brand domain?

Even without an active website, passive domain holding—especially when combined with suspicious MX and SPF configurations—poses a significant risk for email-based impersonation and fraud. Protect your brand infrastructure before it is weaponized.

Check recovery options

Get Expert UDRP & Domain Dispute Assistance
Request a confidential case evaluation from our domain dispute attorneys. We will review your domain situation and reply within 24 hours.

    Thank You for Your Request!
    Our legal team is reviewing your dispute details and will contact you via email shortly.
    Image
    This site uses cookies to improve your experience. By continuing, you agree to our Privacy Policy.
    Privacy settings

    When you visit websites, they may store or retrieve data in your browser. This storage is often required for basic website functionality. Storage may be used for marketing, analytics and site personalization purposes, such as storing your preferences. Privacy is important to us, so you can disable certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may affect the performance of the website.

    Manage settings

    Necessary
    Always active

    These cookies are necessary for the website to function and cannot be disabled in our systems. They are usually only set in response to actions you take that constitute a request for services, such as adjusting your privacy settings, logging in, or filling out forms. You can set your browser to block these cookies or notify you about them, but some parts of the site will not work. These cookies do not store any personal information.

    Marketing

    These elements are used to show you advertising that is more relevant to you and your interests. They can also be used to limit the number of ad views and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the permission of the site operator.

    Personalization

    These elements allow the website to remember your choices (such as your username, language or region you are in) and provide enhanced, more personalized features. For example, a website may provide you with local weather forecasts or traffic news by storing data about your current location.

    Analytics

    These elements help the website operator understand how their website works, how visitors interact with the site and whether there may be technical problems. This type of storage usually does not collect information that identifies the visitor.