About dibbed.dev

One search, 33 places at once.

Picking a name for a product is annoying. Most checkers look at five or six places (a couple of domain TLDs and the big social handles) and call it done. Then a week later you discover an active USPTO trademark, or that the npm slug is taken, or that the Reddit subreddit exists, and you have to rename.

dibbed.dev checks 33 places in parallel:

  • Domains. 14 TLDs (.com, .ai, .io, .app, .dev, .co, .gg, .xyz, .so, .me, .org, .net, .shop, .store) verified via DNS and RDAP.
  • App stores. Apple App Store, Google Play.
  • Code registries. npm, PyPI, crates.io, GitHub.
  • Socials. Reddit (r/ and u/), YouTube, Instagram, X (Twitter), TikTok, Facebook, LinkedIn, Pinterest.
  • Trademark & business records. Live USPTO Elasticsearch search; deep links to EUIPO, Companies House (UK), and SEC EDGAR.

Results are baked into the page server-side, so you can share a link and the recipient sees the exact same data. Most cached lookups complete in under 50 ms; cold lookups take 1–3 seconds while we fan out to the upstream APIs.

How we make money

When a domain is available, we link to register it through Dynadot. If you register through that link we earn an affiliate commission. The price you pay is identical to going direct. That's the entire business model. No premium tier, no ads (yet), no data resale.

What we collect

Every name searched is stored in our database with a counter and the most recent result. We use this to surface popular and trending names back to users later. No IP addresses, no user agents, no account system. Only the slug and what we found.

See the privacy page for the full breakdown.

What we don't do

  • Give legal advice. A clean USPTO check is not a guarantee of unencumbered use. Different classes, common-law marks, and pending applications all matter. Treat us as a fast first-pass filter, then consult an IP attorney before committing to a name commercially.
  • Resell anyone's data. USPTO data is public-domain; we surface it live from the register and don't redistribute it.
  • Track who searched what. The search slug is stored; nothing identifying the searcher is.

Open questions

Found a bug, want a service added, or have a feature request? Email help@dibbed.dev.