For domain owners, resellers, hosting providers and businesses managing larger portfolios, the meeting is worth watching because several ongoing policy, operational and technical discussions could influence how domains are registered, transferred, protected and managed in the future.
Many of the topics below are still in policy development, consultation or implementation. Discussion at ICANN87 does not by itself create a new requirement for registrants or registrars.
At NiceNIC, we are monitoring these developments and will distinguish between proposals, adopted policies and requirements that have actually entered into effect.
Customers who want to understand NiceNIC's current registrar information, policies and public handling standards can review the NiceNIC Trust Center. For information specifically about DNS Abuse reports, review processes, ClientHold, ServerHold and portfolio monitoring, see Domain Abuse Handling & Transparency.
1. DNS Abuse Mitigation: Associated Domain Checks Are Still Under Discussion
One of the most closely watched policy topics ahead of ICANN87 is the DNS Abuse Mitigation Policy Development Process 1, often referred to as DNS Abuse Mitigation PDP1.
The current Initial Report focuses on what ICANN calls Associated Domain Checks.
The working group was chartered to consider whether registrars should have an obligation to investigate other domains associated with a customer account or registrant when actionable evidence shows that at least one domain is engaged in DNS Abuse as defined under the applicable ICANN registrar framework.
The Initial Report currently contains:
- eight Preliminary Recommendations; and
- five Implementation Guidances.
Public Comment is scheduled to close on September 28, 2026 at 23:59 UTC, after which the working group is expected to begin reviewing and analyzing public comments at ICANN87.
What does this mean for domain owners today?
It does not mean that every domain associated with an account must now be suspended or restricted.
The document is an Initial Report, not a final Consensus Policy, and the current work concerns investigation of associated domains following actionable evidence of DNS Abuse.
The eventual requirements may change as the working group reviews public comments and continues the policy-development process.
For customers and resellers, the practical principle remains straightforward: keep domain accounts secure, respond promptly to legitimate abuse notifications, and investigate compromised websites, credentials or services when a security incident occurs.
NiceNIC's current public abuse-handling framework explains how reports are reviewed, what different case statuses mean and what affected customers or resellers can do next. See NiceNIC Domain Abuse Handling & Transparency.
NiceNIC will continue to monitor the policy process and update its procedures where required if and when applicable requirements are formally adopted and become effective.
2. The 2026 New gTLD Round Is Moving Into Its Next Phase
ICANN’s new generic top-level domain program is also entering an important period.
The 2026 Round application window closed on August 12, and ICANN reported receiving more than 1,600 new gTLD applications.
The next major milestone is Reveal Day.
According to the current Applicant Guidebook and ICANN’s pre-evaluation documentation, Reveal Day is expected after the administrative-check stage and, absent extraordinary circumstances, no later than nine weeks after the application submission period closes.
ICANN is expected to publish information including:
- applied-for gTLD strings;
- public portions of applications; and
- initial contention sets involving identical strings.
The precise timing remains subject to ICANN’s process and application volume.
Does Reveal Day mean the new extensions will immediately become available?
No.
An application appearing on Reveal Day is not the same as a delegated TLD that customers can immediately register.
Applications still have to move through the relevant evaluation, objection, contention, contracting and technical processes before successful strings may eventually enter the DNS.
For registrants, domain investors, hosting providers and resellers, however, the public list should provide the first much clearer view of what the next generation of gTLD inventory may look like.
NiceNIC already supports a broad range of existing new generic extensions through its New gTLD Domain Search, while availability of any future extension will depend on successful delegation, registry launch plans and registrar integration.
Customers can also use the main NiceNIC Domain Search to check currently available domain extensions and pricing.
NiceNIC will be watching the new strings, their intended uses and their potential relevance to businesses, resellers and international domain users.
3. Registration Data and Urgent Disclosure Remain Important Areas to Watch
Registration data continues to be another important area of ICANN policy and implementation.
On May 12, 2026, ICANN revised the Registration Data Policy to include a response timeline for certain urgent lawful disclosure requests for nonpublic gTLD registration data from authenticated requestors.
The revised policy describes a 24-hour response timeline for qualifying urgent requests.
There is an important limitation, however:
ICANN states that this urgent-request policy language will not take effect until the required law-enforcement authentication mechanism has been implemented.
ICANN is currently working on a proof of concept for authentication, while the Registration Data Request Service, or RDRS, is continuing beyond its original pilot period.
Does this mean nonpublic WHOIS data will become public?
No.
These discussions concern processes for requesting and, where appropriate, lawfully disclosing nonpublic registration data.
They are not the same as making nonpublic registrant information publicly visible in WHOIS or RDAP.
Domain owners should therefore avoid interpreting every registration-data discussion as a change to public WHOIS visibility.
NiceNIC customers can review how domain privacy currently works, including the fact that privacy availability can depend on the applicable TLD or registry policy, in NiceNIC's Domain Privacy FAQ.
NiceNIC will continue following the applicable registration-data requirements and any future implementation guidance as this work develops.
4. Domain Transfers, Privacy Services and IDNs Are Also in the Implementation Pipeline
Not every important ICANN topic is being decided at ICANN87.
Some projects are already in different stages of policy implementation.
ICANN’s current implementation status includes work relating to:
- Privacy and Proxy Services Accreditation;
- Internationalized Domain Name policy implementation; and
- Transfer Policy Review.
ICANN87 Prep Week also includes a session titled “Policy Implementation and Reviews: What’s New and What’s Next.”
Why should customers care?
Over time, implementation work in these areas can affect practical registrar workflows such as:
domain transfers,
privacy and proxy services,
registration data handling,
and internationalized domain support.
But customers should not assume that an ICANN87 discussion automatically changes how their domain works the following day.
Customers who need to register, transfer or manage a domain under the rules in effect today can use the NiceNIC Domain Center, where current registration, renewal and transfer options are shown.
NiceNIC will continue distinguishing between proposals, adopted recommendations, implementation work and requirements that have actually reached an effective date.
5. Universal Acceptance Is Becoming More Important as the Domain Namespace Expands
On September 9, 2026, ICANN published the final Guidelines for Advancing Universal Acceptance Adoption developed by its Universal Acceptance Expert Working Group.
Universal Acceptance, commonly abbreviated as UA, addresses whether software and online systems correctly accept and process valid domain names and email addresses across the full DNS.
This matters particularly for:
newer domain extensions,
internationalized domain names,
non-ASCII scripts,
and email addresses using newer or internationalized naming formats.
The September guidelines should not be confused with a new customer registration requirement.
They are intended to help advance Universal Acceptance across the Internet ecosystem.
For NiceNIC customers, this topic becomes increasingly relevant as more businesses use new gTLDs, country-code domains and internationalized domain names across websites, forms, email services and applications.
A valid domain should not become unusable simply because a third-party form or application was built around outdated assumptions about what a domain name can look like.
NiceNIC will continue monitoring Universal Acceptance developments and practical compatibility issues affecting domain users.
Customers looking for currently available extensions can browse more than 2,500 TLD options through the NiceNIC Domain Center.
6. Contractual Compliance Updates Are Worth Watching, Without Predicting Their Outcome
ICANN87 Prep Week also includes a Contractual Compliance Update session.
Ahead of the session, it would be premature to predict whether ICANN will announce any particular new enforcement priority or operational interpretation.
However, compliance updates are relevant to registrants, complainants, resellers and registrars because they can help clarify how existing contractual requirements are being interpreted and enforced in practice.
NiceNIC publishes information that customers, abuse reporters, resellers and other parties can independently review through the NiceNIC Trust Center.
For DNS Abuse specifically, the Domain Abuse Handling & Transparency page explains report handling, case statuses, evidence expectations and the distinction between registrar-level and registry-level domain statuses.
NiceNIC will review published ICANN session materials, recordings and follow-up documentation for developments that may materially affect customer-facing processes.
Where an actual policy, contractual requirement or implementation change applies, we will update the relevant public documentation accordingly.
7. One Important Technical Date Comes Before ICANN87: The Root KSK Rollover
There is also an important DNS infrastructure event occurring shortly before ICANN87.
On October 11, 2026, the new root-zone DNSSEC Key Signing Key, known as KSK-2024, is scheduled to become the active signing key for the DNS root.
This is not an ICANN87 policy decision.
It is a planned technical DNSSEC operation.
ICANN specifically advises operators of DNSSEC-validating recursive resolvers to verify that KSK-2024, Key Tag 38696, is present in their trust-anchor configuration rather than simply assuming that automated updates succeeded.
Do ordinary domain registrants need to change their domains?
ICANN’s preparation guidance is directed primarily at operators of DNSSEC-validating resolvers and relevant DNS software or network infrastructure.
If you operate such infrastructure yourself, you should review ICANN’s technical guidance before October 11.
Customers whose resolver infrastructure is operated by an ISP, hosting company, cloud platform or other provider should follow the guidance of that operator where applicable.
The KSK rollover does not mean that every domain owner needs to modify their domain’s DNS records or nameservers.
If a NiceNIC customer experiences a domain-management or DNS-related issue and needs account-specific assistance, the NiceNIC Support Center remains available for troubleshooting.
What NiceNIC Customers Should Do Before ICANN87
For most domain owners, no immediate domain configuration change is required simply because ICANN87 is approaching.
Instead, the practical steps are to:
- keep account and domain contact information current;
- maintain strong account security;
- review and respond to legitimate domain-security or abuse notifications when necessary;
- watch for official announcements before assuming that a proposal has become a rule; and
- if you operate DNSSEC-validating resolver infrastructure, verify readiness for the October 11 root KSK rollover.
Resellers and hosting providers managing larger portfolios should also make sure they can identify affected customers and domains when policy, security or registry-specific actions require attention.
Businesses that manage customer domains at scale can review the NiceNIC Domain Reseller Program, including reseller pricing, bulk domain management, API and WHMCS workflows.
A Note About gTLD and ccTLD Rules
Not every ICANN policy development applies to every domain extension in the same way.
The Generic Names Supporting Organization, or GNSO, develops substantive policies relating to generic top-level domains (gTLDs), while country-code top-level domains operate under different policy structures and registry-specific requirements.
A discussion affecting .COM, .NET or another gTLD should therefore not automatically be assumed to create an identical rule for .UK, .DE, .CN, .AU or another ccTLD.
This distinction is especially important for domain owners managing international portfolios, where registration, verification, transfer, renewal, privacy and DNS requirements can vary significantly by registry.
NiceNIC will continue separating ICANN-wide developments, gTLD requirements and registry-specific ccTLD rules in our customer guidance.
How NiceNIC Will Follow ICANN87
ICANN87 is a multistakeholder meeting, not a single policy announcement.
Some discussions may produce new direction. Others may simply report progress on work already underway.
NiceNIC will therefore evaluate developments using three questions:
What has actually been decided?
When does it become effective?
What, if anything, does a domain owner or reseller need to do?
When a development creates a concrete customer impact, we will update the relevant NiceNIC support, policy or Trust Center documentation.
Until then, we will avoid presenting proposals as final requirements.
Frequently Asked Questions
Will ICANN87 immediately change how my existing domains work?
Not simply because a topic is discussed at the meeting.
Many ICANN policy changes go through policy-development, Board consideration and implementation processes before they become applicable requirements.
Does the DNS Abuse PDP mean every domain in an account can automatically be suspended?
No.
The current PDP1 Initial Report concerns potential obligations to investigate associated domains when there is actionable evidence of DNS Abuse.
It is still an Initial Report and does not itself create an automatic suspension rule for every associated domain.
Customers or resellers dealing with an existing NiceNIC abuse case can review the current handling process through Domain Abuse Handling & Transparency.
Are these DNS Abuse proposals already final?
No.
The Initial Report remains in the policy-development process, with Public Comment scheduled to close on September 28, 2026.
Will ICANN's urgent registration-data rule make my private information public?
The current work concerns lawful requests for disclosure of nonpublic gTLD registration data.
It is not the same as publishing nonpublic information in public WHOIS or RDAP.
ICANN has also stated that the new urgent-response requirement will not become effective until an authentication mechanism has been implemented.
For information about NiceNIC's current domain privacy service and TLD-specific limitations, see the Domain Privacy FAQ.
Will the new gTLDs shown on Reveal Day be immediately available to register?
No.
Reveal Day identifies applications and applied-for strings.
Applications still need to progress through the applicable ICANN processes before a successful new gTLD may eventually be delegated and offered for registration.
Existing new gTLDs that are already available can be searched through the NiceNIC New gTLD Domain Search.
Does the October KSK rollover mean I need to change my nameservers?
Not simply because of the rollover.
ICANN’s readiness guidance specifically focuses on operators of DNSSEC-validating resolvers verifying the new root trust anchor.
Final Takeaway
The most useful way to follow ICANN87 is not to ask:
“What will ICANN change?”
It is to ask:
“Which proposals are still being discussed, which policies have already been adopted, which changes have an effective date, and what action is actually required?”
That distinction matters for registrants, resellers, registries, registrars and anyone responsible for operating domains at scale.
NiceNIC will continue monitoring ICANN87 and related policy developments and will update customer guidance when confirmed changes create a practical impact.
Information in this article reflects publicly available ICANN materials available at the time of publication. Meeting schedules, policy proposals and implementation timelines may change. Where an official ICANN policy, registry rule, agreement, applicable law or later update governs a specific matter, that authoritative source takes precedence.
