Melbourne parser ( - contacts are missing #205

MartyIX opened this Issue Feb 12, 2013 · 3 comments


None yet

3 participants


Hi, I tried the library on and the output I get is:

{:disclaimer=>"<I omitted the text>", 
:created_on=>2000-01-21 00:00:00
:updated_on=>2012-08-08 00:00:00 +0200, 
:expires_on=>2019-01-21 00:00:00 +0100, 
:registrar=>#<struct Whois::Record::Registrar id=nil, name="MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE", organization="MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE", url="">, 
:nameservers=>[#<struct Whois::Record::Nameserver name="", ipv4=nil, ipv6=nil>, #<struct Whois::Record::Nameserver name="", ipv4=nil, ipv6=nil>, #<struct Whois::Record::Nameserver name="", ipv4=nil, ipv6=nil>, #<struct Whois::Record::Nameserver name="", ipv4=nil, ipv6=nil>]}

The *_contacts are missing. Why was the issue #101 closed? Does it mean it should work or that the problem was abandoned? I was unable to find any Melbourne parser so I guess there's no such parser.

Thanks for an answer

A few notes:

1) I tried and the data are parsed correctly but I guess RoboWhois uses an improved version of tthe weppos/whois library.

2) Raw whois record to see that the data are provided in text form:

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to
for detailed information.

   IP Address:
   Whois Server:
   Referral URL:

   Domain Name: TWITTER.COM
   Whois Server:
   Referral URL:
   Name Server: NS1.P34.DYNECT.NET
   Name Server: NS2.P34.DYNECT.NET
   Name Server: NS3.P34.DYNECT.NET
   Name Server: NS4.P34.DYNECT.NET
   Status: clientTransferProhibited
   Updated Date: 08-aug-2012
   Creation Date: 21-jan-2000
   Expiration Date: 21-jan-2019

>>> Last update of whois database: Tue, 12 Feb 2013 09:05:05 UTC <<<

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and

Domain Name..........
  Creation Date........ 2000-01-22
  Registration Date.... 2011-08-31
  Expiry Date.......... 2019-01-22
  Organisation Name.... Twitter, Inc.
  Organisation Address. 1355 Market Street
  Organisation Address. Suite 900
  Organisation Address.
  Organisation Address. San Francisco
  Organisation Address. 94103
  Organisation Address. CA
  Organisation Address. UNITED STATES

Admin Name........... Domain Admin
  Admin Address........ 1355 Market Street
  Admin Address........ Suite 900
  Admin Address........
  Admin Address. San Francisco
  Admin Address........ 94103
  Admin Address........ CA
  Admin Address........ UNITED STATES
  Admin Email..........
  Admin Phone.......... +1.4152229670
  Admin Fax............ +1.4152220922

Tech Name............ Tech Admin
  Tech Address......... 1355 Market Street
  Tech Address......... Suite 900
  Tech Address.........
  Tech Address......... San Francisco
  Tech Address......... 94103
  Tech Address......... CA
  Tech Address......... UNITED STATES
  Tech Email...........
  Tech Phone........... +1.4152229670
  Tech Fax............. +1.4152220922
  Name Server.......... NS2.P34.DYNECT.NET
  Name Server.......... NS3.P34.DYNECT.NET
  Name Server.......... NS4.P34.DYNECT.NET
  Name Server.......... NS1.P34.DYNECT.NET

Ji @MartyIX, the reason why I closed #101 is because there are hundreds of thin whois servers and I don't believe opening one support ticket for each will be a good idea.

My intention would be to keep open only the thin server tickets including a patch or a pull request. I prefer to focus my time on working on the core library rather than spending thousands of hours creating parsers for thin registries. Of course, contributions are always well accepted.

About RoboWhois, the version the system uses is the same of this repo, with a few customizations and experimental parsers I can't release for various reasons.


I created the missing parser '' a week ago. However, I had difficulty merging it to the main branch due to my lack of knowledge of github at this moment. But you can download it from my branch below and put it under your installation path ./lib/whois/record/parser/

I tested it out it worked for me :)


Thanks @yangsec888, but unfortunately I can't merge the parser without all the necessary tests. Each parser must have a full test suite.

Here's an example: f0b347f

If you want to provide a full patch, feel free to do that. :)

@weppos weppos closed this Feb 13, 2013
@weppos weppos was assigned Feb 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment