DMCA & Abuse Reporting
How to file a DMCA takedown notice or counter-notice with XDP.NETWORK, and how to report phishing, malware, and other network abuse.
On this page
XDP.NETWORK ("we", "us"), a PingLess Studios product, respects the intellectual property rights of others and expects the Customers who use the Services to do the same. This page explains how to submit a copyright takedown notice under the Digital Millennium Copyright Act ("DMCA"), how to respond with a counter-notice, and how to report abuse that has nothing to do with copyright.
1. Designated agent
Copyright takedown notices should be sent to our designated agent:
- Name / contact: [[PLACEHOLDER: DMCA agent name/contact]]
- Address: [[PLACEHOLDER: registered address]]
The designated agent is for copyright matters only. Anything else — phishing, malware, network abuse — goes to the abuse contact listed at the end of this page, where it will be handled faster.
2. Filing a takedown notice
For a notice to be valid under 17 U.S.C. § 512(c)(3), it must include all of the following:
- Your physical or electronic signature (typing your full name at the end of an email counts), as the owner of the exclusive right or a person authorized to act for them.
- Identification of the copyrighted work you claim has been infringed — or, if several works are covered by one notice, a representative list.
- Identification of the material you claim is infringing, with enough detail for us to locate it. For us that means the specific URLs, IP addresses, or hostnames involved — "somewhere on this network" is not actionable.
- Your contact details: name, mailing address, telephone number, and email address.
- A statement that you have a good-faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law.
- A statement that the information in the notice is accurate and, under penalty of perjury, that you are authorized to act on behalf of the owner of the exclusive right.
Notices missing required elements may not be processed; we will usually reply explaining what is missing. Please also be aware that under § 512(f), anyone who knowingly makes material misrepresentations in a takedown notice may be liable for damages.
3. What we do on receipt
When we receive a complete notice, we act expeditiously. In practice that means:
- Where the material relates to a Customer's Protected Infrastructure — servers, game servers, sites, or APIs enrolled in the Services — we forward the notice to that Customer and require a response. Where we can technically restrict delivery of specific content (for example, a URL served through the PingLess WAF edge), we may disable access to it while the matter is resolved.
- Where the material is not tied to any Customer, we remove or disable access to whatever is within our control.
One nuance worth stating plainly: we are a mitigation and network provider, not a hosting provider. We do not host the content that flows through the Services, and we cannot delete files from a Customer's server. If the content is hosted on a Customer's own machine, the fastest path to removal is often that server's hosting provider — but we act within our ability, and forwarding, edge-level restrictions, and suspension of Services are all on the table.
4. Counter-notice
If your material was removed or access to it was disabled and you believe that was a mistake or misidentification, you may send our designated agent a counter-notice under 17 U.S.C. § 512(g)(3) containing:
- Your physical or electronic signature.
- Identification of the material that was removed or disabled and the location where it previously appeared.
- A statement under penalty of perjury that you have a good-faith belief the material was removed or disabled as a result of mistake or misidentification.
- Your name, address, and telephone number, and a statement that you consent to the jurisdiction of the federal district court for your judicial district (or, if you are outside the United States, for any judicial district in which we may be found) and that you will accept service of process from the person who filed the original notice.
On receipt of a valid counter-notice, we forward it to the original complainant. Unless the complainant notifies us that it has filed a court action seeking to restrain the alleged infringement, we may restore the material or re-enable access no sooner than [[PLACEHOLDER: e.g. 10–14 business days]] after forwarding.
5. Repeat infringers
We terminate, in appropriate circumstances and at our sole discretion, the accounts of Customers who are repeat infringers. We may also suspend or terminate an account after a single infringement that is particularly clear or serious. Termination is handled under the Terms of Service.
6. Non-copyright abuse
This page is for copyright. For everything else — phishing pages, malware distribution, botnet command-and-control, spam, port scanning, or attack traffic originating from or passing through infrastructure enrolled in the Services — report it to [[PLACEHOLDER: abuse contact email]]. Include the URLs or IP addresses involved, timestamps with time zone, and any evidence you have (headers, packet captures, screenshots). What we prohibit, and what we do about it, is set out in the Acceptable Use Policy.
Version history
| Date | Change |
|---|---|
| Initial publication. |