1. Domain ideas are generated in the browser
A bare word such as "buildwise" is expanded across common top-level domains and a short set of prefixes and suffixes. A full domain such as "example.com" keeps that domain first and compares nearby TLD options. This keeps the first result useful while avoiding hundreds of low-quality permutations.
2. The server checks free public signals
RDAP registration
RDAP can show whether a domain appears registered, which registrar is listed, and key lifecycle dates when the registry publishes them.
DNS records
DNS A, AAAA, MX, NS, TXT, SOA, and CNAME records help distinguish unused names from configured names, mail-enabled names, parked domains, and active sites.
Certificate history
Certificate Transparency records can indicate that a domain or subdomain has been used for HTTPS in the past, even when the current website is sparse.
Website fetch
If DNS resolves to an address, SiteFind checks the HTTPS or HTTP landing page for redirects, page titles, marketplace hosts, parking text, and substantial content.
3. Evidence is scored, then labeled
Every signal is converted into a small evidence item. For example, "RDAP registration found" supports registered or held classifications, while "Explicit for-sale page text" strongly supports a resale or squatter-watch label. The classifier sums these items and applies ordered thresholds so strong resale signals are not hidden by weaker active-site signals.
4. Results should be confirmed before purchase
Public data can be stale, incomplete, rate-limited, or inconsistent. Always confirm availability, price, renewal cost, and transfer requirements with the registrar before making a purchase. For borderline cases, use the evidence notes as a starting point for manual review.