Summary

  • A 10 August 2026 letter from Texas’s State Chief Information Officer says unaffiliated people “may submit, or may have submitted” a .texas application. It does not confirm a filing or identify an applicant.
  • Texas states that it does not support and does object to .texas “and any derivative thereof,” and that it has granted no applicant support for use of the exact string.
  • ICANN’s authoritative Guidebook requires support or non-objection for an exact match of an ISO 3166-2 sub-national place name. It expressly says a string that includes but does not exactly match a defined Geographic Name is outside that evaluation gate.
  • “Derivative” is not one ICANN class. A formal RZ-LGR variant, a visually similar label, a semantically related label, a community-targeting string and a label alleged to violate legal rights follow different rules and decision paths.
  • ICANN should publish a string-scope objection receipt: one row per disclosed applied string, preserving the government’s words while naming the classification, procedural route, standing rule, evidence, decision-maker and outcome.
  • This is not a judgment that Texas’s concerns lack merit, that an application exists, that state law applies to an unidentified applicant or that ICANN will accept or reject any string.

The sentence begins cautiously and ends broadly

The two-page Texas letter is unusually useful because its first paragraph and its operative paragraph have different levels of certainty.

The first is careful. Anthony E. Sauerhoff, writing as Texas State Chief Information Officer, says he understands that people unaffiliated with the state government “may submit, or may have submitted” an application for .texas in the 2026 Round. The phrase is neither confirmation nor accusation. It records a possibility while the application list remains nonpublic.

The letter then cites the new-round rule for exact matches of sub-national place names in ISO 3166-2. It says Texas is listed with the subdivision code US-TX, and concludes that .texas requires a letter of support or non-objection from the state. On that narrow classification, the letter speaks the same grammar as the Guidebook.

The next paragraph expands the object. “At the Governor’s direction,” Sauerhoff says, Texas “does not support and does object to the application for the gTLD string ‘.texas,’ and any derivative thereof.” He argues that use without state consent could mislead the public or imply unauthorized affiliation, create confusion among residents and businesses, and risk reputational harm. The paragraph cites the Texas Constitution and two state statutes concerning deceptive practices and misuse of state insignia.

The second page closes the exact-string record cleanly: “The State of Texas has not granted support to any applicant for use of the ‘.texas’ string.” It carries Sauerhoff’s signature and copies two ICANN staff members and a National Telecommunications and Information Administration team lead. ICANN’s correspondence index records the letter as received correspondence, dated 10 August and published 14 August.

Nothing about this chain should be minimized. The signer and claimed direction are attributable. The state’s exact-string position is explicit. The public can inspect the page rather than rely on rumor.

But the six added words do not explain what a derivative is. They name no other string. They cite no application identifier. They do not say whether the term means a Root Zone Label Generation Rules variant, a label containing texas, a misspelling, a translation, a visual look-alike, a commercial phrase, or any term that evokes the state. One phrase cannot safely perform all those classifications.

No public source yet proves that an application exists

The timing prevents an easy shortcut. ICANN’s round-close announcement says the window closed at 23:59 UTC on 12 August, two days after the letter. More than 1,600 primary applications had been received, and more than 1,100 included replacement strings. The total remained provisional pending payment.

The same announcement says ICANN would conduct an Administrative Check before publishing the public-facing portions on Reveal Day. Absent extraordinary circumstances, that list was expected no later than nine weeks after the window closed. The 2026 Round resources page similarly places publication and string confirmation in the pre-evaluation sequence.

At the 1 September evidence cutoff, the disclosure had not occurred. The letter’s “may submit, or may have submitted” remains the right public tense.

The plural word “Applications” in its subject line cannot be turned into a count. The statement that Texas granted no support cannot identify someone who sought it. The absence of .texas from the current IANA Root Zone Database shows only that the label is not a delegated top-level domain at this time; an operational root ledger is not an application queue. Nor does publication by ICANN transform external correspondence into an evaluation result.

This restraint matters for fairness as well as accuracy. Naming a speculative applicant would attach a government accusation to an entity before ICANN releases the underlying application. Pretending no application can exist would be equally unwarranted. The correct state is not yet publicly disclosed.

The exact match has a real consent rule

ICANN’s Applicant Guidebook homepage identifies V2-2026.04.24 as the authoritative current English version. Its complete text and searchable Module 7 create a specific—not atmospheric—government role.

Section 7.5.2 defines four kinds of Geographic Names that require documentation. The relevant item is an applied-for string that is an exact match of a sub-national place name, such as a county, province or state, listed in ISO 3166-2. ICANN’s plain-language geographic-names FAQ repeats that exact-match condition.

An applicant bears responsibility for identifying the category, consulting the relevant governments or public authorities and determining which level of support is required. The national administration determines the appropriate governmental level or agency. The documentation should be a signed letter clearly expressing support or non-objection and showing an understanding of the requested string and its intended use.

A government is under no obligation to provide such a letter. If required support is absent, the application cannot simply be waved through the Geographic Names Review. The Guidebook provides a defined Extended Evaluation route for missing or incomplete documentation, but not a right to compel a state to consent.

The Geographic Names Panel reviews all applied-for strings, not merely those self-declared as geographic. It identifies the applicable category, determines relevant authorities, and checks whether required communication is legitimate and contains the required material. It can contact the signer to confirm intent and understanding.

ICANN’s 2026 Panel procurement overview makes the evidentiary work more concrete. The expected provider would verify a communication’s legitimacy, the signatory’s authority and intent, and compliance with the Guidebook; ask clarifying questions where needed; write reasoned determinations; and retain the record for at least five years.

This is substantial authority, but it is bounded. If .texas appears as an applied string and the Panel confirms the classification and relevant authority, Texas’s refusal would be consequential by design. The Article is not asking ICANN to dilute that rule.

The Guidebook draws the line immediately afterward

The limit sits one paragraph below the category list. Strings that include but do not exactly match a Geographic Name defined in the section “will not be considered Geographic Names.” Therefore, the Guidebook says, they do not require government support or non-objection during the evaluation process.

That sentence prevents “and any derivative thereof” from becoming an automatic extension of Section 7.5.2. A government can object to another label. It can cite law, confusion, community detriment or public policy. But the Geographic Names Panel must not silently treat every related label as if it were the ISO entry itself.

The boundary serves a practical purpose. Geographic resemblance can extend indefinitely. texasbank, texan, a nickname, a translation, a tourism phrase and a visually similar string have different relationships to the state. If any association were enough to trigger exact-match consent, the external ISO list would become the starting point for an unpublished family of reserved words. Applicants could not know the perimeter from the Guidebook; governments could enlarge it letter by letter; the Panel would be deciding a rule that the public instrument did not state.

The opposite overreaction would also be wrong. Being outside Geographic Names Review does not make a string immune from every other mechanism. It means only that one exact-match gate does not apply. The concern must travel through the route designed for its actual claim.

“Variant,” “similar” and “derivative” are not synonyms

The Guidebook already defines one adjacent term with precision. In Section 7.6, a variant string is considered the same as a primary string by the relevant script community under the RZ-LGR. An applicant seeking an allocatable variant must justify it. A Geographic Name IDN and its applied-for variants are subject to corresponding documentation requirements.

This technical concept cannot be replaced with an ordinary-language intuition. The Article has no Panel result showing that .texas has an allocatable variant and makes no such claim. If a future application contains a formally generated variant, its RZ-LGR status should be recorded and reviewed under the variant rules. If it does not, calling it a “derivative” cannot manufacture that status.

Visual similarity is another separate object. ICANN’s String Similarity Evaluation page describes a manual assessment, supported by pre-screening data, designed to prevent confusion and loss of confidence from visually similar strings in the root. That process compares labels and their variants under specific guidelines. It does not hand a state title to every string that resembles its name.

Formal String Confusion Objections can extend beyond visual resemblance to aural or meaning similarity, but the Guidebook’s Module 4 attaches standing and adjudication rules. The objector must identify the exact applied string and use the applicable dispute provider. Similarity is argued, not presumed by correspondence.

Legal Rights, Limited Public Interest and Community are three other objection grounds. Each has a different claimant and test. A Community Objection, for example, requires an established institution associated with a clearly delineated community and proof of four elements: a delineated community, substantial opposition, strong association with the string and likely material detriment. A government letter may become evidence. It is not the complete test or the decision.

The Texas letter’s statutory references also need their own evidentiary lane. The state could later argue that a specific applicant, proposed use or representation implicates a law. The applicant could answer. A competent panel, regulator or court could decide within its jurisdiction. None of that can be done now without the string, applicant, application text and proper forum. Reporting the citations is not adjudicating them.

GAC channels preserve concern without collapsing authority

Governments have additional ICANN routes after applications become public. Module 4 permits GAC members and observers to issue a GAC Member Early Warning identifying why an application appears sensitive or problematic, including potential national-law concerns. The notice should explain how the applicant might address the concern and provide a contact for dialogue.

An Early Warning has no direct impact on the application. It is a signal, not a veto. It can prompt engagement, an application change, withdrawal, later GAC Consensus Advice or an objection. The Guidebook separately says GAC consensus is not required to issue an individual warning.

GAC Consensus Advice is a different instrument. It must be clearly labeled as such, contain a rationale and operate through the Board process. The Board considers it, and the applicant receives a response opportunity. Combining a state letter, one member’s warning and collective advice into “the government objected” would erase three different authority thresholds.

These channels demonstrate why Texas need not fit every concern inside Section 7.5.2. The exact match has a documentation gate. A non-exact label may generate national-law or sensitivity concerns. A community may allege detriment. A rights holder may invoke legal rights. ICANN can hear each claim without pretending they are the same claim.

Publish one receipt row per real string

The repair is a string-scope objection receipt. It should begin only after an applied string is public; before that, ICANN can index correspondence as general input without implying that a filing exists.

The first fields freeze the object: application identifier, exact primary string, A-label and U-label where relevant, replacement-string state, and every formally applied allocatable variant with its RZ-LGR basis. An ordinary-language “derivative” should remain quoted in the source field, not copied into the variant field.

The next fields record the claimed authority. They should identify the government or public authority, signer, asserted competence, letter date, receipt date, publication date and whether the document supports, does not object, objects, withdraws a prior position or supersedes another letter. The government’s scope should be reproduced accurately, including broad language.

ICANN should then classify each exact applied string. Does it enter Geographic Names Identification? If so, under which category and external-list entry? Does it proceed to Geographic Names Review? Is the concern instead visual similarity, a formal objection, application comment, Early Warning, GAC Advice or a matter outside the program’s evaluative gate? A single label may encounter several routes, but each route needs its own row and state.

For a formal objection, the receipt should name the standing rule, evidentiary standard, dispute provider, filing date, applicant response and panel result. For a GAC instrument, it should distinguish individual warning from consensus advice and record the Board response. For a legal claim, it should link the actual filing and decision while refusing to treat an allegation as judgment.

Finally, the receipt needs correction and supersession history. A later Texas letter could narrow, replace or withdraw the position. A Panel could ask who “derivative” was intended to cover. A disclosed application could show that no related label exists. None of those later facts should silently overwrite the 10 August record.

This design does not ask ICANN to reveal applications before its published lifecycle permits. The pre-disclosure record can carry a confidentiality state. Once application data is public, every claim can be attached to the object it concerns.

The state’s concern is strongest when its route is named

Texas’s worry about implied official affiliation is understandable. A top-level label can appear on public-facing services, email addresses and campaign material. Residents may read a geographic string as a signal of connection, even when registry terms deny one. ICANN should not dismiss that risk merely because a phrase is broader than Section 7.5.2.

But a concern becomes more reviewable, not less legitimate, when its perimeter is explicit. For exact .texas, the state can point to the ISO rule and refuse support. For a different applied string, it can identify the label, the representation it expects, the community or right affected, the evidence and the channel that can produce a reasoned result. The applicant can then answer the claim actually made.

The Panel gains protection too. It need not improvise a derivative-name doctrine from correspondence. It can respect the exact gate, preserve external input and refer each residual issue to the instrument that supplies authority. Written classification explains why two similar-looking cases may follow different paths.

The point is not that the Guidebook is the only source of law or public power. It is that ICANN’s evaluation power must remain legible inside the program it administers. Texas can preserve independent state-law positions. ICANN can preserve its exact-match rule. Neither needs to absorb the other.

Sources

  1. Anthony E. Sauerhoff to Marika Konings, 10 August 2026
  2. ICANN Correspondence
  3. Applicant Guidebook homepage
  4. 2026 Round Applicant Guidebook V2-2026.04.24
  5. Applicant Guidebook Module 7
  6. ICANN 2026 Round Closes with More Than 1,600 New gTLD Applications
  7. 2026 Round Resources
  8. Geographic Names Panel and Reserved Names Panel RFP project overview
  9. Which types of strings are considered Geographic Names?
  10. String Similarity Evaluation
  11. Applicant Guidebook Module 4
  12. Texas DIR executive biographies
  13. IANA Root Zone Database
  14. Lu Heng, The Policy Mirror