RArasengan·Jan 15, 2021
You could also try running your own Handshake [1] node or SPV revolver [2] for uncensored DNS results.
[1] https://handshake.org
[2] https://GitHub.com/handshake-org/hnsd
In Dns.Watch: Public DNS Servershandshake-org
hnsd
C2019–2021
handshake-org / hnsd
hnsd
Handshake SPV name resolver
5Distinct people
8Mentions
0Explicit recommenders
310GitHub stars
What to know before exploring
What it is
Handshake SPV name resolver
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- handshake-org/hsd · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month8 dated mentions
Observed mentions: 2019-08-06 15:56:35 UTC to 2021-01-15 16:51:42 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 2019 | 2019-08-01 00:00:00 UTC | 2019-09-01 00:00:00 UTC | 2 | 0 | 2 |
| Sep 2019 | 2019-09-01 00:00:00 UTC | 2019-10-01 00:00:00 UTC | 2 | 0 | 2 |
| Oct 2019 | 2019-10-01 00:00:00 UTC | 2019-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2019 | 2019-11-01 00:00:00 UTC | 2019-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2019 | 2019-12-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2020 | 2020-01-01 00:00:00 UTC | 2020-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2020 | 2020-02-01 00:00:00 UTC | 2020-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2020 | 2020-03-01 00:00:00 UTC | 2020-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2020 | 2020-04-01 00:00:00 UTC | 2020-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2020 | 2020-05-01 00:00:00 UTC | 2020-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2020 | 2020-06-01 00:00:00 UTC | 2020-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2020 | 2020-07-01 00:00:00 UTC | 2020-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2020 | 2020-08-01 00:00:00 UTC | 2020-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2020 | 2020-09-01 00:00:00 UTC | 2020-10-01 00:00:00 UTC | 1 | 0 | 1 |
| Oct 2020 | 2020-10-01 00:00:00 UTC | 2020-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2020 | 2020-11-01 00:00:00 UTC | 2020-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2020 | 2020-12-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2021 | 2021-01-01 00:00:00 UTC | 2021-02-01 00:00:00 UTC | 3 | 0 | 3 |
What Hacker News says
3 sourcesHandshake has taken a lot of lessons from previous attempts at alternative blockchain DNS roots like NameCoin. Here are some ways its different:
- Handshake names are not *.bit domains like NameCoin they're actually top-level domains. This is because Handshake's purpose is not to decentralize domain names per se but too decentralize the root zone and create a more secure root of trust than Certificate Authorities [1]
- Handshake name auctions were spread out over the course of the first year after launch to prevent early adopters from hoarding all the good names. For instance, .crypto was available in the first few weeks after launch but .information isn't available until next week. This is important because early adopters hoarding names prevents latecomers from supporting the protocol.
- Handshake names are sold via vickrey auction inste
Read the rest
ad of a flat fee. Different names are more valuable than others. Flat fee pricing allows a hoarder to arbitrage that fact by being first whereas auction pricing ensures that names are better distributed. .X sold for 311k HNS[2] (about $40k) whereas other names sell for a few cents.
- Handshake has a light client[3] that can trustlessly verify DNS records on-chain. This is critical because very few people run full-nodes, so without a light client the majority of users would rely on third parties which provides worse security than users resolving names in a decentralized manner
[1] https://news.ycombinator.com/item?id=20995969
[2] https://namebase.io/domains/x
[3] https://github.com/handshake-org/hnsd
It resolves for me! Try installing a handshake resolver directly like hsd [1] for full chain or hnsd [2] for SPV.
[1] https://GitHub.com/handshake-org/hsd
[2] https://GitHub.com/handshake-org/hnsd
In Sci-Hub Is Now on the ‘Uncensorable Web’