Cheat sheet for WHOIS Accuracy Session at 11AM in 311/312
Folks, We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312 For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked. For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate. 10 Registrars have false WHOIS for their own website domains
Too bad the session conflicts with the ongoing open GNSO Council meeting. I'd dispute the relevance of some of these measures to ICANN, and would argue that in many cases, no action is warranted. --Wendy On 06/23/2010 04:30 AM, gbruen@knujon.com wrote:
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
-- Wendy Seltzer -- wendy@seltzer.org Fellow, Silicon Flatirons Center at University of Colorado Law School Fellow, Berkman Center for Internet & Society at Harvard University http://cyber.law.harvard.edu/seltzer.html http://www.chillingeffects.org/ https://www.torproject.org/
Wendy...with all due respect, I cannot see how your statement is even remotely supportable. Port 43 access, to name a single aspect, is part of the RAA. If I'm missing something here, tell me. Please excuse brevity and typos -sent from IPhone On 23/06/2010, at 4:46 AM, Wendy Seltzer <wendy@seltzer.com> wrote:
Too bad the session conflicts with the ongoing open GNSO Council meeting. I'd dispute the relevance of some of these measures to ICANN, and would argue that in many cases, no action is warranted.
--Wendy
On 06/23/2010 04:30 AM, gbruen@knujon.com wrote:
Folks,
We are proving this "Cliffs Notes" version of our WHOIS data from our Registrar audit (http://www.knujon.com/knujon_audit0610.pdf) for today's WHOIS Accuracy Session at 11AM in 311/312
For Web-based WHOIS access: 11 Registrars have "look up" service instead of WHOIS 8 have clearly non-working engines or direct the visitor to some other WHOIS service A Technology Co(Namesystem.com) is manipulating it's own WHOIS record, returns: "Sorry Domain does not exist", and since we've published our report they pulled their port 43 offline completely. Note, this was ONLY for their domain name, all other queries worked.
For Port-43 WHOIS Access 30 Registrars have bad, inconsistent service 55 would not reveal their WHOIS address 6 gave us inaccurate data or the email to them was rejected. One Registrar, Domain Factory, said they were not a Registrar
For Bulk Access (RAA 3.3.6) Namescout and Network Solutions refused to offer the service eNom, Dotster, and Moniker did not respond to our request for information and price for bulk download
Registrars are restoring or maintaining domains beyond the 45 day period of being inaccurate.
10 Registrars have false WHOIS for their own website domains
-- Wendy Seltzer -- wendy@seltzer.org Fellow, Silicon Flatirons Center at University of Colorado Law School Fellow, Berkman Center for Internet & Society at Harvard University http://cyber.law.harvard.edu/seltzer.html http://www.chillingeffects.org/ https://www.torproject.org/
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists.ica...
Visit the NARALO online at http://www.naralo.org ------
Wendy...with all due respect, I cannot see how your statement is even remotely supportable. Port 43 access, to name a single aspect, is part of the RAA. If I'm missing something here, tell me.
Please excuse brevity and typos -sent from IPhone
It's ICANN's long standing pro-crime faction, that wants to remove all accountability for everything. They think they're pro-privacy, but as anyone who has an inbox full of fake drug spam and phishes knows, they're mistaken. R's, John
participants (4)
-
Beau Brendler -
gbruen＠knujon.com -
John R. Levine -
Wendy Seltzer