Summary

  • Tonga is the rare country-code whose primary legislation names the domain outright: section 8(d) of the Communications Act 2015 assigns the Ministry authority over registration and allocation of names under .to, and section 69 makes the Minister or nominated persons answerable to the Internet Assigned Numbers Authority's procedures, conditions and agreements.
  • IANA's delegation row names the government as manager and a US company as technical contact; the company that calls itself the registry's manager says it has run the automated registry since 1997; a second company published .to registry policy in July 2025. No reviewed document reproduces the instrument that connects the authority in the Act to either company.

A statute that does not mumble

Most country-code domains never appear in their own country's legislation. Tonga's does, and the reference is not decorative.

Section 8(d) of the Communications Act 2015, at printed page 19 of the Attorney General's Office copy, assigns the Ministry authority over the registration and allocation of names under Tonga's .to country-code domain. Section 69, at printed pages 43–44, pushes the machinery one level down: responsibility sits with the Minister or nominated persons, subject to the procedures, conditions and agreements of the Internet Assigned Numbers Authority, with provision for ministerial monitoring. The Act's own sentence reads: "The nominated person shall comply with the procedures, conditions of and agreements with the Internet Assigned Numbers Authority."

That is a real chain of authority. It also stops exactly where the interesting part begins. The provisions inspected describe a power to nominate and a duty to comply with IANA's terms. They name no company, no concession, no term and no fee. No TONIC Domains Inc., no Internet Naming Co., no other contractor appears in the text this desk read.

A statute that creates a nomination power is not the same object as a nomination. The gap between them is the whole subject of this briefing.

What the delegation row actually says

IANA's .to delegation page records the code as active and delegated. Its manager field reproduces an entry that reads "Government of the Kingdom of Tonga, H.R.H. Crown Prince Tupouto'a, c/o Consulate of Tonga". The technical-contact organisation is Tucows.com. The linked registry website is tonic.to. The page displays January 7, 2026 as its last update.

Read that row for what it is and it tells you something useful: a manager of record, a technical contact, a website. Read it for what it is not and it tells you something more useful: it states no operating terms, no fee arrangement, no revenue split, no reporting duty, no service level and no remedy. It does not reproduce a contract, because a delegation entry is not a contract. The royal and consular designation is reproduced as recorded here; this desk did not validate it as a current description of any office-holder.

So the record now contains two different facts that are easy to blur. Tonga's law gives a ministry authority over name registration inside the code. IANA records the Tongan government as the code's manager. Neither of those is a statement about who operates the zone, on what terms, or for what consideration.

Two companies, one zone, no appointment

The operator side of the story begins with a sentence on a homepage. Tonic.to states: "Tonic.to is the official website for the .TO top level domain registry and is managed by TONIC Domains Inc." It adds: "Our automated .TO registry has been in operation by TONIC Domains since 1997."

That is a clean, confident claim of operational continuity spanning nearly three decades. As read, the page does not state the company's ownership, the identity of the party that appointed it, the term of any arrangement, any payment to the Government of Tonga, or any reporting obligation. It presents an operational identity, not a legal authority, and the difference matters most to whoever needs to know which company can bind them.

Then there is a second corporate voice in the same zone. Internet Naming Co.'s registry-resources page lists, among its policy documents, "Registry Policies", "Sunrise Policies", ".TO Registry Policies" and a "DNSSEC Policy and Practice Statement". The .TO document itself is a two-page PDF dated July 25, 2025 which requires registrars to accept both that company's general policies and the additional .TO-specific ones, and settles the pecking order bluntly: "In the event of a conflict between specific clauses in the INCO and .TO policies, the .TO policies shall govern."

That is a real exercise of authority over registrars. It is registrar-facing policy, not an appointment. The document reproduces no concession, licence, term, fee, revenue share or reporting obligation binding any operator to the Government of Tonga.

Put the two companies side by side and the record does not resolve them. One says it manages the registry and has done so since 1997. The other publishes the registry's policy in 2025. Neither document states which appoints, which subcontracts, or on what terms. Different operational roles are not necessarily contradictory — a policy administrator and an operating registry can be two hands on one machine. But nothing in the reviewed record tells a reader which hand holds what.

The ministry's own plan reaches the code and then stops

Tonga's side of the arrangement does appear in planning documents, which is more than most codes can claim. The MEIDECC Corporate Plan & Budget 2025/2026–2027/2028, hosted by the Prime Minister's Office, lists at sub-output 7.01.2 on printed page 105 the oversight, management and review of "satellite orbital and .to domain name resources", and describes oversight of .to resources and management of domain-name allocations as a planning output.

So the ministry treats the domain as an asset it oversees. What the inspected output row does not do is name a counterparty, a royalty rate, or any amount of domain-registration revenue payable to the government. The revenue wording adjacent to that output concerns satellite orbital filings and agreements — a different resource with a different commercial logic. A combined satellite-and-domain planning output is not evidence of a domain-revenue arrangement, and it should not be read as one.

What the budget pages did and did not say

The fiscal question deserved a straight answer and did not get one, which is itself worth reporting precisely.

The budget estimate for FY2025/26 opened and identified itself as a 394-page document whose contents include tables headed "Government Total Revenue by Ministry - without Budget Support". Targeted text inspection inside that file did not complete, so no .to-specific line was either located or excluded.

The Final Budget Estimate FY2026–2027 did not open at its government URL. The Ministry of Finance publication page that links the exact file was read; it displays July 14, 2026 and says nothing about .to appointment, fees or reporting.

That leaves the money question open. It does not license the sentence "Tonga receives nothing from .to", and this article will not write it. What can be written is narrower and still consequential: no reviewed document states any amount received by the Government of Tonga from .to registrations, in any currency, for any period.

Why the gap is expensive

A registrar deciding whether to carry .to needs to know which entity can change the rules mid-term. A registrant needs to know whose terms survive a corporate reorganisation. A lender or a due-diligence team looking at a registry business needs the instrument that grants the right, because a self-description is not assignable and a policy PDF is not a term sheet.

Tonga has more paper than most of its peers, and the paper is genuinely good at one end: the statute is explicit, the ministry lists the asset, the delegation row names the state. What the record lacks is the middle. The authority in section 8(d) and the duty in section 69 exist in law; the document that would show a nominated person, a term and a consideration exists somewhere else, or not at all. Nothing read here settles which.

The practical consequence is a verification asymmetry with an unusual shape. Anyone can confirm in one page that Tonga is the manager of record for .to. Anyone can confirm in another page that a company says it has run the registry since 1997. Almost nobody outside the arrangement can confirm the sentence that would join those two facts — and that sentence is the one that decides who answers for the zone. The documents behind this briefing, and the questions they leave open, sit in the .to directory entry.