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

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
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.
    ICANN Rips VeriSign Over Whois Violations | Log in/Create an Account | Top | 70 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    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 Should Not Reveal So Much Info
    by Anonymous on Wednesday September 04 2002, @06:01AM (#9019)
    Dear Anonymous:

    Could you please provide proof of this. A number of registrars and registries are meeting with the FTC later this month, and I believe this would be a useful talking point. Please email me at mike@palage.com. Thanks
    [ Reply to This | Parent ]
    Re: Whois Should Not Reveal So Much Info by Anonymous
    Re: Whois Should Not Reveal So Much Info
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday September 04 2002, @10:11PM (#9036)
    User #2810 Info
    I have done the experiment of using unique email addresses for the WHOIS numerous times over the last few years. The WHOIS datamining spam problem has been there for some time (what do you expect when VeriSign was selling the WHOIS a couple of years ago to anyone with $10k, and it didn't take long for bootlegs to show up), but it is definitely getting worse.

    I did this for my own edification and can't prove to anyone else that these addresses weren't otherwise available by other address hoovering methods, egs: web spiders, where they got my address above, webforms of sites promising privacy and not delivering (which is different than the first, that's not what happened to my above address), and Usenet posts. I'd say these are the big four methods used to create spam databases, and the WHOIS is the best of all as one can more freely use a false or disguised (eg: d_d@emailREMOVETHIS.com) addy in the other instances. With the WHOIS one might not only miss important email from one's registrar (which is why I support a private email address that only the registrant and registrar know, even if there must be a public WHOIS), but now one risks losing one's domain name. So, while I'm not a speculator, both because I have no absolute proof, and because I value my privacy and because I'm not American, I may not be the best poster kid for this either.

    You may want to ask Bret Fausett. He undertook a similar experiment back in February and has periodically mentioned it since (a quick scan of his archives, wow he's given us so much, failed to turn up any but that's my fault). He would also otherwise be much more credible than I, though you are free to use what I say here if you wish. -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