DEV Community

Edward Hsing
Edward Hsing

Posted on

I Bought a Domain at 15. Now It Powers 400,000+ Users.

My name is Edward Hsing.

I’m 18, and I build internet infrastructure.

Today, something I started at 15 serves over 400,000 users, with more than 150,000 GitHub stars.

I was 15 when I bought a domain name.

I didn’t expect it to become something hundreds of thousands of people would end up using.

It wasn’t a startup.
It wasn’t a plan.

I just wanted to see what I could build.

At the time, getting a domain felt unnecessarily hard. It cost money, required setup, and for many people, it was simply out of reach.

That didn’t make sense to me.

So I started experimenting.

It Started With One Question

A friend asked me something simple:

“Can I use a subdomain under your domain?”

I said yes.

Then someone else asked.

And then another.

That was the moment it stopped being mine.

What began as a personal experiment quietly turned into something people started relying on in their projects.

Building Something That Didn’t Exist

There wasn’t a system for what I wanted to do.

No platform designed to let anyone register and manage domains freely, at scale.

So I built one.

That eventually became DigitalPlat FreeDomain - a platform that lets people register and manage domains freely, at scale.

I set up BIND9 on a small VPS.
Wrote my own backend in Python and Flask.
Connected everything directly to the DNS layer.

It wasn’t perfect.
It wasn’t elegant.

But it worked.

And people kept coming.

Growth Without Permission

There was no launch.
No marketing.
No funding.

Just developers sharing it with each other.

Hundreds of users turned into thousands.
Thousands turned into tens of thousands.

And eventually, something I built at 15 became infrastructure.

At some point, it stopped feeling like a project.

It felt like something people actually relied on.

Today, it serves over 400,000 users worldwide, with over 150,000 GitHub stars.

That still doesn’t feel real.

The Part No One Sees

People think building is the hard part.

It isn’t.

Keeping something alive is.

Running a free domain infrastructure means dealing with abuse at scale - spam, phishing, misuse.

You don’t get to ignore it. You have to design for it.

So I built systems to handle it:

Automated review pipelines.
Behavioral pattern scoring.
GitHub-based identity verification.
Structured abuse reporting and response.

Not to eliminate abuse completely - that’s impossible.

But to make sure everyone else can still use the system.

What This Was Really About

At some point, I realized this was never just about domains.

A domain is identity.

It’s the ability to exist on the internet — to build something, share something, create something that is yours.

And for a lot of people, that’s still harder than it should be.

I don’t think it should be.

Access to a digital identity shouldn’t be a privilege.

It should be a basic layer of the internet.

It Became Bigger Than Me

What started as something I built alone didn’t stay that way.

Some of the earliest users stayed.
They helped.
They contributed.

Today, people help manage reports, moderate discussions, and support the system.

It became something bigger than me.

And honestly, that’s the part I’m most proud of.

Looking Back

I didn’t set out to build infrastructure used by hundreds of thousands of people.

I just bought a domain and started experimenting.

But if you keep building - even when no one is watching, even when nothing is certain -

something small can turn into something that matters.

I’m 18 now.
I’m Edward Hsing.

And I’m still building things people rely on.

Because I believe the internet should be something people can access - not something they have to earn.

If you’re interested in how it works, the project is open on GitHub.

Top comments (12)

Collapse
 
itskondrat profile image
Mykola Kondratiuk

there is something about starting young that removes the fear of shipping something imperfect. most people who start later overthink the domain choice, the name, the whole thing. you just bought it and figured it out. that compounding effect over years is hard to replicate

Collapse
 
kiraniyerdev profile image
Kiran Iyer

I second everything he said!

Collapse
 
itskondrat profile image
Mykola Kondratiuk

Ha - appreciated. That instinct to ship before it is perfect is genuinely hard to teach to people who started cautious.

Collapse
 
ben profile image
Ben Halpern

The first website I ever made was using a free domain probably a lot like this service.

Collapse
 
eaglelucid profile image
Victor Okefie

The line that stays: "Growth without permission." That's not a marketing strategy, it's the natural result of building something that solves a problem so cleanly that people tell each other about it before you've even announced it. No launch, no funding, no permission. Just a thing that worked.

Collapse
 
apex_stack profile image
Apex Stack

The abuse-at-scale challenge you described is something I think about a lot. I'm running a programmatic financial data site with 8,000+ stock tickers across 12 languages, and the moment real users start depending on your data, the operational burden shifts from "fun project" to "infrastructure responsibility" almost overnight. Your approach of behavioral pattern scoring and GitHub-based identity verification is really clever — it's essentially using social proof as a spam filter, which scales way better than manual review. Curious whether you've seen patterns where certain TLDs or registration patterns correlate more strongly with abuse, since that kind of signal could help other infrastructure builders design better defaults.

Collapse
 
edwardhsing profile image
Edward Hsing

Yeah I’ve been trying to avoid heavy KYC for that reason.
GitHub OAuth helped mostly by adding friction. It doesn’t stop abuse, but it makes it slower and more expensive to scale, which already filters a lot.
On top of that I block some obvious keywords and patterns, especially stuff commonly used in abuse. Not perfect though, people still try to get around it with nested subdomains.
So a lot of it ends up being reactive too. I monitor abuse lists, work with some security providers, and automate takedowns when something shows up.

Collapse
 
klement_gunndu profile image
klement Gunndu

The part about keeping infrastructure alive being harder than building it really resonated. Ran a small open-source DNS tool for a while and the 3 AM alerts when something breaks hit different when people actually depend on it.

Collapse
 
edwardhsing profile image
Edward Hsing

yeah this part really hits

at some point it just stops being a side project and turns into something people actually depend on, and that feels very different

those 3am moments are real lol

Collapse
 
d3stiny_io profile image
D3stiny

Awesome 👏🥹

Collapse
 
msihlaz567 profile image
Msihlaz567

At 15 that’s impressive. Keep up the good work.

Collapse
 
kiraniyerdev profile image
Kiran Iyer

This is a fantastic story. Your transition from a 15-year-old’s curiosity to managing a registry for 400,000 users is genuinely inspiring.

I particularly appreciated your focus on the "unsexy" side of scaling—handling abuse and maintenance. Using GitHub-based verification as a low-friction "identity cost" is a brilliant, practical solution to the spam problem. It’s rare to see a post that balances indie-hacker success with such grounded technical honesty. Thanks for proving that digital identity can be a public utility rather than just a luxury!