Project ideas from Hacker News discussions.

Verisign .com Domain Name Registry Consumer Class Action

📝 Discussion Summary (Click to expand)

Theme 1 – Allegations of overpricing and the class‑action lawsuit
Many commenters treat the lawsuit against Verisign as the central issue, noting that proof is still lacking and that any settlement would likely benefit lawyers more than users.

  • aliasxneo: "I've always hypothesized this was going on. It'll be interesting to see the results."
  • jeroenhd: "No results yet, just allegations."
  • trilogic: "The real class action case is that the huge stream of money flow is not cashing in Europe at all, not a cent."
  • Kwpolska: "Great, I'm going to get a check for $0.01! Totally worth the millions the lawyers will get."

Theme 2 – Verisign’s operating costs and technical justification
A recurring debate centers on whether the reported ~$3 / domain cost (and the resulting retail price) is justified, with discussion of salaries, overhead, and the engineering effort needed to handle billions of DNS queries.

  • vlyan: >Verisign’s financial filings indicate it costs Verisign approximately $3 per domain to operate .com domains
  • 80fj0348i: "Most of the costs to provide digital services are salaries for the engineers. You need engineers, support staff, lawyers, and some supporting roles like finance and security/compliance to meet the legal and contractual obligations of the service."
  • jasode: "Putting ~170 million .com records into a RDBMS on a 90s computer is not enough infrastructure to serve ~746 billion DNS queries a day … They don't use off‑the‑shelf Redis/PostgreSQL/MySQL and they have more uptime reliability than Github, AWS us‑east‑1, Anthropic Claude, etc."
  • Arnt: "Fyi overhead often add anything up to 100% to the basic salary cost. Office space, hiring, travel, various forms of insurance, these things add up. And serving DNS for the root or a big zone is technically challenging."

Theme 3 – Concerns about centralization, control, and alternatives
Participants frequently raise worries about the concentration of power in a few registries (especially US‑controlled gTLDs), the susceptibility of ccTLDs to national government pressure, and the search for more decentralized or accountable naming systems.

  • trilogic: "If I buy a domain from and in Europe the money got to stay in Europe."
  • navigate8310: "Operators for gTLDs specifically .com .org .net serve large bases and operate under extensive contractual obligations, which can constrain arbitrary targeted enforcement. Than, some ccTLDs that have weaker mechanisms for appeal, leaving registrars and registrants exposed to discretionary decisions by the ccTLD operator or relevant national authorities"
  • chrismorgan: "It’s not just Verisign on .com; the entire gTLD system is corrupt (ccTLDs vary). .org and .info are probably even clearer examples."
  • raquuk: "Between memorable, decentralized, and secure, you can choose at most two."
  • mzajc: "Tor is great for this, as long as you're willing to put up with very long domain names, a mild amount of stigmatization, and an extra software requirement for visitors."

🚀 Project Ideas

Generating project ideas…

OpenRegistry Coop

Summary

  • A cooperative, non‑profit domain registration platform that lets users register .com‑equivalent names at cost‑plus pricing with full financial transparency and community governance.
  • Core value proposition: eliminates arbitrary price hikes by giving members visibility into actual operating costs and a democratic vote on fee adjustments.

Details

Key Value
Target Audience Individuals, small businesses, and developers frustrated with opaque .com pricing and registrar lock‑in
Core Feature Cost‑plus domain registration (registry fee + transparent margin) plus member‑driven governance via token‑less voting
Tech Stack Go backend, PostgreSQL, ICANN‑accredited registry API integration, React frontend, Docker deployment
Difficulty Medium
Monetization Revenue-ready: membership fee $2/mo per domain (covers ops)

Notes

  • HN commenters highlighted Verisign’s $3‑per‑domain cost and executive salary concerns; a coop would let members see those numbers and vote on margins (e.g., “I wonder how much those operating costs would fall if you slashed salaries…”).
  • Provides practical utility by offering a registrar alternative that can be used with existing DNS hosts, reducing reliance on profit‑driven entities.
  • Potential for discussion: could spark a new model for TLD governance and inspire similar coops for ccTLDs.

DomainCostWatch

Summary

  • A web app and browser extension that aggregates real‑time pricing, renewal fees, transfer‑lock policies, and hidden charges from major registrars, alerting users to price gouging or unfavorable terms.
  • Core value proposition: empowers users to make informed domain purchase/renewal decisions and avoid unexpected costs.

Details

Key Value
Target Audience Domain owners, freelancers, startups, and anyone managing multiple domains who dislike surprise price jumps
Core Feature Price comparison engine + renewal/transfer‑lock notifications + cost‑breakdown widget
Tech Stack Node.js/Express, PostgreSQL, scraper puppeteer/cloudflare workers, Vue.js frontend, Chrome/Firefox extension
Difficulty Low
Monetization Revenue-ready: freemium model – free basic alerts, premium $4/mo for advanced analytics and API access

Notes

  • Commenters lamented “I just renewed domain name I own for maybe 20+ years, for $23/yr. This is nuts.” and “Cloudflare sells domains at near cost, $10.46”. A tool that surfaces such disparities would be welcomed.
  • Users also discussed transfer lock frustrations (“you lock yourself in with your current registrar”) – the extension would warn about lock‑in periods.
  • Could foster discussion on registrar practices and encourage price transparency across the industry.

DidName

Summary

  • A decentralized identity naming service that lets users register human‑readable .did names resolved via DNSSEC‑enabled public resolvers, backed by a blockchain‑based ownership record, removing reliance on traditional TLD operators.
  • Core value proposition: provides censorship‑resistant, memorable identifiers without the fees or control of Verisign‑like registries.

Details

Key Value
Target Audience Developers, privacy‑advocates, and users seeking alternatives to traditional domains for personal sites, dApps, or crypto wallets
Core Feature Register .did names, manage ownership via smart contract, resolve via DNS-over-HTTPS using DNSSEC‑validated records
Tech Stack Ethereum L2 (Polygon) for name contract, Go DNS server with DNSSEC, Cloudflare Workers for DoH, Svelte wallet UI, IPFS for content
Difficulty High
Monetization Hobby (open‑source; optional donation via Gitcoin)

Notes

  • HN thread mentioned desire for “independent tld that’s not controlled by any entity” and explored decentralized schemes like Namecoin and .did via split DNS. DidName delivers exactly that with modern DNSSEC and blockchain.
  • Users noted “Since a majority of people use a handful of public DNS resolvers anyways, these resolvers could deploy split DNS for a special‑use domain…”. DidName integrates with existing resolvers, needing no special software.
  • Potential for discussion: could replace reliance on legacy TLDs, reduce costs, and address concerns about corporate overhead and government control.

Read Later