Skip to content
Bulk whois lookup tool
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
app
sample_lists
.gitignore
license.md
package-lock.json
package.json
readme.md
readmenot.md

readme.md


Whoisdigger app

This application is in alpha stage

Whoisdigger is a bulk whois lookup, cross-platform, desktop application built on Electron. Made with builders and creators in mind, rapidly lookup up your favorite domain mashups without risk of third-party logging, domain squatting and other domain lookup issues.

Features

  • Fast single domain lookup and raw reply
  • File or manual wordlist bulk whois
  • Drag and drop wordlist file
  • Bulk raw whois replies (txt) and/or field formatted replies (.csv)
  • Bulk stop/pause/continue mechanism

Planned features

  • Bulk analyser
  • Domain monitor
  • Misc tools
  • Options
  • Help page
  • Proxy integration

Be aware that

Its your sole responsibility what you do with this tool, its intended to let anyone have a chance at finding a good domain in a crowded space. Is also known that repeated whois requests to a server will eventually result in IP blacklisting, you should have a conservative value for time between requests and bit of common sense to minimize the risk of blocks, don't do huge bulk lookups at once or with the same ip, preferably use different proxies between requests.

Quick Start

To stay on the bleeding edge of whoisdigger updates do git clone or for more stability download the latest release.

Latest development changes

For this you'll need to have node, npm and git.

Clone whoisdigger code and install dependencies to your local machine

git clone https://github.com/whois-team/whoisdigger
npm install

After clone, run using

npm start

Or debug using

Windows Powershell

npm run debug-powershell

Windows Command Line

npm run debug-cmd

Latest built binary

Check out releases and download the latest release for your architecture/OS.

Latest tag Check out releases

Using wordlists

Wordlist files should have one word per line without TLDs suffixes, spaces or special characters if intended, they should also be in UTF-8 encoded and follow the example below:

wordlist.txt (Text file)

pow
mow
cow
low
tow

Wordlists by manual input should follow the same rules with the only difference of being pasted at input stage.

Sample wordlists

Whoisdigger provides sample wordlists as example for testing purposes inside sample_lists folder.

Exporting bulk processing results

At export stage the user is given several options, you can decide what domain status to export, if you want domains that threw errors included, their basic information if not available such as creation, expiry and update dates. Exporting as text file will only export invidualized whois replies for each domain in a zip file, as a csv you're able export both basic information and whois replies in text, inline csv or separate csv files in a zip for organization.

Notes on errors

Errors when doing bulk lookups are common due to the nature of bulk requests, this means that requests will get blocked, throttled or delayed resulting in errors. Errors commonly refer to already registered domains so most times you can assume that they're already taken. Uniregistry has a very low threshold on whois requests resulting in temporary block as soon as 3 rapid requests hit their server, in this case you can also assume its taken.

Building

Whoisdigger uses electron-packager for builds.

MacOS

npm run package-mac

Windows

npm run package-win

Linux

npm run package-linux

Built With

License

Distributed under MIT License. See license.md for more information.

Additionally when using WhoisTeam or other GitHub Logos, please refer to GitHub logo guidelines.

You can’t perform that action at this time.