How Do You Report a Phishing Site Behind Cloudflare or a Web Host?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
When a phishing site sits behind Cloudflare or another CDN, the IP address you resolve belongs to the CDN, not the attacker — so a naive hosting report goes to a company that does not host the content. The correct move is to file the CDN's abuse form anyway: CDNs can identify the origin customer behind their proxy and, for clear phishing, can disable the site's proxying or account. In parallel, hunt the origin yourself through DNS history, certificate records, and subdomains that leak the real server, then file with the actual host as well.
Why the IP address lies to you
A CDN sits between visitors and the origin server. DNS for a proxied site resolves to the CDN's anycast addresses, the TLS certificate may be issued to the CDN's infrastructure, and your whois lookup on the IP returns the CDN's abuse desk. None of this is concealment wrongdoing — it is how CDNs provide performance and attack absorption for millions of legitimate sites. But it means the standard 'resolve, whois, report' workflow needs one extra layer of thinking for proxied phishing.
Attackers know this and choose proxied setups deliberately. It costs them nothing, it slows down inexperienced reporters, and some complainants give up after learning the CDN 'is not the host'. Registrars and CDNs both report that phishing behind major CDNs is now routine. The workflow below is the one abuse desks themselves recommend, and it works because CDNs handle phishing complaints at scale every day.
Filing with the CDN, done properly
Use the CDN's dedicated abuse form rather than a generic support ticket, and choose the phishing category specifically. Give the full URL, the impersonated brand, what the page harvests, and your evidence screenshots. State, in one sentence, that you understand the CDN is the proxy and you are asking it to identify and act on the customer account and notify the origin host — that sentence routes your ticket to the right queue instead of earning a form reply explaining what a CDN is.
Set expectations by provider. Major CDNs forward complaints to the origin host and the site owner, act directly on egregious or repeat accounts, and can terminate proxying so the site loses its shield and often its uptime. What they will generally not do is hand you the origin IP address; privacy rules reserve that for law enforcement. Design your process so it never depends on being given that address.
Hunting the origin yourself
Origins leak. Historical DNS records — kept by passive DNS services — often show the server's real address from before the site moved behind the proxy. Certificates issued for forgotten subdomains (mail, dev, cpanel, direct) frequently sit on the origin and resolve straight to it. Error pages, mail headers from the phishing operation itself, and MX records pointing at the origin are other classic leaks. Any one of them can give you the true host to report in parallel.
Work carefully and legally: everything above uses public records about a public-facing site, which is standard abuse-desk practice. Do not probe the origin beyond identifying it, and do not interact with the phishing page beyond capturing evidence. Your goal is an accurate second abuse report naming the real hosting provider, its ASN, and the origin address — the report that actually unplugs the content.
Reporting the real host, and the registrar as backstop
Once the origin host is identified, file its abuse desk the same evidence pack, noting the CDN report reference and the exact URLs. Hosts suspend phishing content routinely and quickly when the report is precise; vagueness ('this customer seems malicious') goes to the back of the queue, while 'this URL serves a credential form cloning this brand, screenshots attached' gets action. If the host is unresponsive across a reasonable window, escalate within the provider and note the non-response for the registrar filing.
The registrar remains your backstop throughout, because registrar suspension kills the domain regardless of proxies and origins. File it in parallel from the start rather than after host hunting fails. A layered incident — CDN notified, origin host reported, registrar filed, blocklists warned — leaves the attacker no cheap move: changing hosts keeps the domain suspended, changing domains loses the blocklist race, and every hour of delay is an hour behind browser warnings.
Preventing the runaround next time
Pre-build this workflow before you need it. Keep a one-page runbook listing the abuse-form URLs for the major CDNs, the large hosting providers, and the registrars your industry sees most, plus your standard evidence-pack checklist. The first phishing site you handle this way takes an afternoon of learning; the fifth takes forty minutes of execution, because the routing knowledge is the slow part and it is entirely reusable.
Monitoring shortens the loop further. A lookalike alert that arrives at registration or certificate issuance — before the phishing mail goes out — turns an emergency into paperwork. DomainGuard's findings include the resolving infrastructure for each live lookalike, so the CDN-versus-origin question is answered in the report itself, and the takedown packet is addressed to the right desks from the first filing.
Five actions to take today
- Resolve the phishing domain and identify whether its IPs belong to a CDN before choosing where to report.
- File the CDN's phishing abuse form with the full URL and a sentence stating you know it is the proxy and are asking it to act on the customer.
- Search passive DNS history and the domain's other subdomains for an origin address leak.
- File the real hosting provider's abuse desk with the same evidence pack once the origin is identified.
- Keep the registrar and blocklist filings moving in parallel so no single slow desk delays protection.
Worked example: Harbor Lane Accounting unplugs a proxied clone
Harbor Lane Accounting, a fictional firm monitoring 6 domains, found a client-portal clone resolving only to CDN addresses. Its CDN abuse report was filed at 09:15 with screenshots and the full URL. A passive-DNS check the same morning found a pre-proxy A record pointing at a budget host; that host's abuse desk received the pack at 11:30 and suspended the origin at 15:45, ending the site even before the CDN finished its own review. The registrar suspended the lookalike domain 2 days later. Total live time of the clone after detection: under 7 hours.
FAQ
Will Cloudflare give me the origin IP if I ask?
Generally no. CDNs share origin details with law enforcement, not complainants. File the abuse report — they can act on the customer and notify the host without disclosing the address to you.
Is filing with a CDN pointless if it does not host the site?
No. CDNs can disable proxying, suspend abusive accounts, and forward your evidence to the origin host. For clear phishing, those actions are routine and often fast.
How do passive DNS services help?
They keep historical records of what a domain resolved to. Many phishing sites were briefly unproxied during setup, and that earlier address often is the real origin server.
Should I wait for the host hunt before filing with the registrar?
Never. File the registrar, blocklists, CDN, and host reports in parallel. Each channel protects differently, and sequencing them costs the attacker nothing but costs victims hours.
What if the origin host ignores the report?
Escalate inside the provider, document the non-response, and lean on the registrar filing — suspension at the registrar ends the domain no matter where it is hosted.