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


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

Subscribe to this blog

RSS feed

Home :: ICANN

20 Oct 2010

ICANN's compliance has a long way to go ICANN

About a month ago I reported a domain to ICANN which has the most completely bogus WHOIS non-information I've ever seen. On Monday they sent me this message.

Take a look at the WHOIS info in the message, which is exactly the same as it was when I reported it. I realize that doing a good job of compliance is hard, but really, we have computers. If Knujon can recognize obviously wrong WHOIS info, why can't ICANN?

Date: Mon, 18 Oct 2010 12:01:01 -0700
To: <me>
Subject: -- Whois Data Problem Report
This message is in follow-up to the Whois Data Problem Report you
confirmed on Fri Sep 3 06:00:18 2010 regarding  As
indicated to you at the time of submission, a copy of your report was
forwarded to the sponsoring registrar for investigation.  We would
appreciate it if you could assist us in monitoring registrar
compliance with Whois data accuracy obligations by selecting one of
the options below:
    1. The data inaccuracy was corrected.  Please go to the following URL:    
    2. The domain has been deleted or re-registered.  Please go to:
    3. The whois data is still inaccurate.  Please go to:
    4. None of the above.  Please go to:
For your reference, the current whois data for the domain is appended below
and your report ID is: 1234
Thanks again for your assistance.
Best regards,
InterNIC Whois Data Problem Reports System
                WHOIS DATA AS OF 2010/10/18
Visit for more information about
<a href="">AboutUs:</a>
Registration Service Provided By: AsiaRegister, Inc.
Domain name:
Registrant Contact:
 7777 uuuu ()
 sdfsdf, uuuuuuuuuuuu uuuuuuuuuuuu
Administrative Contact:
 7777 uuuu (
 Fax: none
 sdfsdf, uuuuuuuuuuuu uuuuuuuuuuuu
Technical Contact:
 7777 uuuu (
 Fax: none
 sdfsdf, uuuuuuuuuuuu uuuuuuuuuuuu
Status: Locked
Name Servers:
Creation date: 19 Mar 2007 02:11:38
Expiration date: 19 Mar 2011 02:11:38
Get Noticed on the Internet! Increase visibility for this domain name by
listing it at
The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us. 
We reserve the right to modify these terms at any time. By submitting 
this query, you agree to abide by these terms.
Version 6.3 4/3/2002
Whois Server Version 2.0
 Domain Name: JETDASH.NET
 Registrar: ENOM, INC.
 Whois Server:
 Referral URL:
 Status: clientTransferProhibited
 Updated Date: 20-mar-2010
 Creation Date: 18-mar-2007
 Expiration Date: 18-mar-2011

posted at: 23:00 :: permanent link to this entry :: 3 comments
posted at: 23:00 :: permanent link to this entry :: 3 comments

comments...        (Jump to the end to add your own comment)

So go on to the next step
John, rather than a failure of policy enforcement, I think this is a somewhat poorly described process. Clearly nothing was done. However, the registrar likely told ICANN they fixed it. ICANN is asking you to report back if there is still a problem. One could argue that they should have at least looked themselves, but they're letting you do the legwork for now, and I would imagine that in many cases, this would be the end of the process, as legitimate whois listing problems would be fixed and confirmed. Please see what happens when you follow the full process. That way we can determine if the process is completely broken or just poorly crafted.

(by Rod Rasmussen 21 Oct 2010 01:28)

I have
When I've done this before and reported that the WHOIS was still wrong, nothing happened. They may well have told the registrar, but since there is no visible followup, report card, or consequences, the bad registrars ignore it.

(by John L 21 Oct 2010 09:18)

All to common
I have called registrars on this before. Under the proper parsing of the language of the ICANN rules, domain names with intentionally false information is supposed to be immediately deleted, but registrars respond that they are supposed to give the time to update or "who do you know the information if intentionally false and that their telephone number is not 1-310-555-1212?

(by Bill Silverstein 22 Oct 2010 19:20)

Add your comment...

Note: all comments require an email address to send a confirmation to verify that it was posted by a person and not a spambot. The comment won't be visible until you click the link in the confirmation. Unless you check the box below, which almost nobody does, your email won't be displayed, and I won't use it for other purposes.

Email: you@wherever (required, for confirmation)
Title: (optional)
Show my Email address
Save my Name and Email for next time


My other sites

Who is this guy?

Airline ticket info

Taughannock Networks

Other blogs

Remembering JD Falk - 10 years later
222 days ago

A keen grasp of the obvious
New Hope for the Dead
464 days ago

Related sites

Coalition Against Unsolicited Commercial E-mail

Network Abuse Clearinghouse

© 2005-2020 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.