Handshake & HNS Names
Handshake is a naming protocol that’s backward-compatible with the existing DNS system and has a deep integration in Skynet.
Skynet uses Handshake as a human-readable naming layer. We do not resolve on their DNS A records, but rather just look for a TXT entry containing a skylink. Skynet Web Portals run full Handshake nodes and do not rely on any centralized services to obtain information about the blockchain.
Because we only rely on blockchain records, we do not support subdomains, secondary name servers, or any records you might set in the "Namebase nameserver DNS records" section on Namebase.io.
Handshake DNS Using a Skylink
When setting a TXT record for your domain, use a skylink format starting with
sia://— this can be a Skylink directly referencing your web app, or a resolver skylink that can be updated to point at other skylinks. Updating a resolver skylink will propagate much faster than modifying your DNS records on the Handshake blockchain, a process which can take several hours. See Resolver Skylinks for more info.
To determine where an HNS name is set to resolve, make a GET request to
An example can be seen here, or try using the widget below, which takes advantage of the
Type Your HNS Name to Where a Web Portal Resolves It
If you want to use your TLD name for hosting a site, dLinks lets you setup a profile page that is deployed to and hosted on Siasky.net. You can use the DNS settings it automatically sets up to point to any skylink or resolver skylink.
This Namebase documentation shows how to manually set the DNS records in the Namebase nameserver DNS records to use their Skynet resolver. Use
_contenthashand a skylink for TXT records and
sia.namebase.io.as the value of an ALIAS record on the
@root or a CNAME record on your subdomain.
A TLD and SLD each using Skynet-hosted Sites