Topic starter
24/06/2026 7:20 pm
TL;DR: ICANN’s 2026 new gTLD round will add another wave of domain namespaces, with more than 1,200 new options introduced in the last expansion and registry operators expected to prove both financial and technical capability, according to DigiCert. Domain identity, DNS, PKI, and email authentication now have to be governed as one trust surface, not separate teams.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “The next wave of new gTLDs is coming in 2026”.
By the numbers:
- The 2012 New gTLD Program introduced more than 1,200 new domain options, including IDNs and names like .futbol and .pizza.
Key questions
Q: How should security teams govern new gTLDs as part of digital trust?
A: Security teams should treat each domain as a governed identity asset, not a standalone technical asset.
Q: Why does domain expansion increase trust and fraud risk?
A: Because more namespaces create more opportunities for inconsistency between the domain’s registration state, its technical resolution, and the trust signals users rely on.
Q: What breaks when DNS, certificates, and email authentication are run separately?
A: Trust becomes fragmented.
Practitioner guidance
- Define domain lifecycle governance Map domain registration, delegation, renewal, certificate coverage, and email authentication to named owners and review cadences so no namespace sits outside accountable control.
- Unify DNS, PKI, and email authentication Establish one operating model for DNS integrity, certificate trust, and domain-based message authentication so policy gaps do not emerge between teams.
- Assess registry provider assurance Require evidence of operational resilience, availability commitments, and security controls from the registry service provider before supporting a new gTLD application.
Bottom line: New gTLD expansion changes domain governance by increasing the number of identities and operators that security teams have to manage.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
25/06/2026 4:34 am
New gTLDs turn domain identity into an identity-governance problem, not a naming exercise. The article is right to frame domains as anchors of digital identity, because namespace growth creates more trust decisions, more operators, and more lifecycle events to govern. For security leaders, the issue is not whether a domain exists, but whether the organisation can prove control, authenticity, and continuity across that domain’s full lifecycle. The practitioner conclusion is that domain governance now belongs in the identity programme, not only in web operations.
A question worth separating out:
Q: How do security teams evaluate a registry service provider for a new gTLD?
A: They should assess whether the provider can sustain availability, technical operation, and secure delegation at the namespace level. In practice, that means treating the provider as part of the control environment and not as a purely commercial choice.
👉 Read our full editorial: New gTLDs in 2026 raise the stakes for domain identity
This post was modified 4 days ago by NHI Mgmt Group