A closed discord.gg server is rebuilt and the members follow, because the operator announces the replacement before the closure lands. The invite changes, the membership does not, and the material is re-posted from copies the members already hold rather than re-obtained.
Left up, 40 exposed copies work out to an estimated $234 a month in diverted subscriptions. Estimate, not a measurement: it assumes 0.45 diverted subscribers per exposed post at an average subscription price of $12.99. Your number depends on your pricing and audience.
Removal route for discord.gg
Resolved live · no account · nothing uploaded
A notice for discord.gg goes to a curated route openDMCA already holds.
2 · RDAP abuse contact— silent.rdap.org returns no RDAP service for the .gg registry. Probed 2026-09-04.
3 · Fallback address— not needed.Not needed — an earlier rung resolved.
4 · Network and search— runs next.Cloudflare detection over DNS-over-HTTPS, then Google and Bing delisting of every indexed discord.gg 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 discord.gg, no page is fetched, and the text is not stored or sent anywhere.
Expect a replacement rather than a restoration. A closed discord.gg server does not come back at the same invite. The replacement uses a new one, so monitoring the closed invite is a permanent false negative.
Watch where the replacement is announced. Successors are announced in the forums and channels that carried the original discord.gg invite. Those pages are the earliest reliable signal available from outside.
Keep the record against the content, not the invite. Log what you reported by material rather than by discord.gg address. A rebuilt server is only provable as a continuation when the record outlives the invite.
Report the sequence rather than each server. Cite the previous invites, their dates and the outcome. A documented series of rebuilt servers is a materially stronger report than another first-time complaint.
Chase the hosts the messages link to. Material inside a discord.gg server usually links out to file hosts. Those hosts have their own routes and removing the files reduces what a rebuilt server can redistribute.
What monitoring a discord.gg server can honestly claim
openDMCA queues each found item as its own leak with its own route and re-runs the queue every thirty minutes. On a messaging surface that interval is what determines whether a report covers one message or the twenty it produced since.
The limit is unchanged: nothing prevents a replacement server. What changes is how quickly it is found, and whether the sequence is documented well enough for the pattern itself to become the subject of the report.
openDMCA gives the first two hops away: you can open check whether a URL came back and run it on a URL of your own, with no account and nothing uploaded.
One thing that catches people out on discord.gg
Rebuilt discord.gg servers re-post from copies the members already hold, which means the material does not have to be re-obtained from any host to reappear. Removing the original file hosts still matters — it limits what can be redistributed to newcomers — but it does not touch what is already in members' hands, and no service should imply otherwise.
Frequently asked questions
Why does a closed discord.gg server come back?
The members and the files already exist. Closing a server removes a container, not the copies the people inside it are holding.
Does removing the file hosts help?
Yes, for anything redistributed to newcomers, and it builds the record. It does not affect copies already downloaded, and openDMCA does not claim otherwise.
Is reporting each rebuild worth it?
Yes. The sequence is the case. A single report about one server is much weaker than a documented series with dates and shared operators.
Check whether a URL you already reported has come back — free, no account.