Do You Actually Own Your Domain? What ICANN Says

Someone was trying to sell their domain. The interested buyer had an attorney involved, the way buyers do when the domain has real value. The attorney asked a straightforward question: can you produce the title?

There is no title. There is no deed. There is a registration record at a registrar, which points back to a registry, which operates under an agreement with ICANN. The domain owner had no document that looked anything like ownership. They had a receipt from the year they registered it and a recurring annual charge on their credit card.

The buyer's attorney used the word "lease." The seller had never heard it described that way. They pushed back. They had registered it themselves. They had paid for it every year. They had never transferred it to anyone.

None of that makes it ownership. Not technically. Not legally.

Here's the thing most domain owners never encounter until they need to act on it: when you register a domain, you are not buying property. You are entering into a licensing agreement with a private intermediary, governed by rules set by a California nonprofit called ICANN. The terms of that agreement determine what you can do with the domain, when you can lose it, and who ultimately controls the rules.

What You Actually Signed

When you register a domain, you agree to at least two documents without usually reading either.

The first is your registrar's registration agreement. This is the contract between you and the company you paid. It covers renewal terms, acceptable use policies, dispute resolution procedures, and the registrar's rights to suspend or terminate your registration.

The second is ICANN's Registrant Rights and Responsibilities document, published in 2013. This document defines what registrants (that is, you) are entitled to and what you are obligated to do. It is the floor beneath your registrar's specific terms. Registrars must comply with it because they operate under ICANN accreditation. Without that accreditation, they cannot offer domain registrations.

Neither document uses the word "own" to describe what you get when you register. The language is "register," "hold," and "renew." You gain the exclusive right to use a domain name for the period you have paid for. That is a license. When the period expires and you do not renew, the license ends.

This is not a technicality buried in fine print to trap you. It reflects the fundamental architecture of how domain names work. There are a limited number of names. A central authority governs who can use which names. That authority cannot sell permanent, unconditional property rights in names it does not itself own in a property-law sense. ICANN manages a global naming system. It licenses access to that system through an accredited network of registrars.

The Three-Layer Structure (Registry, Registrar, Registrant)

Understanding what you actually have requires understanding the system you are operating inside.

The registry is the organization that runs a top-level domain. Verisign operates .com and .net. Public Interest Registry operates .org. Your country's relevant government or designated authority operates your country-code TLD. The registry is the authoritative database for every domain in its TLD. It is not your registrar. You have no direct relationship with the registry unless something goes wrong.

The registrar is the company you pay to register a domain. GoDaddy, Namecheap, Porkbun, Cloudflare Registrar, and thousands of others are ICANN-accredited registrars. They are access points to the registry system. They handle the registration transaction, maintain your contact information, and manage the channel through which you can make changes to your domain.

You are the registrant. You are the third layer. You interact with the registrar. The registrar interacts with the registry. You have no direct relationship with the registry, and no direct relationship with ICANN, except through the rules your registrar must follow because ICANN holds their accreditation.

This is why the answer to "do I own my domain?" depends on what you mean by "own." You have a registered name, the exclusive right to use it for the period paid, and the legal standing to defend against bad-faith challenges. What you do not have is a property deed, fee-simple title, or rights that survive the expiration of your registration agreement.

What ICANN's 2013 Registrant Rights Document Actually Says

ICANN's Registrant Rights and Responsibilities document was published in 2013 after years of advocacy by domain owner communities who felt the system treated registrants as afterthoughts. It established certain baseline protections.

You have the right to accurate and accessible information about your registrar's terms of service, fees, and policies. You have the right to transfer your domain to another registrar, subject to the transfer rules (including the 60-day lock provisions described in the companion article on how to transfer a domain without breaking everything). You have the right to receive advance notice before your domain expires. You have the right to accurate WHOIS information management.

You are also bound by responsibilities. You must provide accurate registration information. You must keep contact details current. You must not use the domain in violation of applicable laws or in bad-faith patterns that could trigger dispute proceedings.

The document does not grant ownership. It grants rights within a licensing framework. That is a specific and meaningful thing. But it is not what most people picture when they think about paying for something.

The UDRP: When Someone Else Claims Your Domain

The Uniform Domain-Name Dispute Resolution Policy, known as the UDRP, is one of the most significant practical implications of the registration-not-ownership structure.

If a third party believes you registered a domain in bad faith to exploit their trademark, they can file a UDRP complaint. An arbitration panel, not a court, reviews the claim. If the panel finds against you, your domain can be transferred to the complainant. You can appeal through national courts afterward, but the burden is on you.

The UDRP exists because domain names can create trademark conflicts in a way that physical property rarely does. A single string of characters can match a brand name in multiple countries, industries, or contexts. ICANN built an arbitration mechanism to resolve these conflicts without requiring national court proceedings in every case.

For most domain owners who registered names for legitimate purposes, the UDRP is not a daily concern. But it is a concrete illustration of the limits of "ownership." A panel of arbitrators can decide your registration should transfer to someone else. That is not something that happens with a house you own in fee simple.

There is a reason the research data shows 13.5% fear and 8.4% anger in conversations about domain ownership. The fear is often the UDRP. The anger is usually people who did not know this was possible until it happened to them or someone they know.

Can You Lose a Domain You Have Held for Years?

Yes. There are several mechanisms.

Expiration. If you do not renew, the license ends. The domain enters a grace period, then a redemption period, then becomes available for new registrations. Years of holding offer no protection once the renewal lapses.

UDRP decision. As described above, an arbitration panel can order a transfer if they find bad-faith registration or use.

Registrar dispute. If your registrar suspends your account for a terms-of-service violation, real or alleged, your domains may be suspended or locked while the dispute is resolved. This is distinct from a transfer. Your domain does not go away, but you cannot use it.

Registry policy changes. Country-code TLDs can change eligibility requirements. The Libya .ly example (where the government revised who could hold .ly domains) is a documented case. If you hold domains in country-code TLDs, you are subject to both the registry's rules and the relevant national authority's authority to revise those rules.

ICANN-accredited registrar failure. If your registrar loses accreditation or goes out of business, ICANN has escrow and transition protocols. These protect domains in principle. In practice, the transition period can be disruptive. Details on how this plays out are in the article on what happens when a registrar shuts down.

None of this means your domain is insecure if you manage it attentively. It means the security comes from the relationship you maintain with the registration system, not from a deed you hold.

Why "Stewardship" Is the More Accurate Mental Model

Here is the reframe that changes how you think about this.

If you do not own your domain in the property-law sense, but you can hold it indefinitely as long as you comply with applicable rules and renew consistently, then the useful mental model is stewardship, not ownership.

A steward manages something of value on behalf of an ongoing relationship. The steward's rights are real. The protections are real. The ability to use and direct the asset is real. But the steward understands that the rights come with responsibilities and operate inside a framework they did not create and cannot unilaterally change.

This is actually how domain management works in practice for anyone who has held domains for a long time. You maintain contact information. You renew. You monitor for disputes. You understand the rules of the TLDs you operate in. You build something on the name that creates value regardless of the registration framework.

Domains are infrastructure. Infrastructure is leased or licensed, not owned outright, more often than we like to admit. Your office space is leased. Your software is licensed. Your domain is registered, which is its own version of the same basic structure.

Shifting from "I own this" to "I steward this" does not diminish the value of the domain or your rights to it. It makes your relationship to it more accurate. And more accurate is more useful when something goes wrong and you need to know what leverage you actually have.

For a longer treatment of this reframe and why it matters for how you build on domains over time, read From Ownership to Stewardship and Domains Are Infrastructure, Not Lottery Tickets.

What This Means Practically

None of this is meant to alarm you. Most domain owners who register names for legitimate purposes, renew consistently, and use their domains for the purposes they registered them for will never encounter the edge cases described above. The framework mostly works.

But there are practical implications worth holding.

You cannot bequeath a domain the way you bequeath property. Domain transfers at death require navigating the registrar's process, which varies. Some registrars handle this better than others. Planning for this now, if the domain has meaningful value to your estate, is worth doing.

You cannot use a domain as collateral in the same way as physical property. Some registrars and specialty lenders have developed domain-backed lending, but the structures are complex specifically because registration is not ownership.

You can be a responsible steward, build significant value on a name, and still be subject to an arbitration process that could transfer it if a trademark dispute arises. Registering defensively, understanding UDRP exposure for names that could intersect with existing marks, is reasonable risk management.

And: the registrar you choose matters more than most domain owners realize. They are the intermediary between you and the registry. Their policies, their practices during disputes, their transfer processes when you want to leave. All of it shapes how easy or hard it is to exercise the rights you do have.

The independent analysis of which registrars actually operate in registrants' interests is in Best Domain Registrars for Long-Term Ownership in 2026. The question of what happens when a registrar operates against your interests is the subject of Can Your Registrar Hold Your Domain Hostage.

The underlying architecture of trust as a system starts here: with an honest understanding of what you hold, what you do not, and how the framework you operate inside actually works.

To understand the practical mechanics of moving a domain when you need to, the step-by-step transfer guide is at How to Transfer a Domain Without Breaking Everything. For the registrar relationship in its hardest form, Can Your Registrar Hold Your Domain Hostage covers what happens when the intermediary stops acting in your interest.