When Hosting Providers Act as Judge and Jury: The Trademark Complaint Problem
The Case That Exposes a Legal Vacuum
Kenneth Gaughan's story is becoming increasingly common in web hosting, but the details reveal something more disturbing than a simple domain dispute. For years, Gaughan ran ESApet.org without incident. Then, in late 2025, both InMotion Hosting and DreamHost terminated his accounts—simultaneously—based on a trademark complaint from Elevate Rank LLC, which owns ESApet.com.
His site went dark. No court order. No formal hearing. Just a complaint, followed by service termination.
Now, in May 2026, Gaughan is fighting back in federal court, and his lawsuit is exposing something that should concern every web developer and small business owner: hosting providers are operating without a clear legal rulebook for handling trademark disputes.
Why DMCA Works for Copyright (But Not Trademarks)
If you've ever received a DMCA takedown notice, you know the process. It's formal, procedural, and—importantly—it gives you a way to fight back. Here's why:
The Digital Millennium Copyright Act, specifically Section 512, creates a safe harbor for hosting providers. If a provider follows the statutory process when they receive a copyright complaint, they're protected from liability. This creates a predictable system:
- Someone files a complaint following specific requirements
- The provider removes content and notifies you
- You can file a counternotice to dispute the claim
- Your content goes back up (unless the complainant files suit)
It's not perfect, but it works because Congress wrote explicit rules.
Trademark law has no equivalent.
When Elevate Rank submitted a trademark complaint to InMotion and DreamHost, there was no federal safe harbor to follow. No statutory process. No mandatory counternotice mechanism. The hosting providers had to make a judgment call—and they chose to terminate service based on a complaint alone.
The Contradictions That Undermine Trust
Gaughan's allegations raise red flags about how these complaints were evaluated:
The timeline problem: Elevate Rank claims first use of the "ESApet" mark in 2017, yet according to Gaughan, the company wasn't even formed until 2021. Meanwhile, ESApet.com apparently sat dormant at some point before Elevate Rank acquired it. Gaughan launched ESApet.org during that dormant period.
This isn't just a technical detail. Trademark rights don't exist in a vacuum—they're tied to actual use and priority. A mark claimed for 2017 but registered by a company formed in 2021 is immediately suspicious.
The promise versus the action: InMotion Hosting told Gaughan they wouldn't take action without a court order or a trademark cancellation notice. Then they did exactly that—took action based on nothing but a complaint. No court involvement. No canceled mark. Just a unilateral decision to shut down his business.
The Bigger Problem: Who Gets to Decide?
This case highlights a critical issue in internet governance: hosting providers are making legal decisions they're not equipped to make.
When you trademark a domain name or a business name, you're claiming exclusive rights to that mark. But those rights exist within a legal framework. They can be challenged. They can be narrow in scope (protecting only certain industries or uses). They can be abandoned if not used. None of this legal complexity is captured in a simple complaint form.
Yet hosting providers—companies primarily in the business of serving websites, not adjudicating disputes—are becoming de facto judges. They have to decide whether a complaint has merit, whether it's legitimate, whether the complainant actually has rights.
Without a statutory safe harbor (like the DMCA provides for copyright), providers face liability risk either way:
- Ignore the complaint? They could be sued for trademark infringement
- Remove the content? They could be sued for wrongful termination
The rational business decision is often to take the conservative route: remove first, let the courts sort it out later. But that leaves innocent website owners in limbo.
What Should Happen (And Probably Won't, Yet)
The trademark complaint problem needs one of three solutions:
Option 1: A statutory safe harbor for trademarks. Congress could extend DMCA-style protections to trademark complaints, requiring a formal process and giving website owners a counternotice right. This would be the cleanest solution but requires legislative action.
Option 2: UDRP expansion. The Uniform Domain-Name Dispute-Resolution Policy already exists for cybersquatting cases. It could be expanded to cover broader trademark disputes, giving both parties a neutral arbitration process that doesn't involve hosting providers.
Option 3: Hosting provider standards. Industry standards could emerge requiring providers to verify that the complainant actually holds a valid trademark, that it's properly registered, and that there's a genuine conflict before taking action. NameOcean and other responsible registrars could lead here.
What This Means for Your Site
If you own a domain or website that bears any resemblance to a competitor's brand—even if you used it first, even if you're in a different industry—you're potentially vulnerable to a complaint.
Your hosting provider might not investigate deeply. They might not verify the complainant's claims. They might pull the plug to avoid legal risk.
Here's what you should do:
Document everything. Keep records of when you launched your site, when you started using your brand name, and any evidence of continuous operation. This matters for establishing prior use.
Register your own trademark if it's important to your business. This gives you a formal legal position and makes it harder for someone else to claim exclusive rights.
Choose your hosting provider carefully. Ask them about their trademark complaint process. Do they investigate? Do they require court orders? Do they offer a counternotice process? Providers like NameOcean that prioritize transparent policies are worth the trust.
Have a lawyer on speed dial. If your site goes down, you may need to act quickly. A DMCA counternotice has specific timing requirements. Trademark disputes may require an emergency court motion.
The Broader Issue
Gaughan's lawsuit is about more than one developer's hosting account. It's about whether companies can build reliable online businesses when service can be terminated based on unverified claims.
The internet's decentralized nature is supposed to be its strength. But that only works when the rules are clear and fair. Right now, trademark complaints operate in a gray zone—and hosting providers are filling that gap by making their own decisions.
Until Congress acts, trademark law remains a vulnerability for website owners. And hosting providers remain caught between two risks, with no clear safe harbor to guide them.
The question Gaughan's lawsuit raises—what legal framework should hosting providers operate under when they receive trademark complaints?—deserves an answer. Right now, we don't have one. And that's a problem for everyone.