Inside ICANNWatch  
Submit Story
Lost Password
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)

    This discussion has been archived. No new comments can be posted.
    WHOIS Enforcement Update | Log in/Create an Account | Top | 13 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re: WHOIS Enforcement Update
    by fnord (groy2kNO@SPAMyahoo.com) on Friday September 20 2002, @08:52AM (#9295)
    User #2810 Info
    To make a point? I guess you missed it. If you want a domain, lame or whatever you consider non-lame, rat them out for inaccurate WHOIS data (eg: if you're not lame mine the WHOIS for deceased @home addresses), wait for the domain to drop and Hey Presto, it's yours.

    And you might want to define what you mean by lame. It's not about kewl sounding names that you can use or resell, that's so 20th century. It's about traffic. If a lame name gets lots of traffic it's normally worth much more than a kewl sounding name that gets none. archive.org doesn't have anything for visosite.com but it was active in spamming. archive.org just balks when asked about fufus.net. While the WHOIS for visosite.com and fufus.net now shows John and Bret in that order, visosite.com presently returns a strange message, and fufus.net points to Bret's icann.blog.

    As for the remaining names which were reportedly deleted in this farcical exercise (VeriSign has many thousands of such inaccurate WHOIS records):

    kokorouta.net doesn't resolve, is apparently registered to VeriSign (no expiry date), has a bit of history at archive.org, and rates one mention (on the ICANN DNSO registrars list) via Google. VeriSign prompts me to backorder it via Snapnames.

    digeronimo.com is the same as the previous, except for one Google mention pointing here [apparently a Florida plastic surgeon], and again archive.org balks.

    kasparatisco.com is the same as the above, except archive.org, while not balking, finds nothing, and Google points here [apparently used in a Usenet spam, if you're spamming Usenet, a one-time throwaway domain for return email is presumably worth the cost of registration].

    stepup.net is a strange one. It doesn't resolve and again archive.org balks [they may be having a bad day], and Google shows a history of it being used for spam. But, while my own WHOIS tools report that it doesn't exist (via both web and direct queries), that is, is unregistered, VeriSign's WHOIS reports:

    Domain Name: STEPUP.NET
    Whois Server: whois.networksolutions.com
    Referral URL: http://www.networksolutions.com
    Name Server: NS2.TO-BUY-THIS-DOMAIN-FAX-305-463-9709.COM
    Updated Date: 16-sep-2002

    >>> Last update of whois database: Fri, 20 Sep 2002 04:57:31 EDT The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and Registrars.

    Domain not found locally, but Registry points back to local DB. Local WHOIS DB must be out of date.

    Kewl nameserver names. So if you want an email address that has already been blackholed, you can now go here and pay a premium for it.

    And from this exercise one might assume that if VeriSign were to ensure that the WHOIS data of all its registrants was valid and 'delete' all those that aren't, it will greatly help SnapNames and eventually WLS, that is, VeriSign. One minute VeriSign escapes threatened ICANN dis-accreditation by the skin of its teeth through updating less than a score of thousands of incorrect WHOIS entries, the next minute they're making even more money through ICANN giving VeriSign the keys to a monopoly to resell pre-used names for more than their original price, including those that they will no doubt eventually flush out for incorrect WHOIS data. Thanks ICANN, your record of being either incompetent or corrupt continues unbroken. -g

    [ Reply to This | Parent ]
    Re: WHOIS Enforcement Update by fnord
    Re: WHOIS Enforcement Update
    by fnord (groy2kNO@SPAMyahoo.com) on Saturday September 21 2002, @05:14AM (#9317)
    User #2810 Info
    It is several individuals complaining which caused ICANN to complain. Beyond that, I guess you don't understand the point of trophy names. -g
    [ Reply to This | Parent ]
  • 1 reply beneath your current threshold.

  • Search ICANNWatch.org:

    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com