domain-search

# Domain search Check availability against registry data, never against parsed whois text alone. Report only verified results, and say which method verified each one. ## The one rule that prevents false positives Every check method must pass a control: a domain you know is registered on the same TLD, through the same route. If the control does not read as "taken", the route is broken and its results are worthless. A broken route returns the same answer as "available" (example failures: rdap.org returns 404 for vine.co, greenhouse.io, and notion.so — all registered). Never report a domain as available from a route with no passing control. Grepping `whois` output for "no match" is the classic trap: registrar boilerplate and rate limit text match those patterns. It once reported showtell.com as available when it had been registered since 1995. ## Method 1. **RDAP first.** RDAP is the registries' official JSON API. HTTP 200 = registered, 404 = available (on a validated route). Prefer direct registry endpoints over the rdap.org proxy, which is slow and misroutes some TLDs. 2. **Find the endpoint** in the IANA bootstrap: `curl -s https://data.iana.org/rdap/dns.json` maps each TLD to its server. A TLD absent from the file has no RDAP; use registry whois. 3. **Registry whois fallback** for TLDs without RDAP. Find the server with `whois -h whois.iana.org <tld>` (the `refer:` line), then `whois -h <server> <domain>`. "Domain Name:" present = taken. Still needs a control. 4. **DNS...