Sam - September 17, 2018

WHOIS SOCKS Proxy Scraping Tool

TutorialsData Scraping

ProxyRack WHOIS Tool is a multi-threaded, socks5 proxy supported NodeJS application that can be used to scrape WHOIS record data or check domain availability.

Features

SOCKS proxy support with or without user credentials
Multi-threaded
NodeJS
Web UI and CLI
Optional: MongoDB to store results

Installation

ProxyRack WHOIS Tool requires node >=8.93
Quick node installation (multiple OS) https://github.com/creationix/nvm

Find the perfect Proxy Product.

Proxyrack offers a multiple options to suit most use cases, if you are unsure our 3 Day Trial allows you to test them all.

Residential proxies

Never get blocked, choose your location

View all option available

Datacenter proxies

Super fast and reliable

View all option available

3 Day Trial

Test all products to find the best fit

View all option available

Install the dependencies and devDependencies and start the web UI server.

$ git clone https://github.com/proxyrack/whois-proxy-scraping-tool.git
$ cd whois-proxy-scraping-tool
$ npm install
$ node index.js --mode server --port 8080 --web-port 8000

For CLI:

$ node index.js --mode file --input domains.txt --output result.txt --output-available available.txt --output-registered registered.txt

proxies.json

Proxies are stored in a JSON file called proxies.json

{
  "proxies": [
    "yourusername:yourpassword@megaproxy.rotating.proxyrack.net:222 socks5"
  ]
}

Example proxy included is from www.proxyrack.com service

config.js

You can modify your MongoDB settings here, proxies file path, results directories and set the number of concurrent threads you want to run

It is OK to completely ignore the MongoDB line here, just specify localhost even if you haven’t set up and installed it.

The software will still run and save results to disk.

'use strict';
const config = {
  db: {
    url: 'mongodb://localhost:27017',
    name: 'whois'
  },
  proxies: {
    path: 'proxies.json'
  },
  numThreads: 50,                        // number of threads per search
  outputDir: './results',
  outputUrl: '/results/'
};