Round 11: What UltaHost Tells Abuse Reporters
November 2026. Earlier rounds measured what UltaHost registers and hosts. This round asks a narrower question: what does the company say to people who report abuse, what does its own published policy promise, and what do the public records show about the domains that were reported? It also sets out the evidence that cuts the other way, and what we cannot establish.
11.1 What UltaHost Tells Reporters, in Its Own Public Replies
UltaHost answers Trustpilot reviews in public. We collected 851 reviews of ultahost.com (read on 5 and 6 November 2026), 843 of which carry a public reply from the company. Eight of those replies, all to 1-star reviews, speak to who may report or what documents are needed. They are quoted below word for word, with the date of the reply and a link to the review. What the reviewer says happened is the reviewer's account; we have not verified it and we do not know what UltaHost did with any individual report.
Six replies: abuse is acted on from organisations or authorities
The wording differs from reply to reply (“verified entities”, “recognized organizations”, “recognized vendors”, “the appropriate authority”), so we describe a pattern in how the replies are worded rather than one rule. None of the six says which organisations or authorities qualify.
“Please note we can't simply suspend a server due to an Abuse Report sent by an individual without any evidence.”
“We only process legitimate abuse reports from verified entities or relevant organizations.”
Reviewer's account (not verified by us): The reviewer describes a report about “ponzi hyip phishing” and pastes a message they say they received; see the box on personal email below.
“Kindly note we only respond to issues of Abuse from recognized vendors. Please reach out to appropriate authority to contact us and we will take action.”
Reviewer's account (not verified by us): The reviewer writes: “Absolutely no help with letting one of your hosted sites continue to steal my content.”
“we do not take action on abuse unless received from the appropriate authority, this is done to protect our customers from malicious report from competitors/malicious actors.”
Reviewer's account (not verified by us): The reviewer writes that they contacted UltaHost “numerous times about copyrighted content on their servers”.
“Kindly note we do not take action on abuse unless instructions are received from an appropriate authority.”
Reviewer's account (not verified by us): The reviewer writes that they submitted an abuse report and that the response was “Kick rocks since you used a Gmail account to submit the report”. That wording is the reviewer's paraphrase; it is not in the reply shown.
“Kindly note we only take action on Abuse from the appropriate authorities. We request you contact them with the facts and they will reach out to us to take action.”
Reviewer's account (not verified by us): The review text reads, in full, “NOT RESPONSIF”.
“Kindly note we only take action from recognized organizations on abuse”
“We recommend you reach out to them to contact us through appropriate channels to take action”
Reviewer's account (not verified by us): The reviewer says ten sites impersonating their business were involved, that they emailed UltaHost's abuse address each time, and that “The most recent take down took them 11 days to resolve despite all of the screenshots/evidence being provided.”
Two further replies: legal documents and evidence
“issues related to trademark infringement or impersonation require proper legal documentation.”
“we kindly ask you to provide a court order or relevant legal documentation.”
Reviewer's account (not verified by us): The reviewer says a site impersonating their brand was being hosted, and that a representative told them on LinkedIn that UltaHost does not investigate abuse unless they submit “a trademark or court order”. This is the only one of the 843 replies we collected that mentions a court order.
“we can't take action on a DMCA report sent by an induvial [sic] without proper evidence and documentation for copyright.”
“If you have any evidence then please share with us to check and take action.”
Reviewer's account (not verified by us): The reviewer writes: “The fake site impersonating our brand is still active, I really don't see any action around my request”. This reply is a DMCA template that invites evidence; we do not read it as a flat refusal.
The Gmail / personal-email rule is not in any UltaHost reply we collected
A rule that reports from personal email accounts are refused circulates among reviewers. It appears in none of the 843 UltaHost replies. It appears only in reviewers' own text: the reviewer of 688c7f1d pasted a message they present as a rejection, which reads in part “we are unable to process or act upon abuse reports submitted from personal email addresses such as Gmail, Outlook, Hotmail, or similar services”, and the reviewer of 690528ad paraphrased the response they received as quoted in the card above. We cannot tell from the review pages whether either wording came from UltaHost, so we attribute the rule to the reviewers only.
A related note: the court-order wording in review 69eae235 is the reviewer's; the reply to that review is about server access, and we do not cite it as evidence of a court-order requirement.
What this does and does not show
- ● Six of 843 collected replies make the organisation-or-authority point, all written between 13 August 2025 and 7 January 2026. Two more (7 February and 15 August 2025) ask for legal documentation or evidence. A text search of the other 835 found no further statement about who may report; one of them, a second DMCA template reply of 15 August 2025, repeats the evidence wording quoted above and is not shown separately. Section 11.5 quotes other replies in which UltaHost describes acting on abuse reports.
- ● The 851 reviews are the ones we collected, not necessarily every review on the profile.
- ● These are replies by support staff to reviewers. They state a position; they do not show how any particular report was handled.
- ● One reply (7 February 2025) asks for a court order. The policy section below shows that the published policy, as read on 6 November 2026, does not require one for phishing or impersonation.
11.2 What the Published Policy Says: Then and Now
UltaHost publishes an Abuse Handling Policy. We hold a capture of it from 8 August 2026, and the Wayback Machine holds captures from 15 October 2025 and 15 July 2026 with the same sentence. We read the live page again on 6 November 2026. The page we read carries no revision date.
| Topic | Then (8 Aug 2026 capture; same in Wayback 15 Oct 2025 and 15 Jul 2026) | Now (page read 6 Nov 2026) |
|---|---|---|
| Reply to the reporter | Under both “Whois Inaccuracy” and “Phishing/419 Scam”: “A response outlining the resolution of the report will be provided to the reporter within 10 days of receipt.” | No 10-day text. Section 4: “We confirm receipt and track the report.” and “We provide decisions, reasons and available remedies where required by law. Otherwise, we provide appropriate updates when practicable.” |
| Trademark and disputed claims | Rights holders are encouraged “to seek resolution through established mechanisms such as the Uniform Domain Name Dispute Resolution Policy (UDRP) or the Uniform Rapid Suspension System (URS)”. | Section 2: “Disputed civil claims may require determination by a court or an appropriate dispute-resolution provider.” |
| Court orders | Not required for phishing reports in the text we hold. | Listed among details a reporter may include, with other items: “relevant court order or official case reference”. Not stated as a requirement. |
| Who may report | No organisation-only requirement in the text we hold. | Asks for “authority to act for a rights holder or organization, where applicable”. The policy does not say reports must come from organisations. |
| Speed and intent | Shorter deadlines in the older text sit under “Content Violation” (copyright), not phishing. | Section 5: “Where actionable evidence establishes DNS Abuse involving a domain we sponsor, we act promptly to interrupt the abusive use.” Section 4: “We do not require proof of a customer's malicious intent before addressing an active threat.” |
Three things to keep straight
- ● When and why it changed is unknown to us. The rewrite falls between our 8 August 2026 capture and our 6 November 2026 read; the latest Wayback capture we found is 15 July 2026. We do not know the date of the change or the reason for it.
- ● The “twenty-four hours” line is not a promise to ordinary reporters. It sits in section 12, which deals with requests from governments and law enforcement, and we do not read it as a response time for a member of the public.
- ● The new text does not say a numeric deadline was dropped. We are comparing two versions of a page. A reader who sent a report while the 10-day sentence was on the page can compare their own record with it; we make no finding about any particular report.
The dated incident entry records this change with its sources.
11.3 What Happens to Reported Domains and URLs
Apart from its last subsection, this section is about UltaHost's registrar role (Ultahost, Inc., IANA 4331). A domain registered through UltaHost is not a domain UltaHost did anything to, and a registry status says nothing about who asked for it. The last subsection covers the hosting role (AS214036), which is measured separately.
The registry record, 6 November 2026
PhishDestroy lists domains it attributes to Ultahost, Inc. as registrar. We took the 932 apex .com and .net names on that list and looked each one up in the registry's RDAP service on 6 November 2026.
| Registry state | Names | Share of 932 |
|---|---|---|
| Active, no registry hold | 481 | 51.6% |
| clientHold | 223 | 23.9% |
| Redemption period or pendingDelete | 56 | 6.0% |
| Not in the registry (RDAP returns not found) | 172 | 18.5% |
Of the 481 active names with no hold, 421 still resolved in DNS when we checked. We cannot tell from a registry record why a name carries a hold, is in redemption or has left the registry: a complaint, non-renewal and a dispute decision can all produce the same status. The list is PhishDestroy's, not a random sample of UltaHost names, and it covers names added over many months, so recently added names have had less time to change state.
PhishDestroy's own time-to-unavailability figure
PhishDestroy's per-domain pages show a “Time to First Unavailability”, defined on the page as the “Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.” We read 100 randomly chosen pages. Forty-five show a report sent to an UltaHost address (abuse@ or [email protected]). Fifteen of those 45 carry a time: the median is about 378 hours (about 16 days) and the range is 6 hours to 2,694 hours. Fifteen pages is a small sample, PhishDestroy is both the reporter and the measurer, and the figure does not show that UltaHost caused any of the outcomes.
Where UltaHost sits in Interisle's registrar phishing tables is set out on its own page: UltaHost in Interisle's Registrar Phishing Tables. That is a different dataset from PhishDestroy's, and the two are not combined.
Hosting role: 6 of 897 recorded URLs were online (feed generated 3 Nov 2026)
This is the hosting role (AS214036), not the registrar role. URLhaus's feed for AS214036, generated on 3 November 2026 at 23:43 UTC (read 4 November), lists 897 URLs, of which 6 (0.67%) were online; a second pull at 14:07 UTC on 4 November showed 899 URLs, 8 of them online (0.89%). On the same feed type, 5 of 54,004 URLs (0.009%) were online for DigitalOcean and 107 of 72,142 (0.15%) for Amazon. By share, the figure for UltaHost's AS214036 is higher than both. The networks differ greatly in size and coverage, and URLhaus counts what it has recorded, not all abuse, so these shares are a rough comparison and not a ranking. AS214036 also does not appear in the hosting-network top-20 tables of the Interisle / Cybercrime Information Center reports we read; those tables list only the top 20, so absence is not a zero.
11.4 Our Own Reports
Abuse reports sent to UltaHost by the owner of this site and by another reporter received no reply. Copies of those reports, with dates and delivery details, are held by this site and can be provided to a regulator, court or journalist on request; they are not published, to protect the reporters from further harassment.
We do not state whether these reports concerned a domain registered through UltaHost or a service it hosts. This is a first-party statement. Two reporters are not a sample, and we draw no general conclusion from them about how UltaHost handles reports from others.
What the two texts say
- ● UltaHost's published policy, as read on 6 November 2026, section 4: “We confirm receipt and track the report.”
- ● ICANN's Registrar Accreditation Agreement, as amended 5 April 2024, section 3.18.1: “Upon receipt of such reports, Registrar shall provide the reporter with confirmation that it has received the report.” Section 3.18.2 separately requires a registrar with actionable evidence of DNS Abuse to “promptly take the appropriate mitigation action(s)” (see the amendment text).
These are the registrar-role texts only (Ultahost, Inc., IANA 4331). We set them beside our statement and make no finding on compliance: whether a registrar has met its agreement is for ICANN to decide. The 24-hour review in section 3.18.3 applies to reports from law enforcement, consumer-protection and similar authorities, which is consistent with our reading of the 24-hour line in UltaHost's policy in 11.2.
11.5 Evidence That Cuts the Other Way
A round that only collected the unflattering material would be a one-sided file. These are the findings that point the other way.
Many listed names are no longer active
Of the 932 names, 223 (23.9%) were on clientHold on 6 November 2026, 56 (6.0%) were in redemption or pendingDelete, and 172 (18.5%) were no longer in the registry. Together that is 451 names (48.4%) that were not in the active, no-hold state. As 11.3 says, the registry record does not show why.
Hosting role: a reviewer says a takedown happened
The reviewer of 695dd9b1 says the most recent takedown took 11 days, which is also a statement that a site came down. That is the reviewer's account, not a figure we measured.
Registrar role: UDRP verifications were answered
In WIPO case D2025-3590 (stripetrade.com, decision of 9 November 2025), the Center requested registrar verification on 5 September 2025 and the registrar transmitted its response on 6 September 2025, within a day; the domain was transferred to the complainant, Stripe, Inc. Twelve UDRP decisions name Ultahost, Inc. as registrar and in all twelve the panel ordered transfer; see UltaHost's Legal and Regulatory Record.
UltaHost's other public replies about abuse
Not every reply in the collection is about who may report. In these five, written between September 2025 and July 2026, UltaHost says it acts on abuse reports. Each is quoted word for word with the date of the reply. They are UltaHost's statements to reviewers; where a reply describes a specific suspension, it gives UltaHost's account, which we have not verified.
“We do not encourage infringing activity, however, we offer offshore hosting, besides this.”
“we take action on all cases of abuse.”
Reviewer's account (not verified by us): The reviewer writes: “Reported infringing activity, instead of taking action against the infringers, Ultahost is encouraging them and piracy activity is unchecked.”
“Please note your server was reported for Phishing by multiple authorized agencies and we have zero tolerance policy for Phishing on our Network so your server was suspended and all details were shared with you via Abuse Report.”
Reviewer's account (not verified by us): The reviewer says their account “was suddenly suspended for a complex technical reason I never fully understood” and disputes a billing charge. The reply is UltaHost's account of why the server was suspended; we have not verified it. Trustpilot shows the reply as updated on 29 Nov 2025.
“The service was suspended after our Abuse Team received and investigated reports indicating that the website was involved in a phishing and fraudulent investment campaign.”
Reviewer's account (not verified by us): The review text reads, in full, “Trash your hosting server is trash”. The reply is UltaHost's account of why the service was suspended; we have not verified it.
“Whenever credible abuse reports are received, our Abuse Team investigates them promptly and takes appropriate action, including suspending or terminating services when violations are confirmed.”
Reviewer's account (not verified by us): The reviewer writes: “they allow hosting to scam/cheat people”. The reply adds that UltaHost could not find an account matching the reviewer's name and asks for a client ID or support ticket number.
“Every credible abuse report is investigated, and appropriate action is taken whenever a violation is confirmed.”
Reviewer's account (not verified by us): The reviewer writes that UltaHost provides “hosting to scam and cheat people”. The reply adds that it would need more than a first name to identify the account.
A text search of all 843 replies found at least 12 further replies, to reviews published between 7 August 2025 and 11 September 2026, in which UltaHost says it investigates or acts on abuse reports (for example by suspending a service). We did not count replies that attribute a hold or suspension to a registry or to Spamhaus, or that only say UltaHost takes abuse reports seriously. These are general statements of position, like the replies in 11.1.
UltaHost replies to nearly every low-rated review
In our 851-review collection, 358 of 359 one-star reviews and 45 of 45 two-star reviews carry a public reply. The one without a reply is from 2020. Trustpilot's own counter on the profile read “Replied to 100% of negative reviews” when we read it on 20 August 2026. A reply is not the same as a resolution.
The policy now says it will act promptly
The page read on 6 November 2026 says UltaHost will “act promptly to interrupt the abusive use” where actionable evidence establishes DNS Abuse involving a domain it sponsors, and that it does not require proof of a customer's malicious intent before addressing an active threat. It also does not require a court order for phishing or impersonation, which differs from the reply of 7 February 2025 quoted in 11.1.
What we can and cannot conclude
- ● Supported: in public replies, UltaHost has told reviewers that it acts on abuse only from certain kinds of reporter; the published policy no longer carries the 10-day reply sentence it carried through 8 August 2026.
- ● Supported: about half of the 932 names on PhishDestroy's UltaHost list were still active with no registry hold on 6 November 2026, and about a quarter were on clientHold.
- ● Not established: why any name was held or removed, how fast UltaHost responds to a given report, or why the policy changed.
- ● Not claimed: that UltaHost ignores abuse reports in general, or anything about its motives.
11.6 How to Report Effectively
The policy, as read on 6 November 2026, names a report form at ultahost.com/report-abuse and asks for the exact URLs, dates and times, evidence such as full email headers and screenshots, and any official case reference. Because reviewers say reports sent from personal email addresses were refused, and because six replies point reporters to organisations and authorities, it is sensible to keep a dated record of what you send, to whom, and what comes back.
11.7 Method, Limits and Right of Reply
| Source | What we took from it | Where |
|---|---|---|
| Trustpilot (UltaHost's public replies) | 851 reviews of ultahost.com read 5 and 6 Nov 2026, 843 with a public reply; reply dates from Trustpilot's own review data | trustpilot.com/review/ultahost.com |
| UltaHost Abuse Handling Policy | The page as read 6 Nov 2026 (no 10-day text); our 8 Aug 2026 capture (10-day text, twice) | ultahost.com/abuse-handling-policy |
| Wayback Machine, 15 Oct 2025 | The 10-day sentence appears twice (Whois inaccuracy; Phishing/419 scam) | web.archive.org: 15 Oct 2025 capture |
| Wayback Machine, 15 Jul 2026 | The 10-day sentence still appears twice | web.archive.org: 15 Jul 2026 capture |
| PhishDestroy registrar report | The list of names it attributes to Ultahost, Inc., and its per-domain pages | phishdestroy.io: registrar report |
| Verisign RDAP | Registry status of 932 .com/.net names, probed 6 Nov 2026 | rdap.verisign.com |
| URLhaus (abuse.ch), AS214036 feed | 897 URLs, 6 online, feed read 6 Nov 2026 | urlhaus.abuse.ch/feeds/asn/214036 |
| ICANN Registrar Accreditation Agreement, global amendment of 5 April 2024 | Section 3.18.1 (confirmation of receipt to the reporter), 3.18.2 (prompt mitigation of DNS Abuse), 3.18.3 (24-hour review of authority reports) | icann.org: RAA global amendment (PDF) |
| WIPO decision D2025-3590 | Registrar verification requested 5 Sep 2025, answered 6 Sep 2025 | wipo.int: D2025-3590 (PDF) |
Limits
- ● Reviews are one side. We did not see the reports behind any review, and replies were written by support staff.
- ● Trustpilot pages refuse automated reads. The review text and reply dates come from the review data we collected, not from the linked page; the links are for readers.
- ● Registry status is a snapshot. The 932-name probe is one day, and it shows the state of each name, not its cause.
- ● No comparison group in this section. We did not run the same probe on another registrar's list, so we make no claim that these shares are better or worse than anyone else's.
Right of reply
We are inviting UltaHost to comment on these findings; any reply will be published here in full.