Namebase Learning Center
HomeHelp & Support
English
English
  • Introduction
  • How to
    • Use Handshake names
    • Create Handshake websites
    • Handshake DNS
    • Access Handshake names
    • Get Handshake names
    • Buy Handshake coins (HNS)
    • Transferring HNS & Names
  • Handshake
    • About Handshake
    • Name minting auction
    • HNS coin economics
  • Namebase
    • Vision and mission
    • Private naming
    • Verifying
    • Security
    • Revenue streams
  • Development
    • Developer Guides
      • Traditional website
      • Decentralized website
      • Decentralized blog
      • Decentralized login
        • Handshake-based OIDC Authentication Protocol
        • Using Handshake Login
        • Handshake Login Implementation Guide
    • Resolving Handshake
      • HNS.to
      • HNSDoH
      • Resolving Handshake locally
        • Setting up the light client
        • Setting your Operating System DNS
    • Namebase Record Assistant
Powered by GitBook
LogoLogo

Connect

  • Twitter
  • Discord
  • Github

© 2022 Namebase, Inc

On this page
  • Hosting providers
  • HTTPS

Was this helpful?

Edit on GitHub
  1. Development
  2. Developer Guides

Traditional website

Use a Handshake name as the domain for your traditional website

PreviousDeveloper GuidesNextDecentralized website

Last updated 2 years ago

Was this helpful?

With Handshake, you can use both your root name (i.e. ) and a subdomain (i.e. ) as the domain for your traditional websites.

Conceptually all you have to do is set resource records like A records and CNAME records just like you would with a traditional domain. However, root resource records are , so you need to set an NS record on your root name pointing to a nameserver in order to set A and CNAME records.

If you register your name on Namebase, we configure this automatically for you and provide a free nameserver you can use as well.

Once you've set up your Handshake website, follow this guide to learn how to resolve them on any of your devices.

Hosting providers

If a hosting provider doesn't support Handshake, it's most likely because they have a verification step for custom domains that checks if the custom domain is a valid ICANN domain. In that case, we recommend writing to the hosting provider to relax their verification so that Handshake domains work as well. This is what was done in the case of Vercel.

HTTPS

You can also follow this guide to use your own nameserver:

Many hosting providers such as Vercel, Heroku, and GitHub Pages work with Handshake names. Community members have documented how to use many of them in our general .

One of Handshake's primary goals is to replace CAs with a more secure blockchain-based root of trust. provides an overview of the concept, and community members have documented how to set up HTTPS websites using Handshake in our .

Note that end-user configuration is necessary to visit Handshake HTTPs sites until browsers support it natively. A client app can be created to make this configuration easier in the meantime but such an app doesn't currently exist (if you're interested in making this let the know!).

Setting up a Handshake TLD with a hosted DNS service
Resolving Handshake
Learning Center
This article
Learning Center
community
nb/
welcome.nb/
limited