Verisign defends .com price increases
Verisign has assured investors that it is confident its .com registry agreement is not in jeopardy, after seeing its stock plummet due to uncertainties over the deal.
In a statement yesterday, the company also defended the planned continuation of its price-raising powers.
It emerged last week that the US Department of Commerce is looking into the pricing arrangements of the new .com deal, which ICANN approved back in June.
Commerce has the right — in consultation with the Department of Justice and others — to approve or reject the contract based on its security/stability and pricing terms.
Whatever happens, it’s virtually unthinkable that Verisign will lose the contract. The company said:
While the review process with the Commerce Department may extend beyond Nov. 30, 2012, it could also be concluded by Nov. 30, 2012. In either case, Verisign expects to continue to run the .com registry.
It also said that its ability to increase prices by 7% in four of the six years of the contract is in fact in the public interest, saying in a lengthy statement:
The .com registry has an unequaled record of achievement, with full availability of DNS resolution in .com for more than 15 consecutive years. The economic activity supported by the .com registry is significant by any measure in an environment where the consequences of a failure of even a very short duration or degradation of the Domain Name System (DNS) resolution service, due to either a cyber attack or failure of hardware, software, or personnel, would have significant economic and non-economic impacts to the global economy.
The level of security and stability offered by Verisign is only possible with investments in overcapacity and redundancy, network security, intellectual property (IP) and in human capital: The engineers and employees at Verisign who operate the .com registry and ensure its security and stability. The pricing terms of the .com Registry Agreement enable Verisign to make these investments, develop the necessary IP, know-how and purpose-built systems, respond to new threats to stability as they emerge, and recruit and retain the specialized talent necessary to maintain our network, including dozens of globally distributed constellation sites and data centers in the U.S. and elsewhere.
In essence, Verisign is saying that the security and stability record — which Commerce evidently has already reviewed to its satisfaction — are inextricably linked to its ability to raise prices.
The company’s share price fell 18% in the aftermath of last week’s news, but recovered slightly yesterday — gaining about 11% — after the statement was released.
Right Of The Dot to offer new gTLD contention auctions with Escrow.com
New gTLD consultancy Right Of The Dot has partnered with Escrow.com on a new auction offering designed for new gTLD applicants in contention sets.
The deal, which ROTD said is exclusive, will enable the company to offer trustworthy escrow of funds as part of its auction service.
ROTD is planning three standard types of auction design — sealed-bid, ascending bid and live oral — for when mediation between gTLD applicants fails or is not wanted.
Its fees start at 4% of the winning bid, with the remainder being distributed to losing bidders.
Private auctions are expected in many cases to be the contention resolution method of choice for new gTLD applicants, because the losing bidders get paid when they drop out.
The alternative method laid out in the ICANN Applicant Guidebook would see funds flow instead to ICANN.
ROTD is the consultancy formed last year by well-known domain investors Monte Cahn (formerly of Moniker) and Michael Berkens (author of TheDomains.com).
ICM to intro sponsored search results with $75 credit for registrants
Tearing several chapters out of the Google playbook, ICM Registry is to introduce a sponsored search placement service for .xxx registrants, along with a substantial introductory credit.
The company will give each registrant a $75-per-domain credit against its forthcoming search platform, which in many cases will completely offset the cost of their .xxx domain.
As has been pointed out elsewhere, it’s the AdWords model for porn, following on from the recent launch of search.xxx, which ICM says has already had more than 12 million page views.
The ad system is expected to roll out in “early 2013”, but ICM has launched the credits incentive now in order to get early registrants to renew their domain names.
The vast majority of .xxx’s roughly 140,000 registrations occurred during its first two months of general availability and will be coming up for renewal in December and January.
That said, ICM had said even prior to this announcement that its early renewals were looking promising.
The ad credit will apply to all .xxx domains renewed or registered before January 31, 2013, ICM said in a press release.
The company has long talked about its plans for generating advertising and micropayment-based revenue. Over the long term, selling domains may prove to be a small part of its business.
ICANN looking for new gTLD testing provider on very tight deadline
ICANN is seeking one or more pre-delegation testing providers for its new gTLD program on a very ambitious timetable.
An RFP issued yesterday calls for a company that can scratch-build a testing suite to put new gTLD applicants through the ringer before they go live, and have it up and running by March 25, 2013.
Pre-delegation testing is the last stage of the new gTLD program’s approval process.
Some new gTLD applicants have recently called on ICANN to begin testing as soon as possible — before even Initial Evaluation has finished — in order to speed up time to market.
The Applicant Guidebook suggests that ICANN itself would be doing the testing, and some applicants had made that assumption, but that’s clearly not the case.
The RFP spells out exactly what is required of the testing providers.
First, they’re expected to build bespoke software to run the tests.
In addition to load-testing and verifying the registry’s compliance with standards such as EPP, DNSSEC and Whois, it also needs a custom-made user interface for applicants and back-end integration with ICANN’s wobbly TLD Application System.
ICANN also wants to be able to open-source the software, which seems to rule out any off-the-shelf testing suites.
RFP respondents also need to be able test 20 applicants’ back-ends per week — potentially scaling up to 100 per week — as soon as ICANN starts signing registry agreements next year.
ICANN does not expect to announce the winning provider(s) until December 5. The deadline for responses is November 20.
In short, it looks like a challenging project on a very tight deadline.
I wonder how much institutional knowledge there is out there of, say, DNSSEC, in companies that are not also involved in new gTLD applications as either applicant or back-end.
The pool of possible RFP respondents is likely very small indeed.
The ability to run tests on the testing suite itself may also be limited by the timetable and the possible shortage of guinea-pig registry back-ends.
Why ICANN has waited until this very late date to issue the RFP is a real head-scratcher.
ICANN is offering a 24-month contract with a possible 12-month extension. The RFP can be downloaded here.
Indian domain conference attracts 4,000
While US domain conferences are reportedly becoming sedate affairs, a domain-heavy summit that kicks off tomorrow in Mumbai has more than 4,000 signed-up attendees, according to organizers.
The two-day ResellerClub Hosting Summit, organized by Directi, may have “hosting” in the title, but its sponsors and agenda reveal a strong presence from the domain name industry.
Verisign is the major sponsor, plugging its .com and .net TLDs. Other sponsors include .org, .biz, .co, .asia and .pw.
The agenda features speakers from Public Interest Registry, ICANN, NameMedia and Directi new gTLD applicant Radix.
Demand Media: ignore our Republican gTLD rivals
Demand Media has asked ICANN to “ignore” complaints from the US Republican party about its application for the .republican gTLD.
Last month, the Republican National Committee and the Republican State Leadership Committee submitted comments to ICANN arguing that Demand would be an unsuitable custodian for the gTLD.
Demand is best known for its “unofficial, mediocre and sometimes incorrect” content farms, such as eHow, the letter (pdf) said.
The company should not be allowed to run .republican because it implies endorsement by the Republican party, or some kind of community backing for a non-Community application, the letter said.
This week, Demand has responded, saying it’s nothing but competitive posturing, given that the RSLC has applied for .gop (for “Grand Old Party”, a nickname for the Republicans):
A letter to ICANN from Demand subsidiary and .republican applicant United TLD Holdco, says:
Because the RSLC and RNC have applied for .GOP, an arguably competing string, it is easy to see through these arguments and ignore them as nothing more than an attempt to undermine the credibility of United TLD in order to gain a competitive advantage.
…
By their own admission, RSCL and RNC agree that “.REPUBLICAN has the potential to be a very powerful gTLD.” It is natural then, that they would attempt to discredit United TLD in the hope of eliminating competition for their own string.
The thrust of Demand’s rebuttal is that Republicanism is not an exclusively American movement — other parties around the world use the name — and that it also has generic meaning.
It further argues that the quality of the content Demand provides elsewhere is irrelevant, because the company plans to sell .republican domain names, not produce content there.
Demand has also applied for .democrat, the other major US political party, but did not receive any complaints from the Democratic party during the designated ICANN comment period.
Trademark protection stalemate follows ICANN 45
Trademark interests and new gTLD applicants are at odds about trademark protection — again — following the ICANN meeting in Toronto two weeks ago.
In a welcomed, not-before-time show of cooperation, the Intellectual Property Constituency and Business Constituency submitted to ICANN a bulleted list of requests for improved rights protection mechanisms.
The list is, for the most part, not particularly egregious — calling for a permanent Trademark Claims service and a Uniform Rapid Suspension service that meets its cost goals, for example.
But the New TLD Applicants Group (NTAG), an observer component of the Registries Constituency, has dismissed it out of hand, anyway, saying that the time for policy changes is over.
Here’s the IPC/BC list:
1. Extend Sunrise Launch Period from 30 to 60 days with a standardized process.
2. Extend the TMCH and Claims Notices for an indefinite period; ensure the process is easy to use, secure, and stable.
3. Complete the URS as a low cost alternative and improve its usefulness – if necessary, ICANN could underwrite for an initial period.
4. Implement a mechanism for trademark owners to prevent second-level registration of their marks (exact matches, plus character strings previously determined to have been abusively registered or used) across all registries, upon payment of a reasonable fee, with appropriate safeguards for registrants with a legitimate right or interest.
5. Validate contact information for registrants in WHOIS.
6. All registrars active in new gTLD registrations must adhere to an amended RAA for all gTLD registrations they sponsor.
7. Enforce compliance of all registry commitments for Standard applications.
8. Expand TM Claims service to cover at least strings previously found to have been abusively registered or used.
Most of these requests are not entirely new, and some have been rejected by the ICANN policy-development process and its board of directors before.
The NTAG points out as much in a letter to ICANN management last week, which says that new gTLD applicants paid their application fees based on promises in the Applicant Guidebook, which should not be changed.
Many of the BC & IPC proposed policy changes have been considered and rejected in no fewer than four different processes and numerous prior Board decisions. Indeed, many go far beyond the recommendations of the IRT, which was comprised almost exclusively of trademark attorneys. These last-minute policy recommendations amount to just another bite of the same apple that already has been bitten down to its core.
The new gTLD policy development process is over. Applicants relied on the policies in the final Guidebook in making business decisions on whether to apply. At the time that ICANN accepted applications and fees from applicants, ICANN and applicants entered into binding agreements. ICANN should not change these agreements unilaterally without extraordinary reason and especially not when it would materially harm the counterparties to the agreements.
The Applicant Guidebook, as it happens, asks applicants to explicitly acknowledge that ICANN may make “reasonable
updates and changes” to the rules, even after the application has been submitted.
But if applicants reckon changes would create a “material hardship”, ICANN is obliged to “work with Applicant in good faith to attempt to make reasonable accommodations in order to mitigate any negative consequences”
Independent Objector launches web site
The new gTLD program’s Independent Objector has launched his own web site, independently from ICANN.
Alain Pellet is the French international law expert appointed in May to the IO role. The new web site also reveals that one Julien Boissise is assisting him.
The IO’s job is to file Community Objections and Limited Public Interest Objections against new gTLD applications, should the need arise.
In practice, I’d be very surprised to see any of the latter filed during the current application round, but I’d expect to see several Community Objections.
Pellet will file his objections before January 13, according to the web site. That’s the current objection-filing deadline, which ICANN plans to extend to March 13.
US probing Verisign price hikes, .com contract may be extended
The US Departments of Commerce and Justice are investigating the price increase provisions of Verisign’s .com registry agreement.
Verisign CEO Jim Bidzos disclosed the “review” on a conference call with financial analysts tonight.
It is likely that it will last beyond November 30 2012, the date the current .com agreement expires, he said.
“There’s a possibility it will not be complete by November 30,” he said.
A special six-month extension is likely to be triggered, he said.
“The status of our ability to operate .com is not an issue here,” he said.
He declined to comment on questions related to the likelihood that the company would be forced to change its pricing plans.
Verisign has spent $3.9 million in legal and other fees related to the US review, it emerged during the call.
ICANN approved the contract, which gives Verisign the right to increase its .com registry fees by 7% in four of the next six years, in June.
ICANN will see an extra $8 million in revenue from Verisign as a result.
Due to the special nature of .com, Justice and Commerce approval is required before the contract can be renewed. Verisign had previously expected that to come before November 30.
Verisign shares are trading down 14% in after-hours trading following the news.
Only 2% of phishing attacks use cybersquatted domain names
The number of cybersquatted domain names being used for phishing is falling sharply and currently stands at just 2% of attacks, according to the Anti-Phishing Working Group.
The APWG’s first-half 2012 report (pdf) identified 64,204 phishing domains in total.
Of those, the group believes that only 7,712 (12%) were actually registered by the phishers themselves. The rest belonged to innocent third parties and had been compromised.
That’s a steep drop from 12,895 domains in the second half of 2011 and 14,650 in the first half of 2011.
Of the 7,712 phisher-owned domains, about 66% were being use to phish Chinese targets, according to the APWG.
The group’s research found only 1,350 that contained a brand name or a misspelling of a brand name.
That’s down from 2,232 domains in the second-half of 2011, representing just 2% of all phishing domains and 17% of phisher-owned domains.
The report states:
Most maliciously registered domain strings offered nothing to confuse a potential victim. Placing brand names or variations thereof in the domain name itself is not a favored tactic, since brand owners are proactively scanning Internet zone files for such names.
As we have observed in the past, the domain name itself usually does not matter to phishers, and a domain name of any meaning, or no meaning at all, in any TLD, will usually do.
Instead, phishers almost always place brand names in subdomains or subdirectories. This puts the misleading string somewhere in the URL, where potential victims may see it and be fooled. Internet users are rarely knowledgeable enough to be able to pick out the “base” or true domain name being used in a URL.
Taken as a percentage of attacks, brand-jacking is clearly a pretty low-occurrence offence, according to the APWG’s numbers.
In absolute numbers, it works out to about 7.5 domain names per day that are being use to phish and contain a variation of the brand name being targeted.
Unsurprisingly, the APWG found that Freedom Registry’s .tk — which offers free registration — is the TLD being abused most often to register domains for phishing attacks.
More than half of the phisher-owned domains were in .tk, according to the report.
Recent Comments