[SpamCop-List] Re: Need interpretation/translation

[Spam N Scams Reporter]

Mike Easter wrote:
> Spam N Scams Reporter wrote:
> 
>>Not sure how to report this.
> 
> 
> It depends a little [but not much] on whether you are trying to report a
> source or a spamvertiser [or even something else, like an open smtp
> relay]
>

I was filing a Whois Data Problem Report and didn't know if this data 
was valid or not.

> 
>>Domain Name : hotcap.net
> 
> 
> Generally the domainname registration is *not* the first line of attack.
> The first line of attack is how the netblock provision is reg'd with the
> regional registrar.
> 
<snip>

> 
>>>>Registrant::
>>
>>  Name : &#54028;&#46976; &#48165; &#44592;&#49696;
> 
> 
> Unicode, but mostly bogus.
> 

This is what I was wanting to know. Thanks.


>>  Email : info at hotcap.net
>>  Address : &#44867; &#46020;&#47196; 43
>>  Zipcode : 1111
>>  Nation : AR
>>  Tel : |
>>  Fax :
>>
>>They show as ? in the Whois Data Problem Report. I've run into this
>>numerous times.
> 
> 
> The registrar is
> Registrar: YESNIC CO. LTD.
> 
> The nameservice is 'disputed' - according to the root servers it is the
> same IP as the target and named ns.hotcap.net, but according to the
> registrar yesnic it is ns1 & ns2 activenameserver.info - so apparently
> yesnic isn't up to date.
> 
> Since the registrar yesnic is outawhack, I would give that to internic
> at their site."To report incomplete or inaccurate Registrar Whois data,
> please visit the new Whois Data Problem Report System."
>  http://wdprs.internic.net/
> 

This is what I was doing. I am collecting Whois Data Problem Reports for 
registrars like Yesnic that do nothing to comply with the ICANN 
provisions and file Registrar Problem Reports with ICANN after a couple 
of weeks if the registration has not been corrected.

I figure that eventually, if ICANN receives enough Registrar Problem 
reports about a registrar, they may do something to bring those, like 
Yesnic, into compliance. One can only hope.



> " All accredited registrars have agreed with ICANN to obtain contact
> information from registrants, to provide it publicly by a Whois service,
> and to investigate and correct any reported inaccuracies in contact
> information for domain names registered through them.
> 
> Reports submitted through this facility will be forwarded to the
> appropriate registrar for handling, and the progress of your report will
> be tracked"
> 
> 
> The characters in the yesnic registration are one type of depiction of
> unicode chars, but there's no point in looking them up, because the
> registration looks bogus anyway.
> 

I do like to make sure that it's bogus, not just 'looks' bogus.  I file 
a  lot of reports to ICANN and I would like my reports to be taken 
seriously. I'm looking for more long term solutions other than 
'whack-a-mole' types.

Thanks again,
Brian