Back
Twice Denies Lazarus Enterprises UDRP Complaint Over Founder's Domain Names
In a case that underscores the procedural limits of the in resolving internal corporate conflicts, found itself locked out of its primary domain names after the company's founder unilaterally revoked administrative access. Two separate panels denied the company's complaints in , leaving the legal ownership of
lazarusai.com
and
lazarus.enterprises
entirely unresolved. The decisions expose a critical gap: the UDRP, designed to combat by third parties, is ill-equipped to adjudicate ownership disputes between a company and its own founder.
, an AI software company headquartered in Boston and later reincorporated in Delaware, had been using both domains as its primary digital storefront for customer communications, email infrastructure, and brand identity. Internally, however, the domains were never formally transferred to the company. Ariel Elizarov, the founder, had registered
lazarus.enterprises
before the company's incorporation and later registered
lazarusai.com
in his own name. Although the company paid renewal fees and treated the domains as corporate assets, the registrar accounts remained in Elizarov's name.
The relationship deteriorated in late 2025 for undisclosed reasons. Elizarov retired as CEO and resigned from the board in , and a new CEO was appointed. But Elizarov contested that the board actions were invalid under the company's bylaws, claiming he remained the majority shareholder and lawfully reasserted executive authority in . What is uncontested is that in , Elizarov revoked all other administrative access to the registrar accounts for both domains, effectively locking the company out of its digital presence.
The UDRP Proceedings
The UDRP was created in to address —actors registering domain names corresponding to well-known trademarks in to extort or mislead. The process is fast, typically concluding in under sixty days, without oral hearings, depositions, or cross-examination. To succeed, a complainant must prove three elements: (1) the domain name is identical or confusingly similar to a trademark in which the complainant has rights; (2) the respondent has no in the name; and (3) the name was registered and is being used in . All three must be established.
Lazarus Enterprises filed its first UDRP complaint shortly after the lockout. The panel denied it, finding insufficient evidence of and noting that the factual disputes—regarding the validity of a , the authenticity of its execution, and the rightful authority to speak for the company—required discovery that the UDRP could not provide. The company refiled with a second complaint, but a different panel also denied it.
The second panel acknowledged that the company had developed rights in the name "LAZARUS" through years of use in connection with AI products. Yet that alone was insufficient. The core difficulty lay elsewhere: the between Elizarov and the company in was produced by the company but was not fully executed. The panel could not determine whether it had ever been finalized. Moreover, the company could not explain why the agreement had not been produced during the first proceeding despite being in its own records. Even if accepted, an from could not establish that Elizarov had acted in when he registered the domains in and —a time when no company existed and no trademark had been established.
The panel also rejected the argument that Elizarov's administrative update constituted a new "registration" capable of attracting a fresh analysis. He had always been the . Updating access credentials is not acquiring a domain. The panel declined to find against either side, noting that both parties had at least to legitimacy.
Why the UDRP Failed
The first panel plainly stated that the factual disputes could not be resolved within the UDRP framework. The second panel echoed this:
"The panel could not determine who owns those domain names. That was not a failure of the panel but an honest acknowledgment of the limits of the forum."
The actual questions in dispute—whether the
transferred ownership, whether it was properly executed, whether Elizarov signed it, and who had legitimate authority to act for the company—are questions of contract law, corporate governance, intellectual property assignment, and fiduciary obligation. These require sworn evidence, witnesses, document discovery, and cross-examination—none of which the UDRP provides.
The case illustrates a structural gap: the UDRP is an efficient tool for policing bad-faith registrations by unrelated third parties, but it cannot resolve ownership claims between a company and its own founders. As one panelist noted,
"Property follows registration even if equity shareholders may disagree."
A Cautionary Tale for Corporate Governance
The Lazarus dispute is far from unique. Many early-stage companies register domain names informally: a founder sets up the registrar account, or a technical co-founder holds the credentials. As the company grows, raises capital, appoints a board, and files patents, the domain transfer may be overlooked. The asset is used as though it belongs to the company—because for practical purposes, it does. But in the eyes of the law, it may not.
This matters for any company with limited formal documentation of title. For companies seeking venture investment or preparing for an acquisition, due diligence will expose mismatches between operational use and registered ownership. For companies with multiple founders, the departure of any one of them leaves unresolved questions about who controls registrar accounts. For businesses that have built significant brand equity around a domain they do not legally own, the commercial value rests on an unresolved ownership uncertainty.
Best practices require periodic audits of every domain and digital asset: confirm the , verify that registrar account credentials are held institutionally rather than personally, and ensure access rights are linked to roles rather than individuals. If domains are registered in a founder's or employee's name, a formal written assignment agreement—executed, dated, and recorded—should transfer those registrations to the company. Founder agreements and IP assignment clauses should reference domain names expressly, not merely by implication under a general IP sweep.
The Path Forward for Lazarus Enterprises
The panels could not resolve who owns those domains. That was not a failure of the panels but an honest acknowledgment of the limits of the forum. Resolving the ownership question properly would require a court with full evidentiary powers—the ability to compel discovery, examine witnesses, assess document authenticity, and apply contract and corporate law principles. However, no court has yet been seized of the matter. The ownership question remains open.
What the Lazarus decisions leave behind is a lingering uncertainty: the law does not provide a clean answer when the registrant and the user diverge. Contract may offer clarity, but it must be properly executed. could not answer the question because it was not the right forum. Perhaps this question should never have reached a forum at all. It should have been dealt with clearly, in writing, at the beginning—via an agreement or board resolution. Allowing assumptions and taking ownership for granted turned a manageable governance gap into a costly, unresolved dispute.
For the legal community, the Lazarus case reinforces a vital lesson: domain names are strategic assets deserving the same governance attention as trademarks, bank accounts, and shareholding records. The UDRP has its limits, and those limits can only be avoided by diligent corporate housekeeping.
