Reports about a discord.gg server go through a published request form rather than an abuse address. A registry lookup for the domain returns nothing useful, because the party who can act is the platform rather than anyone in the domain's registration chain.
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.
Skip the registry lookup. A lookup on discord.gg does not produce a contact that can act on server content. The published request form is the route, and it is held in openDMCA's routing table as a curated entry.
Gather what the form actually asks for. The discord.gg route needs the message links, the original work's location, the dates and a statement of authority. Assembling those before opening the form avoids an abandoned submission.
Group the report by problem. List every discord.gg message sharing one problem in a single report rather than filing each separately. The pattern is part of the evidence, and splitting it hides it.
Keep the submission reference. Record what you submitted and when. A follow-up on discord.gg is far more effective with the original reference than as a fresh report describing the same thing again.
Run delisting in parallel where invites are indexed. A public discord.gg invite that appears in search is a separate problem with a separate request, and it does not wait on the platform's process.
Why openDMCA stores discord.gg as a form rather than an address
A routing system built only on email addresses cannot represent a platform whose process is a form with required fields. openDMCA stores discord.gg as a form-type route, which is what lets the dispatcher queue a submission rather than send a message nobody will read.
It also means the resolver never falls through to a registry lookup for this domain. The contact such a lookup returns belongs to the domain's registration chain and has no authority over what a server contains.
openDMCA gives the first two hops away: you can open the contact resolver openDMCA uses and run it on a URL of your own, with no account and nothing uploaded.
One thing that catches people out on discord.gg
discord.gg is one of only two messaging surfaces in openDMCA's seeded routing table with a documented request route, and the seed records it as a form rather than an address. That seeding is why a discord.gg report is dispatched correctly on the first attempt instead of being emailed to a registrar that cannot act on it.
Frequently asked questions
Is there an email address for discord.gg reports?
The published route is a request form. An address resolved from the domain registry belongs to the registration chain and cannot act on server content.
What does the form need?
The message links, the location of your original work, the dates, and a statement that you are authorised to act. Missing the last one is a common reason for a rejection.
How do I follow up?
With the submission reference from the original report. A fresh report describing the same problem starts the process over rather than continuing it.
Resolve the contact for a host you are dealing with — free, no account.