What cloudflare.com is, from the removal side
Cloudflare is a infrastructure surface. The network in front of most leak hosts. Not the host, but the only party that reliably answers. Cloudflare detection over DNS-over-HTTPS, then an abuse report that reaches the origin host behind it.
Route openDMCA holds: Published platform route. cloudflare-abuse-report/index.ts submits the report; detection runs over DNS-over-HTTPS. A notice about cloudflare.com therefore reaches a route that is published and documented.
RDAP probe run 2026-09-04 against the same bootstrap service the takedown dispatcher queries. It returned registrar-abuse@cloudflare.com, which is the registrar's abuse desk rather than the site's.
Removal tasks for cloudflare.com
Each task below is a separate route with a separate outcome on cloudflare.com. Start with the one that matches what you are actually holding — a link, a search result, or a profile.
| Task | What it acts on |
|---|---|
| How to report an infringing site through cloudflare.com | abuse contact |
| How to remove a cloudflare.com-fronted mirror | mirror takedown |
Where a takedown for cloudflare.com stalls
Cloudflare forwards to the origin host and to the origin's provider — it does not remove content itself.
openDMCA routes every URL through the Removal Graph — a live map of which hosts actually remove content, how fast, and through which channel — so each takedown takes the shortest path that has historically worked for that host. For cloudflare.com that means the rungs above are not run in a fixed order: a host with fewer than a quarter of its resolved notices ending in a removal, measured over ninety days with at least five samples, is fast-pathed straight to search delisting instead of spending a second email round on it.