Latest news of the domain name industry

Recent Posts

Post your job opening on DI for $1 a day

Kevin Murphy, March 28, 2012, Domain Services

I’d like to introduce a new jobs feature for DomainIncite readers.

As you’ll be able to see in the sidebar to the left, and in the header above, DI Jobs is now live on the site.

If you’re in the domain name industry you probably already know that most of your colleagues and competitors read DI, so I think this might be a great way for you to find new talent.

I’m using SimplyHired, a third-party service, for the listings. The jobs you can see right now — which may vary based on your IP address — are likely to be what it calls “backfill”.

It’s a bit like Google Adsense, and I’ve been made aware that one or two of the listings might therefore appear to be a bit distasteful to begin with (Whois email address scraping? Really?) but these will be bumped from view once a small number of DI reader jobs are posted.

For now, the top five most recently posted jobs will be listed in the sidebar, and the rest will be accessible via jobs.domainincite.com.

The introductory price for a listing is $90 for 90 days, just a buck a day.

Thick .com Whois policy delayed

Kevin Murphy, February 16, 2012, Domain Registries

ICANN’s GNSO Council has deferred a decision on whether Verisign should have to thicken up the Whois database for .com and its other gTLDs.

A motion to begin an official Policy Development Process on thick Whois was kicked down the road by councilors this afternoon at the request of the Non-Commercial Users Constituency.

It will now be discussed at the Council’s face-to-face meeting in Costa Rica in March. But there were also calls from registries to delay a decision for up to a year, calling the PDP a “distraction”.

Verisign’s .com registry contract and the standard Registrar Accreditation Agreement are currently being renegotiated by ICANN, both of which could address Whois in some way.

Today, all contracted gTLD registries have to operate a thick Whois, except Verisign with its .com, .net, .jobs, etc, where the registrars manage the bulk of the Whois data.

Fight brewing over thick .com Whois

Kevin Murphy, January 3, 2012, Domain Policy

This year is likely to see a new fight over whether Verisign should be forced to create a “thick” Whois database for .com and its other generic top-level domains.

While Verisign has taken a deliberately ambivalent position on whether ICANN policy talks should kick off, the community is otherwise split on whether a mandatory thick Whois is a good idea.

Currently, only .com, .net, .name and .jobs – which are all managed on Verisign’s registry back-end – use a thin Whois model, in which domain name registrars store their customers’ data.

Other gTLDs all store registrant data centrally. Some “sponsored” gTLD registries have an even closer relationship with Whois data — ICM Registry for example verifies .xxx registrants’ identities.

But in a Preliminary Issue Report published in November, ICANN asked whether it should kick off a formal Policy Development Process that could make thick Whois a requirement in all gTLDs.

In comments filed with ICANN last week, Verisign said:

As the only existing registry services provider impacted by any future PDP on Thick Whois, Verisign will neither advocate for nor against the initiation of a PDP.

Verisign believes the current Whois model for .com, .net, .name and .jobs is effective and that the proper repository of registrant data is with registrars — the entities with direct connection to their customers. However, if the community, including our customers, determines through a PDP that “going thick” is now the best approach, we will respect and implement the policy decision.

Thick Whois services make it easier to find out who owns domain names. Currently, a Whois look-up for a .com domain can require multiple queries at different web sites.

While Whois aggregation services such as DomainTools can simplify searches today, they still face the risk of being blocked by dominant registrars.

The thin Whois model can also make domain transfers trickier, as we witnessed just last week when NameCheap ran into problems processing inbound transfers from Go Daddy.

ICANN’s Intellectual Property Constituency supports the transition to a thick Whois. It said in its comments:

Simplifying access to this information through thick Whois will help prevent abuses of intellectual property, and will protect the public in many ways, including by reducing the level of consumer confusion and consumer fraud in the Internet marketplace. Thick Whois enables quicker response and resolution when domain names are used for illegal, fraudulent or malicious purposes.

However, Verisign noted that a thicker Whois does not mean a more accurate Whois database – registrars will still be responsible for collecting and filing customer contact records.

There are also concerns that a thick Whois could have implications for registrant privacy. Wendy Seltzer of the Non-Commercial Users Constituency told ICANN:

Moving all data to the registry could facilitate invasion of privacy and decrease the jurisdictional control registrants have through their choice of registrar. Individual registrants in particular may be concerned that the aggregation of data in a thick WHOIS makes it more attractive to data miners and harder to confirm compliance with their local privacy laws.

This concern was echoed to an extent by Verisign, which noted that transitioning to a thick Whois would mean the transfer of large amounts of data between legal jurisdictions.

European registrars, for example, could face a problem under EU data protection laws if they transfer their customer data in bulk to US-based Verisign.

Verisign also noted that a transition to a thick Whois would dilute the longstanding notion that registrars “own” their customer relationships. It said in its comments:

As recently as the June 2011 ICANN meeting in Singapore, Verisign heard from several registrars that they are still not comfortable with Verisign holding their customers’ data. Other registrars have noted no concern with such a transition

ICANN staff will now incorporate these and other comments into its final Issue Report, which will then be sent to the GNSO Council to decide whether a PDP is required.

If the Council votes in favor of a PDP, it would be many months, if at all, before a policy binding on Verisign was created.

ICANN demands the right to terminate .jobs

ICANN has asked the International Chamber of Commerce to rule that it has the right to terminate Employ Media’s .jobs contract.

It’s filed its response to Employ Media’s demand for arbitration over the disputed Universe.jobs service, which saw the registry vastly expand the .jobs space.

Employ Media “transcended the very intent behind creation of the TLD” with Universe.jobs, which allocated tens of thousands of .jobs domains to the DirectEmployers Association, ICANN said.

The organization wants the ICC to rule that it “may, but is not required to, terminate the Registry Agreement with Employ Media”, as it has already threatened.

Employ Media took ICANN to arbitration in May, after ICANN notified it that it was in breach of its registry agreement and they were not able to settle their differences in private talks.

The registry wants a declaration that it is not in breach.

But according to ICANN, Employ Media is still and has always been restricted to selling domains just to human resources professionals to promote jobs “within their own organizations”.

That’s despite ICANN’s approval of a contract amendment last year that allowed the registry to sell non-companyname .jobs domains.

This liberalization, ICANN says, did not allow the company to launch Universe.jobs, which monetizes at least 40,000 geographical and vocational .jobs through a massive third-party jobs board.

ICANN is now trying to frame the arbitration proceeding around a single question – was its breach notice “appropriate” or not?

The whole debacle is based around two interpretations of the .jobs Charter, which spells out who can register .jobs domains. This is what it says:

The following persons may request registration of a second-level domain within the .JOBS TLD:

– members of SHRM [the Society For Human Resources Management]; or

– persons 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; (iii) are supportive of the SHRM Code of Ethical and Professional Standards in Human Resource Management, as amended from time to time, a copy of which is attached hereto.

Employ Media’s interpretation is fairly literal and liberal – any signed-up SHRM member can register a .jobs domain and somebody at DirectEmployers is a member and therefore eligible.

Becoming a SHRM member is pretty straightforward and cheap. It’s not much of a barrier to entry.

ICANN argues that this interpretation is bogus:

Employ Media has espoused policies that allow a .JOBS domain name (or thousands of them) to be used for virtually any purpose as long as a human resource manager is propped up to “request” the domain. In doing so, Employ Media has failed to enforce meaningful restrictions on .JOBS registrations, as required by the Registry Agreement.

It further argues that Employ Media should have allocated premium .jobs domains through an “open, fair and transparent” process, rather than the “self-serving… backroom deal” with DirectEmployers.

Evidence now filed by ICANN shows that the two organizations have been arguing about this since at least November 2009, when Employ Media launched a Universe.jobs “beta”.

ICANN also now says that it has no problem with Universe.jobs, provided that Employ Media and SHRM amend their Charter policies to make the service retroactively compliant.

The more this dispute progresses and the more convoluted and expensive it becomes, the more it leaves me scratching my head.

You can download the latest arbitration documents from ICANN.

Anti-.jobs coalition keeps up pressure on ICANN

The .JOBS Charter Compliance Coalition, which wants ICANN to rein in .jobs registry Employ Media, has sent a couple of stern letters to ICANN recently.

Neither are especially exciting, but as ICANN has yet to publish them on its correspondence page I thought I’d make them available here.

The first (pdf), sent July 5, demands to know why ICANN has not yet provided an update to its forthcoming arbitration with Employ Media, which was due a few weeks ago.

ICANN and the registry are set to face off at the International Chamber of Commerce over the disputed Universe.jobs service, which ICANN believes was launched in breach of the .jobs Charter.

My understanding is that the arbitration is going ahead, but that ICANN has been granted an extension to the deadline to file its reply.

The second letter (pdf) notes that .jobs’ IANA listing was recently updated with language more friendly to Employ Media’s position that not only human resources managers qualify for .jobs domains.

It asks why this change was made, invoking the Documentary Information Disclosure Policy.

The Coalition is made up of independent jobs site operators unhappy that Employ Media appears to be using its position as the .jobs registry to compete with them.

ICANN tries to dodge .jobs legal fees

“Please don’t sue us!”

That’s the message some are taking away from the latest round of published correspondence between lawyers representing ICANN and .jobs registry Employ Media.

Employ Media last week said it will take ICANN to the International Chamber of Commerce, after they failed to resolve their dispute over the company’s controversial Universe.jobs venture.

Now ICANN has asked the registry’s executives to return to the negotiating table, apparently to reduce the risk of having to spend millions of dollars on lawyering.

In a letter (pdf) to Employ Media’s attorneys, ICANN outside counsel Eric Enson of Jones Day said that ICANN wishes to avoid “costly legal fees associated with arbitration or litigation”:

I again request a meeting among the business persons involved in this matter to discuss potential resolutions before spending more of ICANN’s funding on unnecessary litigation.

The latest round of published correspondence, like the last one, and the one before that, seems to contain a fair bit of legal posturing, with both sides accusing the other of conducting negotiations in “bad faith” for various reasons.

Filing the arbitration notice with the ICC might turn out to be a smart move by Employ Media, knowing how risk-averse and cash-conscious ICANN is.

ICANN is still smarting from the last time it headed to arbitration, for its Independent Review Panel over ICM Registry’s .xxx top-level domain.

ICANN lost that case in February 2010, and had to cover the panel’s almost $500,000 in costs, as well as its own legal fees. The overall price tag is believed to have comfortably made it into seven figures.

But that may well turn out to be small beer compared to the price of losing arbitration against the .jobs registry.

Unlike the IRP, in which both parties pay their own lawyers no matter who wins, Employ Media’s contract states that the losing party in arbitration must pay the legal fees of the winner.

To go up against .jobs at the ICC and lose could hit ICANN’s coffers harder than the .xxx dispute, in other words. That’s not to say it would lose, but with matters as complex as this there is that risk.

It’s worth noting that Employ Media’s lead attorney has form when it comes to reaching into ICANN’s pockets – Crowell & Moring’s Arif Ali also represented ICM Registry in the .xxx IRP case.

.jobs takes ICANN to arbitration

Employ Media, manager of the .jobs top-level domain, has become the first registry operator to take ICANN to arbitration to fight off a shut-down threat.

The company in the last hour said it has filed a Request for Arbitration with the International Chamber of Commerce in Paris, after informal efforts to reach agreement with ICANN broke down.

Employ Media CEO Tom Embrescia said in a statement:

This filing was necessary to ward off ICANN’s unwarranted and unprecedented threat of contract termination. That action created immediate uncertainty about the .JOBS TLD on the Internet and caused significant duress on our business.

ICANN had threatened to terminate the .jobs registry agreement – which I believe is pretty much the only option available to it in the case of a perceived breach – in February.

The filing means .jobs can operate as normal until the situation is resolved.

The dispute is essentially about Universe.jobs, a jobs listing service operated by the DirectEmployers Association using tens of thousands of generic .jobs domain names granted to it by Employ Media.

The .JOBS Charter Compliance Coalition, made up of independent jobs boards, complained to ICANN that Universe.jobs went against the spirit and letter of the original .jobs Charter.

Employ Media says that Universe.jobs was essentially authorized when ICANN approved its Phase Allocation process for handing out generic domains last year.

Employ Media is represented by lawyers from Crowell & Moring, some of the same individuals responsible for ICM Registry’s defeat of ICANN at its Independent Review Panel last year.

The request for arbitration can be read here in PDF format.

War of words over .jobs “breach” claims

Employ Media and ICANN have come to blows again over ICANN’s threat to shut down the .jobs registry for allegedly selling domain names in breach of its Charter.

Both parties are currently talking through their outside counsel, and the possibility of litigation has raised its head in public for the first time.

In the latest set of correspondence published by ICANN, Employ Media sharply (and ironically) criticized ICANN’s decision to publish an earlier set of correspondence on its web site.

The earlier email exchange, which I blogged about here, revealed that ICANN had asked the company to amend its Charter.

Two days later, Employ Media’s lawyers wrote to ICANN’s lawyers to express disappointment with the decision to post these emails, questioning ICANN’s commitment to good faith negotiations.

In light of this apparent bad faith action on ICANN’s part, Employ Media is questioning whether any hope remains for a full and fair exchange of ideas regarding a resolution of its dispute with ICANN.

[ICANN has] substantially hindered Employ Media’s ability to engage in productive and honest negotiations: all future communications will necessarily be more guarded and less open, given the expectation that they will be published to a larger audience

ICANN and Employ Media are currently in a “cooperative engagement” process – a less formal way to resolve their dispute than heading to an arbitration forum or court.

ICANN claims the registry is breaking its Charter commitments to the human resources industry by allocating tens of thousands of .jobs domain names to the Universe.jobs project, which is run by a partner, the DirectEmployers Association.

Independent jobs boards, represented by the the .JOBS Charter Compliance Coalition, believe that Universe.jobs is unfair and not compliant with Employ Media’s own policies.

Employ Media’s latest letter (pdf), which it demanded ICANN publish, drops hints about some of the behind-the-scenes talks (with my emphasis):

Had we known that any part of our communication was to be published, we would have certainly memorialized, in writing, your statements to us that ICANN very much wants to avoid an arbitration over this dispute, and that ICANN was therefore willing to agree to a process for approving a Charter amendment in order to do so. We would also have memorialized our positions, including our position that a Charter amendment is neither necessary nor desirable, but that we were considering acceding to ICANN’s request solely in the hopes of avoiding arbitration

ICANN’s lawyers’ response (pdf), sent April 26, says ICANN was merely fulfilling its transparency obligations by informing the community about the extension of the talks deadline.

They also said that the Employ Media should stop pretending to be surprised that ICANN issued the breach notice and is now asking for a Charter amendment.

ICANN further accused the registry’s lawyers of legal “posturing” which was “seemingly geared solely towards use in future litigation”.

Employ Media was due to deliver a proposed amendment to its Charter by yesterday. ICANN has said it will not take any further actions based on its breach notice until May 6.

Registry avoids .jobs shut-down

Kevin Murphy, April 20, 2011, Domain Registries

Employ Media has come to a deal with ICANN to avoid having its .jobs registry contract revoked, at least for the next few weeks.

Following discussions with ICANN’s lawyers, the company plans to amend its Charter, and has agreed to stop allocating non-company-name .jobs domain names until May 6.

ICANN threatened to terminate the .jobs registry deal in February, after Employ Media started allocating thousands of premium vocational and geographic domains to a partner, the DirectEmployers Association, to act as entry points for Universe.jobs.

In a breach notice (pdf), ICANN said that this use of .jobs domains “is inconsistent with the purpose stated in the .JOBS Charter and represented to the ICANN community”.

The .JOBS Charter ostensibly restricts registrations to human resources professionals, but in practice there’s a great big loophole that allows anybody to cheaply qualify for a domain.

In February, ICANN general counsel John Jeffrey told Employ Media:

By not establishing any meaningful restrictions on who may register second level registrations in the .JOBS TLD, Employ Media put in operation a TLD where anyone can register names, thus defeating the purpose for which the sponsored TLD came into existence.

In its response, the registry noted that it had followed ICANN’s proper procedures for introducing new “registry services”, such as the Phase Allocation Plan that allowed it to seed Universe.jobs.

It accused ICANN of bending to the wishes of the .JOBS Charter Compliance Coalition, a group of independent jobs sites operators that had objected to Universe.jobs.

Employ Media’s chief executive Brian Johnson wrote:

This is a sad day for both the Internet community and the international human resource management community. ICANN should be promoting competition and working cooperatively with its contractual parties, but instead is choosing to ignore the plain meaning of its contract with Employ Media in order to appease some apparently well‐financed and well‐connected provocateurs.

Since that letter (pdf) was sent, ICANN and the registry have been engaged in private discussions aimed at resolving the conflict, as allowed by the registry agreement.

In the latest set of correspondence, exchanged over the last week, it has emerged that ICANN has agreed to give Employ Media time to remedy the situation by amending its Charter.

The letters do not reveal whether the amendments will allow Employ Media to continue to offer Universe.jobs or not. I suspect they will.

The amendments may require the company to consult with its nominal sponsor, the Society for Human Resource Management.

ICANN wants a proposed Charter amendment on its desk by May 2. It has agreed to take no further action related to the breach of contract allegations until May 6.

Registry objects to .jobs shutdown threat

Employ Media will appeal ICANN’s threatened termination of its .jobs registry contract.

The company released a statement (pdf) late yesterday, following ICANN’s unprecedented threat, in which it said ICANN’s claims are “utterly without merit”.

“We view the substance of this notice to be a surprising reversal of position and contradictory to prior decisions issued by its Board of Directors,” the company said.

ICANN yesterday gave Employ Media until the end of the month to cancel its agreement to provide 40,000 .jobs domains to the DirectEmployers Association for its Universe.jobs employment board.

The organization said the allocation of the domains for non-human-resources purposes went against the letter, spirit and intent of the registry’s contract and Charter.

It essentially boils down to a claim that Employ Media hacked its contract to allow it to start making money on names beyond the limited scope of its original “sponsored” community TLD.

The .jobs TLD was originally pitched as a space for corporate HR pages, not independent jobs sites. With Universe.jobs, half of the namespace is an independent jobs site. Employ Media is believed to have a revenue-sharing arrangement with DirectEmployers.

The ICANN breach notice was welcomed by the .JOBS Charter Compliance Coalition, the ad hoc trade group formed by major commercial jobs sites to fight Universe.jobs.

Peter Weddle, executive director of the International Association of Employment Web Sites, said in a press release:

the Dot Jobs Universe was not an innovation but rather an unprecedented attempt by a registry operator to misappropriate an entire TLD for itself and its alliance partner in blatant disregard of ICANN’s rules.

Employ Media disagrees, of course, saying that Universe.jobs came about as a result of its “Phased Allocation” liberalization plan, which was approved by ICANN’s Registry Services Evaluation Process and then survived a Reconsideration Request filed by the Coalition.

The company said: “it is imperative for registry operators to have predictability in the performance of duties and that ICANN has a responsibility to honor its commitments with contracted parties.”

Its registry contract contains a dispute resolution procedure that first calls for bilateral talks and, failing agreement, arbitration via the International Chamber of Commerce.