Changes

* FriGate: Blockchain DNS services provided through a proxy, accelerates access to blocked websites, encrypts traffic, opens Tor sites, and supports EmerDNS.<ref>[https://chrome.google.com/webstore/detail/frigate-vpn/gmgimpdjmagalimgdaeacfcpoimfpikm FriGate, Web Store, Chrome]</ref><ref>[https://fri-gate.org/ FriGate]</ref>

* FriGate: Blockchain DNS services provided through a proxy, accelerates access to blocked websites, encrypts traffic, opens Tor sites, and supports EmerDNS.<ref>[https://chrome.google.com/webstore/detail/frigate-vpn/gmgimpdjmagalimgdaeacfcpoimfpikm FriGate, Web Store, Chrome]</ref><ref>[https://fri-gate.org/ FriGate]</ref>

* [https://handshake.org Handshake]: A DNS-backwards compatible naming protocol. It adds a distributed, decentralized blockchain-based system to the root zone file where TLD ownership information is stored. No one controls it and anyone can use it, allowing for a root zone that is uncensorable, permissionless, and free of gatekeepers. Every peer in the Handshake network [[Cryptography|cryptographically]] validates and manages the root zone, eliminating the need for the Certificate Authority system.<ref>[https://learn.namebase.io/about-handshake/about-handshake About Handshake, Namebase]</ref> The Beacon browser can natively access the

* [https://handshake.org Handshake]: A DNS-backwards compatible naming protocol. It adds a distributed, decentralized blockchain-based system to the root zone file where TLD ownership information is stored. No one controls it and anyone can use it, allowing for a root zone that is uncensorable, permissionless, and free of gatekeepers. Every peer in the Handshake network [[Cryptography|cryptographically]] validates and manages the root zone, eliminating the need for the Certificate Authority system.<ref>[https://learn.namebase.io/about-handshake/about-handshake About Handshake, Namebase]</ref> The Beacon browser can natively access the Handshake domains.

Handshake domains.

:: ''Potential shortcomings'': [[Andrew Allemann]] points out that: Handshake is decentralized at the top level, allowing many companies and people to create top-level domains. However, it is centralized at the second level. [[Namecheap]] sells Handshake domains like .creator, .oo, and individuals pay annual fees for them. These blockchain-based domains have renewal fees and few people can access them. Moreover, with so many top-level domains, few to none may gain general recognition, a problem some people cited in the 2012 [[New gTLD Program]].<ref>[https://domainnamewire.com/2022/01/13/blockchain-domains-and-the-big-challenges-they-face/ Blockchain Domains' Challenges, DNW]</ref>

:: ''Potential shortcomings'': [[Andrew Allemann]] points out that: Handshake is decentralized at the top level, allowing many companies and people to create top-level domains. However, it is centralized at the second level. [[Namecheap]] sells Handshake domains like .creator, .oo, and individuals pay annual fees for them. These blockchain-based domains have renewal fees and few people can access them. Moreover, with so many top-level domains, few to none may gain general recognition, a problem some people cited in the 2012 [[New gTLD Program]].<ref>[https://domainnamewire.com/2022/01/13/blockchain-domains-and-the-big-challenges-they-face/ Blockchain Domains' Challenges, DNW]</ref>

* [http://i-dns.net/ iDNS]: Beginning as a research project at the University of Singapore, this DNS ran under the auspices of the Asia-Pacific Networking Group in 1998 and was incorporated in 1999. i-DNS successfully test-bedded [[IDN]]s over a 6-month period, in collaboration with [[CNNIC]], and the NICs of Japan, Korea, Hong Kong, Taiwan, Malaysia, Thailand, and Singapore.<ref>[http://www.i-dns.net/company/history/history.html Our History, i-DNS]</ref>  

* [http://i-dns.net/ iDNS]: Beginning as a research project at the University of Singapore, this DNS ran under the auspices of the Asia-Pacific Networking Group in 1998 and was incorporated in 1999. i-DNS successfully test-bedded [[IDN]]s over a 6-month period, in collaboration with [[CNNIC]], and the NICs of Japan, Korea, Hong Kong, Taiwan, Malaysia, Thailand, and Singapore.<ref>[http://www.i-dns.net/company/history/history.html Our History, i-DNS]</ref>