If you've ever felt uneasy about how much of your life lives on servers you don't control, that feeling is worth listening to. This post is for anyone — especially girls and women, who are disproportionately targeted by doxxing and stalking — who wants a clear, no-jargon explanation of how owning your own digital identity can make you measurably harder to track down.
The problem: your name lives in someone else's database
Every time you sign up for a website, register a domain through a traditional registrar, or create a social profile, your information gets stored in a centralized database. That database belongs to a company, not to you. It can be:
- Scraped by bots that harvest names, emails, and addresses for resale or harassment campaigns
- Leaked when the company suffers a breach (and most companies eventually do)
- Subpoenaed or handed over without your knowledge or consent
- Looked up through WHOIS records if you've ever registered a traditional domain name in your own name
This is how doxxing usually starts. Someone doesn't need to "hack" you — they just need to find the one database where your real name, address, or phone number was sitting in plain text, waiting.
What changes with a self-controlled Handshake name
Handshake (HNS) is a decentralized naming protocol. Instead of a company holding your name in a centralized registry, ownership lives on a blockchain and is controlled by a private key only you hold. There's no central WHOIS database listing your real name and address next to your domain. No company support desk that can be tricked or pressured into handing over your account. No single server that, if breached, exposes a list of registrants.
In practice, this means:
- No forced personal information. Traditional domain registration in many countries requires submitting your real name, address, and phone number to the registrar. Handshake names don't require this at the protocol level.
- No centralized point of failure. There's no single company database that, if breached or subpoenaed, hands someone your real-world details.
- You hold the keys. Ownership is cryptographic, not custodial — nobody can be socially engineered into transferring your name to a stalker the way a registrar's customer support sometimes can be.
Resolving your name safely
Owning the name is half the picture; resolving it matters too. Using a resolver that respects this decentralized model — like the open-source SkyInclude Browser — keeps your lookups from routing back through centralized DNS providers that log queries. We specifically avoid recommending NextDNS or HDNS.io for this reason, since they reintroduce a centralized logging layer that undercuts the privacy benefit.
A simple way to think about it
Imagine your identity as a house. A centralized account is like renting an apartment where the landlord keeps a copy of your key, your name, and your address on file — and any of their employees, or anyone who hacks their office, can get to it. A self-controlled Handshake name is like owning a house outright: you hold the only key, and there's no landlord's filing cabinet for someone to break into.
Practical first steps
- Learn the basics of how HNS auctions and ownership work before registering anything
- Choose a name that doesn't reveal personal details you wouldn't want public
- Store your private keys offline, the same way you'd protect any other valuable credential
- Use a decentralized-friendly resolver rather than a centralized DNS-over-HTTPS provider
Digital safety isn't about disappearing from the internet — it's about deciding, on your own terms, what's visible and what isn't. Owning your name instead of renting it is one of the clearest ways to take that control back.
Published by NIHON — Handshake Infrastructure & Web3 Identity.