DEV Community: Johnny Picante

What I Learned About TLD Marketing as an Indie Hacker

Johnny Picante — Thu, 25 Jun 2026 18:43:31 +0000

A 12-week retrospective on promoting .Vegas domains to the indie hacker community

When I started this campaign 12 weeks ago, I genuinely wasn't sure if promoting a geographic TLD to indie hackers made any sense. Most of us default to .com, .io, or .dev. The question wasn't whether .Vegas was a good domain — it was whether anyone in our community would see the value in something that, on the surface, sounds like it's only for Las Vegas businesses.

Here's what I learned.

1. The availability angle is real — and underused

The most surprising thing I discovered is how genuinely available .Vegas still is. In a world where every short .com is either taken or priced in the thousands, premium-keyword .Vegas names are sitting there for ~$15/year.

Just yesterday, bullseye.vegas was registered — through MarkMonitor, which handles enterprise brand protection. That's the same registrar used by major corporations to lock down their brand names. When enterprise brand teams start picking up .Vegas names, something is happening.

2. Indie hackers care about names more than they admit

I expected the reaction to .Vegas to be "why would I use that for my dev tool?" What I found was the opposite — project naming is one of the most discussed topics in the indie hacker community. People agonize over .io vs .co, debate whether a weird TLD hurts SEO, wonder if .ai makes their app sound smarter.

.Vegas plugs directly into that conversation. Not as a default, but as a deliberate choice — especially for projects with any entertainment, hospitality, events, or lifestyle angle.

3. Geographic TLDs aren't just for local businesses

This took a while to land. Vegas-the-place and Vegas-the-brand are different things. Las Vegas is one of the most globally recognized names on earth — hospitality, entertainment, nightlife, risk, fun, scale. A project called launch.vegas or events.vegas or network.vegas carries that connotation without needing to be physically located in Nevada.

The framing that worked best: "You don't have to be from Nashville to release a country album. You don't have to be in Vegas to build something that sounds like it means business."

4. Community-native posting is the only thing that works

Hard sells don't land anywhere, but they especially die on Hacker News, Reddit, and Indie Hackers. What worked was showing up with genuine curiosity — asking questions, sharing data, engaging with existing naming discussions. The posts that drove the most engagement were the ones where .Vegas was incidental to a larger conversation about branding, naming psychology, or domain investing.

The worst-performing content was anything that led with "you should register a .Vegas domain." The best-performing was "here's something interesting about how people choose domain names."

5. Renewals tell the real story

The single most convincing data point isn't registrations — it's renewals. The .Vegas registry processes 20–30+ renewals on a typical day. Yesterday: 30 renewals, 6 new registrations. People who registered .Vegas domains years ago are still keeping them. That's retention. That's conviction.

For a domain extension that critics say nobody uses, the renewal numbers tell a different story.

What I'd do differently

More case studies, fewer hypotheticals. Indie hackers respond to "here's a real project that used .Vegas and here's why" better than "here's what a project could look like on .Vegas." The challenge is finding those examples — they exist, but they're quiet about it.

I'd also go deeper on the SEO angle earlier. Local search optimization is one of the strongest arguments for geo-TLDs, and I underweighted it in the early weeks.

Final thought

If you're naming a project today — especially one in events, entertainment, hospitality, nightlife, or anything adjacent to Las Vegas — check .Vegas before you settle for a hyphenated .com. The inventory is still good, the price is still right, and the renewal numbers suggest this TLD has legs.

The best .Vegas names aren't gone yet. But they won't wait forever.

90 Days of Promoting .Vegas to Indie Hackers: What Actually Worked

Johnny Picante — Thu, 11 Jun 2026 18:43:13 +0000

Ninety days ago I set out to raise awareness for .Vegas domains among indie hackers — people building side projects, launching SaaS tools, creating portfolio sites. I had no budget, no ads, just public community posts across Dev.to, Indie Hackers, Reddit, Hacker News, and X.

Here's what I learned.

The Setup

.Vegas is a geographic top-level domain — like .io or .app, but tied to Las Vegas. Vegas is one of the most globally recognized brand names on earth. The bet was: does that geographic cachet have value for indie builders who have nothing to do with Las Vegas?

The answer turned out to be: sometimes yes, and the cases where it works are interesting.

What Didn't Work: The Hard Pitch

Early posts that led with "register your .Vegas domain" got ignored. Community-first platforms like Hacker News and Indie Hackers are allergic to anything that reads as promotion. I got zero traction on posts that felt like marketing, even lightly so.

Lesson: Don't pitch. Contribute first.

What Actually Worked

Genuine questions and discussions outperformed everything else.

The posts that got the most engagement were framed as questions or observations — "How do you pick domain names for side projects?" or "Does geo-TLD branding matter for a project with no geographic connection?" These threads generated real conversation, and .Vegas came up naturally as an interesting case study.

Specificity beats generality.

Generic posts about "domain name strategy" went nowhere. Posts that zoomed in on specific examples — "What would a Vegas-based coworking space called Stack.Vegas communicate vs StackWork.com?" — got picked up. People find concrete examples sticky. Just this week, someone registered stack.vegas — a perfect illustration of the kind of clean, memorable name that's still available on this TLD while the .com equivalent costs thousands on the aftermarket.

The indie hacker angle is real, not forced.

.Vegas domains average around $15/year. When your .com is taken and the aftermarket version is $3,000, a .Vegas alternative isn't a compromise — it might be an upgrade. Nightlife.Vegas reads better than NightlifeApp.com. BitcoinMondays.Vegas (yes, someone just registered that this week) is a perfect event brand name that would have cost a fortune on .com.

The argument for indie hackers isn't "move to Vegas." It's: you're naming a project, not filing a passport. The name needs to be memorable, available, and affordable. .Vegas checks all three if the name fits.

Long-form content built compounding authority.

Medium and Dev.to articles didn't go viral. But they created a body of work that I could reference in community threads without sounding self-promotional. "I wrote about this" is a much better reply than a purchase link.

X/Twitter worked best for name-level conversations.

Short posts like "Someone just registered stack.vegas — that's a clean domain for any dev tool or coworking brand" generated genuine replies. People have opinions about domain names. Give them something specific to react to.

The Numbers (Roughly)

Over 90 days across this campaign:

Consistent daily registrations — typically 3–10 new .Vegas domains per day
48 renewals in a single recent day, with 24 at premium pricing — suggesting holders believe in long-term value
Daily revenue in the $3K+ range from renewals alone

These aren't explosive numbers, but they're steady. The renewal rate in particular tells you something: people who registered .Vegas domains are keeping them.

What I'd Do Differently

Start with community presence before dropping any domain-related posts. Spend the first two weeks just being useful in the communities you want to participate in.
Build a portfolio of specific name examples early. "Here are 20 .Vegas names that would make incredible project brands" is more useful than any amount of strategic framing.
Use real registration data in posts. When I referenced names that were actually just registered that day — rather than hypothetical examples — the posts felt more credible and timely.

The Honest Take

.Vegas isn't for everyone. If your project has nothing to do with Vegas and you're not looking for a punchy, available, affordable domain alternative, don't bother.

But if you're naming a project today and the .com is gone? Worth ten minutes of your time to check what's available on .Vegas. You might be surprised what's still sitting there.

The naming landscape has changed. .io was "startup" a decade ago. .app has carved its niche. .Vegas is still wide open — the interesting names haven't been taken yet.

That window won't stay open forever.

5 side projects that would absolutely nail it on .Vegas

Johnny Picante — Fri, 29 May 2026 18:45:02 +0000

Most indie hackers I know spend an embarrassing amount of time on the naming part. We argue with ourselves over the perfect .com, eventually settle for some janky combo of words with random consonants ripped out, and ship a domain we secretly don't love.

There's a quieter option a lot of builders haven't seriously considered: .Vegas. It's a geographic TLD, but it does NOT require you to be in Las Vegas or build anything Vegas-related. What it does give you is a TLD that sounds bigger than it costs, reads as memorable, and is still wide open in 2026.

I went down a small rabbit hole this week looking at side-project ideas that would have an almost unfair head start on .Vegas. Here are five.

1. A weekend trip planner

Domain: weekend.vegas or trip.vegas

This is the lowest-hanging fruit and I'm honestly surprised nobody's built it yet. A tiny webapp that takes a Friday-to-Sunday window and spits back a fully booked itinerary: flight, hotel, two restaurant reservations, one show, one activity. Three clicks, done.

Why it works on .Vegas: the domain is the elevator pitch. Nobody needs to read your tagline. The URL bar tells you what the product does. That's worth more than most landing-page copy will ever earn.

2. A bachelor/bachelorette party coordinator

Domain: bach.vegas, party.vegas, last.vegas

Group-trip coordination is genuinely awful. Splitwise + a group chat + a shared Notion doc + that one friend who keeps forgetting to Venmo back. There's room for a niche product here that handles the deposit splits, the "who's in for the cabana" upsells, and the inevitable last-minute flight changes.

Why it works on .Vegas: the URL doubles as a tagline. You don't have to explain what kind of trip it's for.

3. A booking aggregator for shows and residencies

Domain: shows.vegas, tonight.vegas

Caesars, MGM, Live Nation, AXS, Vivid Seats, the venue's own ticketing system — finding a good show on a specific Tuesday night is a pain. A scraper-backed booking aggregator that's honest about its affiliate links could carve out a real niche.

Why it works on .Vegas: SEO. Geo-TLDs are a small but real signal for "this site is about Las Vegas," and you're going to be competing for keywords like "vegas shows tonight" anyway. Why fight it?

4. A local-business directory done right

Domain: eats.vegas, coffee.vegas, food.vegas

Yelp is bad and Google Maps is fine but generic. There's actual room for a curated, opinionated local directory in a high-tourism city — the kind of thing that includes one good sentence about each place instead of seventy reviews that contradict each other.

Why it works on .Vegas: a curated directory is exactly the kind of thing that benefits from a strong identity. eats.vegas immediately signals "small, local, opinionated." eats-vegas-guide.com signals "SEO farm, exit quickly."

5. A poker / blackjack / sports-betting tracker

Domain: track.vegas, bankroll.vegas, vig.vegas

I'd build this myself if I weren't already drowning in side projects. A clean web/mobile app that logs sessions, calculates bankroll variance, and gives honest reports on whether you're actually winning over time. The existing apps are dated and feature-bloated.

Why it works on .Vegas: trust signaling. A finance-adjacent product feels more credible on a geo-TLD than on bankrolltracker-app.io.

The honest part

None of these will succeed because of the domain. They'll succeed or fail on whether the product is good, whether you ship it, and whether you can find your first hundred users.

But the domain is a small accelerant. Memorable URLs get shared more in DMs. They get pronounced correctly on podcasts. They feel like a real company. And right now, in 2026, the best ones across .Vegas are still sitting on the shelf for ~$15.

If you're naming a side project this weekend and you haven't checked it as an option, take ten minutes and look. You might find something you like more than the weird .com variant you were settling for.

Have you built anything on a geo-TLD? I'd be curious how the conversions compare to a .com — drop a note in the comments.

The Case for .Vegas as Your Next Project Domain

Johnny Picante — Thu, 23 Apr 2026 16:19:15 +0000

Every developer I know has had the same moment. You finally come up with a project name you actually like. You type it into a registrar. It's taken. You add "app" to the end. Also taken. You try "get" in front. Parked since 2013. You settle on a five-word hyphenated compound that no human will ever type correctly, and you ship anyway.

I want to make a small argument for doing something different: consider a .vegas domain.

I know, I know. Bear with me for 700 words.

The TL;DR

.vegas is a geographic top-level domain, not a gimmick TLD. It was delegated in 2014 and is operated by the City of Las Vegas.
Premium one-word names are still largely available. Two-word names are almost entirely open.
Prices are comparable to .com — typically around $15-$40/year at most registrars.
You do not need to live in or be associated with Las Vegas to register one.
It's memorable in a way generic TLDs are not.

If that's enough to make you go check availability, great. If not, here's the longer case.

The "just ship" argument

Naming paralysis is the silent killer of side projects. I've watched more than one developer friend spend three weekends on branding and zero weekends on code. A lot of that paralysis comes from bouncing off unavailable .coms.

The value of moving to a different TLD isn't that it's better than .com in the abstract. It's that it restores the space of good names. The name you actually wanted — the short, clean, one-word version — is probably available on .vegas right now. You can register it today and get back to building.

The "memorable" argument

Generic TLDs (.io, .dev, .app) solve the availability problem but they don't really say anything. .vegas says something. Even if your project has nothing to do with gambling, entertainment, or the Strip, the word itself carries associations: bold, confident, larger-than-life, a little unserious in a way that can be charming.

That flavor is free branding. payments.vegas sounds like a product. stream.vegas sounds like a product. notes.vegas sounds like a product you'd want to at least click on.

Compare that to notes-app-v2.io.

"But what about SEO / email / trust?"

A few practical notes, because developers always want them:

SEO. Google has repeatedly said that new TLDs are treated the same as legacy TLDs for ranking. Geographic TLDs can carry a soft local signal but otherwise behave like any other domain. Your content and backlinks matter far more than your suffix.

Email deliverability. Modern mail providers (Gmail, Fastmail, Proton, etc.) handle new TLDs fine. Where you'll occasionally see trouble is enterprise spam filters that haven't updated their allowlists in a decade. If your audience is large enterprises with aggressive filters, test before committing.

User trust. This one is real but overstated. Users have been trained on .com, yes, but they've also seen .io, .ai, .dev, .xyz, .co become normal. A clean, short .vegas name in an address bar doesn't look suspicious — it looks distinctive.

Who this isn't for

A few honest caveats:

If your project is a direct-to-consumer app that needs to look as trustworthy as a bank to a 65-year-old, stick with .com.
If you plan to run a serious email newsletter to enterprise buyers, check with your ESP first.
If you've already got traction on another domain, don't move for aesthetic reasons.

Who it is for

Indie hackers launching something this weekend and tired of domain-squatter prices.
Developers naming an internal tool, CLI, API, or documentation site.
Anyone who actually has a Vegas connection and wants to lean into it.
Anyone who wants a name that sounds like a product, not a Kubernetes cluster.

A concrete exercise

Open a new tab. Think of the one-word name you actually wanted for your current project — the one that was taken. Go check it on .vegas. I'd be surprised if it isn't available.

That's really the whole argument. The best names you've been priced out of on the legacy TLDs are sitting on the shelf, at sticker price, on a TLD that makes your project sound a little cooler than it probably is.

You don't need to love Las Vegas to see the value. You just need to have spent one too many hours in a registrar search box.

Ship the thing.

If you've got a .vegas domain running in production, I'd love to hear what you're building in the comments.