DirtyShip has no reliable DMCA contact and reposts content faster than a single notice can clear it. The removal that sticks: report to Cloudflare, delist the URLs from Google, and file with the host found through WHOIS. Do it across the sibling domains it mirrors to, and lead with Google, which is what actually cuts the traffic.
The frustrating thing about DirtyShip is the speed. You can get a page pulled and see the same clip back up within hours, often on a slightly different domain in the same network. That pattern is the whole strategy: the domain sits behind Cloudflare nameservers, it was registered through a bulk registrar (eNom), and the operator stays out of reach while the content bounces between mirrors.
Chasing that with a copyright email to the site is a losing game, because there is no consistent inbox and no incentive to answer. What does work is applying pressure at the layers DirtyShip cannot fake: its CDN, its host, and Google. This guide walks through them in the order that gets results.
If you would rather not babysit a mirror network, our OnlyFans leak removal service files across the domains for you and re-files automatically when a repost lands.
DirtyShip
Contact
No reliable DMCA contact
Response
Direct notices usually ignored
Difficulty
Why the direct route fails on DirtyShip
Three things make emailing the site pointless:
- No reliable contact. Any address it lists is unmonitored, so the notice is read by nobody.
- It reposts fast. Even when a single page comes down, the same file is often back within hours under a fresh URL.
- It mirrors. DirtyShip pushes the same content across sibling domains in its network, so clearing one leaves the copies live on the others.
Instead of asking the site, you go to the companies it relies on and to Google, which decides whether anyone finds the leak at all.
What actually gets your content down
Collect URLs across every mirror
Search your stage name on DirtyShip and its sibling domains, and run a reverse image search. Copy the full address of every page with your content, grouped by domain, and screenshot each before you file.
File a Cloudflare abuse report
DirtyShip resolves through Cloudflare nameservers. Submit your URLs at abuse.cloudflare.com. Cloudflare forwards the report to the real host and usually names that host in its reply, which is how you reach it.
Send the URLs to Google
The highest-impact step. A copyright removal request strips the pages from Google Search, so your name stops pulling up the leak even while the mirrors argue among themselves.
File with the host via WHOIS
Run each domain through a WHOIS lookup to confirm the registrar (often eNom) and cross-check the host Cloudflare named. Send the same URLs and proof of ownership to that host's abuse address.
A quick WHOIS lookup shows the registrar and nameservers for each mirror so you know who to file with.
The step that matters most: Google
For most creators the file on a server is not the real wound. It is your name surfacing leaked content on the first page of Google. Google will remove those URLs for copyright reasons even when the site and its host never answer, so it delivers the biggest drop in exposure for the least effort.
Send every DirtyShip URL through Google's copyright removal request with a link to your original profile as proof. Expect roughly 48 hours. Our guide to removing content from Google covers the form step by step.
Warning
File one round per domain, not one bundled notice for the whole network. Cloudflare, the host, and Google each handle domains separately, and a mixed-domain notice often gets rejected. Keep a short list of the mirrors so you can re-run the loop when a new one appears.
A note on your details
You do not need to give your home address to anyone here. A valid name and email are enough for Cloudflare, Google, and a host. If a form requires a mailing address, use a management or agent address, never your personal one.
Doing it yourself or letting us handle it
DirtyShip reposts in hours. We re-file in kind.
SuppressLeak files across the mirror network, delists you from Google, and re-files the moment a repost lands.
FAQ
Does DirtyShip respond to DMCA notices?
Not reliably. It has no consistent contact and reposts quickly. Cloudflare, the host, and Google are the routes that produce actual removals.
How do I deal with the mirror domains?
Treat each one as its own site: collect its URLs, and file with Cloudflare, its host, and Google separately. Keep a list so you can re-run it when a new mirror shows up.
Can I still get it off Google if the file stays live?
Yes. Google removes leaked URLs for copyright reasons regardless of what DirtyShip does, usually within about 48 hours, which is the outcome most creators care about.
Do I need a lawyer or a registered copyright?
No. You own the copyright the moment you create the content, and none of these steps require a lawyer.
Remove Content from Google
The highest-impact step for mirror networks like DirtyShip.
Read moreFree DMCA Takedown Notice Template
A complete, reusable notice for the host and CDN.
Read moreRemove Leaked Content from LeakGallery
A cooperative site, for comparison, where the email route works.
Read moreOnlyFans Leak Removal Service
Let us cover every mirror and re-file when it returns.
Read more
