The Pirate Atlas

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

How it's handled: The Coomer API is checked on your plan's scan schedule, so new posts can surface before Google indexes them; DMCA notice per URL, then a prepared search-removal request.

Route openDMCA holds: Curated abuse address.

Removal routes for coomer.su — 4 tasks

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

How it's handled: The Kemono API is checked on your plan's scan schedule; DMCA notice per URL, then a prepared search-removal request.

Route openDMCA holds: Curated abuse address.

Removal routes for kemono.su — 4 tasks

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

How it's handled: Found through Google keyword search, or reverse image search of your reference images on Pro and up; DMCA to the resolved abuse contact with evidence captured per URL.

Route openDMCA holds: Curated abuse address.

Removal routes for fapello.com — 5 tasks

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

How it's handled: Site-targeted Google searches find the threads; DMCA to the resolved contact, then a prepared Cloudflare abuse report when the forum stays silent.

Route openDMCA holds: Upstream provider only.

Removal routes for simpcity.su — 5 tasks

Leak-trading forum organised around individual creators.

How it's handled: Site-targeted Google searches find the threads; a host that removed under 25% of at least five resolved takedowns skips the follow-up notice and moves up to search de-listing, with the rest of the escalation ladder still to follow.

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 prepared for a person to submit.

Route openDMCA holds: Curated report form.

Removal routes for bunkr.sk — 6 tasks

Anonymous album host used to mirror reposted galleries.

How it's handled: DMCA to the resolved contact, then a prepared Cloudflare abuse report; links are re-checked daily and anything that comes back is flagged and queued for a new notice.

Route openDMCA holds: Upstream provider only.

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: Curated report form.

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: Curated abuse address.

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: No Telegram scanning today (planned). On Pro and Agency, a t.me link you add gets a DMCA notice emailed to Telegram's published copyright address; each post is re-checked on Telegram's public page.

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 abuse address.

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 requests prepared as a filled-in Google form for you to submit, plus Google's separate explicit-imagery form for deepfakes; 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 abuse address.

Removal routes for x.com — 6 tasks

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

How it's handled: On Pro and Agency, a notice to Discord's copyright agent naming the server, channel and message IDs or the invite code, then Discord's copyright form prepared for a person to submit for the whole server.

Route openDMCA holds: Curated abuse address.

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 abuse address.

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 abuse address.

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 abuse address.

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, listing each reblog URL that carries the copy.

Route openDMCA holds: Curated abuse address.

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

How it's handled: Copy the thread and file URLs as soon as you find them, 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: Curated abuse address.

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: Curated abuse address.

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: Curated abuse address.

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

How it's handled: Abuse reporting per image, including hotlinked copies found in the referring thread.

Route openDMCA holds: Curated abuse address.

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: Curated abuse address.

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

How it's handled: Content-removal request per video URL; removed links are re-checked daily and a reupload is queued for a new notice.

Route openDMCA holds: Curated report form.

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

How it's handled: Content-removal request per video, listing each upload on the uploader's channel.

Route openDMCA holds: Curated abuse address.

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: Curated abuse address.

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

How it's handled: Removal request per URL, listing each item in the member gallery.

Route openDMCA holds: Search delisting 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: Curated abuse address.

Aggregator that mirrors other aggregators rather than scraping sources directly.

How it's handled: A second-order mirror; a notice can name the upstream source as evidence.

Route openDMCA holds: Curated abuse address.

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

How it's handled: Notices should list the paginated URLs rather than the profile root.

Route openDMCA holds: Curated abuse address.

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

How it's handled: Reverse image search of your reference images (Pro and up), 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: Notices to the forum plus parallel notices to every file host the thread links to.

Route openDMCA holds: Curated abuse address.

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

How it's handled: Old threads matter more here than new ones, so check the archive, not only recent posts.

Route openDMCA holds: Curated report form.

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

How it's handled: Reverse image search of your reference images (Pro and up) 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 prepared for a person to submit, which Cloudflare forwards to 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: Filed per URL through Yandex's own removal form, separately from Google and Bing; openDMCA does not prepare these requests.

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.