Minor tweak to existing tool that checks for domain availability (API) & scrapes data

This project was awarded to metrixmedia for $15 USD / hour.

Get free quotes for a project like this
Project Budget
$2 - $8 USD / hour
Total Bids
Project Description

I have an existing tool built. It's pretty simple. It takes the list of input domains (line separated list in a textarea field) and checks for domain availability using the Namecheap API. In addition, the tool also scrapes some data from external sites ([url removed, login to view] and [url removed, login to view]) and parses that back in the array too. No data is stored in a database or anything like that.

Here's the codebase for the tool:

[url removed, login to view]

When checking the availability for 1 or just a few (under say 15) domains, everything works fine.

This is an example of what is returned:

[url removed, login to view]

However, the Namecheap API has some limits to how many domains can be requested in the API call. If the request is too big, then Namecheap does not return any results.

Here's an example of this:

[url removed, login to view]

You can see the [url removed, login to view] example. At first it's reported that the domain does have the .cm domain available, and then if included in a large batch, it's suggested that the domain is not available.

The problem is that this is very misleading. The X mark suggests the domain is available, when in fact it may just show that Namecheap did not return an answer.

The solution here, I think, is that we show a new symbol: "?", if we do not know the status of the domain availability. So if the API response gives an error, then we show the "?", and only show a "X" if we know is not available.

There's also one other feature that I'd like you to work on.

Namecheap's API only permits 100 calls every minute. Our tool checks for 3 domains for each 1 domain inputted. So that means that we can only check 33 input domains per minute. We could have the tool only allow a maximum of 33 domains, but that would be a little inconvenient. So I suggest the following: allow more than 33, but only process 33 at a time. The tool will work on the 33 domains, then wait 65 seconds (ie. include a little buffer) and then work on the next batch, until complete. For sanity, it would be good if the tool would show the number of seconds remaining to the next check + the number of requests complete so far and number of remaining requests.

This is a quick project for a hacker that likes to get their hands dirty. There could certainly be more work for you in the future if the relationship works out well. I have a solid reputation on

Please include the word "mango" as the password in your bid. Bids without the magic word will not be considered.


Awarded to:
Skills Required

Looking to make some money?

  • Set your budget and the timeframe
  • Outline your proposal
  • Get paid for your work

Hire Freelancers who also bid on this project

    • Forbes
    • The New York Times
    • Time
    • Wall Street Journal
    • Times Online