How to Report Hosting Abuse
Taking down a malicious website means reaching the company that actually hosts it. The right desk is the origin provider behind any CDN or reverse proxy, identified through the site’s IP address and ASN; a proxy like Cloudflare forwards the complaint to the site operator and the host.
Updated
- Where to report
- Origin infrastructure host
- Provider response
- Varies by provider
- Immediate mitigation
- Browser blocklists
The order of operations decides the outcome: identify the true origin host from the site’s IP address and ASN, file through that provider’s required channel with exact URLs and observation timestamps, and report the same URL to browser blocklists in parallel so visitors see warnings while the host decides.
Origin host versus reverse proxy
When an impersonating website appears, the first technical step is identifying the network host. Deceptive websites can route traffic through reverse proxies such as Cloudflare (AS13335) or Fastly. A proxied DNS record answers with the proxy’s addresses instead of the origin IP address.
Reporting to the reverse proxy is a valid initial step: Cloudflare, for example, forwards complaints about its pass-through services to the site operator and the hosting provider, and gives the hosting provider the origin IP. For permanent removal, you must identify and notify the provider operating the origin web server. To suspend the domain itself rather than the hosted content, report domain abuse to the sponsoring registrar.
Step 1: Identify the host from IP address and ASN
Resolve the domain’s A and AAAA records to determine the active IP addresses. Look up the Autonomous System Number (ASN) and network allocation in regional internet registries (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC):
- Dedicated cloud host: If the resolved IP belongs to Amazon Web Services (AS16509), DigitalOcean (AS14061), Hetzner (AS24940), or OVHcloud (AS16276), that provider is usually the origin host. AWS also announces its CloudFront CDN from AS16509, so an AWS address can be a CDN edge in front of another origin.
- Reverse proxy: If the IP belongs to Cloudflare (AS13335) or another security proxy, file a report through their portal so the complaint is forwarded to the site operator and the origin host. Cloudflare passes the origin IP to the hosting provider, so keep working on identifying the origin host separately.
The free domain abuse contacts lookup resolves the registrar and hosting abuse channels for any domain or IP address in one query.
Step 2: Provider-specific reporting procedures
Infrastructure providers each set their own reporting requirements. Make reports conform to their respective intake channels. The provider abuse contacts directory lists the documented channel and requirements for the providers below and more.
Cloudflare (AS13335, AS209242)
- Channel: Web form at abuse.cloudflare.com.
- Category: Select “Phishing & Malware” or “Trademark Infringement”.
- Requirement: For copyright reports, Cloudflare asks for information reasonably sufficient to locate the material, such as a link to the page.
- Note: Cloudflare is generally unable to process complaints sent by email; senders will likely receive an automated reply pointing to the form. Domains registered through Cloudflare Registrar go through the “Registrar” category or
registrar-abuse@cloudflare.com.
Amazon Web Services (AS16509, AS14618)
- Channel: Abuse portal at support.aws.amazon.com/#/contacts/report-abuse.
- Backup:
trustandsafety@support.aws.com. - Requirement: For abusive content such as phishing sites, give the specific URLs where the content is located and the reasons you suspect it violates the AWS Acceptable Use Policy.
Google Cloud (AS15169, AS396982)
- Channel: Web form at support.google.com/code/contact/cloud_platform_report.
- Requirement: Supply the service area, the abuse date, and the abusive IP addresses or URLs.
Microsoft Azure (AS8068, AS8075, AS12076)
- Channel: MSRC portal at msrc.microsoft.com/report/abuse.
- Requirement: Select the incident type, such as “URL - Phishing website”.
Hetzner (AS24940, AS212317)
- Channel: Web form at abuse.hetzner.com or email to
abuse@hetzner.com. - Requirement: The form asks for the type of abuse, the evidence you can provide, and your contact information.
OVHcloud (AS16276)
- Channel: Web portal at ovhcloud.com/en/abuse.
- Requirement: The location of the reported content, as a URL or IP address. OVHcloud transfers admissible reports to its customer to take corrective measures, so omit confidential internal details.
Step 3: What to include in the evidence package
Hosts act on reports that locate the content; OVHcloud, for example, requires its location as a URL or IP address. Provide an evidence package containing:
- Probed URL: The full destination URL, including protocol and path (e.g.
https://brand-portal.example/signin). - Timestamp: UTC observation instant matching server access logs.
- Specific copied assets: Note if proprietary visual assets (such as official brand logos or favicons) are mirrored directly on the page.
- Legal notices: If the content directly duplicates your copyright-protected web design or copy, reference the applicable statutory notice (a DMCA notice for United States hosts, or a Notice and Action notification under the EU Digital Services Act).
Step 4: Deploy immediate client-side mitigations
While waiting for host intervention, submit the fraudulent URL to browser anti-phishing services:
- Google Safe Browsing: Report via the phishing report form. Chrome, Firefox, and Safari use Safe Browsing lists.
- Microsoft Security Intelligence: Report via the unsafe site form. Microsoft Defender SmartScreen in Microsoft Edge and Windows warns on reported phishing sites.
- APWG (Anti-Phishing Working Group): Forward phishing emails to
reportphishing@apwg.orgor use their reporting page. Reports can be processed by APWG members and lodged in its eCrime eXchange, shared with its vetted member community.
Takedowns react to sites that are already live. Domain monitoring watches daily registration feeds for the lookalike registration itself, which can be on record before deceptive content is served.
Sources
- Cloudflare: reporting abuse
- Cloudflare: approach to abuse reports by service type
- Cloudflare: DNS proxy status
- Fastly: what is a reverse proxy
- AWS: abuse reporting FAQs and contact channels
- AWS: IP address ranges
- Google Cloud: report suspected abuse on Google Cloud Platform
- Microsoft: MSRC abuse reporting portal
- Hetzner: report abuse and illegal content
- OVHcloud: abuse form
- OVHcloud: terms of use for the abuse form
- IANA: number resources and regional internet registries
- RIPEstat: AS13335
- RIPEstat: AS16509
- RIPEstat: AS14061
- RIPEstat: AS24940
- RIPEstat: AS16276
- RIPEstat: 13.32.0.0/15
- Google Safe Browsing
- Google Safe Browsing: report a phishing page
- Apple: Safari and privacy
- Mozilla: phishing and malware protection in Firefox
- Microsoft Security Intelligence: report an unsafe site
- Microsoft: Microsoft Defender SmartScreen
- APWG: report phishing emails and URLs
- 17 U.S.C. § 512 (Cornell LII)
- EU Digital Services Act (Regulation 2022/2065)
- ICANN: Uniform Domain Name Dispute Resolution Policy
Frequently asked questions
Cloudflare operates as a reverse proxy and content delivery network (CDN). For its pass-through and CDN services, Cloudflare forwards an abuse complaint to the website operator and the hosting provider, and gives the hosting provider the origin IP address so it can locate the content. Cloudflare cannot remove content it does not host, so the website stays live until the hosting provider or the site operator acts.
Several major providers direct reports to web forms. Cloudflare is generally unable to process complaints sent by email and will likely answer one with an automated response pointing to its form. AWS accepts email but says its form allows faster case processing.
Submit the observed URL to anti-phishing blocklists, such as Google Safe Browsing (used by Chrome, Safari, and Firefox) and Microsoft Security Intelligence (Microsoft Defender SmartScreen covers Edge and Windows). Browsers show visitors a warning before they open a listed site while hosting escalation continues.
No. A hosting takedown removes the website files or server instance from the internet. The registrant still owns the domain name itself and can point it at another host unless the domain registration is suspended by the registrar or transferred via UDRP.
Related tools and resources
Ongoing brand monitoring
notolens checks new domain registrations across 1,570 TLDs and app store results daily, search ads multiple times a day, and trademark registers weekly. When a lookalike domain, conflicting mark, copycat app, or ad using your name appears, notolens checks it, explains the risk, and hands you the records and possible next steps.