The ICANN86 Policy Forum in Seville brought the global Internet governance community together to focus on practical, operational, and policy issues shaping the future of the DNS. For the ccTLD ecosystem, the discussions were less about structural expansion and more about strengthening the stability, security, and usability of country-code domains worldwide.

1. DNS Abuse Mitigation Moving Toward Policy Requirements

 A major concrete theme at ICANN86 was the ongoing GNSO Policy Development Process (PDP) on DNS Abuse Mitigation, which is actively working on defining clearer expectations for contracted parties.

Key direction discussed:

  • When registrars are expected to conduct associated domain checks for malicious registrations
  • Moving from voluntary best practices toward more structured policy expectations
  • Coordination between contract enforcement and technical mitigation efforts
  • This signals a shift from “best effort” to more defined responsibilities in parts of the DNS ecosystem. 

2. Registration Data Access (SSAD / Next-Gen Access Models)

Discussions continued on improving access to non-public registration data through evolving models such as SSAD (System for Standardized Access and Disclosure).

Key issues:

  • Making disclosure requests more predictable and auditable
  • Balancing GDPR-style privacy requirements with law enforcement needs
  • Improving consistency across registries and registrars
  • This remains a central tension point in the post-WHOIS environment.

3. DNS Abuse + AI as a Cross-Community Priority

ICANN86 plenary planning highlighted a focused session on:

  • The impact of Artificial Intelligence on DNS abuse
  • How AI is changing phishing, domain generation, and detection methods
  • This reflects a shift toward anticipating next-generation abuse patterns, not just reacting to existing ones.

4. ccNSO Sessions: Operational Resilience and Real Registry Challenges

The ccNSO agenda at ICANN86 was strongly operational in nature, including:

  • Tech Day sessions focused on registry security and DNS operations
  • Discussions on DNS resilience and regulatory impacts on ccTLD operations
  • Work on IANA-related ccTLD disaster recovery and public records
  • Case-study sharing through ccTLD News sessions

These are practical operator-focused discussions rather than high-level policy theory.

5. Root System & Security Stability Work (SSAC / RSSAC Interface)

Technical advisory discussions included:

  • Root server system expectations and operational procedures
  • Joint sessions on DNS security, stability, and resilience (SSR)
  • Continued emphasis on incident coordination across the DNS infrastructure layer
  • This reinforces that ccTLD stability is tightly linked to root and resolver ecosystem resilience.

6. Universal Acceptance & IDNs as Deployment Problems (Not Just Policy)

  •  Unlike earlier phases, UA and IDN discussions at ICANN86 were framed around real-world deployment gaps, not concept validation:
  • Enterprise and government systems still failing to support valid domain formats
  • Fragmentation in software behavior across scripts and languages
  • Continued focus on enabling multilingual Internet usability at scale

Closing Perspective

ICANN86 made one thing clear for the ccTLD community: the work is increasingly operational and implementation-heavy.

  • Rather than new structural debates, the focus is shifting toward:
  • enforceable DNS abuse policy,
  • practical registration data access mechanisms,
  • and real-world deployment of a multilingual, resilient DNS.
Contact Domgate

Explore your opportunities Let's get in touch!

Our team answers within 24 hours on working days.

Your reseller project
How would you like to connect? You can choose more than one.
Which services interest you? You can choose more than one.

Your details are used to answer you, nothing else. How we use your data · Privacy Policy

How we use your data
Your personal data: Domgate uses the details you give in this form to answer your message. Legal basis: our legitimate interest in answering you, or steps taken at your request before a contract (GDPR, Art. 6(1)(f) and (b)). They are read by the Domgate team. If you give your telephone number about sales, local presence, brand protection or our reseller programme, our team may also call you back to present our services; you may object to this at any time. To check that the form is not sent by a robot, Cloudflare (Turnstile) receives technical data from your browser, such as your IP address. We delete the entries of this form 36 months after we receive them. You may ask to access, correct or erase them, to receive them in a portable format, to restrict their use or to object to it, by writing to our data protection officer, Philippe Boos, at [email protected], and you may complain to the CNIL (cnil.fr). More in our privacy policy.