Posts Tagged Registrar

The new “Domain Registry of America”: “Domain Renewal Group”

Today I received my mail from France and noticed a weird letter coming from “US Postage paid, Jamaica N.Y. 11431, Permit #9014″. The letter had the old familiar look you get from those “Domain Registry of Amarica”: american flag, and company name containing the word “Domain” and trying to look like the company handling domain renewals for everyone (that’s the impression you get from the name)… oh and let us not forget the amercan flag, it’s important to be american.

This one contains a return enveloppe to “Domain Renewal Group, 56 Gloucester Rd., Suite 526, London, England, SW7 4UB”. I guess since they posted this to France, it’s only normal they put an address somewhere close.

The letter itself is exactly the same you get from “Domain Registry of America”: your domain will expire soon and you have to reply by date D to renew it.

Even if this letter outlines the fact this is not an bill but an easy way to switch to a different provider, direct marketting of domain owners is seen as bad practice, and as far as I know, only them are doing it, and they are now doing it with different names, most likely to mitigate their bad image over new names the customer hasn’t been warned about.

Whois of the domain domainrenewalgroup.com shows it is owned by “Domain Registrar – Domain Registry Group” with an email on droa.com, the well known “Domain Registry of America”.

Some more remarks on the letter:

  • It introduce the ability to choose a registrar as something new. It says “Privatization of Domain Registrations and Renewals now allows the consumer the choice of Registrars [...]“. The “now” is likely to confuse almost anyone (ability to be a registrar for com/net/org domains has existed since November 30th 1999)
  • The letter focuses on payment and says nothing about the transfer procedure. The customer has no information on the process that will come, with the obligation to unlock domain, etc
  • Nothing is said either about services linked to the domain. For example let’s say you have a web hosting with domain name and you pay 40€/year. This letter tells you you can renew for 28€/year, and while explicitly stating this is a domain renewal, most customers won’t make the difference.
    Also, the letter states that not renewing will result into the customer “losing his online identity, making it difficult for his customers and friends to locate him on the Web”. This  sounds like renewing with them will allow the customer to keep his online presence, which is false.
  • The second paragraph is formulated in a way that will make most people think they have to renew with them. While it is an impressive work of marketting, it lacks something called ethics.

Most registrars have been tired of the plague brought by DROA, and have to tell their customers that those letters are not bills, because customer won’t read. One would expect after all those years DROA to go out of business, but it’s not the case, and they are probably quite comfortable (when I see the price they ask for, I can understand).

Some day another registrar might decide to use the same kind of letter and attempt to trick people into transferring domains at an outrageous price, let’s just hope the practice will become prosecutable before it happens (it is already technically illegal, as whois information is not made for mass-marketting but for fixing technical problems, still DROA seems to be doing fine).

Tags: , , , , , ,

Registrars and authcodes

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: , , , , , ,

GANDI.NET – Registered domains count

You already saw, I guess, the gandi.net statistics on top of their page…

Like many registrars, I can only believe those statistics are faked to make it look like gandi.net is handling more domains than it is actually handling.

Let’s take a simple example: I transfered 17 domains from GANDI, and they still show in the interface, can be “locked”, etc… (nothing happens in reality). Here I believe GANDI might not delete correctly domains transfered to another registrar. While 17 domains might be a really small amount, if it’s the case for all domains transfered from GANDI, it might boost the statistics quite a lot…

Anyway if you want a registrar with fast support and good answers to your questions, come to KalyHost.

Tags: , , , ,

KalyHost – Domain names now available

After some months of work, we finally are able to have our first shop online, with domain names sales and management.

You can see this on the KalyHost page for domains, where you can order many extensions for cheap (.NET are on sale until 27 february).

Sale is done via Paypal, and domain is usable immediatly after sale. You can then manage your domain as you want to. Once we finish setting up webhosting and some other services (affiliation, etc) KalyHost will finally be ready for the real show. For now cheap domains are already a great thing, and I wish more people could have a look at it.

Tags: , , , , ,

OVH, French registrar ignorant of ICANN policies

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: , , , ,