虽然不是CF-Workers-docker代理的原因，但是DMCA实录。 #130
Description
Delivered-To: [YOUR_EMAIL]@gmail.com
Received: by [SERVER_ID] with SMTP id [UNIQUE_ID];
Fri, 17 Oct 2025 08:44:08 -0700 (PDT)
X-Google-Smtp-Source: [REDACTED_SOURCE_ID]
X-Received: by [SERVER_ID] with SMTP id [UNIQUE_ID];
Fri, 17 Oct 2025 08:44:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1760715848; cv=none;
d=google.com; s=arc-20240605;
b=[REDACTED_SIGNATURE]
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=from:reply-to:mime-version:date:to:message-id:subject
:content-transfer-encoding:dkim-signature;
bh=[REDACTED_HASH];
b=[REDACTED_SIGNATURE]
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass [email protected] header.s=scph0619 header.b=[REDACTED];
spf=pass (google.com: domain of msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com designates 192.174.87.157 as permitted sender) smtp.mailfrom="msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com";
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=notify.cloudflare.com
Return-Path: <msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com>
Received: from mta-87-157.sparkpostmail.com (mta-87-157.sparkpostmail.com. [192.174.87.157])
by mx.google.com with ESMTPS id [UNIQUE_ID]
for <[YOUR_EMAIL]@gmail.com>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Fri, 17 Oct 2025 08:44:08 -0700 (PDT)
Received-SPF: pass (google.com: domain of msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com designates 192.174.87.157 as permitted sender) client-ip=192.174.87.157;
Authentication-Results: mx.google.com;
dkim=pass [email protected] header.s=scph0619 header.b=[REDACTED];
spf=pass (google.com: domain of msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com designates 192.174.87.157 as permitted sender) smtp.mailfrom="msprvs1=[REDACTED_ID]=bounces-[REDACTED_CUSTOMER_ID]@notify.cloudflare.com";
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=notify.cloudflare.com
X-MSFBL: [REDACTED_FBL_VALUE]
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=notify.cloudflare.com; s=scph0619; t=1760715847; [email protected]; bh=[REDACTED_HASH]; h=Content-Type:Subject:Message-ID:To:Date:From:From:To:Cc:Subject; b=[REDACTED_SIGNATURE]
Received: from [10.90.36.57] ([10.90.36.57]) by [SERVER_ID] (ecelerity 5.1.0.74632 r(msys-ecelerity:tags/5.1.0.14)) with REST id [UNIQUE_ID]; Fri, 17 Oct 2025 15:44:07 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: [[REPORT_ID]]: Trademark infringement complaint received regarding your site
Message-ID: <[UNIQUE_MESSAGE_ID]>
To: [YOUR_EMAIL]@gmail.com
Date: Fri, 17 Oct 2025 15:44:07 +0000
MIME-Version: 1.0
Reply-To: [email protected]
From: "Cloudflare Trust & Safety" <[email protected]>
Hello,
Cloudflare received an Trademark infringement complaint regarding: [PROJECT_NAME].pages.dev.
Cloudflare received the below copyright infringement complaint regarding your account. If the content identified in the complaint is not removed within 72 hours, Cloudflare will take steps to disable access to the content, consistent with section 512(c) of the Digital Millennium Copyright Act. Please note that these steps will include disabling access to the reported URL on which the content is located, which will affect any other content located on the same URL.
To respond to this notice, please send an email to [email protected] with the following details:
- The report identification number included in the subject line
- A response indicating that the infringing content has been removed OR
- A counter notice as prescribed by the Digital Millenium Copyright Act
If no response is made, Cloudflare may disable access to the reported URLs.
Below is the report we received:
Report ID: [REPORT_ID]
Reported URLs:
hxxps://[PROJECT_NAME].pages.dev/
Original Work Description:
Trademarked Symbol: CHATGPT
Registration Number: [REGISTRATION_NUMBER]
Registration Office: INPI
Counter-notice Information:
Please be aware that a person who knowingly and materially misrepresents that material or activity was removed or disabled by mistake or misidentification may be subject to liability under the Digital Millennium Copyright Act (DMCA). If you have any questions about your rights and obligations, you should consider seeking legal advice.
If you choose to file a counter-notice, you must include the following information:
- Your name, address, phone number, and a physical or electronic signature.
- Identification of the allegedly infringing content and its location before access to it was disabled.
- The following statement: “I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled.”
- The following statement: “I consent to the jurisdiction of the U.S. Federal District Court for the judicial district in which my address is located, or if my address is outside of the United States, for the judicial district in the Northern District of California (where Cloudflare is located), and I will accept service of process from the person who provided the notification of infringement or their designated agent.”
Please submit this information by email to [email protected]. Alternatively, you may send this notice by physical mail. Be aware, however, that we will not process the counter-notice, or begin the 14 day waiting period, until we receive it. If you still wish to mail us your notice, our address is below:
Cloudflare
Attn: DMCA agent
101 Townsend Street
Legal Department
San Francisco, CA 94107
Below are the report submitter's details:
Submitter's Name: Doppel SOC Team
Submitter's Email Address: [email protected]
Submitter's Company Name: Doppel Inc.
Cloudflare Trust & Safety
是部署chatgpt-next-web吃了openai的dmca，而且入口是workers.dev，我的自定义域名部署了ASN墙，自定义域名那边没有被扫到。
但workers.dev被扫了，chatgpt-next-web在workers的部署非常折磨，chatgpt-next-web我早就不用了。
这鬼地方都有人扫，所以鬼知道你部署的项目有什么问题。
workers.dev域名可能都最好禁用一下，反正墙内也难以访问，光让美国的DMCA bot扫了。
我这边是域名里有chatgpt，然后被干爆了。（实际上是因为Clone项目时，这项目还在叫chatgpt-next-web,而不是现在的NextChat）