Browser Extension

Blockchain-based domains do not resolve by default on most Internet providers. We know that it is hard for non-technicians to change OS/router DNS IPs. That's why we have developed extensions for most popular browsers. Surfing Namecoin- and EmerCoin-based domains has never been easier. All apps are absolutely free.

We support the following TLDs: .BIT, .EMC, .COIN, .LIB, .BAZAR and NXT aliases.

rutracker

Chrome/Chromium

Our Chrome extension can be installed from the Chrome Web Store:

Install on Chrome

Opera

You can install the Opera version from the official Opera Add-on Repository:

Install on Opera

Firefox

We are hosting the Firefox version locally. You can install it from here:

Install on Firefox

Firefox 55 is required (Latest Version). Firefox is the only browser that supports extensions on mobile. This makes it possible to resolve blockchain-based domains on mobile.


Usage

Keep in mind that the browser may trigger the search operation if you type "domain.bit" in the address bar. The reason is that these domains are not recognized as standard TLDs in WebKit-based browsers. There are two ways to fix that:

  1. Type the domain with a trailing slash, example: "domain.bit/".
  2. Type the domain with the protocol, example: "http://domain.bit".

NXT alias redirection works via browser‘s "omnibox" feature. Just type "nxt (space or tab) alias_name" in the browser‘s address bar. For example, "nxt (space) peername" will redirect you to peername.com.

Dot BIT domains are served by Namecoin. Dot EMC, dot COIN, dot LIB and dot BAZAR domains are served by EmerCoin. All systems use Bitcoin's Blockchain technology.

Known bugs

  1. The server's directive REQUEST_URI contains the full requested URL instead of the relative path. This is because the app is using the browser's internal proxy. HTTP protocol requires the full URL when the request is made via proxy. Your CMS must be aware of that.
  2. All Nameservers and IPs are cached for seven days. If you change your domain's settings, please wait the cache to expire.
  3. HTTPS is not working. We are searching for the solution.