# Cannot ipns://ipfs.io/ in brave, while other ipns:// sites are good

**URL:** <https://discuss.ipfs.tech/t/cannot-ipns-ipfs-io-in-brave-while-other-ipns-sites-are-good/11832>\
**Category:** Help\
**Created:** [July 25, 2021, 8:11am UTC](https://discuss.ipfs.tech/t/cannot-ipns-ipfs-io-in-brave-while-other-ipns-sites-are-good/11832 "2021-07-25T08:11:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![askender](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/askender/32/5300_2.png) [@askender](https://discuss.ipfs.tech/u/askender)\
**Post date:** [July 25, 2021, 8:11am UTC](https://discuss.ipfs.tech/t/cannot-ipns-ipfs-io-in-brave-while-other-ipns-sites-are-good/11832/1 "2021-07-25T08:11:39Z")

</div>

Other ipns:// sites works well, such as: ipns://research.protocol.ai/  
Only ipns://ipfs.io/ got error:  
ipfs resolve -r /ipns/ipfs.io: could not resolve name

Besides, I can visit [https://ipfs.io/](https://ipfs.io/) well…

```
  (And https://blog.ipfs.io/ doesn't have a ipns version, only support ipfs:// )

```

Doesn’t anyone know why?

---

<div class="post-metadata">

**Author:** ![stebalien](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/stebalien/32/156_2.png) [@stebalien](https://discuss.ipfs.tech/u/stebalien)\
**Post date:** [August 2, 2021, 6:25pm UTC](https://discuss.ipfs.tech/t/cannot-ipns-ipfs-io-in-brave-while-other-ipns-sites-are-good/11832/2 "2021-08-02T18:25:13Z")

</div>

In China? [ipfs.io](http://ipfs.io) is blocked at the DNS level.

> And [https://blog.ipfs.io/](https://blog.ipfs.io/) doesn’t have a ipns version, only support ipfs://

`ipfs resolve /ipns/blog.ipfs.io` seems to work. I assume this is the same problem.

NOTE: you may be able to use DOH to get around this. The latest go-ipfs release has support for this.
