The Pirate Atlas

Bulk-scrapes and re-hosts paid OnlyFans and Fansly posts, indexed by creator handle.

How it's handled: Direct API monitoring catches new posts before Google indexes them; DMCA notice per URL, then search delisting.

Route openDMCA holds: No published contact.

Removal routes for coomer.su — 4 tasks

Sister site to Coomer for Patreon, Fanbox, Gumroad and SubscribeStar content.

How it's handled: Continuous source monitoring plus DMCA; perceptual hashing flags reposts that carry none of your names.

Route openDMCA holds: No published contact.

Removal routes for kemono.su — 4 tasks

Gallery-style aggregator of reposted creator photo and video sets.

How it's handled: Keyword and reverse-image scanning; DMCA to the resolved abuse contact with evidence captured per URL.

Route openDMCA holds: Registrar abuse desk only.

Removal routes for fapello.com — 5 tasks

Forum with per-creator threads where users collate links to reposted sets.

How it's handled: Thread-level monitoring; DMCA to the resolved contact, then the infrastructure route when the forum stays silent.

Route openDMCA holds: No published contact.

Removal routes for simpcity.su — 5 tasks

Leak-trading forum organised around individual creators.

How it's handled: Monitored as a primary source; the escalation ladder routes around low-compliance hosts straight to delisting.

Route openDMCA holds: Registrar abuse desk only.

Removal routes for thotsbay.com — 5 tasks

Album host frequently linked from forums, used to hold reposted sets behind a single share link.

How it's handled: Abuse-contact resolution, Cloudflare detection over DNS-over-HTTPS, then a Cloudflare abuse report against the origin.

Route openDMCA holds: No published contact.

Removal routes for bunkr.sk — 6 tasks

Anonymous album host used to mirror reposted galleries.

How it's handled: DMCA to the resolved contact plus the CDN route; links are re-checked daily and re-filed on resurrection.

Route openDMCA holds: No published contact.

Removal routes for cyberdrop.me — 6 tasks

General-purpose file host commonly used to pass around archives of reposted sets.

How it's handled: Abuse reporting per share URL, paired with delisting of any indexed link.

Route openDMCA holds: No published contact.

Removal routes for gofile.io — 6 tasks

Adult gallery and video site where reposted albums are uploaded.

How it's handled: DMCA with uploader attribution captured from the album metadata at scan time.

Route openDMCA holds: Registrar abuse desk only.

Removal routes for erome.com — 5 tasks

Public channels that redistribute paid content at high velocity, often minutes after a post goes up.

How it's handled: Channel monitoring plus a DMCA notice to Telegram's published copyright address.

Route openDMCA holds: Curated abuse address.

Removal routes for t.me — 5 tasks

Subreddits that repost creator sets, plus accounts that impersonate creators to sell them.

How it's handled: Post-level DMCA through Reddit's published copyright route; impersonation goes through a separate report form.

Route openDMCA holds: Curated report form.

Removal routes for reddit.com — 6 tasks

Surfaces reposted content for your stage name even when the host will not remove it.

How it's handled: Copyright delisting in TCRP format, plus the separate personal-explicit-images route; results are re-checked hourly.

Route openDMCA holds: Search delisting only.

Removal routes for google.com — 2 tasks

Second search index, and the one that also feeds DuckDuckGo and several smaller engines.

How it's handled: Bing content-removal requests generated in bulk from the same URL list as Google.

Route openDMCA holds: Search delisting only.

Removal routes for bing.com — 4 tasks

Accounts that repost paid sets and accounts that impersonate creators to redirect their traffic.

How it's handled: Copyright reporting per post, with impersonation handled on a separate form.

Route openDMCA holds: Curated report form.

Removal routes for x.com — 6 tasks

Invite links to servers that trade reposted sets, usually alongside a paid tier.

How it's handled: Report through Discord's published request form, per server and per message link.

Route openDMCA holds: Curated report form.

Removal routes for discord.gg — 5 tasks

Reposted clips and, far more often, accounts using a creator's face and name to sell someone else's content.

How it's handled: Copyright reporting per post; impersonation through the dedicated report form.

Route openDMCA holds: Curated report form.

Removal routes for instagram.com — 5 tasks

Clipped previews used to funnel viewers to a paid mirror, and impersonation accounts.

How it's handled: Copyright reporting per video; impersonation through the dedicated report form.

Route openDMCA holds: Curated report form.

Removal routes for tiktok.com — 6 tasks

Compilation uploads and channels using a creator's name and likeness in the channel identity.

How it's handled: Copyright claim per video; channel impersonation through the dedicated form.

Route openDMCA holds: Curated report form.

Removal routes for youtube.com — 5 tasks

Boards that re-pin creator images, and profiles built entirely from one creator's photos.

How it's handled: Copyright reporting per pin; impersonation through the dedicated report form.

Route openDMCA holds: Curated report form.

Removal routes for pinterest.com — 5 tasks

Reblog chains that carry a single reposted set across dozens of blogs.

How it's handled: DMCA per post, with the reblog chain enumerated so one notice covers the copies.

Route openDMCA holds: Published platform route.

Boards where reposted sets are dropped into short-lived threads, then archived elsewhere.

How it's handled: Thread capture at scan time, because the thread expires long before a notice cycle completes.

Route openDMCA holds: Registrar abuse desk only.

Encrypted cloud storage used to pass around archives behind a share key.

How it's handled: Takedown per share link, since the file itself is not readable from outside.

Route openDMCA holds: Published platform route.

Fast file host used as a fallback when an album host stops serving.

How it's handled: Abuse reporting per file and list URL, paired with delisting.

Route openDMCA holds: Registrar abuse desk only.

Image host used to keep a copy alive after the original album is removed.

How it's handled: DMCA per image and album URL; hosted images are indexed and image-searchable.

Route openDMCA holds: Published platform route.

Hotlink-friendly image host used to keep forum thumbnails alive.

How it's handled: Abuse reporting per image; hotlinked copies are enumerated from the referring thread.

Route openDMCA holds: Registrar abuse desk only.

Tube uploads of paid clips, usually re-titled with a creator's stage name.

How it's handled: Content-removal request per video, with the stage-name title captured as evidence.

Route openDMCA holds: Published platform route.

High-volume tube where reposted clips are re-uploaded under many titles.

How it's handled: Content-removal request per video URL, re-filed automatically on resurrection.

Route openDMCA holds: Published platform route.

Tube with a channel model, so one uploader often holds a whole catalogue.

How it's handled: Content-removal request per video, with the uploader enumerated across their channel.

Route openDMCA holds: Published platform route.

Tube that mirrors clips from other tubes within hours of an upload.

How it's handled: Content-removal request per video, filed alongside the tube it was mirrored from.

Route openDMCA holds: Registrar abuse desk only.

User-gallery tube where uploads are grouped by member rather than by title.

How it's handled: Removal request per URL, with the member gallery enumerated so one pass covers it.

Route openDMCA holds: Registrar abuse desk only.

Tube with private-video links that are shared outside the site.

How it's handled: Removal request per URL, including private links surfaced by a scan.

Route openDMCA holds: Registrar abuse desk only.

Aggregator that mirrors other aggregators rather than scraping sources directly.

How it's handled: Monitored as a second-order mirror; notices name the upstream source as evidence.

Route openDMCA holds: Registrar abuse desk only.

Profile-per-creator aggregator with a paginated archive per handle.

How it's handled: Handle-level monitoring; notices enumerate the paginated URLs rather than the profile root.

Route openDMCA holds: Registrar abuse desk only.

Aggregator that republishes sets under altered titles to dodge keyword matching.

How it's handled: Reverse-image and perceptual-hash matching, because the title no longer carries the name.

Route openDMCA holds: Registrar abuse desk only.

Forum whose threads point at file hosts rather than hosting anything itself.

How it's handled: Thread monitoring plus parallel notices to every file host the thread links to.

Route openDMCA holds: Registrar abuse desk only.

Long-running forum with deep archives that stay indexed for years.

How it's handled: Archive-depth monitoring; old threads matter more here than new ones.

Route openDMCA holds: Registrar abuse desk only.

Video-first aggregator that re-encodes clips, which breaks exact-file matching.

How it's handled: Perceptual hashing rather than file matching, because the re-encode changes the file.

Route openDMCA holds: Registrar abuse desk only.

The network in front of most leak hosts. Not the host, but the only party that reliably answers.

How it's handled: Cloudflare detection over DNS-over-HTTPS, then an abuse report that reaches the origin host behind it.

Route openDMCA holds: Published platform route.

Removal routes for cloudflare.com — 2 tasks

Search index with its own image search, which often keeps a thumbnail after the page is gone.

How it's handled: Delisting requests filed per URL, separately from Google and Bing.

Route openDMCA holds: Search delisting only.

Meta-engine whose web results are drawn largely from the Bing index.

How it's handled: Handled through the Bing removal request rather than a separate filing.

Route openDMCA holds: Search delisting only.