How to get content removed from x.com

    Content on x.com splits into two different problems: posts that republish your paid material, and accounts using your name and face to sell someone else's. The copyright route handles the first and the impersonation form handles the second, and filing the wrong one usually returns nothing.

    Removal route for x.com

    Resolved live · no account · nothing uploaded

    A notice for x.com goes to a curated route openDMCA already holds.

    1. 1 · Curated host route resolves. https://help.twitter.com/forms/impersonation — host_handlers seed row in supabase/migrations/20260607182000_anonymize_and_impersonation.sql.
    2. 2 · RDAP abuse contact resolves. abuse@godaddy.com — the registrar's abuse desk, not x.com itself. Probed 2026-09-04.
    3. 3 · Fallback address not needed. Not needed — an earlier rung resolved.
    4. 4 · Network and search runs next. Cloudflare detection over DNS-over-HTTPS, then Google and Bing delisting of every indexed x.com URL.

    What happens to what you type: nothing. The domain is matched against openDMCA's routing table in your browser. No request is made to x.com, no page is fetched, and the text is not stored or sent anywhere.

    Every removal route on this page is also listed on the x.com removal hub.

    Removal route demo for x.com, remove job.

    What x.com is, from the removal side

    X is a network surface. Accounts that repost paid sets and accounts that impersonate creators to redirect their traffic. Copyright reporting per post, with impersonation handled on a separate form.

    Route openDMCA holds: Curated report form. host_handlers seed row in supabase/migrations/20260607182000_anonymize_and_impersonation.sql. A notice about x.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 abuse@godaddy.com, which is the registrar's abuse desk rather than the site's.

    Removal tasks for x.com

    Each task below is a separate route with a separate outcome on x.com. Start with the one that matches what you are actually holding — a link, a search result, or a profile.

    Removal tasks and routes for x.com
    TaskWhat it acts on
    How to remove leaked content from x.comremoval steps
    How to find the DMCA contact for x.comabuse contact
    How to deindex x.com links from Googlesearch delisting
    How to stop reuploads on x.comreupload monitoring
    How to report a fake x.com accountimpersonation reporting
    How to report non-consensual imagery on x.comthe non-copyright route

    Where a takedown for x.com stalls

    Search delisting of the post permalink after the post itself is gone.

    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 x.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.

    Not sure which of these applies to what you found?

    The Pirate Atlas lists every surface openDMCA has a route to, and what that route is.

    Back to the Pirate Atlas