← Go back

How Do You Report a Phishing Site to Its Hosting Provider?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

Identify the host from the lookalike's A record — the IP owner's abuse contact — and send the hosting packet stating that the hosted content impersonates your brand and, if true, harvests credentials or payments. Attach dated screenshots and the registrar ticket number if you already filed there, and ask for suspension under the host's acceptable-use policy phishing or impersonation clause.

Run the free brand scan — one domain, no account, no card

What is a hosting provider abuse report?

A hosting provider report targets the company whose servers actually serve the fake site, as distinct from the registrar that sold the domain name. TakedownCoop's host packet is built from the scan's own evidence: the A record in the evidence block identifies the IP owner whose abuse contact receives the filing.

What is a hosting provider abuse report?

A hosting provider report targets the company whose servers actually serve the fake site, as distinct from the registrar that sold the domain name. TakedownCoop's host packet is built from the scan's own evidence: the A record in the evidence block identifies the IP owner whose abuse contact receives the filing.

Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for a hosting provider abuse report: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.

How the scan ranks and records it

The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.

Registrar first or host first?

The two channels attack different halves of the problem: the registrar controls the name, the host controls the content. The registrar packet's checklist assumes you may file there first and escalate to the host at the 72-hour re-check, but nothing in the host packet requires a registrar ticket — it simply gets stronger with one, because the ticket proves the name itself is already under an abuse case.

Write the host report around what the host can verify from its own side: the IP serves a page presenting itself as your brand. Say whether it harvests credentials or payments only if you have seen it do so — the packet's wording is conditional for a reason. Ask for the specific remedy the host's acceptable-use policy provides: suspension under its phishing or impersonation clause, not a vague request to 'do something'.

A worked example, end to end

A fictional accountancy practice, Harbourline Books at harbourlinebooks.com, discovers harbourline-book.com serving a client-login clone. The scan's evidence block shows the A record and its IP owner. The owner files the registrar packet on Monday and the host packet on Tuesday, attaching three dated screenshots of the fake login page and registrar ticket RG-2093. The host's abuse desk can see its own IP in the evidence and the login form in the screenshots — everything it needs is in the first message, so no evidence round-trip is needed.

Turning evidence into a filing

Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.

  1. Identify the host from the A record in the evidence block (IP owner / ASN abuse contact)
  2. State the hosted content impersonates your brand and, if applicable, harvests credentials or payments
  3. Attach dated screenshots and the registrar ticket number if already filed
  4. Ask for suspension under the host's AUP phishing/impersonation clause
  5. Record the filing in the case so the seven-day recheck is scheduled

After you file: tracking the case

The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.

Where efforts like this usually go wrong

A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.

Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.

Keeping it from coming back

Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and a hosting provider abuse report stops depending on whoever happens to notice the fake next.

Frequently asked questions

How do I find who hosts a fake site?

From the A record of the lookalike domain. The scan's evidence block records the DNS detail, and the IP owner's abuse contact is the host packet's recipient.

Should I wait for the registrar before contacting the host?

No. The registrar checklist suggests escalating to the host if the name still resolves after 72 hours, but the host packet can be filed as soon as you have the evidence.

What should I ask the host to do?

Suspend the site under the host's acceptable-use policy phishing or impersonation clause — the exact remedy the packet checklist names.

Does the host need my trademark evidence too?

Include the evidence block, which ties the lookalike to your genuine brand. The screenshots of the live impersonation are what the host can act on fastest.

Keep exploring

TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms

Related guides