How hns.best Works
Understanding how we resolve Handshake domains and the best ways to configure your site for maximum compatibility.
The Resolution Journey
1. Request
User visits name.hns.best
2. Lookup
Gateway queries
HNS Blockchain
3. Records
Finds A, CNAME,
TXT, or NS
4. Action
Proxies Content
or Redirects
✓ Recommended Configurations
A Record (Direct IP)
The most reliable method. Points your domain directly to a server's IP address.
Redirect (TXT url=)
Perfect for forwarding to an existing Web2 site (like Twitter or Substack).
IPFS (Decentralized)
True Web3 hosting. We use public IPFS gateways to serve your content.
⚠️ Use With Caution
NS (Delegation)
Delegating to another nameserver (like ns1.hnsbroker.com) adds complexity.
Our gateway must be able to reach that nameserver to resolve the final IP.
If that nameserver is slow or blocks our queries, your site won't load.
CNAME (Alias)
Works well for platforms like GitHub Pages, but can be tricky with SSL/TLS. Ensure your provider knows how to handle the request.
Why isn't my site working?
1. DNSSEC Failures
If you enabled DNSSEC but your keys are invalid or expired, strict resolvers will reject your domain. Our gateway is lenient, but browsers running HNS resolvers locally might block it.
2. Unreachable Nameservers
If you use NS records, ensure your nameserver allows queries from public IPs and is online. Self-hosting a nameserver at home often fails due to firewalls.
3. Missing Records
Buying the name isn't enough! You must set records (A, TXT, etc.) on the blockchain or your registrar. Use our Debug Tool to check.
Need more help? Check out host.limo for easy HNS hosting.