It turned out pretty nice, it seems GoDaddy is letting you make 116 requests/min (tested, idk their real numbers), and you can submit up to 500 domains per API request, so I have it multithreading sending stacks of 500 domains (and since browsers limit connections to hostnames and I didn't want to use websockets, I had to create a bunch of records in my hosts file that points to, i.e. a.test-server.com, b.test-server.com, c.test-server.com, etc), once it receives the response with domain availability from GoDaddy's API, it then goes out and checks the domains that GoDaddy says is available against the applicable whois server - if it's still available, it adds it to the list. It's dropped down from 1k/sec to at most 75/sec (which isn't too good, but I'm going to write an application in either C++, C#, or VB (haven't decided yet) that way threads aren't limited and I can increase the API call count per minute from in indefinite number (right now it's send 4 -> complete -> send another 4 -> complete, etc) to a solid 116 seeing as there aren't any limitations and it'll run faster as an actual program. Really simple concept, and after the whois implementation to confirm GoDaddy's result, it's 100% accurate. A problem a lot run into is parsing the inconsistent whois responses and having a server and respective parser in place for each extension where it's needed, so I'm leaning more towards integrating 3 APIs to validate eachother from different registrars who allow bulk domain availability checks to increase the performance. If that's available and the request quotas aren't horrible (seems to be common), should be able to get back up to 1k/sec if not faster once I port it from web to native
