Summary

  • The IANA root zone database names NIC-MG (Network Information Center Madagascar) as the .mg ccTLD Manager, gives an Antananarivo postal address, and records a registration date of 1995-07-25 with a last update on 2025-10-02.
  • NIC.MG's own website states in French that it is the official manager of .mg domain names and has been for more than 30 years; that is an affirmative claim by the interested party, not an independently established fact.
  • No delegation instrument, contract, statute, gazette notice or national designation document for the .mg registry was obtained in this review, so the legal basis, scope, effective date and renewal terms of the role are not established here.

A country-code top-level domain looks, from the outside, like a piece of plumbing. A two-letter string sits in the root zone, a name server answers, a WHOIS port replies. The plumbing is real and it is documented. What sits behind the plumbing — who may decide, on what authority, and with what remedy for the person on the receiving end of a decision — is a different kind of record, and for .mg that record is thin.

Start with what the root zone actually certifies. The Internet Assigned Numbers Authority maintains a database entry for .mg that names the ccTLD Manager as "NIC-MG (Network Information Center Madagascar)" and gives a postal address at Tanà Water Front, Esc A, Ambodivona, Antananarivo 101, Madagascar (IANA root zone database, .mg). The same entry records a registration date of 1995-07-25 and a last-updated date of 2025-10-02. Its Registry Information section lists www.nic.mg as the URL for registration services, whois.nic.mg as the WHOIS server and rdap.nic.mg as the RDAP server.

That is a technical record, and it is worth being precise about what it does and does not do. It identifies who is expected to answer for the zone. It does not, by itself, establish a contractual or statutory basis for that expectation, and a root-zone registration date is not evidence that the same operator has run the zone continuously since 1995. The IANA entry is the map, not the title deed.

Now read the registry's own account. NIC.MG's website carries a single French sentence that does the institutional work: "NIC.MG est le gestionnaire officiel des noms de domaine en .mg depuis plus de 30 ans. Il collabore avec les bureaux d'enregistrement nationaux et internationaux pour développer l'extension .mg." (NIC.MG). Translated: NIC.MG is the official manager of .mg domain names and has been for more than 30 years, and it works with national and international registrars to develop the extension.

That sentence is the whole public institutional case, and it is a first-party statement. It is not worthless — a registry that has operated a zone for three decades has plainly done something right, and the sentence is consistent with the IANA record. But "gestionnaire officiel" is doing a great deal of unexamined work. It could describe technical operation of the name servers. It could describe registry administration, the business of accepting registrations and maintaining the database. It could describe a governmental designation, a legal delegation, or some combination of all three.

The reviewed material does not say which, and the difference matters enormously to anyone who needs to challenge a decision.

Consider the position of a registrant whose .mg name is refused, suspended or transferred. To mount a challenge, that person needs to know who decided, under what rule, and before which forum. A technical delegation record tells them which organisation runs the zone. It does not tell them whether that organisation is exercising a delegated public function, a private contractual right, or an administrative discretion — and those three answers point to three different remedies.

Where the designation instrument is not public, the registry's own account of its mandate becomes the de facto record, and the practical answer to "who decides" collapses into whoever holds the zone file.

There is a second authority track here, and it is important not to confuse the two. BTW's own directory record for the entity rests on a single evidence basis: AFRINIC's public member directory, which lists NIC-MG as a member registered or based in Madagascar (AFRINIC membership). That listing was obtained in this review only as a provider summary, without a verbatim member row, and it answers a number-resource question — whether the organisation holds AFRINIC membership — not a domain-name question. AFRINIC membership neither confirms nor contradicts the .mg delegation. It is a separate institutional relationship with its own rules, fees and obligations, and treating the two as one authority would be a category error.

What the review could not obtain is the part that would settle the question. No delegation instrument or legal designation for the .mg registry was obtained. No national statute, gazette notice or regulator instrument addressing .mg was obtained. No registry policy, price schedule, dispute-resolution procedure or registrar accreditation rule was obtained. Those are retrieval outcomes, and they establish non-access only. They do not establish that no such instrument exists, that NIC.MG lacks authority, that any record contradicts NIC.MG, or that anyone concealed anything.

An incomplete source set creates an unresolved evidentiary state, not a verdict.

The honest public formulation is therefore narrow and it is worth stating plainly: NIC.MG describes itself as the official manager of .mg, a role it says it has held for more than 30 years. This review did not independently verify that status, because the designation instrument and any underlying legal text were not obtained. The AFRINIC material addresses a different function and neither confirms nor disproves the delegation.

That formulation is unsatisfying, and the dissatisfaction is the point. A registry is not an ordinary business. It holds a namespace that other people's businesses, brands and correspondence depend on, and it exercises powers — to accept, to refuse, to price, to suspend — that no ordinary business enjoys over its customers' identifiers. Institutions that exercise those powers are usually expected to publish the instrument that grants them, not because paperwork is virtuous, but because the instrument is what makes the power reviewable. A registrant cannot appeal to a sentence on a homepage.

There is a fair counter-argument, and it deserves a hearing. For many ccTLD operators, especially small national registries that grew out of volunteer technical communities in the 1990s, a technical delegation plus three decades of uninterrupted operation is the ordinary and adequate public account. Demanding a published statutory instrument may impose a standard that a company-law jurisdiction can meet and a small registry operating under informal ministerial tolerance cannot. The absence of a published instrument may reflect administrative culture rather than any defect in authority.

Both readings are available on the evidence reviewed here, and choosing between them is not this article's job. What can be said is that the choice is currently unavailable to the public. The material that would let a reader decide — the designation, the contract, the statute, the gazette notice — was not obtained in this review, and the registry's own site does not supply it. Until it is supplied, the .mg authority chain rests on a technical record and a sentence, and the gap between them is where the governance risk lives.