MagicalTux in Japan

Geekness brought me to Japan!

Posts Tagged OVH

Registrars and authcodes

Mar 11

Posted by MagicalTux in Geek Attitude | No Comments

Many registrars out there have found different ways to implement Verisign’s requirement of harder-to-guess authcodes for domains by asking to have at least one symbol character (non letter, non number) in the authcode.

This had different effect on different registrars. For example french registrar OVH have implemented it a bit too well, resulting in authcodes like “d*zuW.;2t/!>pHbU”, while others have decided that it wasn’t their problem, and just added a prefix to their authcodes. This is the case for example of GoDaddy, whose authcodes are limited in randomness. An authcode will look like: “S1-AF94C9510BA1C”. Yeah right, “S1-” followed by an uppercase hexadecimal string. I’m pretty sure Verisign wasn’t expecting this when they published the new requirement.

Anyway conditions to steal a domain are pretty much complex (you need to have it unlocked, need to know the authcode, and once transfer is started, the current registrant must not ask his registrar to cancel the transfer for 5 days, and even after the domain is transferred, there are ways to get it back – it’s just more expensive). Stealing a domain is a complex operation which will most likely be followed by legal repercussions.

Best thing to do is to check from times to times in a whois that your domain is really showing your name and address. If not, you might need to do something about it before it’s too late. You might want to consider transferring your domain to a company which cares about you ;) (we’ll even fight your old provider if troubles arise, they can refuse transfer only in some specified cases, as long as you are owner of your domain).

Tags: , , , , , ,

OVH, French registrar ignorant of ICANN policies

Dec 4

Posted by MagicalTux in Geek Attitude | No Comments

OVH is an ICANN-accredited French registrar which accepted the ICANN 2009 RAA (Registrar Accreditation Agreement).

Being a registrar implies understanding and applying a lot of rules, especially when dealing with domain names transfers.

For example domain name transfers policies defines how the losing registrar and winning registrar must act. Part 3 is especially interesting as it states reasons why a losing registrar can or cannot deny an outgoing transfer.

Allowed reasons to deny a transfer includes:

  1. Evidence of fraud
  2. UDRP action (Unified Domain-name Dispute Resolution Policy)
  3. Court order by a court of competent jurisdiction
  4. Dispute over the identity of the domain name owner
  5. No payment for previous registration period
  6. Express written objection to the transfer from the Transfer Contact (email, fax, paper document, etc)
  7. The domain is locked (only acceptable if registrar provides a mean to remove lock status)
  8. The domain is too young (must be at least 60 days old before transfer)
  9. Domain has been transferred in the last 60 days (or less, up to the registrar)

Any other reason is not acceptable, especially:

  • Non-payment for a pending or future registration period
  • No response from the Registered Name Holder or Administrative Contact
  • Domain is locked (unless is is possible to unlock it)
  • Domain time constraints (except those stated before)
  • General payment default for other services

Our friends at OVH decided to provide extra protection (aren’t they just trying to prevent customer from going elsewhere?) to domain owners, and add a transfer page to authorize outgoing transfers. When transferring from OVH to somewhere else, the contacts are required to accept the transfer on a specific page. Not accepting the transfer within 48 hours means the transfer won’t happen (at least that’s what the page itself says).

  • This is not allowed by ICANN. Even worse since this is explicitly forbidden.
  • This stupid page takes up to 20 seconds to appear, timings from the OVH network itself confirms it
  • It also contains a stupid CAPTCHA which in turn also takes up to 20 seconds to appear
  • For some TLDs (tested with .fr ccTLD) OVH does not apply this procedure, so why only for gTLD ? (tested with .com .net .org .info)

Of course, I first tried to contact the OVH support, by mail, phone and even writing to Octave (the OVH CEO).

Phone attempt was of course useless (“please contact support by mail, ok I’ll tell the administrator too”  but nothing has happened), mail support proven to be even more useless, and Octave didn’t reply.

Mail support timeline:

  • 2009-11-25 00:50:12: Support initial contact explaining outgoing confirmation page is slow
  • 2009-11-28 11:18:48: Support replies asking “which domain is concerned?”
  • 2009-11-28 11:54:53: Reply to support with list of all domains and explicitly says “All domains I am about to transfer from OVH”
  • 2009-11-30 11:06:01: Reply from support “your problem is related to the display time of the tranfer to OVH order page, if you want we can generate the order for you”

The last solution was to contact ICANN, which is now done. Let’s see how this problem will resolve, however I won’t fight with this transfer page unless I’m on a transfer that *must* happen. Let’s see how OVH will justify denying the transfer in the even no reply comes from the domain contacts…

Tags: , , , ,