What if every self-hosting enthusiast could claim a free, legitimate top-level domain designed specifically for their homelab — no squatters, no auction fees, and no dynamic DNS hacks? The Human-Centered Computing Foundation (HCCF) is proposing exactly that: .self, a gTLD built from the ground up for one person, one verified subdomain, and nothing else.
What Is the .self TLD Proposal?
Video: ICANN’s official overview of the 2026 New gTLD Program — the application process behind the .self proposal. Watch on YouTube
The HCCF — a 501(c)(3) nonprofit — has submitted an application to ICANN for a new generic Top-Level Domain called .self under the organization’s 2026 application round (window: April 30 – August 12, 2026). Unlike every other TLD in operation, .self is designed exclusively for individuals running their own infrastructure. No corporate branding, no domain squatting, no resale market — just a free, verified subdomain for every person on Earth who wants to self-host.
The foundation has already qualified for ICANN’s Applicant Support Program (ASP), which reduces the standard $227,000 application fee by 75–85%, bringing HCCF’s out-of-pocket cost to roughly $34,000–$57,000. The organization is also running a crowdfunding campaign via Zeffy to cover the remainder, with 100% of donations going directly to the mission.
One Person, One Subdomain: How .self Works
According to the official .self gTLD proposal PDF published June 16, 2026, the core model is refreshingly simple. Within hours of appearing on Hacker News, the discussion surged to the #1 spot with 294 points and over 170 comments — a clear sign of the community’s hunger for a dedicated self-hosting namespace.
One subdomain per verified person — no parking, no squatting, no reselling. Each individual gets exactly one free subdomain under .self for life.
Built-in identity verification — HCCF is evaluating zero-knowledge proof (ZKP) systems (including Microsoft Vega-style identity proposals) to tie each subdomain to a real person without exposing private data. Worst case, they start with credit-card verification and iterate.
48- to 64-bit subdomain namespace — enough room to give every person on Earth a unique address (7 billion people needs ~33 bits; the plan allocates 40+ bits for future-proofing).
Non-transferable, non-sellable — domains cannot be sold or transferred. If a subdomain is listed for sale, it is forfeited.
Shared Public-Good Services
HCCF plans to bundle a suite of shared infrastructure services that remove the hardest parts of self-hosting:
All shared services will ship as open-source client software — HCCF frames this as a public-good infrastructure layer, similar to what projects like Instatic do for self-hosted publishing: remove the friction, let the community build on top.
The Self-Hosting Boom Backs the Vision
The proposal arrives at a perfect moment. The global self-hosting market was valued at $15.6 billion in 2024 and is projected to hit $85.2 billion by 2034 — a compound annual growth rate of 18.5%. As more users move away from big-tech platforms and toward running their own infrastructure, the need for a dedicated, reputable namespace becomes urgent.
Existing workarounds — free subdomain services like .duckdns.org, mDNS via .home.arpa, or paid .com/.net domains — each come with tradeoffs. DuckDNS works but brands every URL with a third-party domain. .home.arpa is excellent for local networks but invisible to the public internet. Traditional TLDs cost money and invite competition with squatters. HCCF’s .self aims to be the first namespace that solves all three constraints simultaneously.
The Community Debate: Hope Meets Hard Questions
When HCCF posted the proposal to Hacker News on June 30, 2026, it rocketed to the #1 spot with 294 points and 171 comments in hours. The reception revealed a deeply divided but engaged community.
What Enthusiasts Love
A TLD that finally “gets” self-hosting. HN users immediately started brainstorming subdomains — my.self, home.self, lab.self — with the kind of excitement that only a genuinely felt pain point creates.
The public-good funding model. HCCF explicitly compares itself to the Internet Security Research Group (ISRG) and Let’s Encrypt — a nonprofit operating critical internet infrastructure through sponsorships from self-hosted software companies, ISPs, registrars, and digital rights organizations.
Community-driven governance. Every feature, restriction, and policy will be guided by community input, not corporate boardrooms.
Real Skepticism, Valid Concerns
The fundamental tension: “Free domain + free choice = squatting crisis” was one of the sharpest HN observations. History has shown that free TLDs — most infamously .tk — eventually get blocked by browsers and antivirus software after being overrun by scammers and abusers.
TLS trust chain complications. Using .self domains publicly means every browser and client needs to trust .self’s root Certificate Authority — a non-trivial distribution problem that could take years to resolve.
Proof-of-use renewals add friction. HCCF’s proposed heartbeat mechanism (periodic DNS TXT updates to prove the domain is still actively used) undermines the “set it and forget it” appeal of self-hosting.
ICANN costs are real, even with the ASP discount. One commenter with registry experience noted: “The DNS traffic for a million-domain .self is a few TB per month — hobby project money. The real costs are legal and compliance: EPP, RDAP, and the hundreds-of-pages ICANN registry agreement.”
How .self Compares to Current Self-Hosting Domain Options
Video: Setting up a real DNS server at home for self-hosting — the kind of infrastructure a .self TLD would make easier. Watch on YouTube
Why This Matters for Your Homelab
If .self clears ICANN evaluation — a multi-year process that could stretch into 2028 or beyond — it would fundamentally change the economics of running a personal server. Imagine pointing your FlowLauncher dashboard to a lab.self address, hosting your wiki at wiki.self, or serving a portfolio from you.self — all without a registrar bill, all backed by a TLD purpose-built for infrastructure you control.
HCCF’s approach deliberately mirrors the low-friction, optimization-first philosophy we’ve seen reshape adjacent tech spaces: remove the barriers, standardize the infrastructure, and let the community innovate on top.
The Bottom Line
The .self TLD is still a proposal — it has not been approved by ICANN, and the evaluation process will take years. But the fact that a nonprofit has qualified for ICANN’s Applicant Support Program, published a detailed technical proposal, raised community funding, and sparked the most engaged HN thread of the day around a domain namespace says something powerful: the demand for a self-hosting-native TLD is real, urgent, and growing alongside the market it serves.
Whether .self becomes the “Let’s Encrypt of domains” or a cautionary tale about free-TLD economics depends on decisions HCCF is making right now — about identity verification, anti-abuse enforcement, and governance transparency. Either way, it’s the most interesting thing to happen to the domain name system since new gTLDs launched in 2012.
Want more deep dives on the infrastructure powering the self-hosting revolution? Bookmark TekMag for the latest on open-source tools, domain tech, and the movement to take back control of your digital life.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the .self TLD?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The .self TLD is a proposed generic Top-Level Domain by the Human-Centered Computing Foundation (HCCF), designed exclusively for individual self-hosting. Every verified person gets one free subdomain under .self — no squatting, reselling, or corporate use allowed."
}
},
{
"@type": "Question",
"name": "How much does a .self domain cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A .self subdomain is completely free for verified individuals. HCCF qualified for ICANN's Applicant Support Program, reducing the $227,000 application fee by 75–85%, and plans to fund ongoing operations through sponsorships from self-hosted software companies, ISPs, and digital rights organizations — similar to the Let's Encrypt/ISRG model."
}
},
{
"@type": "Question",
"name": "When will .self domains be available?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The ICANN application window runs April 30 – August 12, 2026, but the full evaluation process typically takes multiple years. If approved, .self domains likely won't be available until 2028 or later. HCCF is currently running its staging infrastructure at hccf.onmy.cloud for early testing and community feedback."
}
}
]
}
Originally published on TekMag.
Top comments (0)