Q&A with Author of 'Domain Name Arbitration' Book

DomainNameArbitration - cover.jpg

In the preface to his new book, "Domain Name Arbitration," author Gerald M. Levine says his work "is principally devoted to explaining the process, jurisprudence, and demands of the Uniform Domain Name Dispute Resolution Policy, popularly referred to by its acronym, UDRP."

The book is, as I said in a testimonial printed on the back cover, "an important, thorough and incredibly helpful guide for navigating the UDRP."

Here, Levine answers some questions I had about his book and the UDRP:

Q: Why did you write this book?

A: This goes back to 2004, maybe even 2003 when a colleague asked me to assist him in dealing with a client’s claim that several people were using domain names either corresponding to its trademark or incorporating its trademark. I didn’t know what the remedies were or whether there were any against domain name holders in foreign countries, so I started researching the law, and that’s how I learned about ICANN and the Uniform Domain Name Dispute Resolution Policy, the UDRP. I also went into the statutory remedies under the Anticybersquatting Consumer Protection Act, the ACPA. I thought it interesting that both regimes rolled out in 1999. I started keeping track of the UDRP decisions and began organizing legal conclusions into themes and topics. There were already 15,000 or more decisions from the UDRP by 2005; but only a handful of decisions from the ACPA.

The book initially started as a brief memorandum to the client, and began growing as I added material and transitions from subject to subject. I did a long article for the New York Law Journal in 2005. Then I started organizing my notes to see whether there was enough for a book. This involved numerous drafts before I found the right organization. There were a number of false starts until I hit on a solution I thought would be the most practical and useful in guiding practitioners and parties in understanding what the UDRP was about and what the parties had to do to assert and defend claims of cybersquatting.

Q: Years ago, Corporate Counsel magazine called the UDRP “the preferred option for most trademark owners” for resolving domain name disputes. Do you agree, and why?

A: This view that the UDRP is “the preferred option” for combating cybersquatting is still the current perception, of course, and properly so. The administrative regime has proved astonishingly successful. Just think, if there were no UDRP every dispute in which parties resided in different countries would have to be decided in the countries in which the domain name holders resided. It would be cost prohibitive to do that. The UDRP functions as supranational forum, with its own procedural and substantive law that has been developing into a ripe jurisprudence now for fifteen years. The regime is available to trademark owners regardless of the jurisdictions in which they and domain name owners reside. Any trademark owner anywhere in the world has a remedy against any domain name holder anywhere in the world. The UDRP transcends territorial legal jurisdictions and that’s what’s so remarkable about it.

Also, the majority of disputes involve domain names clearly registered to take advantage of the good will and reputation owners’ trademarks; that certainly accounts for the 85% win rate for trademark owners. It is more cost effective to arbitrate under the UDRP than commencing litigation even in one’s own country. Just looking at the kinds of disputes on the database illustrates the problem. Within 60 to 75 days, or even less in some instances, panels appointed by providers produce reasoned awards. And, some of these awards are astonishingly good. Trademark owners win mainly because there is conclusive proof the domain names were registered and are being used to take advantage of the power of the corresponding trademarks.

Those trademark owners that fail to persuade fall into three categories. First, are those who fail to understand the evidentiary demands for prevailing under the UDRP and present insufficient or no evidence of bad faith. The second category of owners consists of those with weak trademarks composed of common elements that domain name holders are lawfully allowed to register and use as long as they have not registered the domain names with the intention of taking advantage of the trademark owners. The third category consists of trademark owners who concede priority or derive their rights from distant jurisdictions but claim to have the “better right” to the disputed domain name because they are offering “real” goods or services whereas the domain name holders are only monetizing their websites. Measuring distances, incidentally, whether temporally, geographically, and by goods/services offered by each of the parties, is a significant factor in determining whether there’s been an abusive registration.

Q: What are some of the popular misconceptions about the UDRP?

A: The first kind of “popular misconception” was held by domain name holders who were being challenged for their choices of domain names. The early domain players really didn’t understand the relationship between trademarks and domain names, and neither in some cases did trademark owners and lawyers. In the early 2000s there were domain name holders who couldn’t understand why it was unlawful to create close variants of trademarks. They argued they had as much right to variants as trademark owners had to trademarks. This argument was quickly put to rest under both UDRP and the ACPA. This form of cybersquatting received its own classification, “typosquatting.”

There is also another misconception that I’ve seen expressed by domain name holders as well as commentators that the UDRP is biased in favor of trademark owners. In part critics support their view by pointing to the overwhelming percentage of cases that end in favor of trademark owners. But, this is nonsense for the reason I’ve already mentioned. Where defenses are truly meritorious domain name holders prevail. And, if domain name holders lost under the UDRP they can be successful in federal court under the ACPA. In some cases reverse domain name hijacking by trademark owners has proved to be a very costly ordeal.

There is also a popular misconception that the UDRP isn’t working. This criticism is against panelists who follow their own beliefs of what the law should be rather conforming to established law, and this has happened in some recent cases where panelists take the position that the law doesn’t require them to find conjunctive bad faith, but the domain name can be forfeit in their view if there is bad faith use after renewal of registration. Again, this is not the law. There is a strong consensus of Panels that condemns this reading of the UDRP.

It has also been said the bias is endemic because the panelists are drawn from the trademark bar. This too does not bear scrutiny. This is not to say there aren’t some anomalies among decisions that come down; the regret here is that there is no administrative appeal from these decisions. There is, incidentally, an appeal mechanism under the URS, but so far ICANN has not amended the UDRP to provide for appeals.

Q: In researching and writing this book, what did you learn about the UDRP that surprised you the most?

A: What surprised me the most in researching and writing the book is the conceptual integrity of the UDRP. The jurisprudence has advanced in the same way as common law; it is Panel created, and although it is said by the World Intellectual Property Organization in its Overview to be a consensus based regime, it is rare for panelists not to cite precedent in their decisions. Panelists really do strive for predictability and consistency. You see it a lot in split decisions with the dissent taking a different legal approach to the facts. Also, in terms of surprise, is learning about the differences between the UDRP and the ACPA: there is the UDRP way, which is an “and” model; and there is the either/or way of the ACPA. The UDRP is not a trademark court.

Although I wouldn’t call it surprise it is always interesting to learn something new, and in this case it was about the differences between the two regimes and their evidentiary requirements. If there’s a trademark infringement it belongs in federal court. Some panelists want to remake the UDRP to be an administrative version of the ACPA. This is a huge mistake in my opinion.

Q: A lot of early UDRP cases involved pornographic websites and domain names that were truly identical to a company’s trademark, but those issues seem much less common today, as domain name registrants and trademark owners have become more sophisticated. What types of facts or trends are popular today in UDRP cases?

A: There are still domain name holders who respond to challenges of cybersquatting by threatening to repoint domain names to pornographic websites and there are a fair number of cases involving phishing for personal information. But, there are also cases of abusive process in which newly minted trademark owners are initiating complaints against domain name holders who have years of priority. So, the abuse is not always by the domain name holder.

Also, what’s happened is that use of content is much more sophisticated. In the early years bad faith use would be established by examining the content of the website; if it included the trademark owner or contained links to goods or services competitive with the trademark owner, that would indicate bad faith use, and if the trademark owner had priority in the marketplace, it would also establish bad faith registration. Now, the algorithms are so advanced that all of the infringements can be filtered out.

It is important to understand that holding domain names for sale or using them to generate revenue as search sites is not unlawful even though they may be identical or confusingly similar to trademarks.

Q: What do you see as the most contentious issues in UDRP jurisprudence?

A: The most contentious issue in UDRP jurisprudence, which started in a duo of cases in 2009, has been the attempt by a few influential panelists to change its construction to allow for forfeiture regardless of good faith registration if domain names are subsequently being used in bad faith. This view, which hasn’t really gotten anywhere and to my mind is a dead end, attempts to bring the UDRP into alignment with the ACPA. Nevertheless, there are some anomalous decisions sometimes by dissenting panelists that go to great lengths to explain the reasoning behind the view.

Another contentious issue is the use of domain names for commentary and criticism. What exactly is protected? Is it the domain name or the speech on the website? Some panelists hold that domain names identical or even confusingly similar to trademarks are not protected speech. Domain names may be protected if trademark are incorporated into strings that includes pejoratives such as “sucks.” Other panelists, particularly from the U.S. favor protection of domain names as well as content. Even alleged defamation is not enough to favor forfeiture because adjudicating whether material is defamatory is outside the scope of the Policy.

Q: The URS (the Uniform Rapid Suspension System) was intended to be a cheaper, faster alternative to the UDRP for domain name registrations in the new gTLDs, but it has not proven very popular, at least not yet. What do you think of the URS, and will it ever become as popular as the UDRP?

A: You’re right about the URS, and there’s good reason that it’s less popular, even though the remedy, shutting down the website, proceeds more rapidly and is marginally less expensive. The problem from the trademark owners’ perspective is that when the registration ultimately lapses the domain name returns to the pool of domain names and can be registered by another party, and if that happens the trademark owner has to go through the same procedure another time. With the UDRP the trademark owner can take ownership of the domain name and put it permanently beyond reach of cybersquatters.

Nevertheless, the URS is a useful tool to get the domain name out of the cybermarketplace and in that respect is fulfilling ICANN’s intentions in creating it.

Q: The new UDRP rules (as of July 31, 2015) address “locking” a domain name during a UDRP proceeding, which many practitioners believe will help reduce cyberflight. What did your research teach you about cyberflight, and how do you think it might change under the new rules?

A: This is an interesting issue because cyberflight has not shown up in all that many cases; in fact, some registrars were already locking challenged domain names upon receipt of notices from providers. The more important provision under the new UDRP rules is that the domain name holder no longer gets a copy of the complaint until it has been reviewed by the provider; and only after review does the provider serve the complaint on the domain name holder, Under the former rules, the complaint was served on the domain name holder as well as the provider at the same time which enhanced the possibility the domain name holder could move the registration to another registrar. The new rules eliminates that possibility.

The locking, of course, does not solve the problem of cease-and-desist letters. Once domain name holders are put on notice there’s an opportunity to change registrars; and put domain names in proxies to delay the proceedings. Providers and Panels are very attuned to this because the Whois directory discloses the name of the registrar and there is little tolerance for domain name holders who try to disguise themselves.

Are Anti-Abuse Policies a Faster, Better Alternative to the UDRP and URS?

A high-profile, market-moving Internet fraud has brought to light a little-known alternative to the popular domain name dispute policies, and this alternative can provide almost immediate relief for trademark owners. In other words, this tool can be even better -- or, at least, faster -- than either the Uniform Domain Name Dispute Resolution Policy (UDRP) or its speedier cousin, the Uniform Rapid Suspension System (URS).

So, what is it?

It's called a registry operator's "Anti-Abuse Policy."

And here's how it may have worked in one important domain name dispute.

The <bloomberg.market> Fake News Site

According to news reports, someone registered the domain name <bloomberg.market> and posted a fake news article -- mimicking the popular Bloomberg news service -- that Twitter had received an offer to be acquired for $31 billion. As a result, Twitter's stock soared, before Twitter and Bloomberg both exposed the report as fake.

While this cybersquatting incident received a lot of attention, it was, in many ways, no different than a typical domain name spat: Someone registers a domain name that contains a well-known trademark and creates a website that misleadingly confuses the public. These disputes are resolved every day via the UDRP and, with some regularity, the new URS.

But UDRP and URS proceedings can take weeks or months to resolve. In the case of <bloomberg.market>, though, the domain name was "suspended at mid-afternoon" on the same day that the fake Twitter article was published!

How?

It's unclear exactly what happened, but as of this writing the domain name's whois record lists its status as "serverHold" -- which ICANN describes as follows: "This status code is set by your domain's Registry Operator. Your domain is not activated in the DNS."

The Registry Operator's Anti-Abuse Policy

The whois record doesn't say why <bloomberg.market> was put in this status. But ICANN's registry agreement for the <.market> top-level domain has a requirement, known as "Specification 11," that contains an "Anti-Abuse Policy" giving a registry operator broad discretion to suspend a domain name. In particular, the policy says (emphasis added):

Registry Operator reserves the right, at its sole discretion and at any time and without limitation, to deny, suspend, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status as it determines necessary for any of the following reasons:

...

domain name use violates the Registry Operator’s acceptable use policies, or a third party’s rights or acceptable use policies, including but not limited to the infringement of any copyright or trademark...

Plus, the registry operator's own Anti-Abuse Policy gives it "sole discretion" to suspend a domain name that "[i]mpersonat[es] any person or entity."

Thus, it could be that Bloomberg simply complained to the registry operator, Rightside (which, ironically -- given the fake Twitter article on the fake Bloomberg site -- uses the advertising tagline, "Rightside Registry means more opportunity for storytelling").

If Bloomberg complained, Rightside may have concluded that it had the right, under its Anti-Abuse Policy, to suspend the <bloomberg.market> domain name because it infringed Bloomberg's trademark or was being used to impersonate Bloomberg. Which makes perfect sense.

Limitations of Anti-Abuse Policies as Domain Name Dispute Tools

Still, if this is how the dispute was resolved, it raises a number of important questions, most importantly:

  • Since registry operators and registrars generally defer to the UDRP and the URS, why did Rightside exercise its discretion to suspend the domain name in this case?
  • Under what circumstances will Rightside (and other registry operators with similar Anti-Abuse Policies) suspend domain names in the future?

The answers to these questions could be helpful to all trademark owners in cybersquatting disputes. Without such guidance, trademark owners could never rely on Anti-Abuse Policies.

Unfortunately, we're unlikely to get answers to the above questions. As a result, Anti-Abuse Policies will never gain the authority or precedent that UDRP proceedings offer as a result of tens of thousands of published decisions over the past 15 years.

Finally, the <bloomberg.market> story is unfinished even as this blog post was written: One week after the domain name was suspended, Bloomberg filed a UDRP complaint at the Forum (Claim No. 1629058, according to a search of the Forum's website).1 Perhaps because Rightside apparently only suspended the domain name, but the UDRP offers the ability to get a domain name transferred to the trademark owner.

Thus, while invoking a registry operator's anti-abuse policy may be an effective way to get a domain name suspended (or "taken down," as it is sometimes called), doing so is likely to remain an unpredictable and incomplete strategy. At best, it's probably a tool worth considering in addition to traditional approaches such as the UDRP in disputes that are clearly fraudulent and causing immediate and significant damage perhaps not only to the trademark owner but to a larger population.

---

1 Update (August 26, 2015): A UDRP panel ordered transfer of the domain name <bloomberg.market> to Bloomberg Finance L.P. In its decision, the panel wrote: "Complainant alleges that once the... fake article gained media recognition, use of the domain was suspended and currently resolves to a blank page displaying the message: 'Network Error.'"

How to Lose a UDRP Complaint: Don't Support the Facts

Having a strong UDRP complaint is not worth very much if you fail to support your factual arguments appropriately.

That's one harsh lesson from the intriguing dispute around the domain name <thesis.com>, Chris Pearson v. Domain Admin / Automattic, Inc., NAF Claim No. 1613723.

The case was won by the registrant, Automattic, Inc., the company behind the popular WordPress software, which apparently bought the domain name for $100,000 and was allowed to keep it -- despite the UDRP complaint brought by developer Chris Pearson, creator of the "Thesis" WordPress theme.

(For the uninitiated: WordPress is a sophisticated website content management system used by everyone from individual bloggers to leading news sites such as parts of The Wall Street Journal. A WordPress theme is a "skin" or design for a WordPress site that controls the look and presentation of the material on it.)

At first glance, the dispute might not seem so extraordinary, given the fact that "thesis" could be seen as a dictionary or generic word, which, as I've written, often makes for a weak UDRP case. But here, Pearson, the complainant, had a federal trademark registration for the word, and Automattic, the respondent, was apparently (more on that below) using it in a competitive manner by redirecting users to its own website offering a variety of WordPress themes.

The three-member UDRP panel had no trouble finding for Pearson on the first two UDRP elements -- the domain name <thesis.com> was identical or confusingly similar to a trademark in which Pearson had rights, and Automattic had no rights or legitimate interests in respect of the domain name.

However, the third element -- whether Automattic registered and used the <thesis.com> domain name in bad faith -- proved problematic.

When I visited www.thesis.com, I indeed found that it redirected to a website at themeshaper.com, which said: "This is ThemeShaper; a WordPress-powered blog and home to the Automattic Theme Division. We shape beautiful and customizable themes that make the world a better place."

Quite often, UDRP panels find that using someone else's trademark in a domain name in connection with a website that offers competing goods or services is clearly bad faith.

According to Pearson's version of the story -- and he tells a very interesting, and lengthy, story, which includes some nasty history with Automattic -- he passed on an opportunity to buy the <thesis.com> domain name long after he had created his Thesis theme, losing it in a bidding war to Automattic. But Pearson reasoned that "[b]ecause of my trademark, there was no way [Automattic] could legally use the domain for" its WordPress business. When he later saw that is was being redirected to Automattic's theme site (a site that presumably competes with Pearson's own site for his Thesis theme), he said, "I felt Automattic had purchased the domain in a specific attempt not only to prevent me from getting it, but also to, for lack of a better term, show me who is boss."

So, Pearson filed a UDRP complaint -- which, according to Pearson, led to some interesting negotiations and a settlement agreement ready for execution when the UDRP decision was issued.

And, the decision included this fatal (to Pearson) reminder:

Complainant claims that Respondent’s use of the disputed <thesis.com> domain name is to divert and confuse customers and potential customers. The Panel notes that Complainant did not include an exhibit showing that <thesis.com> redirects to a webpage owned by Respondent. The Panel suggests that the submissions might point toward use by Respondent that would support findings of bad faith, pursuant to Policy ¶ 4(b)(iv) if evidence had been adduced to that effect. However, Complainant failed to bring that proof to the Panel.

(Emphasis added.)

In other words, the panel might have found bad faith if Pearson's UDRP complaint made clear that Automattic was in fact using it in connection with a website for WordPress themes. But, as in all UDRP proceedings, the burden of proof is always on the complainant.

As WIPO's helpful "Overview" makes clear, "an asserting party would typically need to establish that it is more likely than not that the claimed fact is true" and "[c]onclusory statements unsupported by evidence" are insufficient.

(Interestingly, the panel's decision in the <thesis.com> case seems to state that Automattic agreed about the domain name redirection, but because UDRP filings are not publicly available, it's unclear exactly what Automattic may -- or may not -- have admitted.)

As a result, the panel said that Pearson's "mere assertions of bad faith are insufficient," and it allowed Automattic to keep the domain name.

Admittedly, how to show in a UDRP filing that one domain name redirects to another is a challenging task. While I don't know what evidence, if any, Pearson included in the complaint, he could have used something as simple as a written declaration to describe the redirect or as sophisticated as a screencast to document it.

Regardless, the bottom line is clear: Don't rely on naked allegations of essential facts that are unsupported by appropriate evidence. Instead, document vital facts with relevant "annexes" that are explicitly contemplated by the UDRP Rules and regularly a part of even the most straightforward UDRP disputes. Doing so could make all the difference.

Three Great Ways Trademark Owners Can Connect with ICANN

Understanding ICANN (the Internet Corporation for Assigned Names and Numbers) is an important but daunting task for anyone concerned about the intersection of domain names and trademarks.

Created in 1998, ICANN is a "not-for-profit public-benefit corporation" that manages the domain name system (DNS). Among other things of particular interest to trademark owners, ICANN created the Uniform Domain Name Dispute Resolution Policy (UDRP), the objection procedures for new top-level domains, the Trademark Clearinghouse, the Uniform Rapid Suspension System (URS) and other rights-protection mechanisms that trademark owners can use (some with more impact than others) to help protect themselves online.

ICANN prides itself on being a "bottom-up, consensus-driven, multi-stakeholder" system -- a description that is simultaneously appealing and confusing. As a result, it is a challenge to truly understand what ICANN does and how to influence its decisions.

Here are three easy things trademark owners can do to get educated and involved:

Visit the ICANN Website and Read Its Resources

Obviously, the ICANN website itself contains a great deal of information about the organization, its background, its leadership and all of its activities. While it's easy to quickly become overwhelmed or confused by all of the information there, here are a few good places to begin:

  • ICANN's "Get Started" page offers a simple introduction to ICANN as well as links to the numerous ICANN meetings held worldwide.
  • The ICANN Learn microsite offers videos and other resources that provide "a new way to learn about how the web works, what ICANN does, how ICANN works, and more."
  • The Beginner's Guides are booklets that offer introductions and overviews on participating in ICANN, understanding domain names, and other topics.

Subscribe to ICANN's E-mail Updates

ICANN offers numerous e-mail lists that provide regular updates about its activities. The subscription form on ICANN's Newsletters & News Alerts page lets you choose what types of issues you want to follow, including general news alerts, the contractual compliance newsletter and more.

While many, if not most, of the e-mail updates that ICANN sends out are unrelated to trademark issues, it's still worthwhile to subscribe, for two reasons: the updates in general provide a great education about ICANN's activities, and issues of interest to intellectual property owners frequently arise.

For example, recent ICANN e-mails informed the public about the "Rights Protection Mechanisms Review," the "Proposed Renewal of .TRAVEL Sponsored TLD Registry Agreement" (which led to an interesting debate about whether this TLD should adopt the URS), and an important upcoming change in ICANN's leadership, which certainly could impact how ICANN operates in the future.

Join the Intellectual Property Constituency (IPC)

The IPC states that it "represent[s] the views and interests of owners of intellectual property worldwide, with a particular emphasis on trademark, copyright, and related intellectual property rights and their effect and interaction with the DNS."

As a member of the IPC, I'm impressed by the important work that this group does on behalf of trademark owners worldwide. While its members don't always agree on everything, of course, the discussions are a great way simply to stay abreast of important intellectual property issues online.

The IPC helped shape the current rights-protection mechanisms for domain names and regularly takes action to ensure that trademark rights are protected online.

For example, the IPC recently wrote a strong letter to ICANN about what it called the "predatory, exploitative and coercive" pricing model created by the registry of the new <.sucks> top-level domain -- which the IPC said would "make[] it more likely that trademark owners’ marks will be registered by cybersquatters for much lower (potentially subsidized) fees at the launch of general availability."

The IPC letter resulted in ICANN referring the matter to the Federal Trade Commission and, although the FTC has not taken any immediate action, this issue quickly gained the attention it deserved and could very well influence the way in which ICANN and registry operators conduct themselves in the future.

Membership in the IPC is available in various categories, and the IPC's website offers great resources, including a brief 2-page PDF document that provides an overview of the IPC itself.

 

When to File a URS Complaint Instead of -- or in Addition to -- a UDRP Complaint

The Uniform Rapid Suspension Systems (URS) -- the dispute policy that applies to new global top-level domain names (gTLDS) -- is often ridiculed as a less-attractive alternative to the longstanding Uniform Domain Name Dispute Resolution Policy (UDRP). But, it actually has some advantages.

Unlike the UDRP, the URS doesn't allow a winning complainant to obtain the transfer of a domain name -- only a limited suspension of it. Plus, as I've written before (see "Why the URS is (So Far) an Unpopular Domain Name Dispute Policy"), the URS is only for “clear cases of trademark abuse” with no “open questions of fact”; and, it has much stricter rules of procedure.

In other words, it's actually more challenging to win a URS complaint and, even if you prevail, the remedy is more limited than in a UDRP proceeding.

Still, there are situations in which the URS is a better option than the UDRP.

URS Filing Fees and Legal Fees are Less Expensive Than the UDRP

Clearly, the URS is much less expensive than the UDRP. The two largest UDRP service providers, the World Intellectual Property Organization (WIPO) and the Forum (formerly the National Arbitration Forum), charge filing fees for UDRP complaints that start at, respectively, $1,500 and $1,350. By comparison, the Forum's URS fees start at only $375. (WIPO does not offer URS services.)

Plus, because the URS is only available for straightforward disputes and its rules severely limit the size of complaints, legal fees for URS cases are often only a fraction of those for UDRP cases.

URS Complaints are Always Filed in English

The UDRP rules state that "the language of the administrative proceeding shall be the language of the Registration Agreement, subject to the authority of the Panel to determine otherwise, having regard to the circumstances of the administrative proceeding." So, except under some limited situations, the registrar's registration agreement will determine the language in which a UDRP complaint must be filed. While many of the largest registrars (such as GoDaddy and Network Solutions) have English agreements, many others do not. As a result, it may be impossible (or, at least, more challenging and uncertain) to file a UDRP complaint against some registrants in English.

On the other hand, the URS rules (PDF) clearly state that "[t]he Complaint shall be submitted in English." No exceptions exist, and I am not aware of any authority that would allow another language for the complaint, or any URS proceeding in which that has ever occurred.

Therefore, English-speaking trademark owners may find the URS more attractive, because translating a complaint may be impractical or expensive (which would diminish the cost-savings feature of the URS described above).

The URS Process is Quicker Than the UDRP

The URS was envisioned as a much quicker option than the UDRP. In reality, though, it is not as quick as many trademark owners would like.

Still, the URS can be very quick. The Forum's timeline shows that URS determinations should be issued within 21 days after a complaint has been filed. And, many determinations have been issued much more quickly, with the average time to a default determination being only 18 days.

By comparison, the UDRP rules envision a timeline of at least 34 days from filing a complaint to a decision. And, in practice, given delays that can occur in commencing the proceeding, appointing the panel and notifying the decision -- as well as common issues such as amendments, supplemental filings and even extensions of deadlines -- it is typical to expect a decision in about 60 days.  Plus, UDRP decisions are not implemented until the expiration of a waiting period of an additional 10 business days.

As a result, if a domain name is actually causing harm to a trademark owner (and not just a domain name that a trademark owner would like to have), then time may be of the essence -- making a URS complaint the better choice.

How the URS and UDRP Can Work Together

While this discussion shows that the URS has certain advantages over the UDRP, it's actually possible to consider both dispute procedures under the right circumstances. Doing so might be an option if all of the following apply:

  • The disputed domain name is a new gTLD.  (The URS and the UDRP apply to new gTLDs, but the URS does not apply to <.com> and most of the traditional gTLDs.)
  • The dispute is appropriate for the URS process.  (Remember that the URS has a high burden of proof -- “clear and convincing evidence.”)
  • The disputed domain name is causing damage to the trademark owner.  (If so, a URS could get the domain name suspended quickly -- in about 18 days, as shown above.)
  • The trademark owner wants to use the disputed domain name or permanently keep it from being used by anyone else.  (Remember that the UDRP, unlike the URS, allows a domain name to be transferred to the complainant.)

In other words, the URS can act as a sort of preliminary injunction, possibly allowing a trademark owner to quickly get a domain name suspended -- and later (at any time during the suspension period) follow-up with a UDRP complaint to seek transfer of the domain name.

Of course, this two-step process is more expensive than taking only the URS or the UDRP route. But it also offers the best of both worlds and should be given serious consideration when the facts, law and desired relief are appropriate.

What Google Will -- and Won't -- Do About Trademarks in Ads

Trademark owners have long been annoyed by how other people and companies use their trademarks online, and one particular source of annoyance is with Google's "AdWords" program.

The issue: Who can use a trademark as a Google search term, and who can use that trademark in a Google search ad?

These questions raise interesting legal issues that courts continue to address. But Google's position is, for the most part, clear. And it's all spelled out in Google's "AdWords Trademark Policy."

Still, confusion often arises because Google draws a distinction between whether the trademark is used as a search term or whether it appears in a Google AdWords advertisement; whether it appears in a link (URL) in the advertisement; whether the advertiser is a reseller of the goods or services bearing the trademark; whether the advertiser provides an informational site about the trademarked goods or services; and where the advertising campaign is targeted.

In other words, Google's policy may be clear -- but it's not necessarily succinct.

And, Google is hesitant to take action, as the search engine leader has made clear:

Google takes allegations of trademark infringement very seriously and, as a courtesy, we investigate matters raised by trademark owners. However, because Google is not a third-party arbiter, we encourage trademark owners to resolve their disputes directly with the advertisers, particularly because the advertisers may have similar ads running through other companies' advertising programs.

Still, Google takes the following approach to trademarks and AdWords -- at least for ads targeting U.S. users -- in response to objections filed via its Trademark Complaint Form:

 

  • If the trademark is simply being used as a search term, Google says that it "will not investigate or restrict the use of trademark terms in keywords, even if a trademark complaint is received."
  • If the trademark appears within the ad text, Google says that it "will investigate and may restrict the use" of the trademark. However, resellers and informational sites (as defined by Google) may be allowed.
  • If the trademark appears only in a link (URL) in the Google ad, Google says that it "will not investigate and restrict use of the trademark in display URLs because the presence of trademarked term within a URL may not necessarily constitute trademark use, such as in the case of post-domain paths or subdomains."
  • If the trademark appears in an "organic" Google search result (that is, not an advertisement as part of Google's AdWords program), then Google says that trademark owners must "contact the site owner directly."

 

Clearly, Google is not eager to restrict its advertisers' activities (after all, these advertisers are Google's prominent source of revenue), though it will do so under limited circumstances.

A trademark owner's best approach to dealing with problematic Google ads is to evaluate the scope of the problem; complain to Google when appropriate (but be sure to provide accurate information or risk getting no help from Google -- or, even worse, see your own ads removed); and contact advertisers directly (because Google's complaint process is not the only course of action).

How to Stay Informed About Domain Name Dispute Decisions

Reading domain name dispute decisions is certainly not for everyone. But for those, like me, who want to stay on top of trends in this area of the law, it's an important and highly informative task.

That's why I review these decisions every day. And you can, too.

Fortunately, it's not difficult to follow domain name disputes -- if you know where to look. Here are the easiest ways to keep informed about new decisions from all of the ICANN-approved dispute resolution service providers for the Uniform Domain Name Dispute Resolution Policy (UDRP) and the Uniform Rapid Suspension System (URS):

 

  • The World Intellectual Property Organization (WIPO) maintains a "Subscribe to WIPO Newsletters" page (www3.wipo.int/newsletters/en/) that includes a check box for "Domain Name Decisions." E-mails contain links to new decisions under the UDRP and other domain name dispute policies managed by WIPO, including many ccTLDs. WIPO also publishes a list of all decisions at www.wipo.int/amc/en/domains/casesx/all.html.
  • The National Arbitration Forum (NAF) has a "Domain Name Decisions Daily Feed" page (dailymail.adrforum.com) with a simple form to receive a daily e-mail update with UDRP and URS decisions, as well as additional policies managed by NAF, including the usDRP (for .us domain names). Decisions also can be searched at www.adrforum.com/SearchDecisions.

Why 'Generic' Domain Names are Inappropriate for UDRP Complaints

A domain name that contains only a common or "dictionary" word (sometimes referred to as a "generic domain name" -- though not to be confused with a generic top-level domain) is often a poor candidate for a UDRP complaint, as decisions repeatedly remind us.

Here are some reasons why UDRP decisions involving a single, common word are won by the registrant. That is, the trademark owner who filed the complaint lost, and the registrant was allowed to retain the domain name.

The Complainant lacks trademark rights.

Example: In Inter123 Corporation v. Lawrence darwish / urbbana, NAF Claim No. 1557370, the Complainant argued that it tried unsuccessfully to purchase the disputed domain name <mobile.co> from the Respondent, and that the Respondent reneged after agreeing to sell it for $59,000. The Respondent said that the dispute was not appropriate for the UDRP and that "pending legal proceedings... involve the same issue."

The UDRP Panel found that the Complainant's trademark applications were only pending; were subject to "resistance" and chosen because they were "entirely apt to describe the character of the [Complainant's] services"; and that the Panel was "not able to conclude that Complainant has common law trademark rights." As a result, the Complainant failed the threshold requirement of every UDRP complaint.

The domain name doesn't target the Complainant.

Example: In Barium AB v. CDN Properties Incorporated, WIPO Case No. D2014-1541, the Complainant was a Swedish company that owned the domain name <barium.se>. The Respondent used the disputed domain name <barium.com> to "host[] advertising links" and in the UDRP proceeding referred to "the generic character of the word 'Barium' being a chemical element of the Mendeleev Periodic Table of Elements No. 56 with the 'Ba' code as well as the Latin name for the southern Italian city Bari."

In its decision, the UDRP panel said that it was "unable to find that the Respondent was aware of the [Complainant's] Trademark and/or the Complainant's business when it registered the disputed domain name" and that it was "also unable to find that the Respondent is trying to take advantage of the Trademark in order to draw traffic to its website, especially considering the fact that the disputed domain name does not appear to have been used to offer goods or services which are similar to or compete with the Complainant's services."

The Respondent's domain name registration predates the Complainant's trademark rights.

Example: In Kite Solutions, Inc. v. Brandon Abbey / Escrow.com, NAF Claim No. 1609855, the Complainant claimed that it owned a federal trademark registration for the word KITE for use in connection with "software as a service platform through which parties can identify opportunities to collaborate, find solutions, and implement advertising and marketing campaigns." The Respondent argued that it had registered the disputed domain name <kite.com> 20 years earlier and had been leasing it to an engineering company.

The UDRP panel found that the Respondent had rights or legitimate interests in the domain because "use of the KITE mark and the original registration of the domain name predate Complainant’s rights in the mark."

The dispute is outside the scope of the UDRP.

Example: In Insolvency Services Group, Inc., As Assignee for the Benefit of Creditors of BIDZ.COM, INC. v. Leon Kuperman / LGK Consulting, NAF Claim No. 1580768, the Complainant argued that the disputed domain name <bids.com> was confusingly similar to its "BIDZ.COM mark." The Respondent argued that the "dispute is outside the scope of the UDRP, involving a complex business history."

The UDRP panel, noting that even the Complainant had stated the dispute was with a former employee, said, "many issues have been raised which would require proof more suited to the thorough scrutiny afforded in litigation" and concluded that it was "a business dispute that falls outside the scope of the UDRP," allowing the Respondent to retain the domain name.

As these decisions demonstrate, a Complainant that wants to obtain a domain name containing only a single, common word may face numerous obstacles in a UDRP proceeding. Therefore, a Complainant would be wise to reconsider whether the UDRP process is appropriate for such a dispute.

8 Easy Ways to Protect Your Domain Name

A domain name can be one of a company's most valuable assets. So, whether you've been using your domain name for years or have just acquired it, you should obviously be sure to protect it -- to ensure that you don't lose it due to oversight, deception or illegal activity.

Here are eight simple things every domain name owner should do to protect itself online:

1. Be sure your domain name is registered to the property entity. Typically, a domain name containing a company's trademark should be registered to the same company that owns the trademark (or, at least a company licensed to use the trademark). Allowing an individual to register a company domain name in his or her own name is asking for trouble when the individual stops working at the company, becomes involved in a dispute with the company, etc.

2. Use a reputable registrar. Many large companies work with "corporate registrars" (such as MarkMonitor) that manage domain names excellently. But if you use a "retail registrar" (such as GoDaddy or Network Solutions), be sure to choose one that is well-known, has been in business a long time, is responsive to customers and, perhaps, located in your country. Saving a few dollars on a domain name registration is short-sighted if you need help later and can't get it -- or, if your registrar goes out of business.

3. Lock your domain name.  It's very easy to "lock" a domain name -- a simple setting typically found on a registrar's domain name management page -- and doing so prevents a domain name from being transferred to another registrant or registrar until the domain name is unlocked.

4. Use a strong registrar password and protect it diligently.  This should be treated with as much care as a password for an online bank account or any other highly sensitive website. Failing to do so could allow someone else to access your domain names -- which they could unlock and transfer behind your back.

5. Go ahead and register (or renew) your domain name for the longest period possible. Many domain names can be registered for up to 10 years, and doing so now makes it less likely that your domain name will lapse simply because you forgot to renew it.

6. While you're at, choose your registrar's "auto renew" option so your domain name registration should renew before it expires. Just be sure you always keep a current payment method (or two!), such as a credit card, on file; and update your payment information when your credit card expires.

7. Be smart about the contact information you provide in your registration, and keep it current. For example, consider using different contacts for the "registrant," "admin" and "tech" contacts, so your registrar will have multiple ways to reach you. And don't use an e-mail address containing the domain name that is the subject of the registration -- if there's a problem with the domain name, then your registrar might not be able to contact you at that e-mail address.

8. Be aware of domain name scams. Unfortunately, unscrupulous registrars and other bad guys online often try to trick domain name registrants into paying unnecessary fees or to transfer their domain names unknowingly. When in doubt, delete or ignore suspicious e-mails about domain names and contact your registrar directly with any questions or concerns.

Following these eight steps will help to avoid many of the problems that can arise with domain name registrations, eliminating costly (and sometimes fatal) disruptions in business.