# How can I prevent phishing with ipfs?

**URL:** <https://discuss.ipfs.tech/t/how-can-i-prevent-phishing-with-ipfs/18820>\
**Category:** Help\
**Created:** [December 22, 2024, 6:39pm UTC](https://discuss.ipfs.tech/t/how-can-i-prevent-phishing-with-ipfs/18820 "2024-12-22T18:39:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nokemono](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/nokemono/32/6262_2.png) [@nokemono](https://discuss.ipfs.tech/u/nokemono)\
**Post date:** [December 22, 2024, 6:39pm UTC](https://discuss.ipfs.tech/t/how-can-i-prevent-phishing-with-ipfs/18820/1 "2024-12-22T18:39:28Z")

</div>

How can I prevent phishing with ipfs?  
I think ipfs is vulnerable to phishing because of the low address readability.

---

<div class="post-metadata">

**Author:** ![ylempereur](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/ylempereur/32/5528_2.png) [@ylempereur](https://discuss.ipfs.tech/u/ylempereur)\
**Post date:** [December 22, 2024, 8:42pm UTC](https://discuss.ipfs.tech/t/how-can-i-prevent-phishing-with-ipfs/18820/2 "2024-12-22T20:42:08Z")

</div>

Well, it depends if you mean as a content provider or as a consumer.

As a provider, don’t run a public gateway. Or, if you do, make sure it only serves your content, and nothing else.

As a consumer, IPFS really doesn’t make any difference, as phishing is a web problem, regardless of how it’s served. The only real answer is constant vigilance; don’t enter your information unless you have verified where you are entering it (and yes, there are ways even around that, but that’s a deeper problem that has to do with how the internet works, and has no simple solution).