Architelos launches new gTLD anti-abuse tool

Architelos, having consulted on about 50 new gTLD applications, has refocused on its longer-term software-based game plan with the recent launch of a new anti-abuse tool for registries.
NameSentry is a software-as-a-service offering, currently being trialed by an undisclosed number of potential customers, designed to make it easier to track abusive domains.
Architelos gave us a demo of the web site yesterday.
The service integrates real-time data feeds from up to nine third-party blocklists – such as SURBL and SpamHaus – into one interface, enabling users to see how many domains in their TLD are flagged as abusive.
Users can then drill down to see why each domain has been flagged – whether it’s spamming, phishing, hosting malware, etc – and, with built-in Whois, which registrar is responsible for it.
There’s also the ability to generate custom abuse reports on the fly and to automate the sending of takedown notices to registrars.
CEO Alexa Raad and CTO Michael Young said the service can help streamline the abuse management workflow at TLD registries.
Currently, Architelos is targeting mainly ccTLDs – there’s more of them – but before too long it expects start signing new gTLD registries as they start coming online.
With many new gTLD applicants promising cleaner-than-clean zones, and with governments leaning on their ccTLDs in some countries, there could be some demand for services such as this.
NameSentry is priced on a subscription basis, based on the size of the TLD zone.

More than half of new gTLD apps have comments

Over half of ICANN’s 1,930 new generic top-level domain applications have received comments, two days after the original deadline for having them considered expired.
There are 6,176 comments right now, according to the ICANN web site, and the DI PRO database tells me that they’ve been filed against 1,043 distinct applications covering 649 unique strings.
It looks like .sex is in the lead, with 275 comments — I’m guessing all negative — followed by its ICM Registry stablemates .porn (245) and .adult (254), due to the Morality in Media campaign.
The controversial dot-brand bid for .patagonia, which matches a region of Latin America, has been objected to 205 times.
Some that you might expect to have created more controversy — such as .gay (86) and .islam (21) — are so far not generating as many comments as you might expect.
Donuts has received the most comments out of the portfolio applicants, as you might expect with its 307 applications, with 685 to date.
Famous Four Media’s applications have attracted 416 and Top Level Domain Holdings 399.
Despite applying for .sexy, Uniregistry has a relatively modest 64 comments. That’s largely due to it managing to avoid being whacked by as many duplicate trademark-related comments as its rivals.
There have been 1,385 unique commenters (trusting everybody is being forthright about their identity) with as many as 486 affiliations (including “self” and variants thereof).

Big hotel chains pick a side in .hotel gTLD fight

Many of the world’s major hotel chains say they plan to object to every .hotel new gTLD application but one.
A coalition of many recognizable hotel brands, led by InterContinental, has filed comments against six of the seven .hotel applications, as well as the applications for .hotels, .hoteis and .hoteles.
They say they want the Independent Objector to object to these applications on community grounds. Failing that, they’ll file their own official Community Objections.
The comments (PRO) were filed by the Hotel Consumer Protection Coalition, which appears to be one of those ad hoc organizations that exists purely to send letters to ICANN.

HCPC encourages the Independent Evaluator to submit a formal Community Objection if necessary. (Guidebook, Sec. 3.2.5.) Failing either of these occurrences, HCPC will seriously consider filing a Community Objection of its own – unless, of course, Applicant voluntarily withdraws its application.

The coalition’s members include the Choice Hotels, InterContinental, Hilton, Hyatt, Marriott, Starwood and Wyndham hotel chains. Together, they say they have over 25,000 hotels in over 100 countries.
The lucky recipient of the coalition’s tacit support is HOTEL Top-Level-Domain, the Luxembourg-based applicant managed by Johannes Lenz-Hawliczek and Katrin Ohlmer, which is using Afilias as its back-end.
It’s one of only two .hotel applicants flagged in the DI PRO database as planning to use a “restricted” business model. Only hotels, hotel chains and hotel associations will be able to register.
The other applicant with planned restrictions is a subsidiary of Directi, though its application suggests that any eligibility requirements would only be enforced post-registration.
HOTEL Top-Level Domain is also the only applicant that appears to be pursuing a single gTLD. All but one of the others are portfolio applicants of various ambitions.
Top Level Domain Holdings, Donuts, Famous Four Media and Fegistry all plan “open” business models for .hotel, while Despegar Online is planning a single-registrant space.
The Hotel Consumer Protection Coalition’s support for HOTEL Top-Level Domain is conditional, however. The company has apparently had to agree to explicitly exclude:

“any entity other than a hotel, hotel chain, or organization or association that is not formed or controlled by individual hotels or hotel chains”

It’s also agreed to “immediately suspend” any “clear violations”, such as cases of cybersquatting, when notified by coalition members, and to include its members’ brands on a Globally Protected Hotel Marks List.
The support has apparently been granted extremely reluctantly. InterContinental explicitly does not support the new gTLD program, and Marriott has previously said it thinks .hotel is pointless.
I can’t imagine a .hotel supported by companies that have no plans to use it being particularly successful.

Enjoy your weekend — ICANN extends new gTLD comment period

ICANN has extended the public comment period on new gTLD applications by 45 days, after pressure from intellectual property interests and the US government.
The window to have comments considered by evaluators, which was set to close on Sunday, will now end September 26. ICANN said:

After review and discussion of the community’s input, and careful consideration of the implications and impacts the additional time may have on the processing of applications, we have extended the application comment period an additional 45 days.

That’s in line with what the Intellectual Property Constituency asked for last week, but rather less than the Association of National Advertisers wanted.
To date, over 5,500 comments have been filed, but about half of those can be attributed to the same five or six brands, most of which are using the same consultant-prepared language in their filings.
The most immediate consequence of the change today, I expect, is that all the predictably last-minute commenters in the ICANN community get to enjoy their weekends instead.
And I checked: September 26 is a Wednesday.

Did Google withdraw three new gTLD applications?

Is Google behind the three new gTLD applications that have already been withdrawn?
ICANN senior veep Kurt Pritz revealed yesterday that three applications were already on the scrap heap, long before they’ve been evaluated, but he didn’t say which ones.
After a helpful nudge from a DI commenter, my best guess now is that they’re Google’s applications for .and, .are and .est.
As I blogged here and reported here over a month ago, these three strings are all protected geographic names, under ICANN’s rules.
They’re the ISO 3166-1 alpha-3 codes for the United Arab Emirates, Estonia and Andorra, which would be classified as country names and therefore banned by the Applicant Guidebook.
Many thanks to Silvia for the reminder.

Infodump: what we learned about new gTLDs today

ICANN held a webinar today in which it detailed a whole lot of the current thinking about the evaluation phase of the new gTLD program, including some new deadlines and target dates.
Senior vice president and acting program head Kurt Pritz fought through a cold to give new gTLD applicants more information and clarification than they’d received since Prague in June.
These are some of the things we learned:

• Three applications have been withdrawn already. We don’t know which ones.
• There have been 49 requests to change applications. Again, we don’t know which ones yet. ICANN is in the process of finalizing a threshold check to allow or deny these changes, details of which it expects to publish soon.
• “Clarifying Questions” are the new buzzword. CQs — yes, they have an acronym — are additional questions the evaluators need to ask applicants before they can score parts of their application. The vast majority of applications are going to get at least one CQ. The two-week deadline to respond to these questions, as described in the Applicant Guidebook, will likely be ignored in many cases.
• About 90% of applications will get a CQ about their financial status. This mainly concerns their Continuing Operations Instrument, the super-complex and expensive back-up cash commitments each applicant had to secure. But applicants who got letters of credit don’t need to panic if their banks have recently had their ratings downgraded.
• Another 40% can expect to get questions about their technical plans. Some applicants may have relied too heavily on their back-end providers to describe their security plans, it seems.
• About half of all geographic gTLD applications have not yet supplied letters of support from the relevant government. This was already anticipated and is accounted for by Guidebook processes however, Pritz said.
• Don’t expect an answer to the metering question any time soon. Batching may be dead, but ICANN does not expect to figure out its replacement — a way to throttle new gTLDs’ go-live dates — until October. There’s an open comment period on this and plenty more jaw-wagging to come.
• Objections will come before Initial Evaluation results. This sucks if you’re a likely objector. The deadline for filing objections is January 12, 2013, but evaluation results are not expected until June 2013 at the earliest. This means the much cheaper option of waiting to see if an application is rejected before paying for an objection is no longer a viable strategy. But it’s good for applicants, which will get a little more visibility into their likelihood of success and their costs.
• Contention sets will probably be revealed in November. The String Similarity Panel, which decides which gTLDs are too similar to each other to co-exist, is not expected to give its results to ICANN until late October, four and a half months after the June 13 Reveal Day — so applicants won’t know the full size of their contention sets until probably a couple of weeks after that.
• The new gTLD public comment period will probably be extended. After several requests, ICANN is very probably going to give everyone more time to comment on the 1,930 1,927 applications, beyond the August 12 scheduled closing date. An announcement is likely on Friday.

DI PRO offers full-text new gTLD comment search

With ICANN today saying that it is “very inclined” to extend the public comment period on new gTLD applications, I thought it timely to announce a new feature for DI PRO subscribers.
If you’ve used ICANN’s web site to try to read some of the 4,000+ comments received to date, you might have noticed that it’s not always particularly easy to find what you’re looking for.
So I thought I’d write something a bit more functional.
These are some features of the new DI PRO new gTLD public comment search engine that I don’t think the ICANN site currently offers:
Search the full text of the comments. This is useful for, say, figuring out which comments discuss particular themes or issues, or are part of organized astroturf campaigns.
Search and sort by commenter affiliation. Want to see every comment filed by Tiffany or Lego or Heinz? If the commenter has disclosed his or her affiliation, you can do that.
Search by partial commenter name. There’s no need to remember the full name of the commenter you’re looking for. First name, last name, or just a few letters will suffice.
Search by alternate applicant name. The DI PRO database understands which applications originate from the likes of Google and Donuts and Famous Four Media, even if the application has been filed by a subsidiary with a different name.
The database is updated at least twice daily, rather than in real-time, so users may find a small delay between the time a comment appears on the ICANN site and the time it is indexed by DI.
Subscribers can start searching here.

Congressmen say new gTLDs need more comments

Senior members of the US Congress have asked ICANN to prove that it’s giving the internet community enough opportunity to comment on its 1,930 new gTLD applications.
A letter from the chairs and ranking members of the House and Senate judiciary committees sent to ICANN yesterday basically implies rather heavily that, again, ICANN’s new gTLD program outreach sucks.
Sens. Leahy and Grassley, and Reps. Smith and Conyers write:

many members of the public outside the ICANN community are unaware that the New gTLD program is underway. Of those who are aware, few know about the public comment process or comprehend that their opportunity to participate in this forum is scheduled to end in less than a week.

Probably not coincidentally, the letter comes soon after requests for more time to comment from the Association of National Advertisers and the Intellectual Property Constituency.
The IPC wants another 30-45 days added to the comment period, which is currently set to close — at least for comments that will be forwarded to evaluators — this Sunday.
The Leahy letter highlights the need for comment on “potentially sensitive names like ‘.church’, ‘.kids’, and ‘.sucks'”, which should be a cause for concern for at least seven gTLD applicants.
Given who’s pulling the strings here, it’s not surprising that the letter also highlights the demands from IP interests for stronger rights protection mechanisms, such as a permanent Trademark Clearinghouse service.
They write:

ICANN’s current policy only requires the Clearinghouse to be available for the first 60 days after a registry launches. Moreover, the Clearinghouse will only give notice when someone registers a website that is identical to a trademark; not when the website contains the trademark in a varied form.
As an example, this means that a nonprofit such as the YMCA will receive notice only if a user registers a website such as www.yrnca.give or www.ymca.charity within the first 60 days of the “.give” or” .charity” registry. The YMCA would not receive notice if a person registers those names after 60 days, or if someone registers a closely related name such as www.ymcaDC.charity.

(To which I add, as an aside: and what if Intel wants to register www.buymcafee.shop?)
I think the Congressmen/ANA/IPC have a point, anyway, at least about the lack of commenting from people outside the tightly knit ICANN community.
A lot of data was released on Reveal Day, and much more has been released since.
There are 1,930 new gTLD applications.
The public portions weigh in at almost 400 MB in HTML format and generally run to between 15,000 and 50,000 words apiece.
The 20,000 published application attachments (which MD5 hashing reveals comprise close to 3,000 unique files) are currently taking up about 6 GB of space on the DI PRO server (where subscribers can cross-reference them to see which files show up in which applications).
It’s a lot to read.
That must be at least part of the reason there hasn’t been a single community-based objection comment about Google’s single-registrant .blog application yet.
For me, that’s the benchmark as to whether anyone in the real world is paying attention to this program.
I mean, seriously: no bloggers are concerned about Google using .blog as an exclusive promo tool for its third-rate blogging platform?
What’s worrying the Congressmen is that ICANN’s expensive Independent Objector is not allowed to object to an application unless there’s been at least one negative comment about it
The IO can file community-based objections on behalf of those who cannot afford to do it themselves, but it’s not at all clear yet what the cut-off date for the IO to discover these comments is.
Hopefully, when ICANN reveals its proposed evaluation timetable this week, some of these questions will be answered.

ICANN trademark tech summit confirmed for Brussels in just two weeks

ICANN has confirmed that it will hold a technical summit to discuss the forthcoming Trademark Clearinghouse in Brussels less than two weeks from now.
The two-day meeting will be held at the offices of Deloitte, which along with IBM has been contracted as the TMCH provider, from August 20 to 21.
As you might expect by now from the new gTLD program, the summit’s organization wasn’t particularly timely or well-communicated, leaving parts of the community fuming.
The meeting was demanded by registries and registrars at the Prague meeting in June — they want a chance for their technical guys to get into the nitty-gritty of the TMCH implmentation.
But confirmation that it’s actually going ahead only arrived in the last couple of days, leaving companies in the US and Asia-Pacific regions facing steep last-minute air fares or the less-ideal option of remote participation at ungodly hours.
I get the impression that the TMCH providers, which have been less than communicative with the registrars and registries they will soon be servicing, might be as much to blame as ICANN this time.
The TMCH is a repository for trademark data that new gTLD registries will be obliged to use in their sunrise and immediate post-launch periods.
While the policy argument has ostensibly been settled, many technical details that still need to be ironed out could have huge implications.
For example, if the registration process flow requires live queries to the TMCH, downtime could be devastating for registries if, as is expected, several gTLDs wind up launching simultaneously.
And if the TMCH protocols prove to be too complex and costly for registrars to implement, many may not bother, potentially leading to a bunch of damp squib gTLD launches.
So it’s important stuff. DI may even be in attendance, hotel prices and/or Belgian vagrancy laws permitting.

Tonight a new gTLD went live

Just as people are starting to get seriously stressed about the imminent introduction of new gTLDs, a timely reminder that this is actually the third time ICANN has run a new gTLD program.
.post has just gone live.
The gTLD, which was applied for by the Universal Postal Union as part of the 2003/2004 round, has been in limbo since it was approved in December 2009, while the UPU figured out what to do with it.
It’s going to be tightly restricted to members of the international postal community, so it doesn’t carry any of the baggage of the last new gTLD launch, .xxx.
The registry has switched back-end providers since it first applied. It had planned to go with CORE, but following a competitive bidding process last year it’s moved to Afilias instead.
I’m not currently aware of any live second-level domains; tests on www.post and nic.post and a few other usual suspects are treated by my browsers as search queries.
The news of .post’s addition to the DNS root was tweeted by ICANN chief security officer Jeff Moss this evening.