analysis .foo - gTLD (Generic Top-Level domain)

[Eric Lyon]

Today, I'll be analyzing the .foo gTLD to see if I can dig up any helpful data points that could be stacked with someone elses research into the .foo extension.

The registry for the .foo gTLD is Charleston Road Registry Inc., which is a wholly owned subsidiary of Google. Operating under the name Google Registry, they have managed the .foo top-level domain since it was delegated in 2014

Source

Anyone can register a .foo gTLD on a first-come, first-served basis, as there are no specific eligibility restrictions. While targeted at developers and tech enthusiasts for projects and portfolios, it is available to the general public. A key requirement is that HTTPS is mandatory for all .foo websites to work properly

Source

Note: At the time of this analysis, there was a 1-character minimum to register a .foo domain. There were also a lot of 1-character .foo domains available to register, but with a low-4-figure premium registration cost.

With the above in mind, lets dive right in...

.foo domain registration costs​

According to Tldes.com the .foo registration cost ranges from $9.81 to $15.14.

.foo domains registered today​

According to DNS.Coffee there are 4,186 .foo domains registered today.

Public .foo domain sales reports​

It's hard to find any .foo domain sales reports online, indicating they are all privately sold.

Note: NameBio.com shows "0" .foo domain sales.

5-year .foo domain growth summary​

The registration history of the .foo gTLD shows a distinct transition from a dormant, restricted extension to a growing niche for the developer community. Based on data from DNS.Coffee, the last five years reveal a massive 12,211% total growth since 2021.

.foo Yearly Registration Growth (2021–2026)
The following totals from DNS.Coffee illustrate the growth trajectory:

• April 2021: 34 registrations
• April 2022: 35 registrations
• April 2023: 61 registrations
• April 2024: 2,497 registrations
• April 2025: 2,965 registrations
• April 2026: 4,186 registrations

Growth Analysis & Key Milestones

The Pre-Launch Plateau (2021–2023)
For the first three years of this period, the .foo gTLD was essentially stagnant, with registrations remaining below 100. During this time, the extension was likely in a "Sunrise" or limited-access phase, or simply not yet marketed to the general public by Google Registry.

The General Availability Explosion (2023–2024)
The most significant turning point occurred between April 2023 and April 2024, when registrations jumped from 61 to 2,497, a staggering 3,993% increase in a single year. This corresponds with Google opening the extension for General Availability in late 2023, allowing anyone to register names on a first-come, first-served basis.

Steady Market Adoption (2025–2026)
Since the initial surge, growth has remained consistent:

• 2024 to 2025: Growth slowed to a steady 18.7% as the initial "gold rush" for short or clever names concluded.
• 2025 to 2026: Growth accelerated again by 41.2%, bringing the current total to 4,186 domains. This suggests that while NameBio.com still shows 0 public sales, the primary market is gaining momentum as more developers discover the extension.

Note: Despite the impressive growth percentages, the absolute number of 4,186 registrations confirms that .foo remains a highly specialized namespace. The lack of secondary market sales indicates that users are registering these domains for personal use, technical projects, or developer branding rather than for financial speculation.

8 niches for .foo domains​

1. Placeholder & Sandbox Environments
Because "foo" is the industry-standard metasyntactic variable, this is the primary niche for developers. It is used for temporary staging sites, API testing environments, and "sandbox" versions of applications where code is vetted before moving to a production domain like .com.
2. Coding Tutorials & Documentation
Educational platforms and individual developers use .foo for instructional content. It provides a clever, "on-brand" URL for syntax guides, "Hello World" examples, and documentation repositories that cater specifically to students of computer science.
3. Cybersecurity & "Ethical Hacking" Portfolios
The mandatory HSTS/SSL security requirement makes .foo naturally attractive to security professionals. It serves as a subtle signal of technical competence for penetration testers and researchers who want their personal portfolio to reside on a "secure-by-default" extension.
4. Developer Humor & Personal Branding
The extension is a "tech-insider" joke. It is a top choice for personal blogs, resumes, or landing pages for software engineers who want to showcase their personality. A name like [FirstName].foo is a distinctive alternative to the more crowded .dev space.
5. Open Source Project Mirrors
Small-to-medium open-source projects often use .foo for mirror sites or community-run forks. Given the low registration cost (approximately $10.18 on Cloudflare), it is an affordable way for contributors to host experimental versions of shared code.
6. Tech-Themed URL Shorteners
Companies and influencers in the DevOps or Engineering space use .foo to create branded, short links for social media. Because the extension is only three characters long, it is ideal for creating concise redirects for GitHub repos or technical whitepapers.
7. "Esoteric" Programming Language (Esolang) Hubs
The "quirky" nature of the name appeals to the niche community of esoteric programming languages (like Brainfuck or Piet). It is frequently used for hosting compilers, interpreters, or galleries of code written in non-traditional languages.
8. Local Dev Tooling & Utilities
Developers of CLI (Command Line Interface) tools or browser extensions often use .foo for the official landing page of their utility. It fits the "utility-first" aesthetic of the command line, where "foo" and "bar" are constants in daily workflows.

What a .foo domain hack might look like​

Since the .foo extension is short and ends in a double "o," it’s a great candidate for domain hacks, the practice of combining the word before the dot with the extension after the dot to spell a full word or phrase. With 4,186 registrations currently reported by DNS.Coffee, many common English words ending in "foo" or "fo" may already be taken, but the creative possibilities remain a major draw for this gTLD.

The "Full Word" Hack
This is the most common method, where the domain name and the extension combine to spell a single dictionary word.

• Sea.foo (Seafood)
• Kung.foo (Kung Fu)
• Tofu.foo (To-fu) – A repetitive but memorable play on the "fu" sound.
• Snave.foo (Snafoo/Snafu) – A play on the military slang for a chaotic situation.

The Phonetic "Full" Hack
Since "foo" is phonetically identical to "full," many hacks use the extension to complete words that end in that sound.

• Beauti.foo (Beautiful)
• Success.foo (Success-full)
• Power.foo (Powerful)
• Grace.foo (Graceful)

The "Action" or "State" Hack
This uses the "foo" extension to represent the concept of a "fool" or "fooling around," often used for entertainment or prank sites.

• April.foo (April Fool)
• DontBeA.foo (Don't be a fool)
• Dancing.foo (Dancing fool)

The "Language & Culture" Hack
In some languages or subcultures, "fu" or "foo" has specific meanings (like "luck" or "wealth" in Chinese transliterations), allowing for cultural hacks.

• GoodLuck.foo
• Kung.foo (As mentioned, referencing the martial art).

The "Developer Humor" Hack
Because developers already use "foo" as a placeholder, the hack is often meta—referencing the code itself.

• Bar.foo (A play on the "foobar" sequence).
• Git.foo (A play on "git" and "foo").

Note: While these hacks are clever, remember that NameBio.com currently shows 0 public sales for .foo. This means that while a hack like Sea.foo might be a fun brand, its resale value is currently unproven in the secondary market. Additionally, you will still need an SSL certificate for any of these "hacks" to load properly in a browser.

9 lead sources for .foo domain outbound campaigns​

1. GitHub (User Repositories & Profiles)
This is the "home" of the .foo audience. Search for developers who have popular repositories or unique project names that would pair well with a .foo extension (e.g., a project named "Snafu" is a perfect lead for sna.foo).

• Strategy: Look for users with "Foo" in their repository titles or example code.

2. Stack Overflow (Power Users)
Identify users who contribute heavily to tags like python, javascript, or devops. These users understand the "foobar" reference and are the most likely to appreciate a .foo domain for a personal portfolio or technical blog.

• Strategy: Target users who have "Developer Story" profiles or links to personal sites that currently use clunky subdomains.

3. Niche Job Boards (Hiring Managers in Tech)
Browse boards like Dice, Hacker News (Who is Hiring), or AngelList (Wellfound). Companies looking for "Creative Engineers" or "Full Stack Developers" might find a .foo domain to be a clever recruiting landing page (e.g., JoinOur.foo).

4. Product Hunt (New Launches)
Monitor daily launches for developer tools, APIs, or "indie hacker" projects. If a product has a long or complicated URL, they are prime candidates for a shorter, punchier .foo redirect or "sandbox" domain.

5. Dictionary-Based "Word Endings" Lists
Since domain hacks are a primary use case, use a tool like MoreWords or WordHippo to export lists of words ending in "ful," "foo," or "fu."

• Strategy: Cross-reference these words with active businesses (e.g., a seafood restaurant named "Ocean's Bounty" is a lead for OceanSea.foo).

6. Twitter/X (Tech Influencers & DevRel)
Follow hashtags like #100DaysOfCode, #DevRel, and #CodeNewbie. Influencers in these spaces often look for unique branding to stand out. A .foo domain fits the "quirky tech" aesthetic perfectly.

7. Reddit (r/webdev, r/programming, r/cscareerquestions)
Monitor discussions where users ask for advice on personal branding or "what to name my project." You can identify leads who are actively seeking a domain but haven't committed to one yet.

8. Upwork/Fiverr (Web Developers)
Look for freelancers who specialize in building "Developer Portfolios" or "Landing Pages." These professionals are "influencer leads"—if you convince them of the value of .foo, they may recommend it to dozens of their future clients.

9. Local "Kung Fu" or "Tofu" Businesses
For the "phonetic hack" niche, search local business directories (Yelp/Google Maps) for businesses where "Foo" or "Fu" is part of the brand. A martial arts studio using CityKungFu.com might find CityKung.foo to be a much more memorable marketing URL.

Helpful Outbound articles and tools

• How to leverage an Ai Assistant to find domain leads
• How to leverage Social media to find domain leads
• How to leverage Job Boards to find domain leads
• eMail Marketing Best Practices for Domain Outreach
• List of FREE tools for outbound domain sales
• Outbound Domain sales Tips

Legal considerations when selling a domain to an existing business​

Approaching a business to sell a domain name that matches or mimics their trademark is a legal minefield. Because the .foo extension is often used for "hacks" (like brand.foo), you are at a higher risk of being flagged for cybersquatting.

The Anticybersquatting Consumer Protection Act (ACPA)
In the U.S., the ACPA allows trademark owners to sue domain registrants who, in bad faith, register or use a domain that is identical or confusingly similar to a distinctive mark.

• The Risk: If a court determines you registered a .foo domain specifically to "extort" a trademark holder, you could be liable for statutory damages ranging from $1,000 to $100,000 per domain.
• "Bad Faith" Indicators: Proposing a sale price that is significantly higher than your out-of-pocket costs (like the $10.18 registration fee) can be used as evidence of bad faith.

Uniform Domain-Name Dispute-Resolution Policy (UDRP)
This is the process used by ICANN (the governing body for domains) to resolve disputes. To lose a domain via UDRP, the trademark holder must prove three things:

1. The domain is confusingly similar to their trademark.
2. You have no rights or legitimate interests in the domain (e.g., you aren't actually running a business called "Sea.foo").
3. The domain was registered and is being used in bad faith.

• The .foo Catch: Since NameBio.com shows 0 public sales, you cannot easily argue that the domain has a high "market value" based on previous comps. This makes it harder to defend a high asking price against a UDRP claim.

Trademark Dilution and Infringement
Even if you aren't "squatting," using a domain in a way that weakens a famous brand’s identity is called dilution.

• Example: If you register Apple.foo and host a tech blog, Apple Inc. can claim infringement because users might mistakenly believe the site is an official Apple developer sandbox.
• The "Confusion" Test: Courts look at whether an "ordinary consumer" would be confused about the source or sponsorship of the website.

Reverse Domain Name Hijacking (RDNH)
On the flip side, if you have a legitimate reason for owning the domain (e.g., your name is "John Foo" and you own John.foo), and a big company tries to bully you into giving it up via legal threats, they can be found guilty of RDNH. However, this is an expensive and difficult defense to mount.

Potential Outbound Campaign Strategy:

• Check the USPTO Database: Before buying a .foo domain, search the USPTO TESS database to see if the word is a registered trademark in a relevant class.
• Avoid "Cold Selling" High Prices: Avoid emails that say, "I have your trademarked name, pay me $5,000." Instead, frame the domain as a brand asset you are looking to rehome.
• Establish a "Legitimate Use": If you are holding a domain, having a landing page that shows a non-competing, legitimate use (like a developer project or a "coming soon" for a unique blog) provides a better legal defense than a "This Domain is For Sale" parking page.

Potential .foo domain investing strategy​

Based on our analysis of the current market data, specifically the 4,186 registrations reported by DNS.Coffee, the 0 public sales recorded on NameBio.com, and the mandatory HSTS/SSL security requirements, the best investment strategy for .foo is not a traditional "buy and flip" model. Instead, it should be a Utility-Driven Branding strategy. Because there is no established secondary market, you cannot rely on "hope as a strategy." You must focus on domains that have immediate, intrinsic value to a very specific end-user.

The "Developer-First" Portfolio
Since the audience is almost exclusively technical, your "inventory" should reflect developer culture.

• The Play: Register short, punchy terms related to the "foobar" ecosystem or CLI (Command Line Interface) terminology.
• Targets: Terms like Sna.foo, Debug.foo, Script.foo, or Deploy.foo.
• Why: These are the leads most likely to pay a modest premium ($100–$500) to have a "cool" vanity URL for their open-source projects or personal portfolios.

High-Quality Phonetic Hacks
Traditional domain hacks use suffixes to complete words. With .foo, you are specifically looking for words ending in the "full" or "foo" sound.

• The Play: Use tools to find dictionary words that end in "ful" and check for availability.
• Targets: Beauti.foo, Grace.foo, or Success.foo.
• Why: These have "cross-over" appeal outside of the tech niche. A lifestyle influencer or a boutique brand might be willing to adopt a .foo hack if the .com and .net are unavailable.

The "Secure Sandbox" Pitch
Position your domains as functional assets rather than just names.

• The Play: Focus on the security aspect of the gTLD. Because .foo is on the HSTS preload list, it is "secure by default."
• Targets: Names like Vault.foo, Safe.foo, or Auth.foo.
• Why: You aren't selling a name; you are selling a pre-configured secure environment for a company’s internal staging or testing site.

Conservative "Hold" Strategy
Since Cloudflare offers these domains at a wholesale price of $10.18, the "carrying cost" (annual renewal) is very low.

• The Play: Build a small, high-quality portfolio of 10–20 names rather than 1,000 mediocre ones.
• Why: With zero public sales on NameBio, you should treat .foo as a long-term speculative play. If the registry grows from 4,186 to 40,000 in the next few years, the first secondary sales will likely be the "purest" hacks (like Kung.foo or Sea.foo).

Outbound-Only Monetization
Do not wait for buyers to find you. Because there is no "market" yet, you must create the market.

• The Play: Use the GitHub and Product Hunt lead-gen strategy we discussed. When you see a high-growth project with a name that fits your domain, reach out immediately.
• Why: A developer who just got 5,000 stars on GitHub is your highest-probability buyer. They have the "social capital" and the technical need for a branded .foo redirect.

Summary Checklist for Your Potential Strategy:

1. Low Volume, High Quality: Only register names that make sense as a word or a famous tech phrase.
2. Avoid Trademarks: Given the 0 sales history, the legal risk of "brand.foo" far outweighs the potential $10 registration profit.
3. Price for Liquidity: Since there are no $10,000 sales yet, aim for "impulse buy" pricing (e.g., $199–$499) when performing outbound.

Helpful Outbound articles and tools

• How to leverage an Ai Assistant to find domain leads
• How to leverage Social media to find domain leads
• How to leverage Job Boards to find domain leads
• eMail Marketing Best Practices for Domain Outreach
• List of FREE tools for outbound domain sales
• Outbound Domain sales Tips

Questions for you​

• Do you own any .foo domains?
  • If so, how are they doing for you?
• Thinking about investing into .foo domains?
  • If so, what niche will you target and why?

Remember, at the end of the day, a domain name is truly only worth what a buyer and seller agree on.

What works for one may not work for another and vice versa.

Have a great domain investing adventure!

 

[zouhair lamdarbi]

Incredible deep-dive, @Eric Lyon. The data visualization and market breakdown here are top-tier.

Stacking on your research from a purely B2B, Corporate, and FinTech broker's perspective, I usually filter out new gTLDs entirely. However, analyzing your data points brings up a fascinating contrast in acquisition models.

1. The Corporate Trust Deficit
The enterprise end-users I target (SaaS, Supply Chain, Logistics) require the institutional trust and frictionless authority that only a legacy .com provides. While developers love a good "sandbox" extension, C-suite executives signing off on mid-to-high 4-figure acquisitions do not.

2. The Liability vs. ROI Ratio (UDRP Risk)
I completely agree with your ACPA/UDRP warning, and I'd take it a step further:

• Without solid secondary market comps (0 NameBio sales as you correctly noted), defending a UDRP over a $10 registration becomes an unnecessary and expensive uphill battle.
• The ROI on flipping a domain hack for $199–$499 is immediately neutralized by the legal liability of holding pseudo-trademarked terms.

3. The "Velocity of Capital" Verdict
Your analysis of the "Developer-First" utility makes perfect sense for a high-volume, low-ticket outbound strategy. It is a pure volume game.
Conversely, my operational model relies on low-volume, high-ticket liquidations (strictly 4-figure+ B2B .com assets).

Conclusion:
While I will personally be keeping my capital deployed in the B2B .com space, this is an absolute masterclass for anyone looking to build a micro-portfolio targeting the tech/dev community.

Appreciate the detailed write-up! Bookmarking this for the structural breakdown alone.