DotCooperation and the price of keeping .coop credible

Summary

• DotCooperation LLC is worth judging from a renewal counter, not from an abstract list of top-level domains. A cooperative that can keep a cheaper .org, .com or local country-code address still has to decide whether .coop earns its premium by making cooperative identity more credible, more searchable and harder to fake.
• The strongest evidence for DotCooperation is institutional. IANA lists DotCooperation LLC as the .coop sponsoring organisation, with Tucows.com, Co. as the technical contact, Tucows Registry Services name servers, whois.nic.coop and an RDAP endpoint at https://rdap.registry.coop/rdap/. ICANN's 2024 sponsored registry agreement names DotCooperation as the sole registry operator and preserves the sponsored purpose for cooperatives.
• The main pricing proxies show a small, high-touch namespace. DotCooperation says more than 4,500 cooperative organizations in 95 countries have bought about 9,000 .coop names; ICANN's October 2025 monthly transaction report lists 8,645 total domains, 53 attempted adds, 425 one-year net renewals and 50 grace-period deletes; 101domain listed .coop at USD 89.49 registration and USD 99.99 renewal, Netim listed EUR 78 renewal, and EuroDNS listed EUR 162 registration and renewal.
• The cost base is not only DNS. DotCooperation has to maintain ICANN compliance, data escrow, monthly reporting, RDAP and WHOIS service, DNSSEC-capable delegation, registrar contracts, backend dependence on Tucows, abuse handling, eligibility verification and community-facing policy work. Its 2026 verification policy says verification cost is included in .coop registration pricing, but the registrant bears document-submission costs.
• The weak point is scale. A namespace near 9,000 names cannot spread verification, policy, backend, reporting, support and marketing overhead the way open commercial namespaces do. The same restriction that protects credibility also limits speculative demand, registrar enthusiasm and impulse registrations.
• Network and DNS records prove delegation, public lookup surfaces and technical dependency, not operator security outcomes. The fact that .coop has DNSSEC keys, RDAP responses and Tucows-operated name servers does not prove that every .coop registrant runs secure mail, safe web hosting or clean customer systems.
• The judgement would change if .coop showed sustained registration growth without weakening eligibility, a clear drop in renewal friction, broader active registrar availability, lower verified retail prices, transparent abuse-volume evidence, or cooperative-sector adoption by large visible organizations that made .coop a normal primary address rather than a trust badge used by a minority.

The renewal is really a vote on credibility

Start with a cooperative whose board is reviewing the annual domain bill. The organization already has a working website, a mail domain that members recognize, search results that point to the right place, and perhaps a national country-code address that local customers understand. The .coop renewal is the awkward line item. It is visibly more expensive than many ordinary domains. It may require staff to remember eligibility documents and registry policy. It may not be stocked by every cheap registrar the organization already uses. The question is not whether the letters are attractive. The question is whether the letters still make trust cheaper.

That is the right unit for DotCooperation LLC. The company does not sell a mass-market namespace in the same way .com sells familiarity or .org sells a broad nonprofit feel. DotCooperation sells a narrower promise: if a user sees a .coop address, the name should belong to a cooperative or an organization whose work is principally tied to cooperatives. That promise is valuable only if someone believes it. Belief depends on eligibility checking, transparent policy, working registration data services, abuse response, registrar access and enough visible adoption that the address does not look abandoned.

DotCooperation's own public description frames the bargain this way. Its .coop page says the domain is reserved for cooperatives and supporting organizations, that it is restricted to verified cooperatives, and that this exclusivity helps visitors recognize an organization as a genuine cooperative: https://identity.coop/the_dotcoop_domain/. The page also says a .coop registration automatically places the registrant on the Cooperative World Map. The marketing claim is simple, but the economics are not. A restricted namespace costs more to run per domain because every registration asks a human and institutional question that an open namespace avoids: who is this registrant, and does the registrant belong here?

That makes DotCooperation a small infrastructure trust business. It has a contract with ICANN, public root-zone responsibilities, registry-service obligations and a community-facing mission. It also owns Domains.coop, a registrar, while managing a network of retail partners. Its about page says DotCooperation was formed in 2001 by NCBA CLUSA as a subsidiary and became jointly owned by NCBA CLUSA and the International Cooperative Alliance in 2012: https://identity.coop/about-us/. The same page says DotCooperation is the registry of .coop and .creditunion, owns Domains.coop, and works through ICANN-accredited retail partners.

The renewal decision therefore has three layers. The first is identity: a .coop name says the registrant is part of the cooperative movement. The second is distribution: a cooperative must be able to buy, renew, transfer and manage the name through real registrars without turning the process into a niche procurement exercise. The third is discipline: DotCooperation has to keep the namespace restricted enough that the signal does not degrade. If any one layer fails, the renewal premium becomes hard to defend.

The hard part is that all three layers cut against easy growth. Open eligibility would sell more names but weaken the trust signal. Higher verification standards protect the signal but add friction. More registrars improve access but require registrar education. Lower prices could widen adoption but may not cover a high-touch cost base. DotCooperation's job is to keep that balance visible enough that a cooperative treasurer understands why .coop is not priced like a disposable defensive registration.

What DotCooperation actually controls

IANA's root-zone record is the cleanest identity anchor. It lists DotCooperation LLC at 1775 I Street NW in Washington, DC as the sponsoring organisation for .coop, lists Violetta Nafpaktiti at DotCooperation as administrative contact, lists Tucows.com, Co. in Toronto as technical contact, names Tucows Registry Services name servers, and gives whois.nic.coop plus https://rdap.registry.coop/rdap/ as registration data services: https://www.iana.org/domains/root/db/coop.html. The record was last updated on 2026-03-10 and shows a registration date of 2001-12-15. That is not a branding page. It is the public delegation record.

The historical IANA report explains why this structure matters. The 2001 report says ICANN selected a small number of initial new top-level domains after a controlled expansion process, and that .coop was a sponsored top-level domain with DotCooperation LLC delegated authority to develop policies governing eligibility within the .coop TLD: https://www.iana.org/reports/2001/coop-report-13dec01.html. In other words, .coop was designed from the start as a community namespace, not an open inventory pool.

ICANN's current sponsored registry agreement preserves that model. The 2024 agreement says the TLD was delegated in 2002 for cooperatives and cooperative organizations under a sponsored charter approved by the National Cooperative Business Association, and that ICANN designates DotCooperation as the sole registry operator for .coop: https://www.icann.org/en/registry-agreements/details/coop. It also says DotCooperation must develop and enforce policies in a way that gives members of the TLD community opportunities to discuss and participate in the policy process. That is a public-interest burden as well as a public-interest asset.

This is why DotCooperation should not be analyzed as a domain reseller with a nice mission statement. It is a registry sponsor with a delegated policy role. It must provide the technical and administrative functions of a registry while preserving a narrower community promise. The value proposition is not only "buy a domain." It is "buy a domain in a namespace where the sponsor has accepted responsibility for keeping eligibility meaningful."

The eligibility page states the operating rule in plain language. .coop is restricted to cooperatives and other relevant support organizations meeting .coop criteria, and the primary eligibility categories include democratically controlled member-owned cooperatives, associations made up of cooperatives, organizations majority controlled by a cooperative, and entities whose operations or practice area are principally dedicated to serving cooperatives: https://identity.coop/policies/eligibility-policy/. The page also says all organizations must provide proof and that DotCooperation conducts audits and reserves the right to cancel or modify a domain name under its policies.

That restriction is the product. If anyone could buy .coop without proof, the address would become a slogan. If the rules are too slow or unpredictable, legitimate cooperatives will avoid the name. The registry has to sell trust while making that trust operationally tolerable.

Verification is part of the price

The 2026 verification policy turns the renewal question into an operating process. It says .coop is available only to cooperatives and organizations meeting eligibility criteria, and that DotCooperation is required by its ICANN contract to ensure registrants meet those criteria: https://identity.coop/wp-content/uploads/2026/02/Verification-policy-01.26-final.pdf. It also states that verification is the process of assuring that organizations registering and using a .coop domain name are eligible. This is not optional back-office decoration. It is how the namespace defends its meaning.

The policy lists proof types. A cooperative may show membership in a national or sectoral apex organization, governance documents such as bylaws that show democratic control and member ownership, or corporate filings showing formation as a cooperative under local law. A cooperative still forming may provide draft governance documents or incorporation filings, but the policy says DotCooperation will ask for status updates every six months. Associations of cooperatives, cooperative-controlled organizations and service organizations have their own proof routes. The verification burden therefore varies by registrant type and jurisdiction.

The pricing implication is explicit. The policy says the cost of verification is included in the cost of .coop domain registrations, while DotCooperation will not pay charges incurred by the registrant when sending documents or material to prove eligibility. That means the registrar price contains more than registry database entry and DNS delegation. It has to carry a verification function, community knowledge and exceptions work. It also means the registrant still faces non-cash friction: staff time, documents, delayed activation risk and uncertainty if eligibility is hard to prove.

The process adds teeth. The 2026 policy says verification starts as soon as a .coop domain is registered and the registrant is asked to provide documentation within two days. If eligibility is not confirmed, DotCooperation sends another request and gives 30 days. If there is no response within that period, the domain is placed under serverHold, preventing DNS resolution. If DotCooperation determines the registrant is ineligible and the registrant does not dispute the decision within 10 calendar days, the status becomes refused and the names are revoked with no refund of registration fees. That is a serious control system.

This is exactly why a cooperative should ask whether .coop is worth renewing. The answer cannot be "because it is cheap." It is not trying to be cheap. The answer must be that the verification cost creates a public signal other domains cannot copy. A cooperative that uses .org may still be a genuine cooperative, but .org does not itself say that a sponsor has checked cooperative eligibility. A local country-code name may be excellent for national reach, but it usually does not carry a movement-wide cooperative credential. A .com name may be familiar, but it is open to anyone.

That does not make .coop automatically superior. Many real cooperatives will choose a local domain for customer trust, a .com for search familiarity, or .org for nonprofit recognition. But if DotCooperation's verification process is credible and manageable, .coop can be a compact trust badge in the address itself. If the process becomes slow, obscure or expensive relative to the benefit, the same verification function becomes a renewal tax.

The small scale is visible in the registry reports

The public monthly registry reports show how narrow the business really is. ICANN's October 2025 .coop transaction report lists 8,645 total domains across registrars: https://www.icann.org/sites/default/files/mrr/coop/coop-transactions-202510-en.csv. DotCooperation's own about page says more than 4,500 cooperative organizations from 95 countries have purchased about 9,000 .coop domain names: https://identity.coop/about-us/. Those numbers are close enough to tell the same story. This is a global identity namespace, but it is tiny by commercial domain standards.

The same October 2025 transaction report shows a renewal-heavy pattern. It lists 53 attempted adds, 35 one-year net adds, five two-year net adds, five three-year net adds, three five-year net adds, 425 one-year net renewals, 54 two-year net renewals, 10 three-year net renewals, 50 deleted domains in grace and two deleted domains without grace. That is not a land-rush profile. It looks like a mature niche namespace in which existing holders matter more than new speculative demand.

Registrar concentration is also visible. In October 2025, Domains.coop Limited held 3,885 of the 8,645 listed total domains, or about 44.9%. EnCirca held 1,318, Gandi held 854 and Ascio held 782. The top four together held about 79.1% of listed domains. Add 101domain with 417 and Soluciones Corporativas with 328, and the top six held about 87.7%. ICANN's activity report for the same month lists 163 operational registrars, but the transaction report shows that real volume is concentrated in a much smaller channel set: https://www.icann.org/sites/default/files/mrr/coop/coop-activity-202510-en.csv.

That matters for market power. A cooperative may theoretically be able to register .coop through many ICANN-accredited registrars, but the practical retail experience depends on whether the registrar carries .coop, understands eligibility, can explain verification, prices renewals clearly and can handle transfers without losing the cooperative customer in a generic support queue. DotCooperation's registrar page says an ICANN-accredited registrar can become a .coop registrar at no charge, but should check contract terms with the backend operator Tucows because it may need to maintain a deposit account: https://identity.coop/for-registrars/. The page also says DotCooperation staff manage verification directly and registrars should understand when to activate or delete a .coop registration upon verification or failure to verify.

The public service load is not zero just because the namespace is small. ICANN's October 2025 activity CSV reports 8,223,809 port-43 WHOIS queries, 86 web WHOIS queries, 1,211,098 RDAP queries, 419,089,865 DNS UDP queries received and the same number responded, plus 4,338,553 DNS TCP queries received and responded. These are point-in-time report fields, not a measure of human demand. Automated lookups can overwhelm ordinary user interest. But they show that even a small TLD has to operate public lookup and DNS surfaces at internet scale.

This is the central economic tension. The revenue base is small; the public service obligations are not proportionately small. Data escrow, RDAP, DNS, registrar support, policy maintenance and abuse handling still have to exist. A .coop name therefore cannot be priced only against the marginal cost of a database row. It has to carry the overhead of a small, restricted, globally visible registry.

Retail prices expose the trust premium

Retail pricing shows how the renewal feels to a cooperative buyer. 101domain listed .coop registration at USD 89.49 per year and renewal at USD 99.99 per year, with information updated on 2026-06-12: https://www.101domain.com/coop.htm. Netim listed .coop registration and renewal at EUR 78 per year excluding VAT, transfer at EUR 56.50 and restoration at EUR 98.50: https://www.netim.com/en/domain-name/coop-domain. EuroDNS listed .coop annual and renewal fees at EUR 162, transfer at EUR 162 with a one-year extension included, and reactivation at EUR 25 plus the renewal fee: https://www.eurodns.com/domain-extensions/coop-domain-registration. TLD-List, an aggregator rather than a registrar, showed a spread from around USD 70 registration to higher renewal prices, with Gandi listed at USD 78 registration and USD 167.98 renewal in its table: https://tld-list.com/tld/coop.

These prices are not identical because registrars set their own retail margins, currencies, bundles and promotions. But the pattern is clear. .coop is not a USD 10 commodity. It is a high-double-digit to triple-digit annual commitment before staff time, hosting, email, security certificates, redirects and brand migration. The comparison becomes sharper on EuroDNS's page, which displayed .org alternatives at a promotional EUR 8.30 per year against a regular EUR 25 and other community-flavored alternatives below .coop's EUR 162 annual fee. A cooperative does not need a finance department to notice the gap.

The gap can be rational. Restricted eligibility is not free. DotCooperation includes verification cost in registration pricing. A small namespace cannot amortize overhead across millions of names. Tucows backend services, ICANN compliance, public registration data service, DNSSEC-capable infrastructure, dispute handling, registrar education and abuse response all have to be funded. The problem is not that .coop costs more. The problem is whether the cooperative can see the benefit clearly enough to keep paying.

The October 2025 ICANN numbers make the revenue logic more concrete. If the active namespace is about 8,645 names and retail renewals cluster in the USD 80 to USD 160 range depending on registrar, then the gross retail market is modest. Even a rough retail multiplication produces a small global pool before registrar margins, backend costs, ICANN fees, verification labor and DotCooperation's own policy and community costs. This is not a hidden hyperscale domain business. It is a narrow identity system that has to preserve margin without making the badge too expensive for small cooperatives.

ICANN fees add a useful floor. The 2024 sponsored registry agreement says the fixed annual registry-level fee is USD 500 if there are fewer than 5,000 registered names and USD 5,000 if there are at least 5,000 but fewer than 50,000 registered names. If the registry reaches 50,000 or more names, a registry-level transaction fee of USD 0.75 applies for each annual increment of an initial or renewal registration during the quarter. The agreement also describes a variable registry-level fee with a transactional component that shall not exceed USD 0.25. These are not the main cost of running .coop at its present scale, but they show the compliance framework and the way registry size changes the fee model.

The interesting threshold is 50,000 names. .coop is far below it. If DotCooperation grew from about 9,000 names to 50,000 without weakening eligibility, it would have more revenue capacity but also a different ICANN fee profile and a larger verification burden. If it stays near 9,000, the value proposition must come from strong renewal retention and a visible trust premium rather than volume.

Backend dependence is a feature and a vulnerability

DotCooperation does not appear to operate every technical layer by itself. IANA lists Tucows.com, Co. as the technical contact and the .coop delegation uses Tucows Registry Services name servers. The .coop registrar page says the registry service provider is Tucows Registry Services and that registrars may use login credentials for the .coop portion of Tucows' portal: https://identity.coop/for-registrars/. A live RDAP query for identity.coop on 2026-07-05 returned an ICANN-profile RDAP response whose notice said the data is provided by Tucows Registry and that Tucows Registry is authoritative for WHOIS information in top-level domains it operates under contract with ICANN.

This dependence is not suspicious. Small registries often use specialized backend providers because registry operation requires systems, security, escrow, EPP, RDAP, WHOIS, DNS, monitoring, reporting and continuity capabilities that are expensive to build from scratch. For DotCooperation, the question is whether outsourcing lets it focus on eligibility, community policy and registrar education while using a competent technical provider. The answer looks structurally sensible.

It still creates bargaining and continuity risk. Backend pricing is not publicly disclosed in the pages reviewed. Contract terms, service-level commitments, deposit requirements and switching costs are private. If backend costs rise, DotCooperation has limited scale to absorb them. If backend service quality weakens, the cooperative identity mission does not matter to resolvers, registrars or registrants who need reliable systems. If DotCooperation ever had to change backend provider, registrars, RDAP endpoints, reporting processes and technical operations would need careful transition.

ICANN's agreement anticipates continuity risk at a general level. It requires data escrow, monthly reporting, registry performance specifications and emergency transition arrangements. The agreement says ICANN may designate an emergency interim registry operator if emergency thresholds for registry functions are reached, and that DotCooperation must provide data needed to maintain operations. This is the kind of clause no ordinary registrant wants to think about. But for a restricted registry, it is part of the credibility bundle.

The DNS evidence should be read with care. IANA lists name servers at ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info and ns10.trs-dns.org with IPv4 and IPv6 addresses. A local DNS query on 2026-07-05 returned the same TRS-DNS name-server names for the .coop apex, and a DNSSEC query returned DNSKEY records using algorithm 13. These records show the public delegation and DNSSEC-capable surface. They do not prove that every .coop domain is signed, that every registrant uses safe hosting, or that DotCooperation has no abuse exposure.

DotCooperation's own public website also shows ordinary third-party dependencies. A DNS check on 2026-07-05 returned ns1.blacknight.com and ns2.blacknight.com for identity.coop, Microsoft 365 mail protection for MX, and TXT records referencing Microsoft verification, Sendinblue, FogBugz, Sendinblue SPF handling and specific IPs. That is not a negative finding. It is a reminder that even the sponsor's public-facing identity service depends on outside mail, hosting and service providers. The trust product is governance and operation, not full-stack self-sufficiency.

Abuse control is necessary, but public evidence has limits

For a restricted namespace, abuse control is not only a security function. It is brand protection. If .coop becomes a phishing or spam surface, the damage is not limited to affected victims. It weakens the idea that .coop means cooperative legitimacy.

The contractual obligation is stronger than a voluntary statement. ICANN's 2024 agreement requires DotCooperation to publish an abuse contact and handle reports related to malicious conduct, including DNS Abuse. The agreement defines DNS Abuse by reference to malware, botnets, phishing, pharming and spam when spam serves as a delivery mechanism for those other forms. It also requires the registry operator, where it reasonably determines based on actionable evidence that a domain is being used for DNS Abuse, to take timely mitigation action reasonably necessary to help stop or disrupt the abuse, including referral to the sponsoring registrar or direct action where appropriate.

DotCooperation's own anti-abuse policy gives the registry broad operational discretion. The policy says all .coop names are subject to the policy and that the registry may cancel, lock, hold, delete or otherwise act on names to protect DNS integrity, comply with court orders or law-enforcement requests, avoid liability, respond to malware, comply with internet-stability specifications, comply with the .coop charter or comply with Delaware and other applicable law: https://identity.coop/policies-and-agreements/. The policy prohibits malware, botnets, phishing, piracy, deceptive practices, impersonation, unsolicited advertising, viruses, unauthorized mail relay, email harvesting and other harmful conduct.

This is the right policy posture, but public readers should not confuse policy with measured outcomes. The ICANN monthly reports used here do not publish a clean .coop abuse volume count. The activity report publishes lookup and DNS traffic and registrar operations; the transaction report publishes domain counts, renewals, transfers and deletes. Those are useful operational indicators, not abuse-rate metrics. Without transparent per-TLD abuse statistics from DotCooperation or an independent measurement body, the public can judge obligations and response tools more easily than outcomes.

The small size of .coop helps and hurts. A small, verified namespace should be less attractive to automated mass abuse than cheap open TLDs because attackers must overcome price, eligibility and review friction. But a small namespace also has limited staff and budget. A single high-profile abuse incident could carry more reputational weight because the trust claim is narrower. DotCooperation cannot rely on obscurity. It has to show that the same verification process that protects eligibility also supports quick response when a verified registrant is compromised or when a bad registrant slips through.

RDAP accountability is part of that response system. IANA lists the RDAP server, and the identity.coop RDAP query returned a redacted but structured response with registration, expiration, last-changed and registrar information, plus an abuse contact attached to the registrar. Redaction is normal under modern registration data policy. The key issue is whether legitimate reporters can reach the right registrar and registry channels quickly. In a cooperative namespace, the expected user is not a professional abuse desk at a hyperscale platform. It may be a member, customer, local cooperative federation or small business that has seen a suspicious page. Accessibility matters.

The cooperative market is large, but the reachable domain market is not

The cooperative movement is not small. The International Cooperative Alliance says cooperatives have more than 12% of humanity as members and that the largest 300 cooperatives and mutuals report total turnover of USD 2.4 trillion: https://ica.coop/en/cooperatives/facts-and-figures. DotCooperation's registrar page says the global cooperative community comprises more than 1 billion members: https://identity.coop/for-registrars/. On paper, that is an enormous identity market.

But a billion cooperative members do not translate into a billion domain registrations. Most members never choose the organization's domain. Many cooperatives are tiny. Many operate locally, in languages and jurisdictions where a country-code domain is more natural. Large cooperatives may have decades of brand equity in .com, .org or country-code addresses. Credit unions have their own specialized naming issues. Agricultural, retail, housing, worker and platform cooperatives have different customer audiences. A cooperative may support the movement and still decide that its primary customer address should be local, short and familiar.

DotCooperation's own adoption numbers make the gap visible. More than 4,500 organizations in 95 countries and about 9,000 names is real global reach, but it is a small fraction of the cooperative universe. That does not mean failure. It means .coop is a selective credential rather than the default address of the movement. The commercial task is to make that credential worth keeping.

This explains why .coop's competition is not only other restricted domains. The real competitors are the domains that cooperatives already use. A grocery cooperative may want a short national retail address. A credit union may choose a .com name because members use mobile banking and call centers built around the brand. A housing cooperative may use a city or country-code domain because residents search locally. An advocacy cooperative may prefer .org because donors and policy readers understand it. A platform cooperative may want .io, .app or .com because users think in product terms rather than governance terms.

The advantage of .coop is that it says something those addresses do not. The disadvantage is that it may say it to fewer people. If customers do not recognize .coop, the organization must explain the address. If staff must maintain both a legacy domain and a .coop domain, .coop becomes an additional domain rather than the primary identity. DotCooperation's .coop page tries to lower that barrier by saying organizations can use both domains to address their website: https://identity.coop/the_dotcoop_domain/. That is practical, but it also admits the reality: for many cooperatives, .coop may be a trust layer beside another address, not the whole digital identity.

The renewal value is strongest when the cooperative identity itself is a sales, membership or legitimacy asset. A worker cooperative, community finance organization, cooperative federation, fair-trade group or cooperative support provider may gain real clarity from .coop. A local retail cooperative whose customers already know the store may get less incremental value. DotCooperation has to serve both without pretending their needs are identical.

Registrar availability is a distribution test

DotCooperation's registrar economics are unusual because the registry must preserve eligibility while still letting registrars sell. Its registrar page says there is no charge for an already ICANN-accredited registrar to become a .coop registrar, but the registrar should check backend-operator terms and may need a deposit account with Tucows: https://identity.coop/for-registrars/. It also says registrars should familiarize themselves with verification because DotCooperation staff manage verification directly.

That design lowers the formal entry fee but does not eliminate the practical cost. A registrar must support a restricted product, explain eligibility, handle activation questions, deal with customers whose domains may be held for non-response, and decide whether the expected volume justifies product maintenance. For a registrar that sells high-volume open TLDs, .coop can look like a support-heavy SKU. For DotCooperation, registrar education is part of distribution cost.

The ICANN reports show the difference between formal and practical availability. October 2025 activity data says there were 163 operational registrars, while the transaction report shows most domains concentrated in a handful of names. That may be efficient for a niche registry, but it creates channel dependence. If the top registrar has service issues, pricing changes or strategic drift, a large share of the namespace feels it. If smaller registrars stop actively promoting .coop, new demand may not see the option.

Retail price variation reinforces the point. A cooperative checking three registrars can see USD 99.99 renewal at 101domain, EUR 78 at Netim and EUR 162 at EuroDNS. TLD-List shows an even wider market spread. The same registry promise can therefore feel moderately expensive, very expensive or confusing depending on the registrar. In an open namespace, shoppers may be used to hunting prices. In a restricted namespace, the buyer may be a cooperative administrator who simply needs a dependable renewal. Price opacity or variation can become friction.

Transfers are another test. EuroDNS says transfer costs EUR 162 with a one-year extension included. Netim says transfer is EUR 56.50 excluding VAT and then EUR 78 per year. 101domain lists transfer at USD 89.49 per year. These are not inherently unreasonable, but they matter because a cooperative that dislikes its registrar may compare the transfer cost against simply keeping a cheaper legacy domain elsewhere. DotCooperation's trust premium survives only if the registrar experience feels orderly.

The best sign would be broader active retail support without weakened verification. The worst sign would be a namespace that is technically available through many registrars but practically served by a narrow set with uneven pricing and limited customer education. DotCooperation's public reports currently point closer to the second pattern than the first, though a niche registry may not need mass registrar promotion to function well.

The regulatory bargain is stable until it is not

The 2024 ICANN agreement gives DotCooperation a stable authority framework, but stability is not the same as freedom from risk. DotCooperation must comply with consensus policies, temporary policies, registry data escrow, monthly reporting, registration data publication services, registry performance specifications, public interest commitments and abuse obligations. It also has community obligations around policy development. These requirements are the price of being a delegated registry sponsor.

At current scale, the ICANN annual fixed registry-level fee is modest: USD 5,000 for a TLD with at least 5,000 and fewer than 50,000 registered names. But compliance cost is not just the fee. The registry still needs systems and people to meet the agreement. It must produce monthly reports within the required time. It must preserve data escrow. It must operate RDAP and WHOIS service according to current policy. It must maintain accurate IANA data. It must coordinate with backend and registrar partners. It must handle abuse reports and eligibility disputes. The cost is organizational, not only contractual.

The regulatory risk is that the burden changes faster than the revenue base. Registration data policy has already shifted from old public WHOIS norms toward RDAP and redacted data. Abuse obligations have become more explicit. Security expectations rise. If ICANN or law-enforcement pressure increases around abuse response, even clean restricted registries must document more. If privacy rules change, registration data workflows change. If a registry backend consolidates or reprices services, small sponsored namespaces have less bargaining room.

There is also legitimacy risk inside the cooperative community. The 2024 agreement says DotCooperation must maintain the representativeness of policy development and provide opportunities for community participation. A cooperative namespace cannot be credible if policy appears detached from cooperatives. DotCooperation's ownership by NCBA CLUSA and the International Cooperative Alliance helps because those organizations are movement institutions. But ownership does not replace daily trust. Eligibility decisions, reserved-name choices, dispute handling and verification standards must feel fair across countries, languages, legal forms and cooperative traditions.

The 2026 verification policy acknowledges that cooperative legal frameworks vary across the world and that DotCooperation uses ICA activities, policies and cooperative-identity guidance when reviewing cooperative registrants. That is necessary, but it also gives the registry judgment calls. A worker cooperative, producer cooperative, cooperative-controlled subsidiary, apex body and service organization do not all prove themselves the same way. The risk is not only that bad actors get in. It is also that legitimate organizations in less familiar jurisdictions face more friction.

The renewal decision therefore includes a governance bet. A cooperative pays for .coop because it trusts DotCooperation to keep the boundary meaningful and fair. If that trust weakens, the domain becomes a narrow address with an expensive renewal. If it strengthens, the renewal becomes a contribution to a shared digital identity system.

Unofficial market signals are cautious, not enthusiastic

The domain market does not treat every TLD equally. Open, cheap, broadly recognized extensions attract speculation, defensive portfolios and mass registrar promotion. Restricted, verified, mission-specific extensions attract a different pattern: fewer names, higher unit prices, less aftermarket excitement and more dependence on end-user conviction.

.coop fits the second pattern. TLD-List shows only 18 registrars in its retail price table and a wide spread of registration and renewal prices: https://tld-list.com/tld/coop. ICANN's October 2025 transaction report shows a small renewal-heavy namespace with 8,645 total domains. DotCooperation's own page says about 9,000 names across more than 4,500 cooperative organizations. These are not signs of a speculative gold rush. They are signs of a small community namespace where the name has to be bought for use, not resale.

That is probably healthy. A restricted cooperative namespace should not depend on domain investors. If .coop became attractive primarily as speculation, eligibility would be under pressure. The better unofficial signal is whether cooperative organizations actually use .coop as a live address and whether registrars can explain it without burying the restrictions. Retail pages from 101domain, EuroDNS, Netim and INWX all describe restrictions, DNSSEC support or cooperative use in some form. That is good. The less good signal is that prices and process details vary widely enough that a casual buyer may not know what the normal renewal price should be.

There is also an aftermarket problem. The stronger a domain becomes as an identity badge, the more valuable short or category names become. The eligibility and domain-name category policies can help control that problem, but they also add policy work. Reserved or premium names may be necessary for fairness, but opaque allocation would harm trust. DotCooperation's value rises if cooperatives believe important names are handled for the movement rather than quietly captured by whoever pays first.

The best unofficial signal would be visible primary use by cooperatives whose members already trust the cooperative model. The .coop page says active domain holders are placed on the Cooperative World Map, and DotCooperation maintains stories.coop as part of its community presence. The point is not traffic for its own sake. It is repetition. If members, customers and employees see .coop often enough on real cooperative services, the renewal premium becomes easier to explain. If .coop remains a secondary redirect for many organizations, the renewal has to be justified as a badge rather than a primary customer channel.

What would change the judgement

Several facts would change the view of DotCooperation quickly. The first is growth quality. A sustained rise from about 9,000 names toward a much larger base would improve overhead absorption, but only if eligibility remains strict. Growth by relaxing verification would be a false positive. Growth by bringing more genuine cooperatives into active primary use would be the strongest positive signal.

The second is renewal behavior. October 2025 shows many more renewals than attempted adds, which is normal for a mature niche. If renewals stayed strong despite high prices, it would suggest that existing cooperatives see value. If deletes and non-renewals rose while adds stayed low, it would suggest the premium is losing force. A clearer public retention metric would help outside observers distinguish loyalty from inertia.

The third is registrar health. A broader active registrar base with clear pricing and competent eligibility support would make .coop easier to buy and keep. Concentration in Domains.coop may be natural because the registry owns that registrar and understands the community. But channel resilience improves if several independent registrars actively serve cooperatives well.

The fourth is abuse evidence. The contract and policy posture are strong, but public abuse-volume data would strengthen the case. Low abuse rates relative to size would support the idea that price and verification deter bad actors. Rising abuse or slow mitigation would undermine the whole trust premium. The absence of clean public per-TLD abuse data is therefore an evidence gap, not a conclusion.

The fifth is backend cost and service transparency. Tucows dependence looks sensible, but backend fees and service terms are not public in the reviewed material. A registry with fewer than 10,000 names is sensitive to fixed costs. Any backend repricing, outage, transition or reporting failure would matter more than it would in a huge open namespace.

The sixth is cooperative-sector adoption. The International Cooperative Alliance describes a movement with massive economic and membership scale, but .coop adoption remains a small subset of that universe. If more prominent cooperative federations, retailers, financial cooperatives, worker cooperatives and platform cooperatives made .coop their primary address, the badge would become more valuable for everyone. If prominent cooperatives keep using .com, .org and country-code addresses while .coop remains supplemental, DotCooperation must keep proving why a secondary identity is worth renewing.

The verdict: .coop is a trust product with a narrow margin of error

DotCooperation's position is defensible but not easy. The company has a real delegated role, a clear community mission, ICANN-recognized authority, a formal eligibility process, a 2026 verification policy, a public abuse policy, Tucows technical support, RDAP service, DNSSEC-capable delegation and a small but global base of cooperative registrants. Those are meaningful assets.

The weakness is that the product is expensive precisely because it is meaningful. A registrar can sell .com cheaply because .com does not ask whether the buyer belongs to a movement. A country-code registry can be locally meaningful because users already understand the national address space. .org can borrow decades of broad nonprofit recognition. .coop has to make a more specific argument every year: this address says we are a cooperative, and the registry did the work to make that claim credible.

For a cooperative deciding whether to renew, the answer should be practical. If members, customers, funders, partners or peer cooperatives recognize .coop and care about the cooperative identity, the renewal can be worth far more than the domain bill. It reduces explanation cost and differentiates the organization from ordinary businesses. If the audience does not understand the signal, if the domain is only parked, or if the organization already has a stronger local address, .coop may be a mission-aligned badge rather than a necessary channel.

For DotCooperation, the strategic work is to keep the badge from becoming either too cheap or too costly. Too cheap, and eligibility pressure rises. Too costly, and small cooperatives leave or never arrive. Too open, and the signal degrades. Too restrictive, and legitimate organizations choose easier names. Too dependent on one registrar channel, and access narrows. Too spread across generic registrars, and customer education weakens.

The present evidence points to a credible but small namespace whose value depends on discipline. The public record does not show a mass-market growth story. It shows a renewal and verification business attached to a global movement. That can be a durable role if DotCooperation keeps the trust premium visible: strict eligibility, fair verification, transparent pricing through registrars, responsive abuse handling, stable technical service and enough community adoption that a .coop address feels like a cooperative credential rather than a decorative suffix.

The cooperative at the renewal counter should therefore ask one question: does this address make our cooperative identity easier to believe? If yes, DotCooperation is selling something real. If no, the domain is just an expensive string, and an expensive string is not what .coop was created to be.