Traditionally we ran our own DNS servers or relied on those providers we ran websites or apps under, or even public DNS services provided by Google or OpenDNS.

We registered Domains in the standard way via our registrar or cloud provider, changed their nameservers, pointed them to where we wanted them to be and then built our infrastructure off the back of that. 

Year over year, we would reregister the domains, often for increasing prices. Contend with spam, worry about security, leaking network data, DoS attacks, hackers and more. As we all do. 

Its been that way for over 30 years (from our perspective). Technology Stacks have being created, systems have evolved but much has stayed the same. 

Today, we are migrating to a more decentralized web. One that is geared more for IoT, AR, VR, AI, Big-Data, Gaming, Sciences, The Environment and the People but doesn’t rely on a centralized provider. 

Ground up approach. 

Today’s internet is reliant on DNS. The Domain Name System which turns a name, like, www.google.com, into an ip address, like 142.250.69.196. Reading right to left, the .com points to a Top Level Domain Server, which contains a record for google.

This would normally be Google’s own nameservers, and these, have a record for the www part. Taken altogether, without going into details, it tells our computers how to find the website hosted on a remote computer which can be found using the path .com -> google -> www. 

The custodians of these systems are registrars like ICANN who, through third party’s, allow you purchase your domain name from, say godaddy, or amazon.

This system works for the most part, but there are issues with it. Such as when a domain is shut down or taken over by hackers, stolen or defaced. Using the current system there isn’t really a way prevent this without using your own custom DNS servers (and there are people who run domain servers who handle Top Level Domains which ICANN and the rest of the internet do not commonly support). This can also be abused. Such as with man in the middle attacks, setting up your own dns server in between a legit user and some endpoint and redirecting the www part to some other ip address. Worse, they can even see what address you are trying to visit. 

HDNS – Handshake DNS

Switching to HDNS, normal websites like google.com and youtube.com still work seamlessly and we gain access to the 10,000 (and growing!) websites on Handshake’s decentralized Internet.

More news on what this entails will come later. For now, our legacy systems are still active and we are in the process of building out a new Dashboard, API’s and Infrastructure build around Identity and Domain Name ownership. 

DNS is usually slow and insecure. Your ISP and anyone else listening in on the Internet can see every site you visit and every app you use, even if their content is encrypted. Creepily, some DNS providers sell data about your Internet activity or use it to target you with ads.

HDNS supports DNS-over-HTTPS, the modern and encrypted DNS protocol that protects against DNS spying and tampering. Learn More

HDNS is a collaboration between Namebase and DNS industry veterans who have built DNS infrastructure used by millions of consumers.

Our goal in creating HDNS is to make it easier for everyday Internet users to access the decentralized Internet through Handshake in a secure and private way.