Usage
ds apple --tld com,net # a specific list
ds apple --tld all # every known TLD (~1650 lookups)
ds apple --tld popular # a curated set of ~38 common TLDs
ds apple --tld rdap # only TLDs that have an RDAP service
ds apple --tld @tlds.txt # one TLD per line, `,` and `#` comments ok
ds apple.com # a full domain, checked as-is
Results stream in as they arrive. + is available, - is taken, ? could not
be answered:
+ mybrand.dev AVAILABLE $15.98 rdap 415ms
- apple.com TAKEN $14.98 rdap 978ms
? google.pt UNKNOWN - - 3548ms whois: connecting to whois.dns.pt:43: timed out
summary: 1 available 1 taken 1 unknown (3 checked in 3.5s)
The fourth column is the average yearly registration price for the TLD; -
means no price is on file for it.
The exit code is 0 if anything is available, 1 if nothing is, 2 on a
startup error — so ds mybrand --tld com -q && echo free works in a script.
Several names at once
Comma separated, as separate arguments, or from a file. Every name is checked against every TLD:
ds apple,orange,bangla,english --tld com,net # 4 names x 2 TLDs = 8 lookups
ds apple orange bangla --tld io
ds @names.txt --tld com,net,io --available-only
names.txt takes one name per line; commas work there too, # starts a
comment, blank lines are ignored and duplicates are dropped:
apple
orange, bangla # both checked
english
Saving the results
Nothing is written unless you ask for it:
ds mybrand --tld all --save # available.txt, unavailable.txt
ds mybrand --tld all -o results # a directory implies --save
ds mybrand --tld popular --append # so does --append
available.txt— one domain per lineunavailable.txt— registered domainsunknown.txt— only when a registry could not be reached, so a failed lookup is never filed as “available”
With --json the same three files are written as available.json,
unavailable.json and unknown.json, each a JSON array of the full results
rather than a list of names:
ds mybrand --tld all --save --json # available.json, unavailable.json
--append merges into the array already in the file, so the result is still
one valid JSON document.
--available-only trims what is printed, not what is saved.
These pages are generated from the project README, so they never drift from what ships with the binary.