Published

UltaHost's Legal and Regulatory Record

Which courts, dispute panels and regulators have recorded the name Ultahost, Inc., what each record actually says, and which searches came back empty. Every item below is a primary document we read, linked or cited by case number. Most of it is not a finding against UltaHost, and we say which is which, item by item.

1. A Federal Court Schedule That Lists Ultahost, Inc.

TelevisaUnivision, Inc. and Televisa, S. de R.L. de C.V. v. Luis Fermín Gil Alphand, et al.

US District Court, Southern District of Florida · 1:26-cv-23911-KMW · document 40 (report and recommendation) · document 43 (order)

Document 43 states: “Judge Lett's Report (DE 40) is AFFIRMED AND ADOPTED.” Document 40 prints a schedule headed “Third-Party Service Providers — In ‘Active Concert’ Binding (FRCP 65(d)(2))”; document 43 enters an updated Schedule A with the same entries. In both, entry 81 reads:

81 — “Ultahost, Inc.” — “Domain registrar (Roja Directa)”

What this is, and what it is not

  • ● Ultahost, Inc. is not a defendant in this case.
  • ● It is one of more than a hundred third-party providers on the same schedule, alongside providers such as Namecheap, GoDaddy and Cloudflare. Appearing on it is, in our reading, not evidence of wrongdoing by anyone listed.
  • ● The documents record no conduct by Ultahost, Inc. They do not say what, if anything, was requested of it or what it did.
  • ● The restraining order at document 11 does not mention Ultahost, Inc. (we read it as part of this check).

This is the same docket Round 10 reported; it was introduced there as the only federal docket we had found that names the company. See Round 10, section 10.1 for the order's operative language and the other providers on the schedule. Docket: courtlistener.com (1:26-cv-23911).

2. Twelve Domain-Dispute Decisions That Name It as Registrar

The Uniform Domain-Name Dispute-Resolution Policy (UDRP) lets a trademark owner ask a panel to transfer a domain registered in bad faith. A decision names the registrar only because the registrar is the party that confirms who holds the domain. 12 UDRP decisions name Ultahost, Inc. as registrar; in all 12 the panel ordered transfer of the disputed domain to the complainant. Eight were decided by WIPO and four by the Forum (formerly the National Arbitration Forum), between and .

CaseDecidedProviderDisputed domainComplainantOutcome
D2025-24322025-08-05WIPObpce-energeco.comBPCE (FR)Transfer ordered
D2025-20602025-08-19WIPOkinhusblacwell.comHusch Blackwell LLP (US)Transfer ordered
D2025-35902025-11-09WIPOstripetrade.comStripe, Inc. (US)Transfer ordered
D2026-01832026-03-14WIPObelfius-kunden-sec.comBelfius Bank SA/NV (BE)Transfer ordered
D2026-02732026-03-19WIPOuniqacapitalmarkets.comUNIQA Insurance Group AG (AT)Transfer ordered
D2026-12602026-05-21WIPO (French)colissimo.orgLa Poste (FR)Transfer ordered
D2026-17372026-06-19WIPOuniquecapitalmarkets.comUNIQA Insurance Group AG (AT)Transfer ordered
D2026-30562026-08-31WIPObreadfinancialapp.comBread Financial Payments, Inc. (US)Transfer ordered
FA21631452025-07-30Forumteslasharehubs.comTesla, Inc.Transfer ordered
FA21663182025-08-19Forumarculus-pro.comArculus Holdings, L.L.C.Transfer ordered
FA22266102026-07-09Forumacimaleasingapp.comACIMA DIGITAL, LLCTransfer ordered
FA22370052026-09-01Forum8 “roberthalf” domainsRobert Half Inc.Transfer ordered

Source: the 12 decisions as published by WIPO and the Forum, collected 4 Nov 2026. We left the registrants' names out. Two rows share a complainant and a respondent (UNIQA); two rows share a respondent (the two “…app.com” domains).

An example: WIPO D2025-3590, Stripe, Inc. (9 November 2025)

The decision records: “The disputed domain name <stripetrade.com> is registered with Ultahost, Inc. (the ‘Registrar’).” The panel ordered that the domain be transferred to the complainant, Stripe. The respondent did not file a response.

The registrar's part is on the record, and it is routine. WIPO's request for registrar verification went out on 5 September 2025; the decision records that the Registrar transmitted its verification response, disclosing the registrant and contact information, on 6 September 2025, one day later. wipo.int: D2025-3590 (PDF)

What these decisions are, and are not

  • ● The respondent in each case is the registrant of the domain, not Ultahost, Inc. A transfer order is a ruling on that registrant's right to the name. It is not a ruling about the registrar. These are not cases in which Ultahost, Inc. was a party, and nothing in this table is a finding about it.
  • ● Ultahost, Inc. appears because the domain was registered through it. That a domain was registered through UltaHost is not the same as UltaHost having done anything.
  • ● In the Forum cases the registrar's record is a short e-mail confirming the registrant, a standard step.
  • ● The count is a lower bound: it is what the providers' search engines return for the name. See the list of what we could not search below.

3. The One Dispute Where the Respondent Says It Operates as ultahost.com

Ulta Beauty, Inc. v. Doughouz Group / Doughouz Group Ltd

Forum claim number FA2503002147925 (FA2147925) · decision dated · panelist David E. Sorkin · disputed domain ulta-host.com, registered with Tucows Domains Inc.

Ulta Beauty, the US beauty retailer, asked for ulta-host.com to be transferred to it. The respondent, which the decision places in Turkey (the Forum's search index gives Istanbul), filed a response that the panel called noncompliant. The panel recorded the respondent's own statement:

“Respondent states that it operates as ultahost.com, a global web hosting and Internet service provider.”

The panel concluded that “relief shall be DENIED” and ordered that the domain “REMAIN WITH Respondent”. It found the name confusingly similar to the ULTA mark, but held that the complainant had not shown the respondent lacked rights or legitimate interests, nor bad faith. It considered it likely that the respondent registered the name “as a defensive registration aimed at protecting its UltaHost brand and <ultahost.com> domain name”, and wrote that the respondent “has operated what appears to be a legitimate business” under the Ulta Host name for more than five years.

Why this is on the page, and what it does not show

  • ● It is a primary record in which the respondent states, in a proceeding, that it operates as ultahost.com. That statement is the respondent's, as recorded by the panel; the decision does not test it.
  • ● The dispute was about a trademark in a lookalike domain name. It says nothing about abuse handling, phishing, or any customer.
  • ● The respondent won. The panel's view of the business, quoted above, is favourable to it, and we include it for that reason.

Decision: adrforum.com/DomainDecisions/2147925.htm.

4. The ICANN Compliance Entry

ICANN's public compliance-notices page (read 6 November 2026) lists one entry for Ultahost, Inc. (IANA#4331), filed under “Breach”: a notice sent on 5 February 2025. The page then records these steps:

DateWhat ICANN's page records
5 February 2025Notice of Breach to Ultahost, Inc. (IANA#4331) listed on ICANN’s compliance-notices page
7 March 2025Cure period extended until this date
17 April 2025Cure period extended until this date
29 April 2025Cure period extended until this date
9 June 2025Cure period extended until this date
20 March 2026Cure period extended until this date
23 March 2026“Breaches Cured”

The page also shows “Data and Documents Under Review by ICANN” between the extensions. The entry ends with “Breaches Cured 23 March 2026”. It does not record an escalation to termination, which the same page does record for other registrars.

The notice itself is a PDF linked from that page; this section relies only on what the compliance page records. Source: icann.org/compliance/notices. Earlier coverage: Round 10, section 10.5.

5. The UK Company on the Register

Companies House (read 6 November 2026) lists ULTAHOST LTD, company number 14567126, incorporated . Its filing history shows dormant-company accounts filed for all three accounting years to date: to 31 January 2024 (filed 23 September 2024), to 31 January 2025 (filed 9 March 2026) and to 31 January 2026 (filed 7 April 2026).

We draw one narrow conclusion: this company has filed dormant accounts, not trading accounts. We do not know which legal entity operates the hosting service, and we do not claim that this company does. The register gives no answer to that question, and the Forum decision in section 3 is the respondent's own statement rather than a registry record.

Source: Companies House: ULTAHOST LTD (14567126).

6. Searched, Nothing Found

A negative is only worth reporting with its method. For each source below we ran the query and, where one was available, a positive control (a search that must return results, to show the search engine works). A zero without a working control is listed as unchecked, not as clean.

WhereWhat we searched forResult
CourtListener, RECAP (federal dockets and filings)“Ultahost”, “Ultahost, Inc”, “UltaHost Inc”1 case: Televisa v. Gil Alphand (section above). Positive control met. “Ulta Host” and “ultahost.com”: 0.
CourtListener, court opinionsthe same name shapes0 opinions.
WIPO full-text decisions“Ultahost”; “ultahost.com”; “Doughouz”“Ultahost”: 8 decisions (the WIPO rows above). “ultahost.com”: 0. “Doughouz”: 0. Positive control: “Namecheap” returned 5,559 documents.
Forum (National Arbitration Forum), all rule sets including URS“Ultahost”; “Doughouz”; “ultahost.com”“Ultahost”: 5 decisions (the four Forum rows above, plus FA2147925). “Doughouz”: 3. “ultahost.com”: 2. No URS hit. Positive control: “Namecheap” returned 3,960 cases.
CAC (Czech Arbitration Court) UDRP decisions“Ultahost” in text, respondents and domains0, with a working positive control.
UK Find Case Law (National Archives)“ultahost”, “doughouz”, “ultahost limited”, “ulta host”0 results (4 Nov 2026), with a working control on the same endpoint.
Advertising Standards Authority, US Federal Trade Commission, US state attorneys generalUltaHost / Ultahost, Inc.Web-search pass only on 6 Nov 2026, with no positive control: nothing found. That is not a database search and does not exclude a matter.

What we could not search, so cannot call clean

  • ● Lumen (takedown-notice database): blocked to us (bot challenge on the website, an API token needed for the API). Not checked, and not the same as zero.
  • ● ADNDRC and MFSD (other URS providers): not checked.
  • ● WIPO party-name search (as opposed to full-text): not checked; the WIPO count of 8 is the full-text engine's, and a decision that spells the registrar differently would be missed.
  • ● Court records outside what we could reach: CourtListener’s RECAP index holds only what users uploaded, so a zero there does not exclude a case on PACER.

7. How to Read This Record

Across the sources we could search, the name Ultahost, Inc. appears in one federal court schedule as a non-party, in twelve domain disputes as the registrar of a domain that was then transferred, in one dispute as the respondent's stated operating name (which the respondent won), and in one ICANN compliance entry that ends in “Breaches Cured 23 March 2026”. No court or dispute panel we found has ruled against Ultahost, Inc.

That is a thin record, and thin cuts both ways. It does not show that the company is a bad actor, and a short record of its own is not a clean bill of health, because the searches have the limits listed in section 6. The questions about how reports are handled are examined, with dated sources, in the Round 10 and methodology pages.

If you hold a court, regulator or dispute-panel record that names UltaHost and is not here, or a correction to anything above, write to [email protected] (see our corrections policy); we will add it, dated.