Internet and e-mail policy and practice
including Notes on Internet E-mail


2013
Months
Jan

Click the comments link on any story to see comments or add your own.


Subscribe to this blog


RSS feed

Add to My Yahoo!

Subscribe with Bloglines


[Valid RSS]

Home :: ICANN

07 Jan 2013

ICANN WHOIS Compliance -- legend or myth? ICANN

Every once in a while, when I come across a domain whose WHOIS is particularly bad, I send it in to ICANN's WDPRS reporting system. So here is the entire entry for the domain ename.net:

Domain Name : ename.net
Registrant :
kongdejing
Domain Name Server :
dns1.iidns.com
dns2.iidns.com
dns3.iidns.com
dns4.iidns.com
dns5.iidns.com
dns6.iidns.com
查看完整whois请到:http://whois.ename.net/ename.net
For more information,please go to: http://whois.ename.net/ename.net

(If you visit that web site, it's not much more informative, other than saying that the registrant is ENAME TECHNOLOGY CO., LTD.)

So I sent in a report saying that it was missing, well, everything. And here's what I got back from ICANN:


Dear Reporter,

Thank you for submitting a Whois Data Problem Report concerning the domain name ename.net.

ICANN has reviewed and closed your complaint because it does not meet the criteria for a valid Whois Data Problem Report. Specifically, your complaint was closed because it:

  • is incomplete (i.e., lacks sufficient detail)
  • is too broad (i.e., lacks sufficient specificity)

If you have reason to believe that your complaint should not be closed, please forward your copy of this e-mail, along with any other relevant information, to ICANN Contractual Compliance at compliance@icann.org. ICANN will review your submission and, if appropriate, forward it to the registrar to ensure compliance.

Sincerely,

Khalil Rasheed
ICANN Contractual Compliance


Who knew? If your WHOIS has no information at all, you're all set, because the complaints are "too broad."

If anyone knows "Khalil Rasheed" or his boss, you might suggest to them that they work on dealing with reports rather than just blowing them off. I have heard that under the new régime, compliance is now a priority, but perhaps word hasn't filtered down to the ranks yet.

Update: A week and a half later someone at ICANN compliance wrote back and said

ICANN acknowledges receipt of your email and complaint concerning the Whois data for the domain name ename.net . The complaint will be reviewed again and processed according to ICANN's standard approach (see http://www.icann.org/en/resources/compliance/approach-processes).

I'll let you know what if anything happens. Spot checks suggest that ename's WHOIS is totally broken and returns no contact information for anyone.

Update (Oct 2014): ICANN wrote back several weeks later saying that ename had fixed their WHOIS, which they had, and as far as I can tell it's worked ever since.

In October 2014, Mr. Rasheed called me out of the blue and apparently wanted to do sommething about this long closed 19 month old complaint. I said no thanks.


posted at: 11:23 :: permanent link to this entry :: 1 comments
Trackback link is http://jl.ly/ICANN/ename.trackback

Topics


My other sites

Who is this guy?

Airline ticket info

Taughannock Networks

Other blogs

CAUCE
CASL Comes into Force
149 days ago

A keen grasp of the obvious
Progress in e-mail
71 days ago

Related sites

Coalition Against Unsolicited Commercial E-mail

Network Abuse Clearinghouse



© 2005-2014 John R. Levine.
CAN SPAM address harvesting notice: the operator of this website will not give, sell, or otherwise transfer addresses maintained by this website to any other party for the purposes of initiating, or enabling others to initiate, electronic mail messages.