About Namester.ai

Where the data comes from

We collect each marketplace's public listing data and API results on a fixed schedule: Namecheap every hour, GoDaddy once a day, Dynadot once a day, DropCatch twice a day, and Sedo twice a day. Prices, bid counts and end times are only as fresh as that marketplace's last pull — not live to the second — and they can be incomplete. Before you bid or buy, open the listing on the marketplace itself: its price and status are the ones that count.

What we don't do

We don't sell domains, run auctions, or take bids or payments for domains. The marketplace link on a domain page takes you to the marketplace that lists it, and you buy there. The only thing we charge for is an optional subscription plan — the pricing page shows what each plan adds and whether it can be bought right now. Searching is free.

AI search

On Discover, the sentence you type is sent to a third-party AI model, through OpenRouter, which turns it into ordinary search filters. The filters are shown on the page and you can remove any of them. AI parsing has a limit that depends on your plan: 10 new sentences per day (UTC) when you are not signed in, counted per IP address; 30 per day with a free account; 30 per hour on a paid plan. There is also a site-wide daily total. Past either limit, Discover runs no search and says so; you can still set filters yourself on the full list. The model can misread a sentence, so check the filters before you rely on the results.

The Namester Score

The score ranks demand, not price, and each domain page breaks down how its score was built. The Features page explains the model.

The NamesterDomainScanner bot

Requests that identify themselves with this user agent come from Namester.ai:

NamesterDomainScanner/1.0 (+https://namester.ai/about)

It is an administrator-only tool that asks the .si registry’s public RDAP service whether a name has a registration record, to shortlist names worth confirming with a registrar. It sends HEAD requests, which return only a status code, so it does not retrieve or keep anyone’s contact details.

It sends one request at a time, at least 2 seconds apart, and has a daily request cap. When the registry answers 429 or 503 with Retry-After, it waits at least as long as asked. If the registry stops answering, it pauses with longer and longer waits, and after repeated pauses it stops until a person has checked. It connects directly from our own server, without proxies or rotating IP addresses.

If you run a registry and want us to slow down or stop, write to: hi@namester.ai

Contact

Questions, corrections or requests about your data: hi@namester.ai