Understanding Non-Standard Decentralized TLDs

Nonstandard decentralized top level domains include .bit, .eth, .coin, .lib, .emc, .bazar, .onion and many more. These are typically non-national decentralized alternatives to traditional Top-Level Domain registries. They will not show up in typical Google or Yahoo search indexing and are accessed using non-profit DNS servers. DotBit is a top-level domain that falls outside most commonly used Domain Name System (DNS) of the Internet, and is not sanctioned by the Internet Corporation for Assigned Names and Numbers (ICANN).

Why should I be interested in Non-Standard Decentralized TLDs?

These domains are decentralized domain name systems providing robustness and much more protection for users and businesses. A .bit is less proned to domain hijacking or domain registrar security hacks while also offering DNS Neutrality and stops large corporations from logging your personal search engine information and using this data for thier benefit. Decentralized domains significantly reduce the costs of domain ownership, increase the security of domain ownership and reduce the overhead of datacenters. The use of decentralized domains will also provide users with cheaper products and services. Decentralized TLDs and thier benefits will not be found using todays popular search engines.

How do I access a non-standard decentralized TLD

Use of a .bit requires a supporting public DNS server such as the OpenNIC DNS project. The easiest way to access .bit without downloading softare is a web browser plug-in or simply add the OpenNIC DNS servers to your windows “Local Area Connection Properties”. There are also websites who offer direct access to these domains such as GoDexa.com. The ZeroNet project is also growing in popularity. ZeroNet is a decentralized web browser application that allows you to use your browser without any changes. Any of these options will allow access to DotBit domain names.

We are still developing our .bit domain and it will contain all the essentials such as access to your wallet and a blockchain explorer. When this is in full production you will be able to find information on how to access and use this domain in the comments section of your KeyStore file. Below is a tutorial on how to access .bit domains from your windows machine by adding a non-profit DNS server.

Add DNS servers on Windows 10 to allow .bit addresses

• From the Windows 10 search tool, type Control Panel and then press the Enter key
• Select Network and Internet
• Select Network and Sharing Center
• Select Change adapter settings on the left-hand side of the screen
• Double click your Local Area Connection
• Select properties
• In the items window double click Internet Protocol Version 4 (TCP/IPv4)
• At the bottom select Use the following DNS server addresses and enter the DNS servers provided.
• You can also select advanced then select the tab DNS. This will allow you to add more DNS servers or include your current ISP DNS servers.

[siteorigin_widget class=”SiteOrigin_Widget_Image_Widget”][/siteorigin_widget]
[siteorigin_widget class=”SiteOrigin_Widget_Image_Widget”][/siteorigin_widget]
[siteorigin_widget class=”SiteOrigin_Widget_Image_Widget”][/siteorigin_widget]


DNS SERVER DNS SERVER HOST NAME ns3.any.dns.opennic.glue ns1.nc.us.dns.opennic.glue ns1.vie.at.dns.opennic.glue ns5.ca.dns.opennic.glue ns1.ch.dns.opennic.glue ns3.cz.dns.opennic.glue ns1.ru.dns.opennic.glue ns1.ka.in.dns.opennic.glue ns1.nl.dns.opennic.glue

.BIT Insecure Browser Connection Warnings Why?

So you finally can access .bit and now your browser does not like https connections to .bit addresses. This is because standard TLDs use a third party to sign SSL certificates. This has been money in the pockets of browser companies and SSL certificate authorities and is not necessary in order to create an encrypted and secure connection between a browser and a server. As a matter of fact decentralized domains are less likely to be hijacked than standard domains reducing the need for third parties to sign certificates.

Most .bit addresses today will carry a self signed cerificate. This certificate is signed by the owner of the .bit address and linked to the correct server. A self signed certificate offers the same security connection as a certificate authority but without the central authority of course. Browsers do not like self signed certificates because they are tied to the corporations who pay them to include third party certificates. This is why you will get an insecure connection warning. Users will have to manually add self signed SSL certificates the first time they visit an SSL secured site with a .bit address.

FireFox – Your connection is not secure
• Click Advanced
• Click Add Exception
• Verify the Location field is indeed https://www.galaxycoin.bit
• Click confirm security exception

You now have added this .bit address to your browser. It will still give a warning that the connection is not secure because it does not have a central authority signature but this does not mean you are not safe. To see that its using a secure encrypted connection click the lock by the address. Click the arrow right and then click more information. At the bottom of the screen you will see your connection has been established using encryption.