ICANN ICANN Email List Archives

[irtp-b-rec8]


<<< Chronological Index >>>        Thread Index >>>

Comments about "Standardizing and Clarifying WHOIS Status Messages"

  • To: "irtp-b-rec8@xxxxxxxxx" <irtp-b-rec8@xxxxxxxxx>
  • Subject: Comments about "Standardizing and Clarifying WHOIS Status Messages"
  • From: Dieter Anders <prodomainname@xxxxxxxxx>
  • Date: Fri, 9 Mar 2012 10:33:06 +0000 (GMT)

1) There should be a link on Internic.net under the Whois section on the main 
page and on the result page that leads to a page with all existing status and 
their descriptions.


2) All gTLD registry operators should be required to use the same status names, 
which would correspond to the standard EPP status codes (for example Verisign 
currently uses the EPP status code "RedemptionPeriod" while other registry 
operators use the term "Pending Delete - Restorable".

3) All gTLD registry operators and registrars should also be required to 
provide a link on their Whois search page that redirects either to the page of 
the Internic website with the description of all status or to a similar page on 
their own websites.

4) In the case of gTLDs where a thin registry applies, registrars should be 
required to include the Whois data from the relevant registry into their own 
Whois search results.

5) The link to the website http://www.uwhois.com should be removed from the 
Internic website (who can tell if the owner of http://www.uwhois.com does not 
make any front-running?) and replaced by an indication that the Whois search 
tool on Internic.net only works for gTLD domain names and that people who want 
to query ccTLD domain names should visit the website of the corresponding 
registry operator (with a link http://www.iana.org/domains/root/db/ for finding 
the relevant website).

6) A link to a domain name / Punycode converter should be added to the Internic 
website with a note that domain names with diacritical signs or non-Latin 
characters should be queried with the punycode.


<<< Chronological Index >>>        Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy