Cops seize 1,800 domains in 2010

Nominet helped the UK’s Metropolitan Police seize 1,800 .uk domains during 2010, many of them just prior to Christmas, according to the Met.
The domains all allegedly hosted “bogus” sites that were “either fraudulent or advertising counterfeit goods which failed to materialise”, the Met said.
While a statement from the Police Central e-Crime Unit said it had worked with “registrars” to shut down the domains, it also credited Nominet a role:

The sites are run by organised criminal networks and thought to generate millions of pounds which can then be used to fund further illicit activity.
The preventative action was carried out in partnership with Nominet – the public body for UK domain name registrations – and involved a concentrated effort around the festive period; a time when we traditionally see an upsurge in this type of crime as fraudsters take advantage of the increased number of online consumers.

It’s not the first time the UK police, with Nominet’s aid, have swooped to shut down such domains.
In December 2009, a similar announcement from the PCeU, which said that 1,219 domains had been turned off, was greeted less than warmly by some.
Web hosting companies reportedly often ask for a court order before shutting down sites. When VeriSign helped US law enforcement seize 80+ domains in November, it did so subject to a court order.
It seems domains in the UK may not be subject to such judicial oversight.
Nominet chief executive Lesley Cowley, discussing the December 2009 seizures in a recent interview, would only tell me that the police had “instructed” Nominet to shut down the domains.
According to The Register’s coverage, Nominet used the lack of authentic Whois data as legal cover for those seizures.
But there is a new Nominet policy development process under way, initiated by the UK Serious and Organised Crime Agency, which seeks to amend the standard .uk registrant agreement to give a stronger contractual basis for seizing domains when they appear to break UK law.

1 Comment Tagged: .uk, eceu, met, metropolitan police, nominet, socaPolice Central e-Crime Unit

Incumbents get the nod for new TLD apps

Domain name registries such as Neustar, VeriSign and Afilias will be able to become registrars under ICANN’s new top-level domains program, ICANN has confirmed.
In November, ICANN’s board voted to allow new TLD registries to also own registrars, so they will be able to sell domains in their TLD direct to registrants, changing a decade-long stance.
Late last week, in reply (pdf) to a request for clarification from Neustar policy veep Jeff Neuman, new gTLD program architect Kurt Pritz wrote:

if and when ICANN launches the new gTLD program, Neustar will be entitled to serve as both a registry and registrar for new gTLDs subject to any conditions that may be necessary and appropriate to address the particular circumstances of the existing .BIZ registry agreement, and subject to any limitations and restrictions set forth in the final Applicant Guidebook.

That doesn’t appear to say anything unexpected. ICANN had already made it pretty clear that the new vertical integration rules would be extended to incumbent gTLD registries in due course.
(However, you may like to note Pritz’s use of the words “if and when”, if you think that’s important.)
Neustar’s registry agreement currently forbids it not only from acting as a .biz registrar, but also from acquiring control of greater than 15% of any ICANN-accredited registrar (whether or not its sells .biz domains).
That part of the contract will presumably need to be changed before Neustar applies for official registrar accreditation or attempts to acquire a large stake in an existing registrar.
VeriSign and Afilias, the other two big incumbent gTLD registries, have similar clauses in their contracts.

Comment Tagged: afilias, applicant guidebook, ICANN, neustar, new TLDs, verisign, vertical integration

ICANN sets date for GAC showdown

ICANN and its Governmental Advisory Committee will meet for two days of talks on the new top-level domains program in Geneva from February 28, according to GNSO chair Stephane Van Gelder.
As well as the Applicant Guidebook (AGB) for new TLDs, the meeting is also expected to address the GAC’s outstanding concerns with the .xxx TLD application.
While I’d heard Geneva touted as a possible location, this is the first time I’ve heard a firm date put to it. As well as Van Gelder, other sources have heard the same date.
Talks ending March 1 would give ICANN less than two weeks before its public meeting in San Francisco kicks off to get the AGB into GAC-compatible shape before the board votes to approve it.
Is that a realistic timeframe? I guess that will depend on how the GAC meeting goes, the depths of the concessions ICANN decides to make, how receptive the GAC is to compromise, and whether it is felt that more public comment is needed.
Also, as I speculated last week, ICANN may have to officially invoke the part of its bylaws that deals with GAC conflicts, which it does not yet appear to have done, if it wants to approve the Guidebook at the end of the San Francisco meeting in March.
If the program is approved in March, that would likely lead to applications opening in August.
There’s likely to be one ICANN board meeting between now and Geneva – its first meeting of the year is usually held in late January or early February – so there’s still time for ICANN to make changes to AGB based on public comment, and to get its process ducks in a row.
There’s also plenty of time for the GAC to provide its official wish-list or “scorecard” of AGB concerns, which I believe it has not yet done.
Van Gelder also wonders on his blog whether the Geneva meeting will take place in the open or behind closed doors.
ICANN’s director of media affairs, Brad White, put this question to ICANN chair Peter Dengate Thrush during a post-Cartagena interview. This was his answer:

We haven’t actually resolved the rules of engagement with the GAC on this particular meeting but the standard position for all organizations within ICANN is that they are open… On the other hand if at any point think we the negotiation could be assisted by a period of discussing things in private I guess we could consider that.

That looks like a “maybe” to me.

Comment Tagged: applicant guidebook, gac, governmental advisory committee, ICANN, new TLDs, xxx

VeriSign takes over .gov

VeriSign has taken over registry functions at .gov, the top-level domain for the US government.
IANA records show that VeriSign Global Registry Services was named technical contact for .gov possibly as recently as this Monday.
The TLD is still administratively delegated to the US General Services Administration. Google’s cache of the IANA site shows the GSA was the technical contact for .gov as recently as October 29.
VeriSign certainly kept this contract win quiet.
At least, the first I heard about it was tonight, in an email VeriSign sent to the dns-ops mailing list, asking DNS administrators to reconfigure their DNSSEC set-up to reflect the change.

A KSK [Key Signing Key] roll for the .gov zone will occur at the end of January, 2011. This key change is necessitated by a registry operator transition: VeriSign has been selected by the U.S. General Services Administration (GSA) to operate the domain name registry for .gov.

The email expresses the urgency of making the changes, which are apparently needed in part because .gov was signed with DNSSEC before the root zone was signed, and some resolvers may be configured to use .gov as a “trust anchor” instead of the root.
The .gov TLD is reserved for the exclusive use of US federal and state government departments and agencies.
It’s certainly a prestige contract for VeriSign.
This appears to be the GSA page awarding the contract to VeriSign, in September, following an RFP. It’s valued at $3,325,000.

1 Comment Tagged: .gov, DNSSEC, general service administration, verisign

Go Daddy offers Whois privacy for .co domains

.CO Internet has started allowing registrars to offer Whois privacy services for .co domains, according to Go Daddy.
In a blog post, Go Daddy’s “RachelH”, wrote:

When the Internet Corporation for Assigned Names and Numbers (ICANN) and .CO Internet S.A.S. drafted the .co policy earlier this year, they decided to hold off on private registration to prevent wrongful use of the new ccTLD — especially during the landrush. Now that .co has carved its place among popular TLDs, you can add private registration to your .co domain names.

Unless I’m mistaken, ICANN had no involvement in the creation of .co’s policies, but I don’t think that’s relevant to the news that .co domains can now be made private.
During its first several months, .CO Internet has been quite careful about appearing respectable, which is why its domains are relatively expensive, why its trademark protections were fairly stringent at launch, and why it has created new domain takedown policies.
It may be a sign that the company feels confident that its brand is fairly well-established now that it has decided to allow Whois privacy, which is quite often associated with cybersquatting (at least in some parts of the domain name community).
It could of course also be a sign that it wants to give its registrars some love – by my estimates a private registration would likely double their gross margin on a .co registration.

1 Comment Tagged: .co, .co internet, cctlds, go daddy, privacy, whois

ICANN to tackle Trojan TLDs

When failing community-based top-level domain registries attempt to change their business models, ICANN may in future have a new way of dealing with them.
That seems to be a possible result of Employ Media’s controversial .jobs liberalization plans and the subsequent Reconsideration Request, which I blogged about last week.
The .jobs reconsideration revealed that not only are Reconsideration Requests a rubbish way to appeal ICANN’s decisions, but also that the Registry Services Evaluation Process is often a rubbish way to handle major contract changes.
The RSEP was introduced back in 2005 in belated response to a couple of controversial “services” that VeriSign, testing boundaries, had planned to unilaterally introduce in the .com registry, notably Site Finder and the Waiting List Service.
But since then the process has been used as a general-purpose tool for requesting changes to registry contracts, even when it’s debatable whether the changes fit the definition of “registry services”.
For example, when .jobs launched five years ago, it was put into Employ Media’s contract that the TLD was designed for companies to register their brands and list their jobs, and that’s all.
But that model didn’t work. It’s one of the least successful TLDs out there.
So the registry decided it could make more money with general purpose jobs boards, using generic .jobs domains. But it did not necessarily want to let existing independent jobs sites take part.
For want of a better term, I’ll call this an example of a “Trojan” TLD – a registry that gets its attractive TLD string approved by ICANN after making a certain set of promises, then later decides to move the goal posts to broaden its market, potentially disenfranchising others.
I’ve no reason to believe it was a premeditated strategy in Employ Media’s case, but precedent has now been set for future TLD applicants to use “community” as a foot in the door for broader aspirations.
To take a stupid, extreme, unrealistic example, imagine that ICM Registry’s .xxx flops badly. Should the company be allowed to start selling all the good .xxx domains to churches and other anti-porn campaigners? That would be a pretty big departure from its promises.
There were similar concerns, although not nearly as loudly expressed, with regards to Telnic’s recent contract changes, which will allow it to start registering phone number domain names in .tel, despite years of promises that it would not.
Go Daddy’s policy chief Tim Ruiz objected to the proposal on the grounds that it would be “unfair to other [.tel] applicants and potential applicants to allow an sTLD to change its purpose after the fact.”
The ICANN Board Governance Committee, which handles Reconsideration Requests, acknowledged these problems in its decision on .jobs in Cartagena (pdf), concluding that it:

thinks that the Board should address the need for a process to evaluate amendments that may have the effect of changing, or seeking to change, an sTLD Charter or Stated Purpose of a sponsored, restricted or community-based TLD.

The BGC seems to be saying that the RSEP is not up to the task of dealing with community-based TLDs that later decide their business plans are not the money-spinners they had hoped and want to loosen up their agreed community restrictions.
The committee went on to say that:

Because such a process may impact gTLDs greatly and is a policy issue, the GNSO is the natural starting point for evaluating such a process. We therefore further recommend that the Board direct the CEO to create a briefing paper for the GNSO to consider on this matter, and for the GNSO to determine whether a policy development process should be commenced.

So the GNSO will soon have to decide whether new policies are needed to deal with broad contract changes at failing community TLDs.
Any new policies would, I believe, be binding on community TLDs approved under the new gTLD program as well as older sTLDs, so it will be an interesting policy track to follow.

1 Comment Tagged: .jobs, board governance committee, community tlds, employ media, ICANN, new TLDs, reconsideration, registry services evaluation process, rsep, sponsored tlds

OpenRegistry latest player in new TLD market

OpenRegistry has become the domain name industry’s newest top-level domain registry operator.
The new company, which went by the name Sensirius while in stealth mode, announced itself officially at the ICANN meeting in Cartagena two weeks ago.
Jean-Christophe Vignes is giving up his operational role at EuroDNS to be CEO of the new company, which hopes to bring more modular, custom-tailored options to organizations that want to launch new TLDs.
For “open”, read “flexible” – OpenRegistry plans to differentiate itself by offering clients “a la carte” options, rather than the one-size-fits-all services it believes some competitors offer.
“We’ve noticed that no two clients are the same,” Vignes said. “Some of them are already pretty well taken care of when it comes to drafting applications and so on, and just need the registry solution, but others are happy to have the full suite of our services.”
The idea is that a city TLD or niche community TLD will not necessarily have the same needs as a full-blown mass-market gTLD, Vignes said.
OpenRegistry plans to make three packages available at first, according to its web site – all-inclusive, managed registry, and software-only. Prices appear to start at around 100,000 euros.
The software itself is based on the registry expertise used in the design of Belgium’s .be and EurID’s .eu, although it appears to be a fresh creation.
Vignes said that it will be able to natively handle start-up functions such as premium domain auctions and interfacing with the IP Clearinghouse.
The company does not intend to apply for its own TLDs, Vignes said, allowing it to focus on its clients.
But it does plan on being somewhat selective on which TLDs with which it works, with “feasibility studies” one of the services on offer.
Like the incumbent registry triumvirate of VeriSign, Afilias and Neustar, OpenRegistry hopes that the ICANN-accredited registrar community will be a good source of clients.
ICANN recently said it plans to lift restrictions on registrars applying for and running registries.

4 Comments Tagged: cartagena, ICANN, jean-christophe vignes, new TLDs, openregistry, sensirius

Whistleblower alleged shenanigans at DirectNIC

A former employee of a company allegedly affiliated with domain name registrar DirectNIC claimed the company operated a fraudulent domain arbitrage scheme using Yahoo ads and Parked.com.
Mark Deshong filed a whistleblower lawsuit in August. It was settled in October, but its claims are quite interesting, and don’t appear to have been reported on elsewhere.
Until April this year, Deshong worked for a company called Keypath LLC, a domain registration and monetization company based in Tampa, Florida.
According to his lawsuit (pdf), Keypath is owned by the same bunch of people (notably Sigmund Solares and Michael Gardner) who run DirectNIC and Parked.com, as well as entities including Intercosmos Media Group and The Producers Inc.
Deshong said he was fired after blowing the whistle on a “fraudulent” scheme to bilk money out of Yahoo Search Marketing using the old practice of domain arbitrage.
The suit claimed Keypath bought ads on YSM to bring traffic to sites such as cameras.com that, in turn, displayed nothing but contextual ads generated automatically by YSM.
The company would pay Yahoo small amounts for the traffic it received, but would be paid larger amounts for the traffic it sent elsewhere.
That’s domain arbitrage in a nutshell. It was commonplace among domainers back in 2007 and earlier, and Keypath was far from the only company engaged in the practice.
Yahoo tried to put a stop to arbitrage on its ad network in February 2008, as Domain Name Wire reported at the time, but the lawsuit alleged that Keypath carried on regardless, using bogus identities.
This is when the “fraudulent” behavior is alleged to have commenced.
The suit claimed Keypath “created fictitious, unregistered DBA [Doing Business As] company names” in order to obtain up to 1,000 credit cards from Regions Bank.
The complaint, in an eyebrow-raising paragraph, goes on to list almost 100 of these alleged DBA companies’ names.
Each one of these companies would get a Gmail or Hotmail email address and a Skype phone number for the city where the “fictitious” company was supposedly based, the complaint alleged.
A proxy server would be obtained in each of these cities, which Keypath would use to access YSM and order ads pointing to parked pages, under the guise of one of the DBAs, the suit alleged.
The scheme covered about 50,000 domains and made about $375,000 during January 2010, according to the complaint.
The lawsuit was filed under Florida’s whistleblower act, so while it alleged multiple illegal acts (such as bank fraud and wire fraud) on Keypath’s part, it only attempted to prove wrongful termination.
Deshong basically claimed that he was canned after telling his superiors he could no longer carry out duties he believed to be illegal – he didn’t want to go to jail.
In its response (pdf) to the complaint, Keypath denied essentially all of Deshong’s claims.
It also denied that the company has ties to DirectNIC, Michael Gardner, Sigmund Solares, Intercosmos, Parked.com or The Producers.
(Probably a disingenuous claim. Florida company records show they’re all currently or recently linked to businesses located at 5505 West Gray Street in Tampa, Parked.com’s main US office. Keypath’s web site shows the same address).

Keypath also accused Deshong of a shakedown, attempting to “extort an unreasonable severance package”, and said that he had “improperly retained” a company laptop after he was fired.
The suit was settled out of court (pdf) on October 25th for an undisclosed sum.
The lawsuit is only tangentially related to the cybersquatting lawsuit Verizon filed against DirectNIC earlier this year. That case appears to be currently tied up in a pre-trial discovery/jurisdictional nightmare.

16 Comments Tagged: directnic, intercosmos, keypath, mark deshong, michael gardner, parked.com, sigmund solares, the producers

Did .jobs win or lose in Cartagena?

Employ Media, the .jobs registry, had a victory in Cartagena last week, when the ICANN board voted not to overturn its August decision to allow .jobs to relax its registration policies.
The company will now be able to continue with its RFP process, allocate premium generic .jobs domains to its partners, auction them, and generally liberalize the namespace.
But the registry may not have got everything it wanted.
For at least a year, Employ Media, along with the DirectEmployers Association, has been pushing the idea of creating a massive free jobs board called universe.jobs.
The site would be fed traffic from thousands of premium geographic domains such as newyork.jobs, texas.jobs and canada.jobs, as well as vocational names such as nursing.jobs and sales.jobs.
Because Employ Media was previously only allowed to sell domains that corresponded to the names of companies, such as ibm.jobs and walmart.jobs, it asked ICANN to change its contract to allow these new classes of generic names to be registered.
The registry submitted a Registry Services Evaluation Process request, which was approved by the ICANN board in early August. The contract was amended shortly thereafter.
A few weeks later, a group of jobs sites including Monster.com, calling itself the .JOBS Charter Compliance Coalition, filed a Reconsideration Request, asking ICANN to reverse its decision.
The Coalition was concerned that the contract changes would enable universe.jobs, creating a potentially huge competitor with an unfair SEO advantage, while continuing to prohibit independent jobs sites from registering .jobs domains.
While the .jobs contract had been amended, the .Jobs Charter, which restricts those who can register .jobs domains to members of the human resources community, was not.
This potentially presented a problem for universe.jobs, as DirectEmployers may not have qualified to be a registrant under the charter.
But Employ Media’s RSEP proposal talked about creating a “self-managed class” of domains – the domains would belong to the registry but would be shared with third parties such as DirectEmployers.
That would have created an interesting precedent – registries would be able to keep hold of premium generic domain names and allow them to be “used” by only partner companies that agree to enter into revenue-sharing agreements.
But that “implementation method was withdrawn” by Employ Media after the ICANN Board Governance Committee asked about it as part of its Reconsideration Request investigation.
The BGC, while rejecting the Coalition’s request (pdf), also asked ICANN’s compliance department to keep a close eye on Employ Media, to make sure it does not overstep the bounds of its charter:

the BGC recommends that the Board direct the CEO, and General Counsel and Secretary, to ensure that ICANN’s Contractual Compliance Department closely monitor Employ Media’s compliance with its Charter

Even though its Reconsideration Request was denied, the .JOBS Charter Compliance Coalition counted both of these developments as a big win for its campaign, saying in a press release:

Given the Board’s commitment to aggressively monitor Employ Media’s implementation of the Phased Allocation Program, the Coalition is highly confident that ICANN will not permit Employ Media to register domain names to “independent job site operators” for purposes of operating job sites.

So does this mean that universe.jobs is dead?
Apparently not. Talk in the halls at the ICANN Cartagena meeting last week leads me to believe that the registry has figured out a way to launch the service anyway.
And DirectEmployers this Monday published a white paper (pdf), dated January 2011, which says universe.jobs will launch early next year.
DirectEmployers declined to immediately comment on its plans when I inquired this week, and the white paper sheds little light on the technicalities of the plan.
Judging from a promotion currently being run by EnCirca, a .jobs registrar, it seems that companies will only be able to list their jobs on universe.jobs if they own their own companyname.jobs domain.
EnCirca’s offer, which alludes to the .jobs sponsor, the Society for Human Resources Management, a “SHRM special“, says:

NEWS ALERT: December 13, 2010: ICANN has RE-CONFIRMED the .Jobs registry’s plan to allocate generic occupational and geographic-related .jobs domain names. Register your companyname.jobs to be part of this new initiative.

It will be interesting to see how domain allocations are ultimately handled.
While Employ Media’s request for proposals is ostensibly open, it looks a little bit like a smokescreen for its plan to hand big chunks of the .jobs namespace to the universe.jobs project.
But who will be the registrant of these domains? And will the allocations violate the .jobs charter? Will the registry carry on with its plan to create new “self-managed” class of domain names?
I think we’re going to have to wait for the new year to find out.

3 Comments Tagged: .jobs, .jobs charter compliance coalition, directemployers association, employ media, encirca, ICANN, reconsideration request, rsep

Possible new TLDs timeline revealed

ICANN’s decision to delay the approval of its new top-level domains Applicant Guidebook last week in Cartagena left one big question hanging:
When will the program open for applications?
ICANN had pencilled in May 30 for the launch, but the new delay appeared to make that impossible. In the absence of an announcement from ICANN, nobody really knows what the current timetable is.
A few possible answers have now emerged with the publication this week of ICANN staff briefing documents (pdf) used by the board to make their original decision to target May 2011.
An October 28 document entitled “New gTLD Launch Scenarios”, penned by ICANN’s Kurt Pritz and Carole Cornell, explores the board’s options for approving a launch timeline.
It notes that applications cannot be solicited until ICANN has finished its mandatory four-month outreach/marketing campaign, which in turn can’t kick off until the AGB has been approved.
I’ll let the rest speak for itself:

If the Board were to approve the Guidebook after the January/February meeting, the announcement and communications campaign launch would be made shortly thereafter. The first applications could be received as early as (but not earlier than) 1 July 2011.
If the Board elects that a full comment analysis and sixth version of the Guidebook be written, with approval at the Silicon Valley meeting, the approval would be followed by an April announcement and communications campaign launch. First applications could be received as early as (but no earlier than) August 2011.

And here’s a lovely graphic illustrating the options (click to enlarge):

Given that we now know that the ICANN board intends to meet with the Governmental Advisory Committee to address its outstanding issues in February, the final scenario – with a San Francisco approval and August launch – now seems more likely.
Most of the rest of the briefing document is heavily redacted.

6 Comments Tagged: applicant guidebook, cartagena, ICANN, new TLDs, san francisco