joepie91
/
python-whois
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A python module for retrieving and parsing WHOIS data
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
65 Commits
2 Branches
0 Tags
1.8 MiB
DIGITAL Command Language 78.6%
Python 12.6%
Org 3.1%
PostScript 1.5%
Roff 1.5%
Other 2.7%
 
 
 
 
 
 
develop
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6dbc743e7f'
${ noResults }
Go to file
Sven Slootweg 6dbc743e7f Rename keys and get rid of null filling 11 years ago
pythonwhois Rename keys and get rid of null filling 11 years ago
test Improved normalization 11 years ago
.gitignore Ignore egg building files 12 years ago
README.md README clarification 11 years ago
pwhois Rename keys and get rid of null filling 11 years ago
setup.py Remove jwhois dependency, separate retrieval and parsing logic, implement registrant parsing for several registries, fix some other regexes, add test data 11 years ago
test.py Fix instructions for test.py 11 years ago

README.md

pythonwhois

A WHOIS retrieval and parsing library for Python.

Dependencies

None! All you need is the Python standard library.

Goals

  • 100% coverage of WHOIS formats.
  • Accurate and complete data.
  • Consistently functional parsing; constant tests to ensure the parser isn't accidentally broken.

Features

  • WHOIS data retrieval
    • Able to follow WHOIS server redirects
    • Won't get stuck on multiple-result responses from verisign-grs
  • WHOIS data parsing
    • Base information (registrar, etc.)
    • Dates/times (registration, expiry, ...)
    • Full registrant information (!)
    • Nameservers
  • Optional WHOIS data normalization
    • Attempts to intelligently reformat WHOIS data for better (human) readability
  • pwhois, a simple WHOIS tool using pythonwhois
    • Easily readable output format
    • Can also output raw WHOIS data
    • ... and JSON.
  • Automated testing suite
    • Will detect and warn about any changes in parsed data compared to previous runs
    • Guarantees that previously working WHOIS parsing doesn't unintentionally break when changing code

It doesn't work!

  • It doesn't work at all?
  • It doesn't parse the data for a particular domain?
  • There's an inaccuracy in parsing the data for a domain, even just a small one?

If any of those apply, don't hesitate to file an issue! The goal is 100% coverage, and we need your feedback to reach that goal.

Contributing

Feel free to fork and submit pull requests! If you change any parsing or normalization logic, ensure to run the full test suite before opening a pull request. Instructions for that are below.

Pull requests that do not include output from test.py will be rejected!

Adding new WHOIS data to the testing set

pwhois --raw thedomain.com > test/data/thedomain.com

Checking the currently parsed data (while editing the parser)

./pwhois -f test/data/thedomain.com/ .

(don't forget the dot at the end!)

Marking the current parsed data as correct for a domain

Make sure to verify (using pwhois or otherwise) that the WHOIS data for the domain is being parsed correctly, before marking it as correct!

./test.py update thedomain.com

Running the full test suite

./test.py run all

Testing a specific domain

./test.py run thedomain.com