<div><div dir="auto">George,</div><div dir="auto"><br></div><div dir="auto">Yes, that is the domain. My point being, this domain was renewed after it was suspended for phishing.</div><div dir="auto"><br></div><div dir="auto">I referred to the Chrome browser display as evidence that it was in fact renewed (you are correct though, there doesn't appear to be another phishing site back up and running at the moment, with that said I didn't check the MX records to see if email was being exploited)...although there is nothing in the URS policy that prevents that from happening as far I as understand.</div><div dir="auto"><br></div><div dir="auto">Also, the trademark owner may have other remedies available, but assuming no appeal, does it make sense to require the trademark owner to file another dispute, i.e. a UDRP, to recover the same domain that was suspended under the higher burden of proof required in URS proceedings?</div><div dir="auto"><br></div><div dir="auto">Best regards,</div><div dir="auto">Claudio</div><br><div class="gmail_quote"><div>On Tue, Dec 5, 2017 at 5:37 PM George Kirikos <<a href="mailto:icann@leap.com">icann@leap.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Claudio,<br>
<br>
Are you talking about the domain beginning with c, and which also<br>
contains a hyphen? I'll link to the current WHOIS at DomainTools of<br>
the domain name it seems to be, instead of the domain itself:<br>
<br>
<a href="https://whois.domaintools.com/client-boursorama.frl" rel="noreferrer" target="_blank">https://whois.domaintools.com/client-boursorama.frl</a><br>
<br>
According to the WHOIS, the nameservers are:<br>
<br>
Name Server: <a href="http://ursns1.adrforum.com" rel="noreferrer" target="_blank">ursns1.adrforum.com</a><br>
Name Server: <a href="http://ursns2.adrforum.com" rel="noreferrer" target="_blank">ursns2.adrforum.com</a><br>
<br>
It appears that the domain name did get renewed, but it didn't matter<br>
(except to the extent it saves the complainant registration fees to<br>
register it itself), as it's still on a registry lock/hold, see:<br>
<br>
Domain Status: serverDeleteProhibited<br>
<a href="https://icann.org/epp#serverDeleteProhibited" rel="noreferrer" target="_blank">https://icann.org/epp#serverDeleteProhibited</a><br>
Domain Status: clientHold <a href="https://icann.org/epp#clientHold" rel="noreferrer" target="_blank">https://icann.org/epp#clientHold</a><br>
Domain Status: clientTransferProhibited<br>
<a href="https://icann.org/epp#clientTransferProhibited" rel="noreferrer" target="_blank">https://icann.org/epp#clientTransferProhibited</a><br>
Domain Status: serverTransferProhibited<br>
<a href="https://icann.org/epp#serverTransferProhibited" rel="noreferrer" target="_blank">https://icann.org/epp#serverTransferProhibited</a><br>
Domain Status: clientUpdateProhibited<br>
<a href="https://icann.org/epp#clientUpdateProhibited" rel="noreferrer" target="_blank">https://icann.org/epp#clientUpdateProhibited</a><br>
Domain Status: serverUpdateProhibited<br>
<a href="https://icann.org/epp#serverUpdateProhibited" rel="noreferrer" target="_blank">https://icann.org/epp#serverUpdateProhibited</a><br>
<br>
So, it's not being misused at present. Chrome might be using an<br>
outdated domain blocking list (i.e. no one got it to update the list,<br>
presumably, to have it removed from the list).<br>
<br>
Sincerely,<br>
<br>
George Kirikos<br>
416-588-0269<br>
<a href="http://www.leap.com/" rel="noreferrer" target="_blank">http://www.leap.com/</a><br>
<br>
<br>
<br>
<br>
On Tue, Dec 5, 2017 at 5:18 PM, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>> wrote:<br>
> For ease of reference, URS decisions can be searched on the NAF website,<br>
> see: <a href="http://www.adrforum.com/SearchDecisions" rel="noreferrer" target="_blank">http://www.adrforum.com/SearchDecisions</a><br>
><br>
> You can search for the keyword 'phishing' and set the domain status to<br>
> 'suspended' (for example, see the 2nd domain that is displayed after you run<br>
> this query in the search box)<br>
><br>
> This domain was registered on: 10/25/16, suspended on 11/25/2016, on<br>
> 10/25/17 (the expiration date) the Whois was updated, the current expiration<br>
> is 10/25/18. The current Whois information for this domain matches the Whois<br>
> listed in the URS complaint.<br>
><br>
> Domains that are suspended through the URS resolve to a webpage that says:<br>
> "The Domain Name you’ve entered is not available. It has been taken down as<br>
> a result of dispute resolution proceedings pursuant to the Uniform Rapid<br>
> Suspension System (URS) or .us Rapid Suspension System (usRS) Procedure and<br>
> Rules."<br>
><br>
> This domain does not resolve to the URS suspended landing page described<br>
> above. Rather, my web browser (Chrome) recognizes the IP address as being<br>
> associated with a potential malware/phishing site and displays a "Dangerous"<br>
> warning. So in my view, its pretty clear this domain name was renewed.<br>
><br>
> Best regards,<br>
> Claudio<br>
><br>
><br>
> On Tue, Dec 5, 2017 at 4:40 PM, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Rebecca,<br>
>><br>
>> Thanks. I think the article states that some domains were inadvertently<br>
>> renewed by the registrar. It doesn't say the registrant is not able to renew<br>
>> them.<br>
>><br>
>> In my post, I cited to domains listed on the NAF website that were<br>
>> suspended for alleged phishing, and those domains appear to be renewed<br>
>> because the Whois shows: 1) the same registrant; 2) an update made on the<br>
>> expiration date, extending the registration for one year.<br>
>><br>
>> All good fodder for our group to consider for possible solutions.<br>
>><br>
>> Best,<br>
>> Claudio<br>
>><br>
>><br>
>><br>
>> On Tue, Dec 5, 2017 at 4:15 PM Tushnet, Rebecca <<a href="mailto:rtushnet@law.harvard.edu" target="_blank">rtushnet@law.harvard.edu</a>><br>
>> wrote:<br>
>>><br>
>>> Interesting post. It seems that the domains only showed up as renewed<br>
>>> because of administrative issues, however, based on the end of the article,<br>
>>> and were not actually under the control of the original respondent. So the<br>
>>> phishing concern seems addressed.<br>
>>><br>
>>> Rebecca Tushnet<br>
>>> Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
>>><br>
>>> Sent from my phone. Apologies for terseness/typos.<br>
>>><br>
>>> On Dec 5, 2017, at 3:26 PM, claudio di gangi <<a href="mailto:ipcdigangi@gmail.com" target="_blank">ipcdigangi@gmail.com</a>><br>
>>> wrote:<br>
>>><br>
>>> Jon,<br>
>>><br>
>>> I agree with you about having this question/issue considered by our WG<br>
>>> and potentially addressed with policy recommendations.<br>
>>><br>
>>> I've heard concerns from trademark owners who've had difficulties<br>
>>> securing the abusively registered domain that was suspended in the URS<br>
>>> procedure after it came up for renewal. For example, there are several URS<br>
>>> cases (on the NAF website) that involve alleged phishing activity, where the<br>
>>> domain was suspended, and now it appears renewed by the same registrant.<br>
>>><br>
>>> This practice is described in greater detail within this blog article:<br>
>>> <a href="https://domainnamewire.com/2016/11/18/strange-thing-happening-domain-names-suspended-urs/" rel="noreferrer" target="_blank">https://domainnamewire.com/2016/11/18/strange-thing-happening-domain-names-suspended-urs/</a>,<br>
>>> which states: “The most common thing that happened to these first 50 domains<br>
>>> is that they were renewed. Twice. And they still show the original owner who<br>
>>> lost the URS in Whois.”<br>
>>><br>
>>> Best regards,<br>
>>> Claudio<br>
>>><br>
>>><br>
>>> On Fri, Dec 1, 2017 at 3:19 PM, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hi Jon,<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks for the reminder and apologies for missing that question. We’ll<br>
>>>> add it to the table.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Best,<br>
>>>><br>
>>>> Julie<br>
>>>><br>
>>>><br>
>>>><br>
>>>> From: Jon Nevett <jon@donuts.email><br>
>>>> Date: Friday, December 1, 2017 at 3:04 PM<br>
>>>> To: Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
>>>> Cc: Susan Payne <<a href="mailto:susan.payne@valideus.com" target="_blank">susan.payne@valideus.com</a>>, "<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>"<br>
>>>> <<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>><br>
>>>> Subject: Re: [gnso-rpm-wg] [Ext] RE: Action Items from 30 November<br>
>>>> Working Group Call<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks Julie. I may have missed it, but I had asked on a prior call<br>
>>>> that we add a question regarding whether a losing respondent may renew the<br>
>>>> domain name at issue at all, for one more year (like the complainant),<br>
>>>> during the pendency of an appeal, or forever.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks!<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Jon<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Dec 1, 2017, at 1:50 PM, Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>><br>
>>>> wrote:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Hi Susan,<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks so much for catching that! I tried saving it again as a PDF, but<br>
>>>> it still comes out truncated; I’m not sure why. In any case, I’ve uploaded<br>
>>>> it as a Word document and it looks fine that way.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> I’ve also attached the file.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Kind regards,<br>
>>>><br>
>>>> Julie<br>
>>>><br>
>>>><br>
>>>><br>
>>>> From: Susan Payne <<a href="mailto:susan.payne@valideus.com" target="_blank">susan.payne@valideus.com</a>><br>
>>>> Date: Friday, December 1, 2017 at 1:35 PM<br>
>>>> To: Julie Hedlund <<a href="mailto:julie.hedlund@icann.org" target="_blank">julie.hedlund@icann.org</a>>, "<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>"<br>
>>>> <<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a>><br>
>>>> Subject: [Ext] RE: Action Items from 30 November Working Group Call<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Hi Julie, thanks for these notes from the call. Regarding the revised<br>
>>>> table – there is a link here<br>
>>>> (<a href="https://community.icann.org/pages/viewpage.action?pageId=58729948" rel="noreferrer" target="_blank">https://community.icann.org/pages/viewpage.action?pageId=58729948</a>) to a<br>
>>>> version of the table of 30 November, however only part of the table is<br>
>>>> displaying (I tried downloading too and it made no difference). Would you<br>
>>>> mind re-uploading please – assuming this is the revised table?<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks<br>
>>>><br>
>>>> Susan<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Susan Payne<br>
>>>> Head of Legal Policy | Valideus Ltd<br>
>>>><br>
>>>> E: <a href="mailto:susan.payne@valideus.com" target="_blank">susan.payne@valideus.com</a><br>
>>>> D: +44 20 7421 8255<br>
>>>> T: +44 20 7421 8299<br>
>>>> M: +44 7971 661175<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> From: gnso-rpm-wg [mailto:<a href="mailto:gnso-rpm-wg-bounces@icann.org" target="_blank">gnso-rpm-wg-bounces@icann.org</a>] On Behalf Of<br>
>>>> Julie Hedlund<br>
>>>> Sent: 30 November 2017 16:51<br>
>>>> To: <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
>>>> Subject: [gnso-rpm-wg] Action Items from 30 November Working Group Call<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Dear all,<br>
>>>><br>
>>>><br>
>>>><br>
>>>> The action items noted by staff from the Working Group call held on 30<br>
>>>> November are as follows:<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Suggested Approach from the WG members on the call: To identify topics<br>
>>>> addressed by the Charter questions and capture high-level questions/data<br>
>>>> points for each topic. Suggested questions are:<br>
>>>><br>
>>>> 1) Has it been used?<br>
>>>><br>
>>>> 2) What was the original purpose and is it being fulfilled?<br>
>>>><br>
>>>> 3) Bearing in mind the original purpose, have there been any unintended<br>
>>>> consequences?<br>
>>>><br>
>>>> 4) What changes could better align the mechanism with the original<br>
>>>> purpose/facilitate it to carry out its purpose?<br>
>>>><br>
>>>> 5) How many managed to prevail?<br>
>>>><br>
>>>> Action Items:<br>
>>>><br>
>>>> Develop a strawman of high-level questions and Charter question topics.<br>
>>>> (forthcoming)<br>
>>>> WG to provide comments/thoughts about the proposed approach.<br>
>>>> If the approach is agreed to, WG to analyze the topics addressed by the<br>
>>>> Charter questions against the high-level questions.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Question 1: Should the ability for defaulting respondents in URS cases<br>
>>>> to file a reply for an extended period (e.g. up to one year) after the<br>
>>>> default notice, or even after a default determination is issued (in which<br>
>>>> case the complaint could be reviewed anew) be changed?<br>
>>>><br>
>>>> Action Item: Staff to look up where the 1-year period for Question 1<br>
>>>> originated.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Question 2: Should the Response Fee applicable to complainants listing<br>
>>>> 15 or more disputed domain names by the same registrant be eliminated?<br>
>>>><br>
>>>> Action Item: Staff to look up the origin of the response fee for 15 (and<br>
>>>> more) domains, and why 15 was chosen as a number.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Revised Table:<br>
>>>><br>
>>>> Action Item: Staff will post to the wiki space a revised version of the<br>
>>>> table with excerpts from the notes. Please note that these will be<br>
>>>> high-level notes and are not meant as a substitute for the transcript or<br>
>>>> recording. The recording, transcript, Adobe Connect chat, and attendance<br>
>>>> records are posted on the wiki.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Best regards,<br>
>>>><br>
>>>> Julie<br>
>>>><br>
>>>> Julie Hedlund, Policy Director<br>
>>>><br>
>>>> <URS Sub Team Questions Table - 30 November<br>
>>>> 2017.docx>_______________________________________________<br>
>>>> gnso-rpm-wg mailing list<br>
>>>> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
>>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> gnso-rpm-wg mailing list<br>
>>>> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
>>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> gnso-rpm-wg mailing list<br>
>>> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> gnso-rpm-wg mailing list<br>
> <a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
_______________________________________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org" target="_blank">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></blockquote></div></div>