BRregistry's registry fee prices accountable resource trust

Summary

• The buyer's question is not whether a short local domain string is pretty. It is whether JPY 1,320 a year, the public price shown by BRregistry for .okinawa and .ryukyu acquisition and annual cost, buys enough accountable control to beat the direct substitute: an informal social handle, a marketplace page, a free or cheap subdomain under someone else's name, or a lower-cost generic name with weaker local signal and weaker provenance. Source: https://www.brregistry.com/service/newgtlds.html
• The operating burden being transferred is durable registry administration: root-zone delegation, registrar access, registration data services, DNSSEC practice, IDN rules, abuse reporting, continuity obligations, data escrow, monthly ICANN reporting and a clear sponsoring organisation in the IANA record. Those duties are not glamorous, but they are the reason a domain can outlast a campaign, a vendor change or a staff handover. Sources: https://www.iana.org/domains/root/db/okinawa.html and https://www.iana.org/domains/root/db/ryukyu.html
• The strongest public evidence is convergent rather than single-source: IANA identifies BRregistry as sponsoring organisation for .okinawa and .ryukyu; ICANN registry-agreement pages identify BRregistry as operator; BRregistry publishes service prices and policy pages; ICANN monthly reports show continuing domains under management; and Japan's corporate-number page identifies the legal company. Sources: https://www.icann.org/en/registry-agreements/details/okinawa, https://www.icann.org/en/registry-agreements/details/ryukyu and https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=6130001056725
• The evidence does not prove that every registrant is satisfied, that support replies are fast, that abuse complaints are resolved well, or that BRregistry earns attractive margin on the retail fee. The decisive private metrics would be renewal cohorts by channel, gross profit per active domain after registry back-end and ICANN costs, abuse-ticket response and closure times, DNS/RDDS incident minutes, and churn reasons after the first renewal.
• The economic thesis survives, but only as a disciplined small-registry thesis: the fee prices accountable resource trust for businesses and community publishers that value an Okinawa/Ryukyu signal enough to pay for formal records, while public data still leaves open questions about retention quality, support quality and the operator's unit economics.

A resource holder considering a BRregistry name is not buying a line of text in isolation. The buyer is deciding whether to pay a recurring registry-service fee for a formally delegated, transferable and accountable identifier, or to rely on a substitute that looks cheaper until control becomes contested. The substitute may be a free social page, a page inside a hotel-booking platform, a handle inside a marketplace, a URL under a web agency's domain, a short-term campaign subdomain, or a generic domain registered through the cheapest available channel. Those options can work for low-stakes discovery, but they transfer control to someone else's account system and often weaken the evidence trail when the holder needs to prove ownership, move suppliers, respond to abuse, recover from staff turnover or show that the name is genuinely tied to Okinawa or Ryukyu.

BRregistry's own service page makes the visible fee small: it lists the acquisition and annual cost for the .okinawa and .ryukyu domains through Namegear at JPY 1,320 including tax, and says renewal from the following year is the same amount. Source: https://www.brregistry.com/service/newgtlds.html. That number is the retail-facing price signal, not the whole economics of the registry. Under the hood, a registry has to maintain delegation records, registrar interfaces, nameserver service, publication of registration data, DNSSEC practice material, IDN rules, abuse reporting, contractual notices, monthly reporting to ICANN and continuity arrangements. The buyer usually sees only the invoice and the renewal reminder. The value is in the operating burden that does not have to be recreated inside the buyer's organisation.

The direct avoided-cost comparison is therefore not a simple JPY 1,320 versus zero. It is JPY 1,320 versus the cost of informal control: brand ambiguity, platform lockout, unclear responsibility when a page is hijacked or spoofed, weaker evidence in a dispute, harder supplier migration, and a less traceable abuse route if a domain is misused. A small tourism operator, local association, publisher, software project or event organiser can decide that the local signal is not worth it. That is rational if the domain is disposable. But if the name is expected to act as a public identifier, the registry fee prices a bundle of trust attributes that are hard to build after the fact.

The strongest public evidence starts with IANA. The .okinawa root record names BRregistry, Inc. as sponsoring organisation, lists GMO Registry, Inc. as administrative and technical contact, lists whois.nic.okinawa, names the RDAP endpoint at https://rdap.gmoregistry.net/rdap/, and records .okinawa delegation and later redelegation history. Source: https://www.iana.org/domains/root/db/okinawa.html. The .ryukyu root record provides the same structure for whois.nic.ryukyu and the same RDAP endpoint. Source: https://www.iana.org/domains/root/db/ryukyu.html. The 2016 IANA redelegation reports for both strings say the proposed sponsoring organisation was BRregistry, that applicant matching, contact confirmations and technical conformance were completed, and that the sponsoring organisation in the Root Zone Database has overall responsibility for managing delegation details. Sources: https://www.iana.org/reports/c.2.9.2.d/20160613-okinawa and https://www.iana.org/reports/c.2.9.2.d/20160613-ryukyu.

That evidence proves responsibility for the top-level delegation. It does not prove customer delight, nor does it show the economics of any one domain holder. ICANN's registry-agreement pages identify BRregistry as the current operator for .okinawa and .ryukyu, with agreement dates of 5 December 2013 and 9 January 2014 respectively. Sources: https://www.icann.org/en/registry-agreements/details/okinawa and https://www.icann.org/en/registry-agreements/details/ryukyu. The downloadable agreements contain the public machinery behind the service: data escrow, public access to registration data, interoperability and continuity obligations, emergency transition language, performance specifications, fees paid to ICANN, abuse mitigation obligations, RDDS service-level language and continuing-operation instruments. Sources: https://itp.cdn.icann.org/en/files/registry-agreements/okinawa/okinawa-agmt-html-05dec13-en.htm and https://itp.cdn.icann.org/en/files/registry-agreements/ryukyu/ryukyu-agmt-html-09jan14-en.htm.

The missing proof groups into three buckets. Economics: the public record does not show BRregistry's registry-service margin after registrar share, back-end service fees, ICANN fixed and transaction charges, legal compliance and support. Reliability: the public record shows obligations and public DNS/RDDS endpoints, but not the operator's incident minutes, support queues, failed updates, complaint handling or near misses. Retention: ICANN reports show domains under management, additions and renewals, but not why holders renew, lapse or transfer. Two or three decisive metrics would change the judgement: renewal rate by first-year cohort and registrar channel; gross profit per active domain after direct registry costs; and median plus 95th-percentile time to resolve abuse, registrant-data and registrar-support tickets.

The fee is small because the burden is mostly invisible

The temptation with a domain such as .okinawa or .ryukyu is to treat it as a marketing garnish. That misses the operating work hidden inside the word "registry." The resource holder does not run the top-level database, maintain root-zone contacts, publish a WHOIS or RDAP service, coordinate accredited registrars, manage reserved names, keep DNSSEC practice material, publish abuse rules, maintain continuity arrangements or report monthly activity to ICANN. Those tasks sit behind the service. When they work, they feel uneventful. When they fail, the domain stops being a clean public identifier and becomes a governance problem.

BRregistry's service page describes .okinawa and .ryukyu as domains for Okinawa and Ryukyu and places the price next to acquisition and annual cost. Source: https://www.brregistry.com/service/newgtlds.html. Its GeoTLD page frames .okinawa as a GeoTLD for Okinawa prefecture and .ryukyu as a GeoTLD for Okinawa prefecture using the historical Ryukyu name. It also publishes policy links for domain-name registration policies, abusive use, searchable WHOIS access, IDN policy and DNSSEC practice statements. Source: https://www.brregistry.com/geotlds/. A buyer may not read those policy pages before renewing. The pages matter because they show that the service is not only a label sale. It sits inside a public rule set.

The registry-service fee is also not the same thing as a registrar checkout price. Domain registrants buy through registrars or service sites, and retail prices can vary. BRregistry's own visible price through Namegear is a local anchor; third-party registrar pages and price lists show wider market prices, sometimes in dollars and sometimes with higher renewal charges. Namegear's domain-extension page lists .ryukyu with a dollar price and explains it as a Ryukyu Kingdom/Okinawa-related domain. Source: https://namegear.co/en/p/extensions/. E-domain's Japanese price page lists .okinawa and .ryukyu in a group priced at JPY 1,320. Source: https://www.e-domainde.com/price/index.html. Name.com and Directnic show .okinawa and .ryukyu in wider registrar price lists at materially higher dollar amounts. Sources: https://www.name.com/pricing and https://directnic.com/pricing. These are market signals, not proof of BRregistry's wholesale economics.

For the holder, the fee should be evaluated against the avoided cost of ambiguity. A city-focused tourism shop using a social handle can be discovered cheaply, but the handle does not create a root-delegated domain record. A community association using a free subdomain may avoid renewal reminders, but it also relies on another party's domain and account lifecycle. A local publisher using a generic domain may reach a broader audience, but loses the geography in the identifier. A domain under .okinawa or .ryukyu does not guarantee legitimacy, but it gives the holder a name that sits inside a published delegation, can move through registrar mechanisms and can be checked against public registry data services.

That distinction is the economic lens for BRregistry. The fee is not high enough to be treated as enterprise software. It is better understood as a small recurring price for accountability infrastructure. The question is whether the buyer expects the name to carry enough local trust, continuity value and evidentiary weight to justify paying for that infrastructure each year.

What the public record proves

The IANA root records are the most important proof because they identify the top-level delegation. For .okinawa, IANA names BRregistry as sponsoring organisation and lists GMO Registry as administrative and technical contact. It also lists four gmoregistry.net name servers, a WHOIS server at whois.nic.okinawa, and an RDAP server at https://rdap.gmoregistry.net/rdap/. Source: https://www.iana.org/domains/root/db/okinawa.html. For .ryukyu, the structure is the same, with whois.nic.ryukyu. Source: https://www.iana.org/domains/root/db/ryukyu.html. The records were last updated in 2019 and preserve the original registration dates in 2014.

Those records prove who is publicly responsible at the root-zone level. They also prove that the registry's operational surface is not purely local: the administrative and technical contact is GMO Registry, and the name servers use the gmoregistry.net domain. This is important because it separates brand ownership, legal sponsoring responsibility and technical service delivery. BRregistry can be the sponsoring organisation while relying on a specialised registry back end for technical functions. For a buyer, that can be positive if the back end is competent; it can be negative if responsibilities are hard to interpret. The public record supports the first half of the statement, not the second.

The IANA redelegation reports add a governance layer. The 13 June 2016 reports for .okinawa and .ryukyu state that BRregistry was the proposed sponsoring organisation and that applicant matching, contact confirmations, technical conformance and other processing were completed. Sources: https://www.iana.org/reports/c.2.9.2.d/20160613-okinawa and https://www.iana.org/reports/c.2.9.2.d/20160613-ryukyu. That is not a performance review. It is evidence that the delegation transfer to BRregistry passed the procedural and technical checks needed for the root-zone change.

ICANN's registry-agreement pages provide the contract layer. .okinawa is shown with operator BRregistry and agreement date 5 December 2013. Source: https://www.icann.org/en/registry-agreements/details/okinawa. .ryukyu is shown with operator BRregistry and agreement date 9 January 2014. Source: https://www.icann.org/en/registry-agreements/details/ryukyu. The .okinawa page also lists assignment documents from Business Ralliart to BRregistry, renewal notice material and amendments. The .ryukyu page does the same. This supports a careful statement: BRregistry is the named operator in ICANN's public contract pages, and the older BusinessRalliart origin was moved into BRregistry through documented assignment materials.

Japan's corporate-number page closes another part of the identity loop. It records the Japanese legal entry for BRregistry, corporate number 6130001056725, and lists the current head-office address in Kyoto city with a change-history trail. Source: https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=6130001056725. BRregistry's own company overview says it was established in January 2016, has capital of JPY 5,000,000, lists Toshiyuki Nakanishi as representative director, identifies BusinessRalliart as the major shareholder and says BRregistry is a 100 percent consolidated subsidiary of BusinessRalliart. It also lists ISMS certification registration number ICMS-SR0166, JIS Q 27001, and telecommunications business notification K-26-00042. Source: https://www.brregistry.com/company/overview.html. That proves legal continuity and governance context; it does not prove the stand-alone economics of the registry business.

The public records therefore prove a narrow but important set of facts: BRregistry is not merely a reseller page, it is named in the root and contract records for two GeoTLDs; it has a Japanese corporate identity; it publishes public service and policy material; and it sits inside ICANN's registry contract structure. The records do not prove that the public fee is profitable, that customers understand the trust bundle, or that support performance is strong.

The registry contract turns a domain into a duty

The registry agreement is where the buyer's "trust" becomes operational duty. The .okinawa and .ryukyu agreements require data escrow, public access to registration data, compliance with interoperability and continuity specifications, emergency transition cooperation, performance records and payment of registry-level fees to ICANN. Sources: https://itp.cdn.icann.org/en/files/registry-agreements/okinawa/okinawa-agmt-html-05dec13-en.htm and https://itp.cdn.icann.org/en/files/registry-agreements/ryukyu/ryukyu-agmt-html-09jan14-en.htm. The details are not retail copy. They are the institutional skeleton behind the annual fee.

Data escrow matters because a domain registry is a database of delegated names and contacts, not a set of isolated web pages. If the operator fails, escrowed data is one of the mechanisms that can keep domains from becoming stranded. Emergency transition language matters for the same reason: the agreements contemplate ICANN designating an emergency interim registry operator if critical thresholds are reached. The buyer may never read that clause, but it is part of the reason a formally delegated domain is different from a page under an unmanaged subdomain.

The agreements also require public registration data services. In older contract language this appears as WHOIS and web-based WHOIS; modern root records also list RDAP. The value for the holder is not that all personal details are public. The value is that the registry has to maintain a lookup surface and a policy framework for who can access what, under what conditions, and how abuse or dispute signals can reach the responsible parties. BRregistry's searchable WHOIS access terms state that users of the searchable WHOIS service must have a legitimate reason, may not use the information for marketing, spamming or data-mining, and face a limit of 50 queries per 24 hours. Source: https://www.brregistry.com/geotlds/policy/whois/. That is not a perfect accountability system, but it is an explicit one.

Abuse policy turns accountability into action rights. BRregistry's abusive-use page says the operator's core aims include safe, secure, stable, relevant and enjoyable namespaces; identifies threats such as pharming, phishing, malware, botnets, spam and illegal content; gives a GMO Registry abuse contact at abuse@gmoregistry.com; and reserves rights to deny, cancel, transfer or lock a name when needed to protect registry integrity, comply with law or respond to prohibited conduct. Source: https://www.brregistry.com/geotlds/policy/use/. This does not prove that every abuse report is handled well. It proves that a public route exists and that the registry has stated response powers.

For the resource holder, this is the fee's core economic benefit. Informal control can be cheap because it externalises abuse handling, continuity and dispute evidence. Formal control costs a recurring fee because someone has to maintain an accountable record and a published operating path. The strongest argument for renewal is not that .okinawa or .ryukyu is fashionable. It is that the buyer wants a name whose control can be documented and defended in a recognised registry system.

Volume shows persistence, not scale comfort

ICANN's monthly registry reports make the small-registry economics more visible. The latest non-empty .okinawa transaction file checked for this article, November 2025, summed to 8,804 total domains across 67 registrar rows, with visible net adds and renewals reported by registrar. Source: https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv. The latest non-empty .ryukyu transaction file checked, December 2025, summed to 1,512 total domains across 67 registrar rows. Source: https://www.icann.org/sites/default/files/mrr/ryukyu/ryukyu-transactions-202512-en.csv. The corresponding activity files show large DNS query counts, WHOIS query counts, RDAP query counts and SRS operation counts for their months. Sources: https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-activity-202511-en.csv and https://www.icann.org/sites/default/files/mrr/ryukyu/ryukyu-activity-202512-en.csv.

Those figures support persistence, not abundance. .okinawa has enough volume to show an active namespace, but it is not a mass-market generic. .ryukyu is much smaller. A registry with this profile must make the economics work through lean operations, back-end leverage, low support burden, channel discipline and enough renewals to offset the fixed work of compliance. The ICANN agreement's fee language says the registry operator pays ICANN a fixed registry-level fee of US$6,250 per calendar quarter plus transaction fees under the base agreement. Source: https://itp.cdn.icann.org/en/files/registry-agreements/ryukyu/ryukyu-agmt-html-09jan14-en.htm. That fee is one part of the cost base, not the whole one, and the existence of later amendments means the exact current fee structure should be checked against the full current agreement package before modelling margin.

The public monthly reports do not show why a registrant renews. A name may renew because it is valuable, because it is on auto-renew, because it is parked, because it sits inside a defensive portfolio, because the holder forgot it exists, or because a registrar uses it in a bundle. They also do not show support contacts per domain, reseller economics or local marketing conversion. This is why the right private metrics are cohort renewals, active-use share, channel gross margin, abuse/support workload per thousand names and churn reason. Without those, volume is evidence of use, but not proof of a strong product-market fit.

Third-party industry trackers and registrar listings help with market visibility but require caution. nTLDStats lists .okinawa with BRregistry as registry and GMO Registry as registry back end, and breaks down registrar shares. Source: https://ntldstats.com/tld/okinawa. Its .ryukyu page gives the same category of market view. Source: https://ntldstats.com/tld/ryukyu. These sources are useful for cross-checking market structure and channel concentration; they are not official registry reports. Registrar price pages show that .okinawa and .ryukyu are available through multiple channels, but they do not reveal wholesale terms. Sources include https://namegear.co/en/p/extensions/, https://www.name.com/pricing and https://directnic.com/pricing.

The economic interpretation is therefore balanced. A buyer paying JPY 1,320 through the visible BRregistry service page is paying a modest price for a local identifier backed by public registry obligations. BRregistry, however, has to make that modest price work across small namespaces, contract duties, back-end service, registrar distribution and compliance. The thesis is attractive only if renewals are stable, support load is low and the local identity value remains durable.

Accountability is local in brand and distributed in operations

BRregistry's identity is local to Japan and to the Okinawa/Ryukyu domain proposition. Its company page locates the business in Kyoto, gives a representative telephone number, lists directors, identifies BusinessRalliart ownership and discloses certification and telecommunications notification details. Source: https://www.brregistry.com/company/overview.html. Its history page is sparse, recording establishment in January 2016. Source: https://www.brregistry.com/company/history.html. Its service and GeoTLD pages tell the market story: these are domains for Okinawa and Ryukyu, intended to help regional businesses, services, culture and information show local connection. Sources: https://www.brregistry.com/service/newgtlds.html and https://www.brregistry.com/geotlds/.

Operationally, the public record is more distributed. IANA lists GMO Registry as administrative and technical contact for both TLDs and points registration services to GMO Registry. Sources: https://www.iana.org/domains/root/db/okinawa.html and https://www.iana.org/domains/root/db/ryukyu.html. BRregistry's abuse page also routes abuse reporting through a GMO Registry contact. Source: https://www.brregistry.com/geotlds/policy/use/. DNSSEC practice statements are presented as GMO Registry documents. Source: https://www.brregistry.com/geotlds/policy/info/dnssec/. That is not unusual in the registry market. Many smaller or specialised TLDs rely on experienced back-end providers. But it affects how to read accountability.

The buyer should not infer that every operational task is performed by BRregistry employees in Kyoto. The better inference is that BRregistry is the accountable local registry operator and sponsoring organisation, while specialised registry infrastructure and contacts appear through GMO Registry and, in name-server network records, additional registry-network providers. A RIPE RDAP query for the IPv4 address 37.209.192.4, one of the a.gmoregistry.net addresses listed by IANA, identifies a GoDaddy Registry allocation and an abuse contact in the registry-network layer. Source: https://rdap.db.ripe.net/ip/37.209.192.4. An APNIC RDAP query for 2001:dcd:1::4, one of the IPv6 addresses listed by IANA, identifies Bombora Technologies/GoDaddy Registry network contact material. Source: https://rdap.apnic.net/ip/2001:dcd:1::4. Those number-resource records are evidence about the network layer behind name service. They are not separate entities in this article's analysis, and they do not prove BRregistry's customer support model.

This distributed operating surface can still be a strength. A small local registry can benefit from a specialised back-end environment with established DNS, EPP, WHOIS/RDAP and DNSSEC operations. It can also create interpretive risk for a buyer trying to know who answers what. The public record gives several accountability addresses: BRregistry's own company and contact pages, GMO Registry administrative and technical contacts in IANA, a GMO Registry abuse email in BRregistry's abuse policy, and RIR records for name-server address blocks. A rigorous buyer values that because it creates routes for verification. A skeptical buyer asks whether those routes lead to timely service when something goes wrong.

The article's thesis depends on that distinction. The registry-service fee prices accountable trust only if the distributed accountability chain works in practice. Public records show the chain. Private support and incident metrics would prove whether it works.

Policy pages give the namespace its rules

The formal value of a registry is not only DNS availability. It is also the rules that decide what can be registered, what must be withheld, how abusive use is handled, and how internationalised names are treated. BRregistry's GeoTLD policy index links to registration policies, abuse policy, searchable WHOIS access terms, IDN policy and DNSSEC practice statements. Source: https://www.brregistry.com/geotlds/. The registration-policy page points to .okinawa and .ryukyu domain-name registration policies and sunrise dispute policies. Source: https://www.brregistry.com/geotlds/policy/regist/.

The IDN policy says BusinessRalliart offers Japanese Internationalized Domain Names in both .okinawa and .ryukyu and describes technical requirements using IDNA2008, including A-label validity and compliance with RFCs 5890-5893. Source: https://www.brregistry.com/geotlds/policy/info/idn/. This matters because a local Japanese GeoTLD without IDN discipline would create confusion. Variant handling, syntax requirements and standards compliance are not retail features, but they reduce ambiguity for registrants and registrars.

DNSSEC practice material matters for a different reason. BRregistry's DNSSEC page says GMO Registry's DNSSEC Practice Statements can be downloaded there. Source: https://www.brregistry.com/geotlds/policy/info/dnssec/. A buyer should not read that as proof that every registrant deploys DNSSEC correctly at the second level. It proves that the top-level operator publishes practice material and points to the back-end registry's DNSSEC framework. That is part of the trust bundle because nameservers and signed delegations are infrastructural, not cosmetic.

Abuse policy is the most commercially relevant rule set because it addresses downside risk. The public policy lists spam, pharming, DNS interference, phishing, malware, botnets, illegal content and hacking as abusive uses, says technical analysis may be conducted, gives an abuse contact and reserves intervention rights. Source: https://www.brregistry.com/geotlds/policy/use/. For a legitimate registrant, intervention rights are double-edged. They help protect the namespace and reduce bad-neighbour risk, but they also mean the registry can act on a domain under specified conditions. The value is in a clear, published policy rather than arbitrary silence.

Searchable WHOIS terms add privacy and accountability tension. BRregistry's terms ask users to have a legitimate reason and prohibit marketing, spamming, data-mining and unlawful use, while recording search information and limiting queries. Source: https://www.brregistry.com/geotlds/policy/whois/. That posture reflects the modern registry dilemma: make enough data accessible for accountability without enabling bulk harvesting. For the resource holder, this is part of the fee's value if they care about accountable use without excessive exposure.

These policy pages are not evidence of flawless enforcement. They are evidence that BRregistry has chosen to publish the rules around a domain holder's resource. The economic value appears when a domain becomes important enough that rules matter: a disputed local name, a phishing complaint, a registrar transfer, a DNSSEC question, a data-access request or a renewal after a staff change.

Continuity is the quiet part of the product

Continuity rarely sells a domain name in the checkout moment. It becomes decisive when something breaks. A domain holder may assume that a renewal fee buys only another year of use. In a registry context, it also funds the system of records, escrow and operational obligations that help keep the namespace transferable and recoverable. ICANN's agreements require registry operators to comply with data escrow procedures, public registration-data access obligations, interoperability and continuity specifications, performance specifications and emergency transition requirements. Sources: https://itp.cdn.icann.org/en/files/registry-agreements/okinawa/okinawa-agmt-html-05dec13-en.htm and https://itp.cdn.icann.org/en/files/registry-agreements/ryukyu/ryukyu-agmt-html-09jan14-en.htm.

The IANA delegation reports show that technical conformance and contact confirmations were part of the delegation and redelegation checks. Sources: https://www.iana.org/reports/c.2.9.2.d/20140227-okinawa, https://www.iana.org/reports/c.2.9.2.d/20140331-ryukyu, https://www.iana.org/reports/c.2.9.2.d/20160613-okinawa and https://www.iana.org/reports/c.2.9.2.d/20160613-ryukyu. Again, that is not a live uptime score. It is proof that the namespace entered and later changed its root-zone sponsorship through recognised procedures rather than informal handover.

BRregistry's own news page for the category labelled as incident information does not read like a rich operational incident archive in the public view checked for this article; it includes accounting-document notices and holiday notices rather than a detailed public record of DNS or RDDS incidents. Source: https://www.brregistry.com/news_list.html?category_code=2. That should not be overread. A quiet public page may mean low incident disclosure, no major public incidents, or simply a disclosure style that does not expose technical details. The public evidence cannot distinguish those cases.

The right buyer question is therefore practical. If the name is a disposable campaign, the continuity premium may be unnecessary. If the name is tied to bookings, payments, local identity, community trust, public information or a long-running service, continuity becomes part of the cost of doing business. JPY 1,320 a year is trivial compared with the cost of a confused migration, lost account, impersonated page or domain dispute. But the fee is only worth renewing if the public registry framework is matched by operational competence.

Continuity also interacts with transferability. A domain registered through a formal registry and registrar structure can move between registrars under established rules. A social handle or platform URL may not move at all. A subdomain can disappear when the parent domain changes, the host relationship ends or a vendor account is terminated. The registry fee prices the option to keep the identifier portable inside a recognised domain system.

Customer evidence is thin, so market signals must be used carefully

Public customer chatter around .okinawa, .ryukyu and BRregistry is not rich enough to support a broad claim about customer enthusiasm. There are registrar pages, price lists, third-party TLD trackers and policy materials, but not a large body of public registrant case studies, support reviews or community discussions visible in the sources checked for this article. That absence matters. It means the economic analysis should lean on official records and market signals, not anecdotes.

The official market signal is domain count. ICANN monthly reports show active domains under management and registrar distribution. The November 2025 .okinawa transaction file summed to 8,804 total domains across 67 registrar rows. Source: https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv. The December 2025 .ryukyu transaction file summed to 1,512 total domains across 67 registrar rows. Source: https://www.icann.org/sites/default/files/mrr/ryukyu/ryukyu-transactions-202512-en.csv. These numbers are enough to show that the namespaces are not empty. They are not enough to show strong growth, deep engagement or high renewal satisfaction.

The unofficial market signal is registrar visibility. Namegear, E-domain, Name.com, Directnic and other domain retailers list the strings in broader catalogs. Sources: https://namegear.co/en/p/extensions/, https://www.e-domainde.com/price/index.html, https://www.name.com/pricing and https://directnic.com/pricing. This shows that a buyer can access the TLDs through more than one channel. It does not prove actual sales quality, support quality or local community adoption. Some listings are static catalogs; some prices may be stale or promotional; some channels may have little demand.

Third-party TLD statistics fill part of the gap. nTLDStats pages for .okinawa and .ryukyu identify BRregistry and show registrar distribution snapshots. Sources: https://ntldstats.com/tld/okinawa and https://ntldstats.com/tld/ryukyu. These are useful for orientation and cross-checking, but official ICANN reports remain stronger for monthly activity. A careful investor or enterprise buyer would reconcile both, then ask for private renewal and active-use data.

The missing customer evidence does not defeat the trust thesis. It limits it. The article can say that BRregistry sells a low-cost formal registry service for two local GeoTLDs with public accountability records. It cannot say that the market strongly prefers those strings or that the fee has clear pricing power. Pricing power would require evidence that registrants renew because the domain creates measurable business value, not simply because the fee is low enough to ignore.

What the registry evidence proves, and what it does not

Registry evidence is unusually good at proving responsibility. IANA and ICANN records show who is responsible for the top-level domain, what contacts are published, what services are listed and what agreement materials exist. They are also good at proving that certain rule sets exist: registration policies, abuse policy, searchable WHOIS terms, IDN policy and DNSSEC practice statements. Sources: https://www.iana.org/domains/root/db/okinawa.html, https://www.iana.org/domains/root/db/ryukyu.html and https://www.brregistry.com/geotlds/.

Registry evidence is weaker at proving experience. It does not show how fast a registrar support request is answered, how often a registrant fails validation, how many abuse reports are false positives, how many are resolved, whether a small business understands transfer rules, or how many domains are actively used rather than parked. Monthly reports show transactions, not user satisfaction. Source: https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv. WHOIS and RDAP records show lookup infrastructure, not necessarily the quality of data behind every registrant.

Corporate evidence proves identity, not product quality. Japan's corporate-number page and BRregistry's company overview identify the company, its address, group relationship, capital, officers and certifications. Sources: https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=6130001056725 and https://www.brregistry.com/company/overview.html. That helps distinguish the legal operator from a thin resale page. It does not prove that the registry has enough commercial momentum or support capacity.

Back-end and number-resource evidence proves operating dependencies, not local control. IANA's name-server records point to gmoregistry.net; RIR RDAP records for the published name-server addresses point to registry-network allocations and contacts. Sources: https://www.iana.org/domains/root/db/okinawa.html, https://rdap.db.ripe.net/ip/37.209.192.4 and https://rdap.apnic.net/ip/2001:dcd:1::4. That is useful for accountability mapping. It does not turn the IP addresses, prefixes or contacts into the subject of the article, and it does not measure BRregistry's own operating staff.

This precision matters because the economic lens is trust. Trust is not the same as belief. Public records create checkable trust: the buyer can see the operator, contacts, policies, reporting and continuity duties. Private metrics create operational trust: the buyer can see renewals, support outcomes, abuse outcomes and uptime. BRregistry's public case is strong on checkable trust and incomplete on operational proof.

The fee's value changes by buyer type

For a local tourism or culture business, the value is identity and continuity. A .okinawa domain can signal place in the name itself. A .ryukyu domain can carry historical and regional meaning. BRregistry's GeoTLD page explicitly frames the strings around Okinawa, Ryukyu, regional culture and global promotion of the Okinawa brand. Source: https://www.brregistry.com/geotlds/. The fee is worth it if that signal improves trust, recall or differentiation enough to justify an annual line item.

For a defensive brand holder, the value is control. Registering a relevant local string may prevent ambiguity, impersonation or reputation leakage. The abuse policy and dispute mechanisms do not eliminate defensive-registration cost, but they provide a public rule framework. Source: https://www.brregistry.com/geotlds/policy/use/. A defensive holder will care less about local storytelling and more about transfer rules, renewal reliability, registrar availability and intervention rights.

For a public-interest or community publisher, the value is accountability. A formal domain can make the publisher easier to verify than a social handle. The IANA root record, WHOIS/RDAP listing and registry policy pages create a traceable path. Sources: https://www.iana.org/domains/root/db/okinawa.html and https://www.brregistry.com/geotlds/policy/whois/. That does not guarantee authenticity, but it gives readers, platforms and investigators a stronger record trail than many informal options.

For a pure performance marketer, the value may be weaker. If search ranking, ad conversion and short-term campaign speed dominate, a generic domain or platform page may outperform a local GeoTLD. The low fee reduces the downside, but low cost alone is not a reason to carry unused names. The registry-service fee is economically justified when the identifier has lasting control value.

For registrars and resellers, the value is channel economics. A TLD with modest retail price and small volume must be easy to sell, renew and support. Registrar rows in ICANN reports show distribution, but not margins or support cost. Sources: https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv and https://www.icann.org/sites/default/files/mrr/ryukyu/ryukyu-transactions-202512-en.csv. A reseller would need wholesale price, renewal rate, refund rate, support contacts, premium-name rules and transfer friction to decide whether the TLD is worth active promotion.

This segmentation keeps the thesis honest. BRregistry's fee prices accountable resource trust, but not every buyer needs that trust equally. The stronger the need for durable local identity, verifiable control and orderly transfer, the stronger the renewal case.

Scale risk is the other side of accountability

A small regional registry can be valuable and economically uncomfortable at the same time. The public records show persistence, not scale comfort. The .okinawa and .ryukyu strings have enough registrations and registrar rows to show that the namespaces are alive, but they do not resemble mass-market generic namespaces. That matters because the accountable work described above includes fixed duties: contract compliance, monthly reporting, registrar coordination, DNS and RDDS operation, abuse handling, policy publication, data escrow and continuity planning. Those duties do not disappear when monthly create counts are low.

This is the point where the buyer's annual fee has to be judged differently from a simple software subscription. A large registry can spread infrastructure and compliance cost across millions of names. A smaller GeoTLD must recover the cost of formal accountability across a narrower demand pool. The fee therefore has to do two things at once: stay low enough that local businesses and community publishers do not see it as a tax on identity, and still support the registry functions that make the name more credible than an informal substitute. BRregistry's visible JPY 1,320 anchor is attractive for adoption, but it leaves the outside analyst unable to see whether the upstream registry unit is comfortably funded.

Scale also affects abuse economics. A small namespace may have fewer abusive registrations in absolute terms, but it may also have fewer active registrants over which to spread monitoring and response cost. One confirmed phishing or impersonation case can consume more labor than many ordinary renewals. The public abuse policy proves that the response path exists; it does not show whether the cost of that path is covered by ordinary registration and renewal economics. This is why abuse response should be treated as a cost center, not only a policy promise.

For renewal buyers, small scale can be a feature when the domain's job is distinctiveness. A local cultural organisation or tourism project may prefer a sparse namespace where the geography is clear and the desired label has not been crowded out. But small scale can become a liability if registrar availability narrows, if support knowledge is thin, or if a future buyer worries about long-term investment in the namespace. ICANN agreement continuity, IANA delegation records and monthly reports reduce that concern. They do not eliminate it.

The public record would become much stronger if BRregistry or its retail channels published a few aggregated operating indicators. Renewal rate by cohort would show whether initial buyers keep valuing the names. Active-use share would show whether names support real websites, mail, redirects or services rather than only defensive holding. Abuse response time would show whether accountability is operational rather than theoretical. Registrar concentration would show whether distribution risk is rising or falling. None of those figures requires disclosure of individual registrants. Together they would turn the small-registry thesis from plausible to measurable.

Economics, reliability and retention decide the next judgement

The first decisive economics metric is gross profit per active domain after direct registry costs. Public sources show retail price signals and ICANN duties, but not wholesale split, registrar margin, back-end service fees, internal staffing or compliance cost. The registry agreements show ICANN fee obligations; BRregistry's service page shows a retail anchor; monthly reports show total domains. Sources: https://www.brregistry.com/service/newgtlds.html, https://itp.cdn.icann.org/en/files/registry-agreements/ryukyu/ryukyu-agmt-html-09jan14-en.htm and https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv. The private question is whether a few thousand active names can cover the fixed trust infrastructure without weakening support.

The second metric is reliability by service, not only public uptime. DNS availability, RDDS availability, RDDS update time, EPP responsiveness and emergency thresholds are named in contract materials. Source: https://itp.cdn.icann.org/en/files/registry-agreements/okinawa/okinawa-agmt-html-05dec13-en.htm. A buyer would want recent DNS/RDDS incident minutes, maintenance notifications, failed update counts and registrar-impacting incidents. The public activity reports show queries and SRS operations, but not customer pain.

The third metric is retention by cohort and channel. A one-year price can create curiosity. Renewals reveal durable value. BRregistry's service page says renewal cost remains the same through the visible channel. Source: https://www.brregistry.com/service/newgtlds.html. ICANN transaction files show net renewals by registrar and term length, but not why the holder renewed. A strong private case would show that names registered for local identity renew at high rates, that churn is concentrated in defensive or speculative portfolios, and that support issues do not drive lapses.

The fourth metric is abuse and accountability performance. BRregistry publishes an abuse policy and a contact. Source: https://www.brregistry.com/geotlds/policy/use/. The private metric would be median first-response time, closure time, number of confirmed abuse cases, number of wrongful or disputed suspensions, and how often registrar coordination is required. For a legitimate holder, accountable abuse handling reduces namespace risk. Overbroad or slow handling can create business risk.

The fifth metric is active-use share. Total domains can include defensive registrations, parked names and inactive pages. Active-use share would show how many names host real content, email, redirects or service endpoints. That matters because a namespace dominated by inactive names can look stable while having weak community value. Public monthly reports cannot answer this. Third-party web crawl or DNS data could help, but would still need careful interpretation.

Until those metrics are public, the correct conclusion is measured. BRregistry offers a visible, low-cost path into two Okinawa-linked GeoTLDs with public accountability records. The registry fee looks worth renewing for holders that value local identity and formal control. The public evidence does not yet justify a stronger claim that the fee has broad pricing power or that BRregistry's small namespaces are economically comfortable.

Compact public evidence register

Evidence	URL	What it proves	What it does not prove
BRregistry service price and domain positioning	https://www.brregistry.com/service/newgtlds.html	Shows .okinawa and .ryukyu as regional domains and gives visible annual/acquisition fee through Namegear.	Does not show wholesale economics, registrar margin or all market prices.
BRregistry GeoTLD policy index	https://www.brregistry.com/geotlds/	Shows public policy surface for registration, abuse, WHOIS access, IDN and DNSSEC.	Does not prove enforcement quality or customer awareness.
IANA .okinawa root record	https://www.iana.org/domains/root/db/okinawa.html	Names BRregistry as sponsoring organisation and lists WHOIS/RDAP/name-server details.	Does not prove support performance or renewal intent.
IANA .ryukyu root record	https://www.iana.org/domains/root/db/ryukyu.html	Names BRregistry as sponsoring organisation and lists WHOIS/RDAP/name-server details.	Does not prove support performance or renewal intent.
IANA .okinawa redelegation report	https://www.iana.org/reports/c.2.9.2.d/20160613-okinawa	Shows 2016 redelegation to BRregistry passed applicant, contact and technical checks.	Does not measure post-delegation uptime or abuse handling.
IANA .ryukyu redelegation report	https://www.iana.org/reports/c.2.9.2.d/20160613-ryukyu	Shows 2016 redelegation to BRregistry passed applicant, contact and technical checks.	Does not measure post-delegation uptime or abuse handling.
ICANN .okinawa registry-agreement page	https://www.icann.org/en/registry-agreements/details/okinawa	Identifies BRregistry as operator and points to agreement, assignment, renewal and amendment materials.	Does not show private commercial performance.
ICANN .ryukyu registry-agreement page	https://www.icann.org/en/registry-agreements/details/ryukyu	Identifies BRregistry as operator and points to agreement, assignment, renewal and amendment materials.	Does not show private commercial performance.
BRregistry abuse policy	https://www.brregistry.com/geotlds/policy/use/	Gives abuse categories, abuse contact and intervention rights.	Does not show response times, confirmed cases or false positives.
BRregistry WHOIS access terms	https://www.brregistry.com/geotlds/policy/whois/	Shows access conditions, legitimate-use framing and anti-harvesting limits.	Does not prove lookup data quality for every record.
ICANN monthly .okinawa transactions	https://www.icann.org/sites/default/files/mrr/okinawa/okinawa-transactions-202511-en.csv	Shows registrar rows, total domains and transaction categories for November 2025.	Does not reveal renewal reasons or active-use share.
ICANN monthly .ryukyu transactions	https://www.icann.org/sites/default/files/mrr/ryukyu/ryukyu-transactions-202512-en.csv	Shows registrar rows, total domains and transaction categories for December 2025.	Does not reveal renewal reasons or active-use share.
Japan corporate-number page	https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=6130001056725	Identifies BRregistry's Japanese legal record and current registered address.	Does not prove registry economics or service quality.
BRregistry company overview	https://www.brregistry.com/company/overview.html	Shows company address, directors, ownership, certification and telecom notification.	Does not isolate registry-segment revenue or costs.
RIR record for published IPv4 name-server address	https://rdap.db.ripe.net/ip/37.209.192.4	Shows network-layer accountability for one published name-server address.	Does not identify BRregistry as network operator or measure DNS service quality.
RIR record for published IPv6 name-server address	https://rdap.apnic.net/ip/2001:dcd:1::4	Shows network-layer accountability for one published name-server address.	Does not identify BRregistry as network operator or measure DNS service quality.

The bottom line is that BRregistry's fee is economically credible when treated as a trust-and-continuity fee rather than a vanity-domain fee. The public record shows a legal company, two delegated GeoTLDs, a registry contract layer, policy pages, abuse contact, WHOIS/RDAP accountability surface, DNSSEC and IDN materials, monthly activity and continuing registrar distribution. A cautious buyer should still ask for private metrics before treating the service as more than a small but useful accountability layer: renewal cohorts, support outcomes, abuse response, uptime, active-use share and unit margin. Until then, the renewal decision turns on how much the holder values formal control over an Okinawa or Ryukyu identifier compared with cheaper but weaker substitutes.