Round 8, published

Round 8 Investigation: The Registry Record

August 2026. Seven rounds listened to customers and to UltaHost's own marketing. This one goes to the registries. Almost everything below comes from a primary record: ICANN's own compliance index and monthly registrar files, UK Companies House filings, RIPE's routing database, three threat-intelligence datasets, the free court record, and two pages on UltaHost's own website that sit awkwardly beside one another.

Published alongside a retraction. The same day this round went up, we corrected our own record: a claim that UltaHost was “stonewalling actual lawsuits” had no citation and the court record shows none, two companies we described as registered UK entities do not exist on the UK register, and a birthplace and ethnicity line we had published was uncited and relevant to nothing. Those changes are itemised in the changelog. We mention it here, at the top, because a report about a company that asserts more than it can support has no standing unless it applies the same test to itself.

8.1 They Sell DMCA-Ignored Hosting and Cite RAA 3.18

Start with the two documents that need no interpretation. Both were live on UltaHost's own website on . There is no intermediary, no leak, and no inference; this is the company describing itself, twice, in incompatible registers.

ultahost.com/dmca-ignored-vps

“Fast and Reliable Offshore DMCA Ignored VPS Hosting” (the page headline), then “Protect your data privacy and avoid copyright issues with UltaHost's DMCA Ignored VPS. Enjoy secure, confidential hosting with optimal speed and unlimited bandwidth.”

Page title: “Best Offshore DMCA Ignored VPS Hosting”. Bitcoin appears in the site-wide currency selector.

ultahost.com/abuse-handling-policy

UltaHost's Abuse Handling Policy, as captured on August 8, 2026, stated:

“As an ICANN-accredited registrar, UltaHost strictly adheres to Section 3.18 of the Registrar Accreditation Agreement (RAA), which mandates the timely handling of abuse reports…”

“For cases involving confirmed malicious intent (such as phishing attempts, malware distribution, financial scams, or child exploitation content), the domain will be immediately disabled without prior notice.”

The same captured page promised a reporter a resolution “within 10 days of receipt”. This wording is absent from the policy page as read on November 4, 2026.

Being precise about what this is

We are not alleging that selling DMCA-ignored hosting is illegal, and in our reading it is not, strictly, a contradiction of RAA §3.18: a registrar's obligations over domain abuse are a different duty from a hosting provider's response to a copyright notice. A lawyer for the company could correctly point that out. What the two pages establish is the positioning: the avoidance of copyright enforcement is sold as a product feature, in the page title, while ICANN accreditation is cited as evidence of diligence. Everything in the rest of this report is a test of which of those two documents the infrastructure actually resembles.

8.2 What Is Actually Running on Their Network

UltaHost runs its own autonomous system, AS214036, assigned by RIPE in October 2024. That makes its contents measurable by anyone. We read three public datasets filtered to that ASN.

998
URLhaus entries listed against AS214036's IPs
125 dated before the ASN existed; 873 from 15 Oct 2024 on
9
botnet C2 indicators on 7 addresses (ThreatFox)
all at 100% confidence
2,110
phishing scans (urlscan)
total reported as ≥10,000

The C2 list is the finding that matters, and it is different in kind from phishing volume. ThreatFox lists nine command-and-control indicators, on seven addresses; five of the indicators (on four addresses) are commercial red-team frameworks: Cobalt Strike, Sliver (twice), Brute Ratel C4 and Havoc. These are post-exploitation tools (what an intruder uses after breaching a network). The remainder are XWorm (twice, on one address), AsyncRAT and Bashlite.

[SUPERSEDED Nov 4, 2026] The nine indicators and five frameworks above are the Aug 8, 2026 reading. ThreatFox now lists 1 (the Cobalt Strike server at 192.142.18.214, last seen 10 May 2026). ThreatFox indicators age out of its index after roughly six months, so the fall is not evidence that eight servers were taken down.

One address, two frameworks

192.142.18.214 appears twice in ThreatFox, carrying two different commercial intrusion frameworks ten months apart. ThreatFox records the nine indicators as first seen between 15 April 2025 and 23 March 2026.

Where this evidence is weaker than it looks

  • ● The trend is down, not up. URLhaus volume peaked in 2025 (528 URLs) and stands at 79 in 2026. We are not claiming an escalation. Anyone citing the 998 total should know that it counts URLhaus entries listed against AS214036's addresses; 125 of them are dated before the ASN was assigned on 15 October 2024 (37 in 2022, 11 in 2023, 77 in 2024) and 873 date from that day on.
  • ● Most of it is botnet noise. Only 54 of the 998 carry Windows-crimeware tags; the bulk are tagged Mirai or Gafgyt (IoT botnet malware).
  • ● 10,000 is a cap, not a count. urlscan's unfiltered total for the ASN is reported here as at least 10,000 because that is where anonymous results stop.
  • ● And a negative we went looking for. AS214036 is not on the Spamhaus ASN-DROP list. We checked, and we publish it.
  • ● No comparison group. We did not measure other hosts' ASNs. Nothing here says UltaHost is worse than its peers on these metrics, only what is on its network. Its abuse policy describes immediate disabling of domains in cases of confirmed malicious intent.

8.3 The Stronger Signal: Their Own cPanel Plane

Sharing an autonomous system proves little on its own. Any large network has customers it never meets, and “bad thing found on big network” is a weak argument that could be made about almost any host. So we went one layer deeper, to reverse DNS.

A number of domains scanned on urlscan, many carrying phishing or fraud tags, resolve to hostnames like cp11.ams1.ultacp.com and cp5.fra1.ultacp.com. That is not merely UltaHost address space. It is UltaHost's own managed cPanel shared-hosting control plane, the product a paying customer is given a login to. Across 78 submissions we found 20 distinct domains, several scanned the same week we looked.

ClusterDomainsOn
Crypto-presale domains whose names include financial-media brand namesspx40k-fxempire.com · spxpresale-cryptoslate.com · gro24h-cointelegraph.com · gro24h-cryptoslate.com · spx40k.comcp11.ams1
Bank-named domains (scanner tags: advance fee fraud / phishing)theroyalbankgroup.com · stridesglobalbk.onlinecp11.ams1
Chemical-supplier-named domains (scanner tags: advance fee fraud, drug)labchems.org · usalabchems.comcp11.ams1
Adobe- and AliExpress-named domains (flagged phishing by VirusTotal vendors)adobeviewer.com · adobe-docviewer.com · adob-viewer.com · aliexpressboost.comcp11.ams1
Other phishing / fraud tagged by scannersguia-gasescol.com · bright-tether.com · viounavtr.com · startcryptoworld.com · impactboxesau.comcp3.fra1 / cp11.ams1

Why the Adobe cluster is the sharpest of these

A Trustpilot reviewer wrote that UltaHost's LinkedIn representative told them it does not investigate abuse unless they submit a trademark complaint or court order (see our case study). Separately, three Adobe-named domains and an AliExpress-named domain, all flagged by VirusTotal vendors, are on one of its own cPanel servers. The company's own abuse policy, as captured on August 8, 2026 and quoted in 8.1, stated that in cases involving “confirmed malicious intent (such as phishing attempts, malware distribution, financial scams, or child exploitation content)” the domain “will be immediately disabled without prior notice”. That wording is absent from the policy page as read on November 4, 2026.

Limits. A urlscan tag is a scanner's classification, not a court's. We are reporting what the scan records and the PTR records show, not what UltaHost knew, nor when. Several of these were scanned within days of our reading, so we cannot say how long they had been live, and a fast suspension after our snapshot would not be visible to us.

8.4 Gambling-Style Domain Names on One IP, With Infrastructure Evidence

ultahost.com/terms: prohibited uses

“Promote gambling, casinos, gaming, sports betting, daily fantasy sports, lottery or chain letters regardless of content or origin and regardless of your citizenship or the legality of such activities within your country.”

A reverse-IP lookup on 84.200.154.40 returns 290 hostnames. Shared cPanel hosting generates several hostnames per site (www, mail, webmail…), so a hostname count overstates the number of actual sites. Deduplicated to registrable domains, it is 120 distinct domains. Of those, 28 carry an explicit gambling term or Indonesian gambling marker in the name; the other 92 follow a letters-plus-digits shape common to slot brands, which we count separately because the shape alone proves nothing (we did not open the sites).

28
explicit markers
92
letters-plus-digits name shape (no explicit gambling term)
0
left unclassified by name

The explicit set includes bo999slot.com, maxbet111.com, sbo222slot.net, winbet178.com and the 4D series (uranus4d.net, judo4d.org, dna4d.com), “4D” being, as we understand it, a common Indonesian lottery format. The remaining 92 follow the recognisable slot-brand convention of a short word plus two or three digits: angka169.com, hoki818.com, dewa268.com, gemoy666.com.

The same IP served credential-stealing malware

On , URLhaus recorded AgentTesla being served from lion44.net/wp-includes/theme-compat/…, a path (wp-includes) that suggests a WordPress installation, on a domain on that address. In our reading, this shows how a shared address with many sites can end up serving malware whether or not anyone intended it.

Gambling domains also sit directly on the managed cPanel plane described in 8.3: 1xbet-ir.app and 1xbet-iran.app (1xBet-style names, apparently aimed at Iran), zigzagbonus.bet, pinupcasinorussia.click, 1035holiganbet.com, and three ganobet variants.

Our own method, including a mistake we made

Co-tenancy shows what shares an address, not who owns the content, and we make no claim that UltaHost knows about any specific domain. The claim is narrower: on one address of its own shared hosting, 28 of 120 domain names carry an explicit gambling term and the other 92 share a letters-plus-digits shape, and we did not open the sites to confirm what they carry.

Our first classification pass undercounted. It required a word boundary before “slot”, which silently missed bo999slot and capital365slot; it had no rule for the 4D lottery convention at all; and it ignored .org. We found this by reading the domains the classifier had rejected and noticing they were gambling sites too. The corrected classifier prints its residual so the 28-and-92 split can be checked rather than trusted, and the reverse-IP service caps at 500 hostnames, so where we report 500 elsewhere, that is a floor and not a total.

8.5 The Registrar Record, From ICANN's Own Files

This site has reported the ICANN breach since Round 1. Reading ICANN's compliance index directly gives the full sequence for the first time, and it is longer than we had published.

The breach chain, as ICANN records it

  • ● 5 February 2025: Notice of Breach issued
  • ○ “Cure Period Extended Until 7 March 2025”
  • ○ “Cure Period Extended Until 17 April 2025”
  • ○ “Cure Period Extended Until 29 April 2025”
  • ○ “Cure Period Extended Until 9 June 2025”
  • ○ “Cure Period Extended Until 20 March 2026”
  • ● 23 March 2026: “Breaches Cured”

DomainNameWire reported that ICANN's notice gave Ultahost 21 days to cure. From the Notice of Breach to “Breaches Cured” is 411 days (about 13.5 months), with 5 separate cure-period extensions recorded in between.

Two honest readings of that follow, and we will give both. Granting extensions is within ICANN's discretion and is not misconduct by either party; the chain is evidence about ICANN's enforcement posture as much as about UltaHost. And “cured” is narrower than it sounds: it refers to the contractual points in the notice, which DomainNameWire summarised as abuse-request handling, records on request, RDAP, escrow deposits and website disclosures. It is a finding about process, not about abuse levels, which the compliance index does not address.

The registrar's own monthly numbers

ICANN publishes a transaction report for every accredited registrar, every month. Filtering 19 months of the .com files to IANA ID 4331 produces two series, shown below.

Month.com under managementDeleted outside the add grace period [CORRECTED Nov 4, 2026: ICANN's field deleted-domains-nograce = deleted outside the add grace period, expiry purges included]
Oct 202400
Apr 20259,4370
Oct 202521,03833
Dec 202522,9530
Jan 202623,669332
Feb 202623,8691,399
Mar 202624,3781,283
Apr 202625,1791,032

[CORRECTED Nov 4, 2026] The “registrar-initiated removal” reading of the second column is withdrawn, and the paragraph that carried it has been deleted. ICANN defines this field as deletions outside the add grace period, which includes ordinary expiry purges. The figures in the table are unchanged; see the corrected incident record and the Nov 4, 2026 entry in the changelog.

What we are not claiming

[CORRECTED Nov 4, 2026: two sentences that placed these deletion counts beside the cure process are removed; under the corrected field definition the pairing is not supported.] ICANN's files give no reason for any deletion. [WITHDRAWN Nov 4, 2026: a sentence that assumed the deletions were bulk removals is deleted; the corrected field definition does not support it.] We do not assert causation, and no reader should infer it from the dates alone.

8.6 The UK Company Is Dormant

UltaHost's own terms of service extend the agreement across “UltaHost Dubai, UltaHost Istanbul, UltaHost Ltd UK, and UltaHost Inc USA” (as captured on 8 August 2026). In our reading, one of those four corresponds to an entry on a register we can read in full (we do not know whether ULTAHOST LTD is the entity the Terms mean), and what that entry says is that it has filed dormant accounts.

A dormant company, in UK law, is one that has had no significant accounting transactions in the financial year. ULTAHOST LTD (Companies House 14567126) has filed dormant accounts three years running: for the periods ended 31 January 2024, 31 January 2025 and 31 January 2026, the last of them filed on 7 April 2026.

The rest of the filing

  • ● Sole director and company secretary: two officer appointments under the same name
  • ● 75–100% of shares, of voting rights, and of the right to appoint and remove directors
  • ● Resident in Turkey; date of birth recorded as January 1992
  • ● Identity verified under the Economic Crime and Corporate Transparency Act on 21 November 2025
  • ● 0 other UK appointments for either appointment
  • ● No insolvency history and no registered charges; accounts shown as not overdue on the register when read (the accounts for the period ended 31 January 2025 were filed on 9 March 2026)

An inference we refuse to draw

The registered office is 71-75 Shelton Street, Covent Garden, an address widely used as a company registered office (we have not counted the companies registered there). “N companies registered at the same address as UltaHost” is therefore weak evidence, and we will not make that argument even though it would be the easiest paragraph in this report to write.

The only structurally valid test is officer-sharing: whether this director appears on the filings of other companies. We ran it, and it returns nothing. There is likewise no UK-registered ScriptSun, WoWonder, Wolvor or Doughouz company. We previously described two of those as “Ltd” entities on this site and have retracted it. If a wider corporate group exists, it is not visible on the UK register, and we are not going to imply one from a shared mailbox.

8.7 A Sitejabber Notice, and a Trustpilot Warning Reported Second-Hand

Round 7 measured how the headline rating is assembled. The point worth restating in a report about the registry record is simpler: one review platform displays a notice on UltaHost's profile (Sitejabber, read 13 October 2026), and a Reddit commenter reported a Trustpilot one that we could not re-locate. Neither notice is our characterisation.

Trustpilot, as quoted by a Reddit commenter (May 2025)

A Reddit commenter in May 2025 quoted a Trustpilot warning on UltaHost's profile: “We've detected and removed a number of fake reviews for this company.” (comment not re-located on 4 Nov 2026)

Our own capture of Trustpilot's ultahost.com profile on 20 August 2026 records no platform warning, so this card is second-hand and not corroborated by a Trustpilot page we hold.

Sitejabber

“Ultahost has been reported to offer discounts, coupons, or other compensation in exchange for reviews.” (Sitejabber profile notice, read 13 October 2026)

[UPDATED Nov 4, 2026: the Trustpilot card now rests on a May 2025 Reddit comment; no Trustpilot capture of the January 2025 profile is held. The Sitejabber notice was read on 13 Oct 2026 (after this round's 8 Aug date).]

8.8 Reply Rates Where They Are Displayed

This is the pattern that ties the report together, and it is visible in three places at once.

ChannelPublicly scored?Observed responsiveness
Trustpilot reviewsYes: reply rate is displayedEvery one of 200 sampled reviews carried a company reply
BBB complaintsYes, but only in the letter gradeBBB lists a failure to respond to 1 complaint (6 complaints in the last three years, none in the last 12 months; 5 marked unpursuable, unable to locate the business); the grade is C- (read 4 Nov 2026)
Abuse reportsNoA Trustpilot reviewer reports being told a trademark complaint or court order was required

A disclosure that cuts against us

The BBB letter grade is BBB's own rating and is not a measure of customer sentiment overall. We found no customer-review scores on the BBB page when we read it on 4 Nov 2026, so we draw no conclusion from reviews there.

8.9 Litigation: No Case Naming UltaHost as a Party in the Free Record

We searched for court cases naming UltaHost as a party and found none, and we are giving that the same prominence we would have given a hit. Sixteen queries against CourtListener v4 (“Ultahost”, “Ultahost, Inc”, “ScriptSun”, “WoWonder”, “Doughous”) across opinions, dockets and full document text returned zero. The UK's Find Case Law archive returned zero. Companies House shows no insolvency and no strike-off action. [CORRECTED Nov 4, 2026: Round 10 (Aug 24, 2026) found one federal docket that this search missed because the queries used the comma form “Ultahost, Inc”: TelevisaUnivision v. Gil Alphand (S.D. Fla. 1:26-cv-23911), in which Ultahost, Inc. appears only in the schedule of third-party providers. UltaHost is not a defendant. See 10.1.]

We had this wrong, and we have corrected it

Until this week, this site's homepage stated that UltaHost was “stonewalling actual lawsuits filed against the company”. No citation existed for it anywhere on the site, and the search above finds no such lawsuits. That claim is retracted. What survives is narrower: a WebHostingTalk poster wrote in January 2025 that, after cancelling through their credit-card company and getting a refund, they received a threat from UltaHost (“Lawyer, lawsuit, that kind of thing”). We have not verified the account.

Why this is “nothing found”, not “nothing exists”

  • ● RECAP is a large sample, not a census. It holds only those US federal dockets somebody has already paid to retrieve.
  • ● BAILII was not checked. It blocks automated retrieval and we did not work around it.
  • ● Turkey (where Companies House records the sole director of ULTAHOST LTD as resident) and the UAE (where the Terms, as captured on 8 Aug 2026, named a Dubai entity): we did not search Turkish or UAE court records.
  • ● A dispute settled privately, or filed in a US state court, leaves no trace in any of the above.

A same-surname warning, published so nobody else misuses it

Searching the surname in US dockets returns five results. We attribute none of them to anyone. Three are bankruptcy filings bearing the surname. Two were filed in 1996 and 2002, when a person born in January 1992 was four and ten years old, which rules them out arithmetically. A third, filed in 2025, shares a surname and nothing else we can establish. The other two are dockets of unrelated parties in which the search string merely appears. We mention them only because they are the first thing a careless search surfaces, and we would rather rule them out here than see them repeated as findings about this company.

8.10 The People Behind It

This section is now built on the statutory record rather than on data brokers, and it is shorter than it used to be as a result.

Elin Doughouz (spelled “Doughous” on the register): what a register actually says

  • ● Sole director and sole company secretary of ULTAHOST LTD, appointed 3 January 2023: Companies House lists two officer appointments under the same name
  • ● Person with significant control: 75–100% of shares, votes, and the right to appoint and remove directors
  • ● Resident in Turkey, date of birth January 1992
  • ● Identity verified under ECCTA on 21 November 2025
  • ● The Companies House record spells the surname “Doughous”, and the PDF of ICANN's breach notice is filed on ICANN's site under a name that reads “hedlund-to-doughous…” (the addressee is redacted inside the document); Crunchbase's spelling is “Doughouz”. The split matters, because searching only one form returns a false negative

Deen Doughouz is listed as a founder alongside Elin Doughouz on Crunchbase's Doughouz Group profile (Wayback snapshot of 27 April 2022). Crunchbase is self-reported and this rests on that single source, so we label it that way rather than presenting it as established. He holds no appointment at ULTAHOST LTD on the UK register. The frequently repeated “three brothers” framing is not something we can source to a record, so we say “founders per Crunchbase” instead.

Two things we removed, and why

This site previously published a birthplace and an ethnicity for the CEO. Neither carried a citation, and neither bears on a single claim in any of these eight rounds, so both are gone. We also previously gave a date of birth of “January 1, 1992”; the 1st of January is a well-known filler value in commercial people-data records, and the statutory register gives month precision only. It now reads January 1992. We do not publish the director's residential address, which is a matter of public record but is a different act from reporting a directorship. Accountability journalism about a company is not a licence to publish everything discoverable about the people who run it.

8.11 Unverified Leads, Labelled as Such

These are the most quotable items we found and the least proven. They are published as open questions, and nobody should cite them as findings — including us, in a later round, without doing the work first.

Unverified

A company-run subreddit

r/UltaHostHub appears to be operated by the company: both posts we captured there were made by the account u/UltaHost_, the account that replies as “UltaHost” elsewhere on Reddit.

Ruled out

A false positive we are pre-empting

A widely-linked forum thread about an “ultahost[.]gl virus” concerns a CountLoader infection on a different domain with a different TLD, unconnected to this hosting company. It is not evidence about UltaHost, and we are saying so here because it is exactly the sort of thing that gets used to discredit an entire report.

8.12 Verify It Yourself — And Our Method

Every figure in this round comes from a record you can open without an account, with one exception noted below. Every one of these is free; only Companies House needs an account, and its key costs nothing.

SourceWhat we took from itWhere
ICANN compliance noticesBreach notice, five cure extensions, cure dateicann.org/compliance/notices
ICANN monthly registrar reports.com under management + the deleted-domains-nograce field (deletions outside the add grace period), IANA ID 4331icann.org/sites/default/files/mrr/com/
IANA registrar IDsAccreditation status for ID 4331iana.org/assignments/registrar-ids/
UK Companies HouseDormant filings, officers, PSC, other appointmentscompanies house: company 14567126
RIPE RDAPAS214036 registration, maintainer, abuse contactrdap.db.ripe.net/autnum/214036
RIPEstatAS214036 announced prefixes and neighboursstat.ripe.net (announced-prefixes)
abuse.ch URLhausMalware URLs on the ASN, with dates and tagsurlhaus.abuse.ch/feeds/asn/214036/
abuse.ch ThreatFoxBotnet C2 servers on the ASNthreatfox.abuse.ch/browse/tag/AS214036/
urlscan.ioPhishing scans + reverse DNS of scanned pagesurlscan.io (page.asn:AS214036)
HackerTarget reverse IPCo-tenant hostnames on 84.200.154.40api.hackertarget.com/reverseiplookup/
CourtListener v4US litigation record (0 cases naming UltaHost as a party on 8 Aug 2026; see 8.9 for the docket found later)courtlistener.com (“Ultahost”)
Find Case Law (UK)UK judgment record (0 results)caselaw.nationalarchives.gov.uk
UltaHost: DMCA Ignored VPSThe offshore product page quoted in 8.1ultahost.com/dmca-ignored-vps
UltaHost — Abuse Handling PolicyThe RAA §3.18 and suspension quotes in 8.1ultahost.com/abuse-handling-policy
UltaHost: Terms of ServiceThe gambling prohibition quoted in 8.4ultahost.com/terms

Method, including its limits

  • ● Retrieval. Everything above was read directly over HTTP on –, with no commercial scraping service involved. Companies House needs a free API key; the other ten need nothing. The scripts that did the reading are in the site's repository, and the figures on this page are printed by one of them rather than typed by hand.
  • ● Sample limits. The ICANN monthly reports cover 19 months to April 2026 (the latest published when we read them), so the .com and deletion figures are four months old by construction. The reverse-IP service caps at 500 hostnames, and urlscan's anonymous search caps at 10,000 results; where a figure sits at a cap we report it as a floor.
  • ● What we could not reach. Delaware's entity register is CAPTCHA-walled and publishes no officers. BAILII blocks automated reads. We did not search Turkish or UAE court records. AbuseIPDB's per-prefix check across all 86 prefixes was not completed. We report these as gaps rather than filling them with inference.
  • ● No comparison group. We measured no other hosting company's ASN, register or abuse record. Nothing here is a claim that UltaHost is worse than its competitors on any of these metrics. Every finding is an absolute comparison against UltaHost's own published terms, policies and marketing.
  • ● Search is circular here, so we avoided it. Search results can be circular for a subject like this, since pages may quote this site's own figures back, so we avoided search snippets as corroboration. Nothing in this round is corroborated from a search snippet; every number traces to a named primary record.
  • ● Archiving. We submitted the URLs cited here to the Internet Archive so the claims stay checkable if the originals change. Expect UltaHost's own product and policy pages to be the ones most likely to move; we retain dated local copies of all four pages we quote, and the verbatim quotes in 8.1 and 8.4 were checked as exact substrings of those stored copies before publication.

8.13 Editor's Conclusion

Seven rounds asked whether UltaHost treats its customers badly. Round 8 asks a different question (what the primary records show about the business) and sets out what they do and do not say.

A company whose product page offers “Offshore DMCA Ignored VPS Hosting” so that buyers can “avoid copyright issues”, and whose abuse-policy page cites its ICANN accreditation and RAA §3.18. An autonomous system on whose addresses ThreatFox listed nine command-and-control indicators (on seven addresses) on Aug 8, 2026 (since superseded, see 8.2), five of the indicators for commercial red-team intrusion frameworks. Twenty domains seen in scans of its own managed cPanel servers, thirteen of them carrying scanner phishing, scam or fraud tags, and separately three Adobe-named domains flagged by VirusTotal vendors; a Trustpilot reviewer says UltaHost's LinkedIn representative told them it requires a trademark complaint before it will investigate. An IP address where 28 of 120 domain names carry an explicit gambling term (the other 92 share a letters-plus-digits shape), while UltaHost's terms prohibit promoting gambling “regardless of your citizenship or the legality of such activities within your country”; URLhaus recorded AgentTesla, a credential-stealing malware, served from one of those 120 domains (lion44.net) on August 5, 2026. Thirteen and a half months between ICANN's Notice of Breach and “Breaches Cured”, across five cure-period extensions. And ULTAHOST LTD, a UK company whose name matches one of four entities UltaHost's Terms listed when captured on 8 Aug 2026 (the 4 Nov 2026 Terms name only UltaHost Inc USA), which has filed dormant accounts with Companies House three years in a row.

Now the limits, because they are real and this report is worth less without them. The malware trend on the network is down, not up. Most of the URL volume is undifferentiated botnet noise. Co-tenancy shows what shares an address, never who owns it, and we cannot show what UltaHost knew about any specific domain or when. [CORRECTED Nov 4, 2026: a sentence here about a deletion “spike” beside the cure window is removed; the figure is a count of deletions outside the add grace period, which includes ordinary expiry purges; see 8.5.] The company is not on Spamhaus's drop list. There is no litigation against it in the records we searched (see the Nov 4, 2026 note in 8.9 on one federal docket where it is listed only as a third party). Its UK accounts are shown as not overdue on the register when read (the accounts for the period ended 31 January 2025 were filed on 9 March 2026). And a structural allegation about a wider corporate group is one we could not substantiate and are therefore not making: the officer-sharing test returns nothing, and a shared mail-forwarding address is not evidence of anything at all.

What is left after all of that subtraction is still the finding. Nothing here requires a leak, an insider, or a theory of intent. It is a company's own product pages, its own terms of service, ICANN's compliance index and the routing registries' data, read in order — and in our reading, read in order, they describe a business whose stated policies and actual infrastructure do not sit comfortably together.