Google Registry is waking up three sleepers from the 2012 new gTLD application cycle - and I mean sleepers. .eat, .here, and .fly are finally heading toward market after years of quiet delegation.

If you registered your first .com in the 1990s, this feels familiar: another batch of extensions, another sunrise calendar, another round of "should I spec register this or touch grass?"

I pulled dates from Domain Name Wire and NamePros coverage. Here's my investor playbook - no hype, just timelines and traps.

What are .eat, .here, and .fly - and why now?

All three were part of the massive 2012 ICANN expansion round. Google applied for them. They were delegated years ago but largely sat unused - the registry equivalent of a fully built restaurant with the chairs still wrapped in plastic.

.fly has airline and travel DNA. .eat screams food, restaurants, delivery, and culinary media. .here is weirder - location, presence, "click here" wordplay, local guides. Each has natural verticals if Google prices them sanely.

Google Registry's model matters: they tend to enforce quality gates, require HTTPS on many strings, and run premium pricing on dictionary terms. That shapes who actually ends up owning the good stuff.

For domain investors, dormant TLD launches are double-edged. Early movers can snag meaningful names. Late movers inherit leftover inventory and renewal bills on names end users never type.

When is sunrise and general availability?

According to published timelines, sunrise runs roughly September 1 through November 9, 2026. That's the trademark-holder window - brands with registered marks get first shot via TMCH claims.

General availability is expected around mid-November 2026, though Google has adjusted TLD calendars before. I wouldn't book non-refundable launch parties on a single date.

Sunrise is expensive by design. If you're not a brand owner with a valid trademark submission, you're mostly watching from the sidelines - which is fine. GA is where investors and startups actually play.

Mark your registrar notifications now. Channels implement sunrise differently. Some make it easy; some bury the link under three menus and a captcha.

HTTPS requirement - don't skip this detail

Google has signaled HTTPS will be required on these extensions, consistent with other Google Registry TLDs like .app and .dev. If you're used to parking plain HTTP landers on speculative names, adjust your workflow.

For real products, HTTPS-forced extensions are a feature. For bare parking, you'll need TLS on every name or accept limited monetization. I consider that a quality filter, not a bug.

Should domain investors spec register .eat, .here, and .fly?

My honest answer: a little, not a lot. Google launches generate press and early liquidity on premium flips. They also produce graveyards of two-word leftovers nobody renews in year two.

I'd tier my interest:

  • High intent verticals - single-word food verbs on .eat, travel brands on .fly, local/hyperlocal plays on .here if pricing isn't absurd.
  • Brandable compounds - only if you have a buyer persona in mind, not "maybe a startup will want this."
  • Pure dictionary lottery - assume premium tiers and walk away unless you enjoy paying renewal rent on hope.

Compare this to buying established inventory on SaaS-ready domains you can sell today. A launch TLD is a bet on future demand curves. A strong .app or .com on DN Detector is a bet on present buyer behavior - which I prefer for cash flow.

Featured names like AudioNames.com already solve a branding problem this quarter. Waiting for November GA to name your product is a choice, not a strategy.

What does this mean for startups choosing extensions?

If you're a restaurant group, food creator platform, or travel app, these TLDs can be brilliant if you get a clean string at fair retail. "brand.eat" is memorable in a way "brand-delivery-hub.com" is not.

But remember extension literacy. My parents still type .com by reflex. .eat is cute in a pitch deck; it still needs marketing repetition.

For SaaS founders, I'd still default to .app or a solid .com for trust and email deliverability. Use .fly for travel-native products where the extension reinforces the story - not for generic B2B tools because the domain was on sale.

Internal linking habit: when clients ask me about new gTLDs, I send them to our acquisition FAQ and the live marketplace so they separate "cool launch" from "name we can actually close this week."

How do I prepare before November 2026?

Four weeks of prep beats four minutes of panic at GA:

  • Build a want list with alternates - your first choice will be premium or taken.
  • Fund registrar accounts and verify 2FA - GA drops reward ready wallets.
  • Check trademark conflicts even if you're not in sunrise; UDRP exists after launch too.
  • Set a hard budget - spec registries punish unlimited curiosity.
  • Watch NamePros and DNW for pricing leaks and early registrar beta programs.

I'll be tracking launch chatter on our blog. These Google TLDs won't replace .com - but they'll create niche winners, especially in food and travel media.

How do .eat, .here, and .fly compare to .app and .dev?

Google already runs disciplined extensions. .app and .dev succeeded because developers and product teams understood the contract: HTTPS required, clear category signal, premium pricing on gems.

.eat, .here, and .fly will likely follow the same playbook - which means quality names won't be $8 forever. If you're comparing launch speculation to buying a finished brand on DN Detector, ask which asset you can monetize in Q3 2026 versus Q1 2027.

.here is the wildcard. Location brands love it on paper. Typing it in conversation? "We're on here dot … here." Practice the pitch out loud before you register fifty variants.

.fly has the clearest buyer pool: travel, aviation, logistics, and experience marketplaces. .eat has the clearest consumer hook: restaurants, creators, meal kits, review sites. Match extension to story or skip it.

Which registrars will support sunrise - and what should you verify?

Not every registrar participates in every sunrise. Before September, confirm your account supports TMCH claims if you're a brand owner, or GA backorders if you're an investor.

Verify payment limits, corporate verification status, and whether your account manager can escalate during GA minute-one. I've seen premium strings slip away because a card limit blocked a $200 registration. Embarrassing and expensive.

Enable registry lock only after you understand transfer policies on new TLDs. Some launches have quirky transfer freezes in early days. Read the fine print - yes, actually read it.

If you're not chasing sunrise, use the next eight weeks to clean up your existing portfolio instead. Trim renewals, list underperformers, and fund a small GA war chest with a hard cap. Discipline beats FOMO.

Launch season is fun. It's also expensive. If you want a name you can ship on today, browse DN Detector - then optionally sprinkle .eat on top for your food side project.

- DN Detector editorial