Primary Domain
Internet Governance and Routing
Within the Primary Domain facet, Internet Governance and Routing intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Global Regional ISP
ROYA’s AS210837: What Would Prove Operational Control and Durable Repair?
ROYA’s AS210837: What Would Prove Operational Control and Durable Repair? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Global Institutional
ISC’s Five Control Surfaces: What the Public Record Can—and Cannot—Prove
Internet Systems Consortium, Inc. appears across some of the Internet’s most consequential technical systems: BIND and Kea software, an F-root role, Internet-number registry records, observed routing and RPKI authorization. Those appearances are important, but they do not…
ICANN
Where ICANN's Authority Becomes Operational Control
ICANN is often described as a coordinator of Internet identifiers. That description is accurate but incomplete. Its practical authority is assembled across several instruments: corporate purpose, Bylaws, registry agreements, registrar accreditation contracts, compliance…
Global Institutional
INFINITYWIFI and AS210057: Who Can Correct the Record—and Who Can Remedy a Failure?
INFINITYWIFI and AS210057: Who Can Correct the Record—and Who Can Remedy a Failure? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
ICANN
ICANN’s Authority Has Five Separate Links
ICANN’s practical power is easiest to misunderstand when mission, policy, contract, implementation and review are treated as one thing. Its public materials describe a mission centred on Internet unique-identifier coordination, while its agreements and procedures show how…
ICANN
ICANN’s Authority Is Contractual Before It Is Public
ICANN can influence the global identifier system without being a government and without possessing unilateral control over every technical action that follows its decisions. Its authority is assembled from several instruments: corporate bylaws, operational agreements, registry…
ICANN
ICANN’s Authority Is a Chain, Not a Sovereign Grant
ICANN can shape the global identifier system without possessing a general public-law mandate over the internet. Its authority changes form as it moves from corporate purpose to Bylaws, from multistakeholder policy to contractual obligation, and from contract to technical…
IETF
IETF-W3C Is Not One Institution: Authority Depends on the Instrument
The label IETF-W3C suggests a single governance center. The public record describes something more fragmented: the IETF standards process, the IETF Administration LLC, and W3C’s technical and membership structures assign different powers to different bodies. That distinction…
ICANN
ICANN’s Remedies Are Not One Appeal: Who Can Stop, Review or Reverse a Decision?
ICANN’s accountability system does not place every objection on one appellate ladder. It distributes authority among the Board, the Empowered Community, ICANN’s staff-facing reconsideration process and an independent review panel. The practical question is therefore not simply…
Story
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove
DATAMATIX and AS210973: What Public Routing Evidence Can—and Cannot—Prove intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
ICANN
Fifth Allocatable Variant Triggers Full Evaluation Fee
For new applicants, ICANN’s 2026 fee structure includes up to four variant strings, then charges the full evaluation fee for each additional allocatable variant.
ICANN
A Submitted gTLD Application Still Has a Seven-Day Fee Clock
A timely gTLD submission is not complete for processing until ICANN receives the evaluation fee within the separate payment window.
ICANN
Administrative Check Is a Filing Gate, Not a Merits Decision
ICANN’s Administrative Check verifies filing facts and prepares identical-string sets; it does not approve an application on its merits.
ICANN
One RSP Evaluation Can Cover Many gTLDs—Only for Qualified Services
One evaluation may be reused across gTLDs, but ICANN qualification remains tied to specific registry services.
ICANN
RSP Coverage Is a Function Map, Not a Provider Count
An applicant can name several Registry Service Providers and still leave a critical registry function uncovered. ICANN’s 2026 Round framework is role-specific: Main, DNS, DNSSEC and optional Proxy RSPs carry different functions and different limits on how many may serve a gTLD.
ICANN
Naming an RSP Is Not Contracting Confirmation
An applicant can identify a Registry Service Provider in its application, while ICANN separately seeks confirmation from that provider during contracting. The applicant’s selection, ICANN’s request and any actual RSP response are distinct evidence events.
ICANN
RSP Selection Can Wait Until Evaluation, Not Indefinitely
ICANN’s 2026 rules allow an applicant to submit without naming Registry Service Providers, but that flexibility narrows at evaluation: minimum critical registry functions must be covered, or Extended Evaluation may provide more time.
ICANN
Variant-String Sets Enter Contention Together, Not String by String
ICANN’s 2026 rules treat a primary string and its applied-for allocatable variants as one contention unit when different applicants seek strings from the same variant-string-set. That changes how applicants should map competitive exposure.
ICANN
Existing gTLD Variant Applications Receive Processing Priority, Not Approval
ICANN gives one class of applications an earlier place in the processing order: allocatable-variant applications for existing gTLDs from the 2012 Round. That priority changes sequencing, not the substantive outcome.
ICANN
Existing gTLD Variants Bring the Registry Under One 2026 Agreement
An operator seeking allocatable variants of an existing gTLD is not adding isolated labels to an unchanged contract. ICANN’s 2026 rules require a transition to the new Base Registry Agreement and place the existing gTLD and its variants under one agreement.