# Proposal.Get any IPNS address that is highly readable to avoid phishing **URL:** \ **Category:** Help\ **Created:** [December 26, 2024, 1:25am UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835 "2024-12-26T01:25:53Z")\ **Posts on this page:** 8\ **Page:** 1
**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 26, 2024, 1:25am UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/1 "2024-12-26T01:25:53Z")
Wouldn’t it be nice if we could get an arbitrary IPNS address that is highly readable to avoid phishing? I don’t care if it’s paid for. ---
**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\ **Post date:** [December 27, 2024, 4:51pm UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/2 "2024-12-27T16:51:23Z")
`arbitrary` and `highly readable` are contradicting. You’re looking for IPNS via DNS with a little help of [DNSLink](https://dnslink.dev/). ---
**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 29, 2024, 5:12am UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/3 "2024-12-29T05:12:21Z")
There is no contradiction. If a user can specify any address, it can be made human readable. A hash value is not readable. DNS can be censored. It is not a truly web3-like protocol and is not much different than http. ---
**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\ **Post date:** [December 29, 2024, 11:58am UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/4 "2024-12-29T11:58:18Z")
> [@nokemono](#): > > There is no contradiction. If a user can specify any address, it can be made human readable. A hash value is not readable. Well, do tell how you envision that to be possible. Anything that is with human readable names is subject to be attacked by either bots or people registering names en mass (or both). So take that into account 😉 ---
**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 30, 2024, 5:29am UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/5 "2024-12-30T05:29:44Z")
It would be the same as DNS. If you pay for it, you don’t have to worry much about bots. It would also be a source of income for the ipfs community. ---
**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\ **Post date:** [December 30, 2024, 5:19pm UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/6 "2024-12-30T17:19:34Z")
So you **don’t** want to use DNS but you **do** want to use DNS… 😕 You want IPFS to host a new “DNS-like” system… I’d rethink that. Or at least give much more information then the very sparse info you give now. Hey, you might have a great idea! Nice, do tell! But just throwing out a one-liner and assuming us to “interpret it from there” is not gonna help and will get this topic nowhere. ---
**Author:** ![fabiobozzo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/fabiobozzo/32/7459_2.png) [@fabiobozzo](https://discuss.ipfs.tech/u/fabiobozzo)\ **Post date:** [January 2, 2025, 1:20pm UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/7 "2025-01-02T13:20:51Z")
This could be interesting: [https://ipcm.dev/](https://ipcm.dev/) ---
**Author:** ![markg85](https://avatars.discourse-cdn.com/v4/letter/m/41988e/32.png) [@markg85](https://discuss.ipfs.tech/u/markg85)\ **Post date:** [January 2, 2025, 4:29pm UTC](https://discuss.ipfs.tech/t/proposal-get-any-ipns-address-that-is-highly-readable-to-avoid-phishing/18835/8 "2025-01-02T16:29:06Z")
That is cool! I made something like that too a couple years ago ^\_^. I took a similar-like approach. My approach was to store the ABI and the chains it was on on IPFS thus i effectively has multi-chain support. It comes with the downside of having to query the value from chains where it was deployed to figure out the most recent value. My reason was gas prices. They were crazy high back then and L2s were just getting out of beta. Fun little projects to make IPNS replacements 🙂