Seomarlboro/digmyname

**The fastest domain search — or the second. Dispute it.** Free, honest domain availability checks across 50+ TLDs with 6-registrar price comparison.
Links
- Website: https://digmyname.com
- Free API: https://digmyname.com/api
- MCP server: https://digmyname.com/mcp (npm: domain-check-skills-mcp)
- Speed benchmark: https://digmyname.com/speed
Quick start
No install needed to try it — the site and the API are both live.
Free, no API key, no account — 60 requests/minute/IP and 5,000 domains per UTC day/IP. Full docs: digmyname.com/api.
Want your LLM to call it directly instead? One line: claude mcp add domain-check -- npx -y domain-check-skills-mcp — see mcp/README.md.
What it does
DigMyName checks domain availability in real time across 50+ TLDs. Availability is cross-checked against two independent signals on every name — RDAP (resolved via the IANA bootstrap registry) and DNS-over-HTTPS (Cloudflare, Google and AdGuard, hedged) — with a third, Fastly Domain Research, brought in only where those two are not enough (an uncertain answer, a premium suspect, a brand-blocked label, the zones without public RDAP, and the name the visitor typed). When the signals disagree we show an honest **Unverified** state instead of guessing. For the popular extensions the visitor's browser asks the registry's RDAP server and DNS-over-HTTPS directly for the first answer, over connections opened while the name is still being typed; the edge re-checks every card and stays the authority. Prices are refreshed weekly from the registrars' own catalogs and pages.
On top of availability you get side-by-side registrar pricing for 6 registrars, including the renewal traps that first-year promo prices hide (a $1 registration that renews at $61 is not a deal). Everything is also exposed through a free, no-auth JSON API for agents, plus an MCP server so any LLM — Claude, Cursor, Windsurf, Continue, Zed — can check domains directly.
Speed
**Under 0.5 s** to the first answer at the 95th percentile for a cold visitor — 386 ms from the US, 485 ms from the EU, 150 fresh browsers each, September 2026 · the full check with pricing lands in about half a second (median). Everyday numbers, not a lab result — the on-screen stopwatch is the live proof; your numbers vary by network, TLD and cache — see digmyname.com/speed.
Tech stack
- Vite
- React
- TypeScript
- shadcn/ui
- Tailwind CSS
- Supabase edge functions (Deno)
Development
The only requirement is having Node.js & npm installed — install with nvm.
Tests
Benchmark
scripts/bench/first-answer.mjs measures what a cold visitor sees on the stopwatch: each visitor is a fresh browser that loads the home page, pauses, types a name nobody has checked and stops when the first verdict paints. It needs Playwright (npm i playwright && npx playwright install chromium in any scratch folder, then node first-answer.mjs); the bench-first-answer GitHub Actions workflow runs the same script from a US runner on demand. Numbers quoted on the site come from these runs, with date, location, sample size and percentile.