Latest news of the domain name industry

Recent Posts

Want thousands of free .jobs domains? Now’s your chance

Kevin Murphy, August 11, 2010, Domain Registries

Employ Media wants to hear from companies interested in registering .jobs domain names in bulk, at the start of its recently approved landrush process.

The company has set up a web site to handle expressions of interest of “high level business concepts on how these domain names could be developed either individually or in bulk”.

Before now, .jobs domains have been limited to the name of the company registering them. IBM, for example, uses ibm.jobs to bounce to its HR pages.

Employ Media applied to ICANN to liberalize the namespace, allowing the registration of the names of professions and places, and was successful over the objections of many existing jobs boards.

From the press release:

“We believe accepting EOI’s will facilitate dialog with potential RFP applicants. We’re particularly interested in hearing ideas comprising a bulk number of domains,” states Tom Embrescia, Chairman of Employ Media. “Up to now, we’ve only allowed company names such as www.Applebees.jobs and www.UnionPacific.jobs. Now we are looking for ideas for how companies can easily and uniformly distribute their jobs and related information to user-intuitive sites such as www.Chicago.jobs, www.sales.jobs, and www.restaurant.jobs.”

Right now, the company is only looking for 150-word outlines of business ideas. The RFP period will begin shortly after the EOI period closes on August 24 (less than two weeks from now).

Employ Media already has plans in place with the DirectEmployers Association to launch universe.jobs, a free jobs portal using thousands of premium .jobs domains as entry points.

It remains to be seen how concrete these plans are, although the two outfits have already run a “beta test” of the scheme, so I’m guessing they’re quite firm.

If you fancy your chances, the RFP site is RFP.jobs.

There are at least two filthy domain hacks I intend to apply for. All I need to do is think of a way I can pretend they benefit the global HR community, which is an unfortunate prerequisite.

DotFree wants to give away .free domains

Kevin Murphy, August 10, 2010, Domain Registries

A Czech company has become the latest to say it will apply for a new top-level domain, but it’s got a unique twist – domain registration will be free.

The dotFree Group, based near Prague, says it will apply for .free and offer the domains free of charge.

.FREE is going to be a generic Top Level Domain, which is going to be available for free, as the name itself says. Individuals, companies, organizations, groups, etc. are going to be able to register their .FREE website under a desirable name.

Can: open. Worms: everywhere.

  • How many registrars will actually want to carry this TLD?
  • How will dotFree fund its ICANN application fee and ongoing running costs?
  • Will there be a landrush? How will that work?
  • Will there be an after-market? With a no-risk investment, .free would be a domainer’s paradise.
  • How will the registry prevent rampant abuse by spammers?
  • Are these guys serious?

I’ve got a call in, so maybe we’ll find out more soon.

The dotFree Group already offers free domain names at the third level under cz.cc, and sells a pricey script so anyone can become a “registrar”.

The company sounds like it already has the infrastructure to support a small TLD.There are apparently 50,000 .cz.cc domains registered today, which already makes it bigger than some gTLDs.

(Hat tip: @dotRadio)

Iron Mountain beds another registry

Kevin Murphy, August 10, 2010, Domain Registries

Iron Mountain puts itself about a bit, doesn’t it?

The company has signed a co-referral deal with wannabe new top-level domain registry operator UrbanBrain. The deal appears identical to one it inked with Central Registry Solutions in May.

Under these deals, Iron Mountain will refer potential TLD applicants to UrbanBrain (or CRS) and the registries will refer their clients to Iron Mountain for data escrow services.

The press releases don’t make it clear under what circumstances clients will be referred to UrbanBrain versus CRS, but given UrbanBrain is Japanese it could be along geographical lines.

Again, I ask: who benefits most?

My guess is still Iron Mountain, which has already got a pretty tight grip on the ICANN-mandated data escrow market. I can’t see it sending as much traffic to the registries as it receives.

Domainers get love, but no refunds for .co cybersquatters

Kevin Murphy, August 10, 2010, Domain Registries

.CO Internet has ramped up its anti-cybersquatter messaging, promising no refunds for trademark-infringing .co registrants, no matter how much they paid for their domains.

An “Open Letter to .co Domain Registrants”, published by the company yesterday, also contains a shout-out to domainers, which I think may be a first from a domain registry.

The letter points out, as I have previously, that .co is subject to the UDRP on the same terms as other TLDs including .com.

The outcome of a UDRP proceeding is binding, and no refunds will be given under any circumstances — regardless of how much money you may have paid to secure the domain; whether the domain was acquired directly via a domain registrar or through a domain auction venue; and whether you were unaware that you had infringed on someone else’s rights.

There’s similar text on the front page of COauctions.com, where the registry is currently auctioning off contested landrush applications.

Is this just a matter of legal ass-covering? Or are there some gray-area domains in the landrush auction?

Despite all the promotional work the registry performed in the run-up to general availability, there are still plenty of people who seemed to believe .co represented new, lawless territory.

The letter ends with the statement that “.CO Internet is committed to protecting the rights of brand owners, domain investors, and end users.”

Domainers getting some love in the same breath as brand owners is not something you hear every day, particularly from registries.

.CO landrush auctions kick off today

Kevin Murphy, August 10, 2010, Domain Registries

.CO Internet has today started auctioning off domain names that had multiple applicants during the .co landrush earlier this summer.

According to the company, over 2,500 names will be auctioned over the next four weeks. The top three most-contested names were Slots.co, Insure.co and Denver.co.

Other notable .CO domain names up for auction include Mexi.co, America.co, Betting.co, Vitamins.co, UsedCars.co, Happy.co, Ebook.co and Jackpot.co.

Registrants who applied for one of the contested domains need to sign up at www.COauctions.co.

There have been almost 410,000 .co registrations since the Colombian country-code domain was opened up to international registrants last month.

So far, the biggest seller has been o.co, sold to Overstock for $350,000.

Given that slots.com sold for $5.5 million, it seems likely that slots.co could fetch something in five figures or beyond.

Governments want morality veto on new TLDs

Kevin Murphy, August 6, 2010, Domain Registries

ICANN’s Governmental Advisory Committee wants to be able to kill off new top-level domain applications on cultural and religious grounds.

The GAC has finally broken its radio silence on the “morality and public order” or “MOPO” issue that was such a hot topic at the Brussels meeting in June.

A letter to ICANN (pdf), sent by Canadian GAC chair Heather Dryden, leaves little room for doubt where the GAC stands.

The GAC firmly believes that the absence of any controversial strings in the current universe of top-level domains (TLDs) to date contributes directly to the security and stability of the domain name and addressing system (DNS) and the universal resolvability of the system.

As a matter of principle… the GAC believes that the object of stability, security, and universal resolvability must be preserved in the course of expanding the DNS with the addition of new top-level domains.

This is actually quite powerful stuff.

The GAC is basically saying that no new TLDs should be introduced that would be unacceptable to the lowest common denominator world government.

Think Uganda, asked to make a call on .gay.

Think about any oppressed ethnic group without a territory that wants to apply for its own TLD.

The GAC wants ICANN to create a process for governments and others to object to TLD applications on religious, cultural, linguistic, national and geographical grounds.

It could even result in .xxx being objected to, even though it’s technically part of the 2005 round of new TLDs – the GAC wants the objection process to apply to “all pending and future TLDs”.

.XXX to run the ICANN gauntlet yet again

Kevin Murphy, August 6, 2010, Domain Registries

Bring on the Christians!

The contract between ICANN and ICM Registry to run the .xxx adults-only top-level domain is to be submitted for an ICANN public comment period, again.

ICANN’s board resolved yesterday to publish the proposed registry agreement for comment for at least 30 days.

But it has not yet decided whether to refer the deal to its Governmental Advisory Committee, which remains ICM’s major potential pitfall on its route to the root.

As long as the public comment period kicks off quite soon, the ICANN board could be in a position to make that call at its weekend retreat, September 24.

The .xxx application has generated more public comment over the years than all other ICANN public comment periods combined.

Its last such period, earlier this year, saw thousands of comments, most of them filed in response to outreach by right-wing American Christian groups.

Objections are also regularly received from members of the Free Speech Coalition, a porn trade group.

I expect this forum will be no different. It will be interesting to see what tactics are rolled out this time, given previous failures.

Here’s the meat of the latest resolution:

RESOLVED (2010.08.05.21), upon receipt of ICM’s application documentation, ICANN Staff is authorized to post ICM’s supporting documents and proposed registry agreement for the .XXX sTLD for public comment for a period of no less than 30 days.

RESOLVED (2010.08.05.22), upon completion of public comment period, ICANN Staff shall provide the Board with a summary of the public comments and shall make a recommendation to the Board as to whether the proposed registry agreement for the .XXX sTLD is consistent with GAC advice.

RESOLVED (2010.08.05.23), once the Board has received the above public comment summary and recommendation from the ICANN Staff regarding the proposed registry agreement for the .XXX sTLD, the Board shall at its next possible meeting, consider this recommendation, and determine, consistent with the ICANN Bylaws, whether a GAC consultation shall be required.

.jobs gets its landrush windfall

Kevin Murphy, August 6, 2010, Domain Registries

Is .jobs the newest generic top-level domain?

ICANN has approved changes to Employ Media’s .jobs registry contract, meaning the company is now free to start auctioning off premium generic .jobs domain names to the highest bidder.

The decision paves the way for the company to implement its deal with the DirectEmployers Association, under which the DEA plans to use thousands of geo.jobs and industry.jobs domains as portals to a massive free jobs board.

Currently, .jobs domains are only available in the format companyname.jobs, and there have been only about 15,000 registrations. The new contract removes that restriction.

Under the changes, whatever domains are left after the DEA takes its chunk could be auctioned, and then .jobs could be opened up to essentially any registration.

The .jobs contract still restricts who can register domains, however, to so-called Qualified Applicants.

That’s defined like this (my emphasis):

A qualified applicant (“Qualified Applicant”) is a person who is (a) a member of SHRM; or (b) engaged in human resource management practices that meet any of the following criteria: (i) possess salaried‐level human resource management experience; (ii) are certified by the Human Resource Certification Institute; or (iii) are supportive of the SHRM Code of Ethical and Professional Standards in Human Resource Management, as amended from time to time (the “Code”).

Looks like a check-out check-box to me.

ICANN’s resolution was made over the strong objections of many jobs web sites and the International Association of Employment Web Sites.

Palestine gets its own Arabic domain names

Kevin Murphy, August 6, 2010, Domain Registries

ICANN has awarded five more non-ASCII top-level domains under its internationalized domain name fast-track process for country-code TLD managers.

Palestine, Tunisia and Jordan will all shortly receive delegations for Arabic-script versions of their existing ccTLDs. They join previous recipients including Saudi Arabia and Egypt.

Palestine gets فلسطين, Tunisia gets تونس and Jordan gets الاردن.

These apparently translate as “Falasteen”, “Tunis” and “al-Ordan”, respectively, and are presumably more useful to Arabic speakers than .ps, .tn and .jo.

Because they’re all Arabic, the dots appear to the right of the TLD, rather than the left.

The Occupied Palestinian Territory is, of course, a fringe case when it comes to ccTLDs.

But long ago, IANA made it a matter of policy that it would make no decision about which country or territory deserves its own ccTLD.

If it’s on the ISO 3166-1 list, which is overseen by the UN, it’s in. Palestine was added to that list in 1999, and was awarded .ps by ICANN/IANA in 2000.

The .ps registry is sponsored by the Palestinian National Authority’s telecoms ministry.

ICANN has also resolved to delegate Thailand the IDN ccTLD .ไทย and Sri Lanka both .ලංකා and .இலங்கை.

Interestingly, these two TLDs were approved as part of yesterday’s board meeting’s consent agenda.

The three Arabic names were approved separately, preceded by this:

RESOLVED (2010.08.05.13), the Board IANA Committee is directed, in coordination with ICANN’s CEO, to create improvements to the processes and new guidelines for implementation of the IDN ccTLD Fast Track process.

Judgment day for .xxx and .jobs

Kevin Murphy, August 5, 2010, Domain Registries

ICANN’s board of directors will today meet to decide the fate of the .xxx and .jobs top-level domains.

ICM Registry will find out whether its contract to run .xxx will have to face a potentially lengthy review by ICANN’s notoriously slow-footed Governmental Advisory Committee.

Employ Media will find out whether it will be allowed to relax its registration rules to allow non-company-name .jobs domains.

If the board decides no further GAC intervention is needed, ICM will be on a fast track to having its TLD considered for delegation in Cartagena this December.

If Employ Media’s proposal is rejected, it faces more years in the wilderness of managing a registration base in the low tens of thousands.

I have a track record of lousy predictions, but I’m going to go out on a limb again and make a low-confidence prediction that both registries are going to get what they want.

I’m not sure if it’s been noted before, but there are some strong similarities between the two TLDs and their proposals.

In the case of .xxx, some of the main opponents of the domain have been the adult industry itself. With the .jobs liberalization, the loudest outcry has come from jobs boards.

Both are essentially cases of a registry proposing something that makes good business sense for itself, but which is not necessarily what a significant portion of its would-be constituents want.

In the case of ICM, lack of support from the porn business was what originally killed off the application (at least, that was the official line), a decision that ICANN was recently forced to reverse if not recant.

In the case of .jobs, ICANN’s recent summary and analysis of the well-attended public comment period, which the board will be given prior to voting, may be a telling.

Most of the opposition to the .jobs deal was organized by the International Association of Employment Web Sites, which itself sent a long letter spelling out precisely why it thinks the scheme is bogus.

Of the 2,600 words IAEWS submitted, ICANN’s summary and analysis document quotes just two sentences, one of which is this:

“Neither human resources professionals employed in corporate human resources (‘HR’) departments nor executive search/staffing firms [which are part of the .JOBS community] are eligible for membership in IAEWS.”

The quote is pulled from the introduction of the IAEWS letter, rather than the substance of its objection, and the text in square brackets is ICANN’s own insertion.

I can’t think of any reason that text is worth quoting other than in order to dilute the significance of the IAEWS’ arguments against the .jobs liberalization.

Indeed, the document uses more wordage to describe the nature of the IAEWS letter-writing campaign than it does the content of its letters, which can’t look good for the IAEWS.

Employ Media’s response to the IAEWS letter is quoted at greater length, particularly the bit where it compares its own plans to the new gTLD program.

While they claim that the addition of occupation, industry and geographical identifiers at the second level within the .JOBS sTLD will lead to increased confusion within the marketplace, it is hard to reconcile this argument to ICANN’s extensive public policy work and implementation plan in connection with the new gTLD process. The same fundamental economic basis for going forward with the whole new gTLD initiative also applies to this .JOBS RSEP request; these issues should not be re debated and should not delay or deny approval of the .JOBS RSEP request.

If you’re an ICANN board member, aware of how much of ICANN’s credibility is tied up with the new TLD program, can you really argue with that?

Of course, board and staff don’t always agree, so I may be way off the plot here, but it seems to me that .jobs is likely to very soon become a considerably more open namespace.