How to Report Abuse Involving UltaHost

Last updated:

This is a practical guide for anyone who needs to report a phishing page, scam site or impersonation that involves UltaHost, either because the domain was registered through UltaHost, Inc. or because the site is served from UltaHost's network. It follows the channel and the evidence list in UltaHost's own published Abuse Handling Policy (page read 6 November 2026), adds what reporters have told us about the process, and sets out the parallel reports and the escalation route that do not depend on UltaHost at all. It makes no promise about the outcome of any report.

First: which part of UltaHost is involved?

UltaHost plays two different roles, and a report goes to a different place depending on which one applies. Do not assume the two go together.

  • Registrar. The domain name was registered through UltaHost, Inc. (ICANN-accredited, IANA ID 4331). You can check the registrar of record for a domain in the ICANN Lookup tool.
  • Host. The web server behind the page sits on an address announced by UltaHost's network (we record it as AS214036). A domain registered through UltaHost can point at a server somewhere else, and a site on UltaHost's network can use a domain from any registrar.

The policy draws the same line. It says, in its section 1: “When we only register a domain, we generally cannot remove material from an independent host, but we can investigate and take appropriate registration-level action.” It also says that for hosting, the responsible provider is the UltaHost legal entity named in the customer's service agreement. If you report a domain, say which role you are reporting about.

Step 1: Collect the evidence

The policy's section 3 lists what to provide “where relevant”. In summary:

  • The domain, the exact URLs, and any IP addresses of the affected service.
  • A clear description of the activity and the harm.
  • Dates, times and time zone, with logs, full email headers or screenshots.
  • Your contact details, and your authority to act if you report for a rights holder or an organisation.
  • Any urgency, and any court order or official case reference (see Step 4).

The policy also asks reporters to redact unrelated personal information and not to send passwords or executable malware through the form or ordinary email. Save the page with a screenshot and an archive.org capture, but do not enter real credentials into a suspected phishing page to “test” it.

Step 2: Send it through the channel the policy names

As read on 6 November 2026, UltaHost's policy (section 3) says to submit reports through the UltaHost Report Abuse page (which carries a DNS abuse reporting form) or by email to [email protected]. The Report Abuse page adds that reports submitted outside the reporting channel “may experience delays in response”. The policy also says live chat and general support can help route a concern but should not be the only channel for an urgent report.

Use the form, send an email as well if you want a copy in your own mailbox, and note the date and time of each.

Step 3: Who the report comes from

The published policy does not say that reports must come from an organisation, and it does not say that a personal email address is refused. Reporters on Trustpilot nevertheless describe that happening, and UltaHost's public replies to some of them describe a recognised-organisation requirement. These are accounts and replies, not findings about every report:

  • A reviewer who said they had reported a “ponzi hyip phishing” site wrote on 1 August 2025 and pasted a message which, they said, they received in response, saying reports from personal email addresses such as Gmail, Outlook or Hotmail would not be processed and asking for an official business or institutional email domain. UltaHost's public reply to that review (13 August 2025) did not mention personal email. It said: “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.”
  • Another reviewer, in a review dated 31 October 2025, paraphrased the response they got as being refused because they had used a Gmail account. That wording is the reviewer's, not a quotation of UltaHost. UltaHost's reply to that review (1 November 2025) said: “we do not take action on abuse unless instructions are received from an appropriate authority.”

Practical advice that follows from the above, without assuming it is needed: if you have an email address on your own organisation's domain, or your own domain, send from it and say who you are and why you are affected. Do not claim to represent an organisation you do not represent. If you only have a personal address, send anyway, file the parallel reports in Step 6 as well, and keep the reply you receive, if any, in your record.

Step 4: Add an official case reference

The policy lists a “relevant court order or official case reference” among the things to include. A police or fraud-agency reference is the practical version of that for most people. Report the incident to your national agency first (the US FBI's Internet Crime Complaint Center, Action Fraud in the UK, and the others listed under Step 2 of For Victims), then quote the reference number in your abuse report. A reference does not oblige UltaHost to act, but it records that the report is also with a public authority.

A court order is a different thing and is not needed to file a report. In one reply, dated 7 February 2025, to a reviewer reporting a site that impersonated their brand, UltaHost wrote that impersonation matters “require proper legal documentation” and asked for “a court order or relevant legal documentation”. The policy as read on 6 November 2026 lists a court order as an optional field and says disputed civil claims “may require determination by a court or an appropriate dispute-resolution provider”; see the UDRP section below.

Step 5: Follow up on the same case

The policy (section 3) says that for follow-up correspondence you should use the case-specific reply address supplied in UltaHost's notice and include the case reference, and (section 15) that a reporter seeking review should reply through the case-specific channel or write to the abuse address with the case reference, the decision disputed and supporting evidence. Reply to the notice you were sent rather than starting a new thread, so that your messages stay attached to one case.

Section 4 of the policy says UltaHost confirms receipt and tracks the report. The registrar contract also asks registrars to send the reporter a confirmation of receipt (see Step 7). If you get no acknowledgment, record that, with the date you checked.

Step 6: Report in parallel

These services act independently of UltaHost. Filing with them does not depend on how a report to UltaHost is handled, and they can protect people while it is pending.

If the site sits behind Cloudflare, Cloudflare also has an abuse form; see For Victims.

Step 7: Escalate to ICANN (domains registered through UltaHost)

If the domain is registered through UltaHost, Inc. and your report concerns DNS Abuse, you can complain to ICANN Contractual Compliance through ICANN's complaint form. This route concerns the registrar role only. It does not cover a website that is merely hosted on UltaHost's network under a domain from another registrar.

Since the global amendment of 5 April 2024, section 3.18 of the Registrar Accreditation Agreement reads (ICANN's published amendment, PDF): in 3.18.1, registrars shall “provide the reporter with confirmation that it has received the report” and “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse”; and in 3.18.2, “When Registrar has actionable evidence that a Registered Name sponsored by Registrar is being used for DNS Abuse, Registrar must promptly take the appropriate mitigation action(s) that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse.” The agreement defines DNS Abuse as malware, botnets, phishing, pharming, and spam when it delivers one of the others. Trademark and defamation complaints are outside that definition. Whether a particular registrar's handling meets the contract is for ICANN to decide, not this site.

A complaint is strongest when it is about one specific report: the domain, the date you reported, the channel, and what happened next. Our Take Action page has a ready-to-adapt template for it, and a plain account of the February 2025 notice and its March 2026 cure.

If a brand is being impersonated: UDRP and URS

For a domain that copies your trademark, the formal routes are the Uniform Domain-Name Dispute-Resolution Policy (UDRP), run by approved providers such as the WIPO Arbitration and Mediation Center, and, where it applies to the domain's extension, the Uniform Rapid Suspension System (URS). UltaHost's policy (section 10) says it applies the administrative lock for a properly initiated UDRP case and implements decisions under the procedure, including the ten-business-day waiting period. The longer walk-through is in the brand-impersonation section of For Victims.

For context, a search we ran on 4 November 2026 of the WIPO, Forum and Czech Arbitration Court decision archives found 12 UDRP decisions, dated July 2025 to September 2026, that name Ultahost, Inc. as the registrar; in all 12 the panel ordered transfer to the complainant. A registrar line in a UDRP decision records where the domain was registered and does not describe how the registrar handled any abuse report.

Keep a record: checklist

Whatever happens next, a dated record is what lets you escalate (Step 7), tell a journalist, or give a regulator or court something concrete. Keep one line per report, and one folder per case.

  • ☐ Domain, exact URLs, IP address, and which role is involved (registrar, host, or both)
  • ☐ Date and time (with time zone) you first saw the page; screenshot and archive.org capture
  • ☐ The police or agency report number, and the date you filed it
  • ☐ Each report sent: date and time, channel (form or email), exact address, and a copy of what you sent, including headers
  • ☐ Any automatic acknowledgment or ticket number, with the time it arrived
  • ☐ Every reply, in full, with the date; or “no reply as of” with the date you checked (for example day 1, 3, 10 and 30)
  • ☐ The state of the page on each check: still serving, warning page, not resolving (a dated screenshot each time)
  • ☐ Parallel reports: Google, Microsoft, Netcraft, APWG, NetBeacon, with confirmation numbers
  • ☐ ICANN complaint: date filed and the reference ICANN sends you

What a report can and cannot do

UltaHost's policy as read on 6 November 2026 says it does not require proof of a customer's malicious intent before addressing an active threat, and that where actionable evidence establishes DNS Abuse involving a domain it sponsors it acts promptly. It also says (section 17) that it “does not guarantee that every report will result in removal, suspension, compensation or disclosure”, and (section 13) that it does “not guarantee a reporter's anonymity and may need to share the substance of a complaint”. If you are worried about retaliation, leave out your personal details and report through an organisation or a third-party service such as NetBeacon (Step 6).

The policy text can change, so check the date on anything you rely on. See our methodology page for how we read and date sources.

What UltaHost has told reporters in its public replies, how its policy changed, and what happened to reported domains is set out in Round 11: What UltaHost Tells Abuse Reporters.

Sources and when they were read

  • UltaHost Abuse Handling Policy and Report Abuse page: read 6 November 2026.
  • UltaHost public Trustpilot replies: review pages linked above; reply dates as shown there.
  • ICANN Registrar Accreditation Agreement global amendment, effective 5 April 2024 (PDF linked in Step 7).
  • APWG, NetBeacon, Netcraft, Google and Microsoft reporting pages: read 6 November 2026.
  • UDRP decision count: our search of provider archives, 4 November 2026.