Domain Names

.xom, BrandJacking and Error-Search

BusinessWeek is running a column called 'Brandjacking' on the Web. In summary, nobody likes deliberate cybersquatting or typosquatting. But if Typo domain-names did not exist, the traffic would continue to flow to Microsoft or Google via the browser's error search where those very large companies would make money in the same manner as the 'evil cybersquatters'... more

Chinese and Japanese IDN in .BIZ

I just got back this morning from attending the OASIS XRI TC face-to-face meeting with Bill Barnhill, Drummond Reed, Laurie Rae, Les Chasen, Markus Sabadello, Marty Schleiff. A number of good things came out of the meeting, which I'll leave for another blog because this post is about Internationalized Domain Names, not XRI. So we just opened the flood gates for Chinese and Japanese IDNs for .BIZ. This has been my brainchild for the past half a year or so, and represents a significant step forward for our registry in terms of internationalization. more

WIPO Snafu Over britishmuseum.org Case?

WIPO just published a decision regarding the domain dispute over the britishmuseum.org domain name. At first glance, everything seems alright. The world famous British Museum won in a default judgment as the current registrant (the respondent) never replied). However, drill a little deeper and something is amiss. The "parties" section of the case lists the respondent as "British Museum Resources, Limited, West Bay, George Town, Kentucky, United States of America." more

Verizon vs. iREIT et al Court Documents: What Can We Learn?

Verizon filed sued against iREIT and Domain Marketplace a couple of weeks ago in a Texas court, alleging cybersquatting. David Kesmodel's blog broke the story, and I used the PACER system to obtain the court filings, which are posted here. Exhibit 5 makes fascinating reading, especially when point #43 in the main statement of claim says "Exhibit 5 details only one famous trademark for each letter of the alphabet." more

Splitting the Root: It’s Too Late

One of the consistent chants we've always heard from ICANN is that there has to be a single DNS root, so everyone sees the same set of names on the net, a sentiment with which I agree. Unfortunately, I discovered at this week's ICANN meeting that due to ICANN's inaction, it's already too late. Among the topics that ICANN has been grinding away at is Internationalized Domain Names (IDNs) that contain characters outside the traditional English ASCII character set... ICANN has tied itself with the issue of homographs, different characters that look the same or mean the same thing. Once people noticed that IDNs let you register different names that look the same, the intellectual property crowd that has always had a mysteriously great influence on ICANN went into a tizzy and they went into lengthy discussions on what to do about them... more

Putting Some Circuit Breakers Into DNS to Protect The Net

There are a lot of bad, but smart, people out there on the net. They are quick to find and capitalize on vulnerabilities, particularly those vulnerabilities in mass market software. These bad folks are quite creative when it comes to making it hard to locate and shutdown the computers involved. For example, a virus that takes over a victim's computer might communicate with its control point, or send its captured/stolen information, by looking up a domain name. Normally domain names are somewhat static - the addresses they map to don't change very frequently - typically changes occur over periods measured in months or longer. more

Put Security Alongside .XXX

Isn't security as important to discuss as .XSS? The DNS has become an abuse infrastructure, it is no longer just a functional infrastructure. It is not being used by malware, phishing and other Bad Things [TM], it facilitates them. Operational needs require the policy and governance folks to start taking notice. It's high time security got where it needs to be on the agenda, not just because it is important to consider security, but rather because lack of security controls made it a necessity. more

.COM and .NET: Thick Or Thin?

The fallout from the failure of RegisterFly has been largely addressed as an issue of regulation and enforcement. ...ICANN has not historically enforced the escrow obligation, and in any case, if a company has failed, who exactly is going to take responsibility for updating the escrowed data? It seems to me that the problems that have arisen as a result of RegisterFly's collapse have more to do with the design of the "shared registry system" for the .COM and .NET TLDs than they do with ICANN's failure to enforce the RAA. more

Ongoing Internet Emergency and Domain Names

There is a current ongoing Internet emergency: a critical 0day vulnerability currently exploited in the wild threatens numerous desktop systems which are being compromised and turned into bots, and the domain names hosting it are a significant part of the reason why this attack has not yet been mitigated. This incident is currently being handled by several operational groups. This past February, I sent an email to the Reg-Ops (Registrar Operations) mailing list. The email, which is quoted below, states how DNS abuse (not the DNS infrastructure) is the biggest unmitigated current vulnerability in day-to-day Internet security operations, not to mention abuse. more

When Domain Names Aren’t Enough

A recent trend in the Japanese web advertising market may presage changes that could come to the Western world. ...some advertising in Japan now includes a picture of a filled-in browser search box instead of a domain name. The idea is that an advertiser can buy top-of-page advertising at the main search engines for various terms and then suggest to people reading their print ads to use those terms to search. more