Comment Close



Call for
Comments Open
Call for
Vote OpenVote CloseDate of SubmissionStaff Contact and EmailStatement Number
 Removal of Searchable Whois Service From .MEET Registry AgreementNo Statement

Main penholder: Harold Arcos

Assisted by: Holly Raiche


Krista Papac


For information about this Public Comment, please click here 



The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 


The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.



The first draft submitted will be placed here before the call for comments begins.

  • No labels


  1. I already send my comment to the list. It's personal.


    The arguments about the searchable Whois interface for .SHARP can't be
    reused for .MEET without serious reconsideration. .MEET is a TLD open to the
    public. So the impact is different for .MEET and .SHARP.
    The main question is (for me): Do we need Whois at all, or do we need it for
    a specific purpose?
    If we claim a use case for Whois to get in touch with the technical people
    running the delegated zone in the case of technical problems (which is the
    traditional interpretation by the technical community), than the Whois
    service could not be removed.
    If we claim a use case for Whois to get the contact details of the
    administrative persons in the case of misuse (which is the modern
    interpretation by the IP community), than the Whois service could not be
    If we claim a use case for Whois to get the contact details of the
    responsible persons in the case of criminal activities (which is the
    interpretation by the LAEs), than the public Whois service can be shut down
    as long as the unlimited access for those special groups is guaranteed.
    If we claim the privacy rights do outweigh the other use cases (which is the
    modern interpretation by various groups incl. technical), than the Whois
    service has to be shut down as well as the collection of data for even
    internal Whois has to be stopped.
    So from my point of view I'd suggest to keep the public Whois as long as the
    data is collected for the LAEs. If the registry will get a permit to stop
    the public interface, the collection of data has to be stopped also.
    Consequently I oppose the proposal.
    Lutz Donnerhacke
  2. There seems to be some confusion. The RSEP is not a request to eliminate the WHOIS Query function, which is mandatory, but the "Searchable" Whois web query which is an optional capability and allows searching on a wide variety of WHOIS fields including, in some case, partial text (equivalent to wild-card) searches.

    Afilias, who originally applied for the domain volunteered to include such a capability, but they have since transferred the TLD to Google who did not offer such a service for its own applications.The service, in theory, would be available only to authorized users (it is currently open, but as far as I can see, the only domain in use is The searchable WHOIS returns only the domain name, not the entire (viewable) WHOIS entry.

    Both the WHOIS lookup and the searchable WHOIS can be found at

    For details, see the contract at, Exhinit A, Section 3, Page 39-40 and Specification 4, Section 1.10, Page 64.



  3. As Alan has clearly stated above, this is an application for removal of what is now an optional capability to allow searching on a wide variety of WHOIS fields.  This is NOT a request about eliminating the actual WHOIS query function - as required under the RAA.

    Given that  this is only a request for remove an optional capability, and the requirements for the WHOIS query fuction will be met, I strongly suggest that we do not make a subission to this proposal.

  4. Originally I thought exactly what Lutz had said: if this is a publicly used top level domain, you cannot remove WHOIS queries for it.

    However, reading the document, I note that the searchable WHOIS would be removed but "Google Registry will continue to comply with all other WHOIS requirements set forth in the .MEET Registry Agreement." - which means a standard WHOIS will continue to be operated.

    I would be completely against the removal of a standard WHOIS, but a searchable WHOISwith boolean wildcards is not mandatory so I am okay with removing it. As long as the standard WHOIS requirements are met and an end user is able to identify the source of spam or malware or the owner of a domain name with which they are doing business, I am okay with the amendments.