Domain Names and Trade Marks: the UDRP and ccTLD Dispute Policies

A domain name and a trade mark are different things, registered through different systems for different purposes, yet for any brand owner they are tightly bound together. A domain name is an address on the internet, allocated on a first-come, first-served basis by registrars under the relevant registry. A trade mark is a legal right in a sign used to distinguish goods or services, granted by a national or regional office and enforced under that territory's law. Problems arise where the two collide, most commonly when a third party registers a domain that incorporates someone else's brand. This pillar explains that relationship: what cybersquatting is, how the Uniform Domain-Name Dispute-Resolution Policy (the UDRP) works for generic top-level domains, how country-code domains tend to run their own rules, and how brand owners sensibly protect their domains alongside their marks. It is general information, not legal advice, and because national rules and registry policies vary, the reliable step on any specific dispute is to check the relevant provider's published procedure or consult a vetted local firm.

How domain names and trade marks actually relate

The first point to be clear about is that registering a domain name does not give you trade mark rights, and holding a trade mark does not automatically give you the matching domain. They are parallel systems. A registry will generally hand out a domain to whoever asks for an available string, typically without checking whether it conflicts with anyone's brand. Trade mark offices, by contrast, examine applications and grant rights that are territorial and tied to particular classes of goods and services.

Because the domain system is largely automated and global while trade mark rights are examined and local, gaps open up. Two businesses with legitimate rights in the same word in different countries or sectors can both have a fair claim to a domain only one of them can hold. That is not abuse; it is the ordinary friction of a single global namespace sitting on top of many separate trade mark registers. The dispute mechanisms described below are designed to address bad-faith registration, not to resolve every genuine clash of competing honest interests.

It is also worth separating the layers of the domain itself. The part after the final dot is the top-level domain. Generic top-level domains (gTLDs), such as the common commercial extensions and the newer expanded set of strings, are one category. Country-code top-level domains (ccTLDs), the two-letter extensions assigned to territories, are another, and each is administered by its own national or regional registry under its own policy. This distinction matters a great deal for disputes, because most of the gTLD world is governed by a largely harmonised policy while the ccTLD world is not.

Cybersquatting and the related abuses

Cybersquatting, in broad terms, is registering or using a domain name that reflects someone else's trade mark in bad faith, typically to profit from the brand's reputation. The classic case is registering a well-known brand as a domain in order to sell it back to the owner at an inflated price. The same family of abuse includes several recognisable patterns.

Typosquatting targets predictable misspellings of a brand, capturing traffic from users who mistype an address. Combosquatting adds a generic or descriptive word to a brand to suggest an affiliation that does not exist. Some registrations exist purely to host pay-per-click advertising that trades on the brand's pull, and others are used to impersonate the brand for phishing or fraud, which is the most damaging variant because it harms the public as well as the brand owner. The common thread the dispute policies look for is a domain that takes unfair advantage of a trade mark, registered and used without a legitimate basis.

Not every overlap is cybersquatting. Genuine non-commercial commentary, legitimate resale, descriptive use, or a coincidental shared term can all give the registrant a defensible position. The dispute systems are built around testing exactly that distinction, which is why they turn on bad faith and the absence of any legitimate interest rather than on the mere fact of an overlap.

The UDRP for generic top-level domains

The Uniform Domain-Name Dispute-Resolution Policy is the central mechanism for the gTLD space. It was adopted by the Internet Corporation for Assigned Names and Numbers (ICANN), which requires its accredited registrars in most generic top-level domains to incorporate the policy as a condition of registration. Every registrant in those domains agrees to the policy as a condition of registration, which is what makes the system work without a court order: the registrar is bound to implement the outcome. Coverage is not universal, however, since some top-level domains operate adapted or supplementary procedures of their own, so the dependable course is to confirm against ICANN's current list of the domains subject to the UDRP rather than assuming it applies everywhere.

The UDRP is administered not by ICANN itself but by approved dispute-resolution providers. The WIPO Arbitration and Mediation Center was among the first providers approved when the policy launched and handles a large share of cases, but it is one of several. The current list of approved providers is published by ICANN and changes over time. A complaint is decided by an independent panellist or panel on the documents, without hearings in the ordinary case, which makes it markedly faster and cheaper than litigation. It is an administrative proceeding, not a court judgment, and it deals only with the domain; it does not award damages.

To succeed, a complainant generally has to establish three elements, all of which must be present.

The remedies available under the UDRP are limited but practical: the panel can order the domain to be transferred to the complainant or cancelled. It cannot order payment of money, and it does not prevent either party from going to court. Either party may take the matter to court, and where a registrant who has lost commences court proceedings within the period the policy allows, implementation of a transfer is stayed, so a UDRP outcome is best understood as a fast administrative remedy rather than a final adjudication of all rights. The exact length of that court-challenge window is fixed in the current UDRP Rules and can be amended by ICANN, so it should be checked there before relying on it. Because the precise procedural rules, time limits and provider practices are set out in the policy and the rules and can be refined over time, the dependable course is to read the current UDRP and the chosen provider's supplemental rules before filing rather than relying on a summary.

A useful body of decided cases has built up under the UDRP, and the leading providers publish guidance distilling how panels tend to approach recurring questions. That consistency is one of the system's strengths, though each case still turns on its own facts.

Country-code domains and their own dispute policies

The UDRP applies to most generic top-level domains. It does not automatically apply to country-code domains. Each ccTLD is run by its own registry, which sets its own registration rules and its own dispute policy, and these vary considerably from one territory to another.

Several patterns are common. Some ccTLD registries have voluntarily adopted the UDRP, so disputes in those extensions run on familiar lines. Others have adopted a close variant adapted to local law, sometimes administered by WIPO or by a national provider. A number operate an entirely bespoke national procedure with its own tests, its own forum, and its own remedies. And some impose local-presence or eligibility requirements at the registration stage, meaning a foreign brand owner may not be able to hold the domain directly at all without a qualifying local connection.

The practical consequence is that you cannot assume the route you used for a generic top-level domain will work, or work the same way, for a country-code one. The grounds, the evidence, the deadlines and the forum may all differ. For any ccTLD dispute the necessary first step is to identify the registry, read its published dispute policy, and where the local procedure or local-presence rules raise genuine nuance, take advice from a firm familiar with that jurisdiction. Our jurisdiction guides and the broader cross-border materials are a starting point, but the registry's own policy is the controlling document.

Protecting domains alongside trade marks

For a brand owner, domain protection works best as a planned part of overall brand protection rather than a reaction to a problem. A few durable principles hold across territories.

Register your core domains early, ideally before or alongside the trade mark filing, so the obvious addresses are secured before anyone else takes an interest. Beyond the primary domain, many owners take a defensive spread of the most important variants and country-code extensions for the markets that matter to them, balancing the cost of registration against the cost and disruption of a later dispute. There is no single correct breadth here; it is a commercial judgement about which markets and which abuse patterns are worth pre-empting.

A registered trade mark strengthens your hand considerably if a dispute does arise, because both the UDRP and most national policies require the complainant to show rights in a mark. Keeping renewals current, recording the registrant details accurately, and monitoring new registrations that echo your brand all help you act early, when a fast administrative remedy is still the proportionate response. ICANN's new gTLD programme also offers trade mark-based protective mechanisms, principally the Trademark Clearinghouse together with its Sunrise and Trademark Claims services: a centralised trade mark database supporting a priority registration window at launch (Sunrise) and a notification service that warns of later matching registrations (Claims). These are tied to the new gTLD programme, so their availability depends on active gTLD launches or rounds, and the details change. Confirm what is currently available and in scope with ICANN before relying on it.

Where international protection of the underlying mark is the priority, see our overview of the Madrid Protocol for the centralised filing route. How goods and services are categorised under the Nice Classification feeds directly into the trade mark rights a domain complaint depends on, and the marketplace and enforcement side of online brand protection sits alongside domain strategy; both are worth treating as part of the same plan.

Common pitfalls to plan around

A handful of issues recur often enough to flag. First, assuming the UDRP covers everything: it covers most generic top-level domains, and a country-code dispute may need an entirely different procedure, so identify the registry and its policy before you act. Second, leaving registration too late: once an abusive registrant holds the domain, recovery is slower and more expensive than securing it would have been, so the cheap protective registration is usually money well spent. Third, weak underlying rights: because the dispute tests turn on trade mark rights, an unregistered or thinly evidenced mark makes any complaint harder, which is one more reason to align the domain and trade mark strategies. Fourth, missing local deadlines and local-presence rules in ccTLDs, which can lose a domain in one territory while leaving the position intact elsewhere.

None of these is a reason to treat domains as an afterthought. They are reasons to plan the core registrations, the defensive spread, and the dispute route with the same care you give the trade mark itself, and to take local advice where a specific registry's rules genuinely diverge.

Key takeaways

Domain names and trade marks are separate rights that constantly intersect, and the friction between a single global namespace and many local trade mark registers is what creates cybersquatting and its relatives. For most generic top-level domains, the UDRP, administered through WIPO and other approved providers, gives brand owners a fast, document-based route to have an abusive domain transferred or cancelled, on proof of confusing similarity, no legitimate interest, and bad faith. Country-code domains run their own policies, which vary widely, so the controlling document is always the relevant registry's own procedure. The most reliable protection is to register core domains early, hold a registered mark, monitor for abuse, and route specific disputes to current provider rules or to local counsel. This is general information and not legal advice.