How to report abuse and phishing on public IPFS HTTP gateways (ipfs.io / dweb.link)

Site Feedback
1

Reporting abuse can only be done via email to abuse@ipfs.io (per About the IPFS.io Public Gateway).

Notes:

  • ipfs.io has not been “compromised”. It just acts as a neutral proxy to content in the IPFS network. Someone else is hosting that content and providing a “gateway link” to it.
  • If you are sending a URL to a phishing link, replace “https” with “hxxps” as your email provider may filter out phishing links.
  • IPFS Discourse forum administrators and IPFS ecosystem developers (those here, in the Github repositories, in Slack and the rest of community channels) cannot help. They have no involvement nor control of the abuse report handling process and no ownership of the public HTTP gateway infrastructure, domains, ASN, denylists…
  • For the same reason, posting/complaining here cannot and does not expedite anything nor serves as a feedback channel. The only way to reach the people in charge is to email abuse@ipfs.io.
3

Forwarded phishing e-mails to abuse@ipfs.i o get bounced by Gmail.
Catch 22.
If you want phishers reported, you cannot hide behind Gmail’s guards.
How many people would be jumping through the hoops to report your transients?

(And your forum automatically converts e-mail addresses into links, while forbidding new users “more than one link”. So, a headache on headache to communicate with you, guys!)

The original message was received at Thu, 19 Feb 2026 11:50:11 -0500 (EST)
from […]

   ----- The following addresses had permanent fatal errors -----
<abuse@ipfs.io>
    (reason: 552-5.7.0 This message was blocked because its content presents a potential)

   ----- Transcript of session follows -----
... while talking to aspmx.l.google.com.:


DATA


<<< 552-5.7.0 This message was blocked because its content presents a potential
<<< 552-5.7.0 security issue. To review our message content and attachment content
<<< 552-5.7.0 guidelines, go to
<<< 552 5.7.0  https://support.google.com/mail/?p=BlockedMessage d75a77b69052e-50684a49842si253702091cf.77 - gsmtp
554 5.0.0 Service unavailable
4

These days email is not the only way. There is a Web Form, see instructions at: