3 ms·
If you're worried about front running, do host -t ns reallycoollname.com And only if that comes back negative, do a whois. If you're really paranoid, run
by toast0 6y ago
If you're worried about front running, do
host -t ns reallycoollname.com
And only if that comes back negative, do a whois. If you're really paranoid, run your own recursive DNS, so your recursive hits the TLD servers itself. TLD servers aren't going to log checks for names they don't have; they've got better things to do; registry whois servers probably aren't going to log either, but whois shows more intent than DNS queries.
- phgn 6y agoA domain availability check based on DNS seems ideal, but a surprising number of domains actually don't have DNS records, so there are false negatives. For WHOIS I guess the biggest concern is recursive / thin whois servers not operated by the registries. Unfortunately there is no perfect method. I've had this happen to me before, and am starting to believe it was just coincidence. I think there are too many domain queries globally for someone to look through, so I'd suggest not searching a name too often and you're probably good. (I'm building a faster domain search based on DNS and WHOIS data)