Zero analytics. Zero tracking. Provably.

Technology audit

This site uses zero analytics, zero tracking pixels, and zero third-party scripts beyond Google Fonts. You can verify this yourself:

1. Open your browser's Developer Tools (F12 → Network tab) and watch what loads.
2. Run this site through BuiltWith and see the empty tracker list.
3. View our source code — the entire codebase is open.

What we collect

From your searches: Nothing. All search processing happens client-side in your browser. Your keywords, the domains generated, and the results you click are never sent to any server. We have no server to send them to — this is a static site.

From your preferences: Your registrar choice and search count are stored in your browser's localStorage. This data never leaves your device.

From affiliate links: When you click a "Register" button and purchase a domain, the registrar reports the sale to us via their affiliate platform. We learn that a domain was purchased and we earn a commission. We do not learn who purchased it or what searches led to it.

Why front-running matters

Domain front-running is when a registrar or intermediary monitors domain searches and registers (or holds) domains before you can buy them. It's been documented:

Network Solutions (2008): Caught placing searched domains on a 4-day hold, forcing users to register through them. Settled a $1M class action lawsuit. Their own VP admitted the practice "certainly exists."

GoDaddy: Repeatedly accused on Hacker News and forums. At the height of domain tasting (2007), their CEO reported 51.5M of 55.1M registered domains were canceled before the grace period expired.

ICANN's SSAC: Ran 600+ tests. Found no proof — but did not rule it out.

Matt Mazur, creator of the original Lean Domain Search, called the practice "really shady" and maintained a "strict policy" against using search data. We agree.

How we check availability

We do not query registrar search APIs to check if a domain is available. Those queries are exactly where front-running data is harvested.

Instead, we use the .com zone file — a daily snapshot of all registered .com domains published by VeriSign. We load this data at build time into a Bloom filter that ships as a static asset. When you search, the check happens entirely in your browser against this pre-loaded data. No network request is made.

Registrar partnerships

We earn affiliate commissions when you register a domain through our links. Here's how we choose which registrars to recommend:

"Recommended" registrars appear first in our registrar picker. All registrars link directly to their registration page — we never route through an intermediary.

Questions?

View our source code on GitHub. If you find anything that contradicts these claims, please open an issue.