Monday, September 3, 2018

LinkedIn: did some cleaning

I have a lot of contacts on LinkedIn and I would easily write that I n-e-v-e-r shared anything with probably 90% of them so I wonder: what's the point in allowing someone to add me in his list of contacts if he has nothing to tell me?

I once asked to someone who added me (and I accepted him to add me to his list) what was the reason for adding me and the guy...just did not answer me.

3,500 contacts?
I have an important list of more than 3,500 contacts and I use LinkedIn exclusively for work. I don't pay attention to the rest: my friends and family usually contact me on Facebook or send me emails...oh...and they call me too.

I've started a little cleaning on LinkedIn and since it is not possible to massively delete contacts - yes, you have to do that one by one on LinkedIn - I have decided to use the method below:
  • Self proclaimed mentors: go away;
  • Seo specialists and marketing experts: go away;
  • No picture? Go away;
  • The word "influencer" (or equivalent) appears in you title? Go away;
  • You've not answered me after 2 messages: go away;
  • Recruiters: go away;
  • You sell wine: go away ;-)
  • You still use a ".com" domain name? go away (joking);
  • Advertising your number of LinkedIn connections in your signature? Go away;
  • .com Domainers domain name investors: go away;
  • You forgot to put a capital letter to your family name: go away;
  • I don't understand more than 50% of what is written in your signature or title? Go away;
  • No personalized message with the reason why you want to add me on LinkedIn: go away;
  • Not in the new gTLD business (or close to it): go away unless you have a serious question.
Limiting to 300 connections = done
I did clean my list of connections and lowered its number of contacts to 300. I think that makes more sense and as a new method, I will try to stick to 300; meaning that I will remove a connection for one gained.

My email can be used to contact me instead (or visit Jovenet Consulting).

An by the way, I now refuse LinkedIn incoming connection attempts when there's no introduction message ;-)

Tuesday, June 26, 2018

A limit of the multistakeholder governance model

I read the ICANN approved board resolutions and a rationale for resolutions on an independent examination. I found that it tells a lot on how the ICANN is becoming an enormous organization which could be compared to some French administration where you sometimes wonder...what people do there.

ITEMS International was appointed as the independent examiner for the At-Large Review (a working group at the ICANN which works on plenty of important things to make Internet better).

Too focused on internal committees and procedures
I stopped on an Input from the ICANN community and I read:
"...many of the problems identified by the ITEMS report do exist. In particular, that: It is too focused on internal committees and procedures, and that it is too focused on enlarging the power and resources received by ALACin the ICANN ecosystem."
I try hard to follow-up with what some groups work on but I not only have a language barrier, I also DON'T HAVE THE NECESSARY TIME for this and with the volumes of documents to understand and the number of calls to participate to, it really takes time. I also sometimes feel that the very small groups working "on their thing"are making it impossible for any new comer to participate...many working group are most of the time the only one to understand what they are doing.

It also takes longer and longer to decide. Isn't it time to simplify procedures and suggest things like "deadlines"?

The ICANN is important for the Internet to keep working properly but aren't we starting to see the limit of the multistakeholder governance model?

The .GAY and .MUSIC new gTLDs
The .GAY and .MUSIC new gTLDs have been in "stand-by" for years: with all the comments, reports, procedures, discussions...can't someone "do something" for a resolution to be taken?

  • Consideration of Reconsideration Request 18-1 for DotMusic Limited: No resolution taken;
  • Consideration of Reconsideration Request 18-2 for dotgay LLC: No resolution taken.
Unless I am wrong, the new gTLD Applicant Guidebook from the first round of the ICANN new gTLD program says that problems of the first round should all be solved before the next round to start: isn't the multistakeholder governance model helping opponents of a future round here? In the case of .GAY ... there are a lot of opponents.

Friday, June 8, 2018

Job: Director of Channel Development

Dominion Domains, a division of Dominion Enterprises (Norfolk, Virginia) is hiring a Director of Channel Development.


Dominion Domains is the Registry Operator for five Top Level Domains (TLDs) including .autos, .homes, .boats, .yachts and .motorcycles.

Saturday, June 2, 2018

Registered in 1998: Guillon.com is 20 years old

I registered guillon.com in 1998-06-02: that was 20 years ago.

It is my oldest domain name and at the time, I had no idea that I would use it for the rest of my life.

I now use the same ending in ".email"...for Email.

Wednesday, May 9, 2018

Introduction of .APP domains by Google

...and how to secure them
.app, the web's first secure-only open top-level domain (TLD) for mobile apps and developers, is launching on May 8. This in-depth technical talk covers use cases for .app domain names, HTTP Strict Transport Security (HSTS), best practices for secure website development, and the unique security benefits of .app domains thanks to TLD-wide HSTS.

Monday, April 30, 2018

How to index a redirection in Google?

I just hit "site:.sncf" to try to find out which are the two new domain names ending in ".sncf" which were just created and I found nothing new but www.wifi.sncf. The picture below is what appears, indexed in Google:


I clicked on it and noticed (again) that it is a redirection.

Question to Bill Hartzer (@bhartzer) : how do you index a redirection in Google?

Friday, April 13, 2018

UPDATE: Phishing, a few weeks after

I wrote a small article (in French) on several procedures that I just tried at the ICANN and at a Registrar hosting a domain name used for phishing.


What we did
Basically, ICANN offers 2 emails to write to and we also used two different procedures at the Registrar concerned: the abuse email and a dedicated form.

The result is the one expected: the ICANN created a case and answered us the below but none of the other two parties we contacted even answered us.

Answer received from ICANN
Dear Jean Guillon,
Thank you for contacting the ICANN Global Support Center.
I will be happy to provide you with further information. Please note, the 2013 Registrar Accreditation Agreement (RAA) requires ICANN-accredited registrars to provide abuse contact information, take steps to investigate reports, and respond appropriately to any reports of abuse. The full abuse contact requirements can be found in Section 3.18 of the 2013 RAA at: https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#3.18 .
For more information about Registrar Abuse Reports and the type of reports, please see: https://www.icann.org/resources/pages/abuse-2014-01-29-en .
If you wish to submit a complaint to our Contractual Compliance about the registrar failing to comply with the requirements, please complete the form at:https://forms.icann.org/en/resources/compliance/complaints/registrars/standards-complaint-form .
Please allow 3-5 business days for our Contractual Compliance Team to respond to your complaint submission.
I hope this information is helpful to you. Please contact us if you have any additional questions or concerns. This case will now be resolved. Thank you for contacting ICANN.
The ICANN form (...)
I submitted a complaint to the Contractual Compliance Team (as suggested in the answer received by the ICANN) but at this stage, I thought that ICANN would already have acted since I already sent all informations: this form is probably going to be sent to the Register.it

26 of March 2018
  • ICANN ask the same informations + a copy of the abuse email that I sent to Register IT with my authorization to contact them (...);
  • They also write that I did not fill in their form correctly (...).
I resend them all this (...).

13 of April 2018(and after informing the ICANN (who answered it would inform the Registrar))
I received an email from Register.it and here what it says: "Dear Sir according to ICANN request, here below a summary of actions taken by our Abuse Team with reference to your request, please be informed that":
  • "on March 8, 2018 we have received your abuse report (copies of emails received are attached)": I never received confirmation of this.
  • "In the following 24 hours our dedicated Abuse Team has examined the issue and taken the necessary steps to solve it": I seriously doubt it but surprisingly, after complaining several times to the ICANN and after more than a month, Register.it returned with this answer.
  • "Each abuse report requests of course different actions, in this case they intervened removing the dangerous involved folders": do I understand that you removed a client's folder hosted with you? I checked the sub-domain and it is still in place and not pointing to an error.
  • "Customer has been then accordingly informed. Just for your further information in this case RNH and AH are the same entity": I have no idea what this means and I would have expected the domain to be a little more investigated because the whois still shows a "Domain Status:ok".
16 of April 2018
After more than one month exchanging with registrar and ICANN and for one single domain name hosting a phishing operation, ICANN considers that the abuse complaint is closed:
"Dear Jean Guillon,
Thank you for submitting an Abuse complaint concerning the registrar REGISTER.IT SPA. ICANN has reviewed and closed your complaint because:
 
- The registrar demonstrated that it took reasonable and prompt steps to investigate and respond appropriately to the report of abuse. 
ICANN considers this matter now closed.
Please do not reply to the email. If you require future assistance, please email compliance@icann.org; if you have a new complaint, please submit it at http://www.icann.org/resources/compliance/complaints .
 
ICANN is requesting your feedback on this closed complaint. Please complete this optional survey at https://www.surveymonkey.com/s/8F2Z6DP?ticket=changed .
Sincerely,
 
ICANN Contractual Compliance
Let's be honest: WHO GOES AS FAR AS THIS WHEN RECEIVING A PHISHING EMAIL AND WHO UNDERSTANDS SUCH ANSWERS?

Score
Phishers / Gmail filter = 1
Icann / Register.it = 0

Useless procedures
This way to proceed against phishing for end users is an absolute nonsense: the ICANN procedures and rules for such common problems are useless.

Read my article in French.

Monday, April 9, 2018

Will it be .ONLINE or .ONL ?

I just noticed that the .ONLINE new gTLD has a competitor: there is a .ONL extension too. As the registry websites states: ".ONL provides limitless access to everything online. It's the natural domain for all of your online activities".


More about this registry can be found here.

A few numbers
  • The .ONLINE new gTLD has 812.000 domain names registered;
  • The .ONL new gTLD has 5,270 domains registered.
I didn't notice the .ONL Top-Level Domain meant "online" until today (...) so I added to it to the similar TLDs' list.

Friday, March 30, 2018

The .BMW new gTLD

While updating the CARS new gTLD report for the month of March 2018, I noticed that the .BMW new gTLD had 53 ".bmw" domain names registered in February to 108 at the end of March.

From the examples that I tested, most are not redirections anymore but real websites such as: http://ratzel.bmw

Monday, March 26, 2018

For .STEPHANE

I just learnt today that Stéphane Van Gelder passed away.

My friend Murielle called me.

Many of us in France have worked with and for Stéphane. I personally worked many years with Stephane to launch new gTLDs at INDOM (which was then acquired by another company). He is the person who taught me everything that I did not know about domain names: he actually taught me that Versign was a thin registry and not a thick one: I did not know the difference...

When I joined INDOM, years ago, he also was the first French guy to have delivered .BRAND new gTLD studies when we did not even know when the first round of the ICANN new gTLD program would start. Actually, we were very good at what we did but he was the guy to think years in advance.

Stéphane was a person of precision. I remember the number of times he asked me to re-write things because I would not have seen a mistake in a word or have missed an accent: I remember going to his office at Indom 10 times a day and getting back to mine ultra pissed because I would have I missed a correction in a study.

...I don't really know what to write in such circumstances...

Today is a sad day.
RIP Stéphane.

More covers here and here.