ICANN Publishes First Evaluated RSP List: What gTLD Applicants Need to Know

ICANN has published the first List of Evaluated Registry Service Providers (RSPs) for the 2026 new gTLD round, marking an important milestone for organisations planning to apply when the application window opens in April 2026.

For the first time, applicants now have clear, official visibility into which backend registry providers have progressed through ICANN’s technical evaluation process, and which are still completing it.

Summary List – view the full table below.

Why This Matters for New gTLD Applicants

Most new gTLD applicants rely on a third-party Registry Service Provider (RSP) to operate the technical backbone of their TLD, including:

• DNS and Anycast infrastructure

• DNSSEC signing

• RDAP / WHOIS services

• Registry systems and EPP

• Data escrow and compliance reporting

Until now, applicants had limited, fragmented insight into which providers had formally cleared ICANN’s technical checks. That uncertainty made backend selection harder, and introduced avoidable risk into application planning.

This newly published list changes that.

What the Evaluated RSP List Includes

The list published by ICANN shows two key categories of providers:

• RSPs that have fully cleared both technical screening and Registry System Testing (RST)

• RSPs that have cleared screening and are still completing technical testing

ICANN has also confirmed that earlier technical testing issues have now been resolved, allowing previously stalled RSP applicants to move forward.

To make this easier to interpret, we’ve summarised the results in the table above, with “Main” shown as the primary signal and additional services (DNS, DNSSEC, Proxy) displayed for context.

What gTLD Applicants Should Do Now

If you’re planning to apply in the 2026 new gTLD round, this list should now feed directly into your planning.

Your chosen RSP is fully evaluated:
You can confidently name them in your application and significantly reduce the risk of technical evaluation delays.

If your RSP is still in progress:
You may still proceed, but you should actively monitor their testing status and ensure you understand the implications if timelines slip.

You haven’t chosen an RSP yet?
ICANN strongly encourages applicants to identify a successfully evaluated provider where possible. While it remains optional to name an RSP at submission, doing so can simplify and accelerate evaluation

What’s Coming Next From ICANN

ICANN has also confirmed that:

• IDN services and additional registry services will be added to the evaluated RSP list in early March 2026

• A second RSP evaluation period will run concurrently with the April 2026 application window

• The list will be updated on an ongoing basis as providers complete evaluation

In short: this is a living reference point, not a one-off publication.

Choosing the Right Registry Service Provider Still Matters

While ICANN’s evaluation confirms technical readiness, it doesn’t tell you whether an RSP is the right fit for your specific TLD.

That’s where strategy comes in.

Different TLD models place very different demands on a backend provider:

• .brand TLDs prioritise control, security, and bespoke workflows

• Open or generic TLDs need registrar reach, launch support, and scale

• Geo and community TLDs require policy nuance, localisation, and experience

Choosing the wrong RSP can limit growth, inflate costs, or create friction long after delegation.

A Practical Guide to Choosing the Right RSP

To help applicants move from a long vendor list to a focused shortlist, we previously published:

Registry Service Provider (RSP): Choosing the Right Backend
A practical guide for new gTLD applicants — with an RSP Selector

The guide explains what an RSP does, what really matters at selection time, and how to avoid common mistakes. It also includes our RSP Selector, a quick way to shortlist providers that align with your TLD type, priorities, and risk profile.

What the RSP Selector does

• Turns a long list into a clear shortlist in minutes

• Filters by TLD model (.brand, open, community, geo)

• Highlights evaluation status so you’re never shortlisting in the dark

(Detailed comparative data are available to clients.)

Key Questions to Ask Once You Have a Shortlist

Once you’ve narrowed the field, these questions help turn “maybe” into “yes or no”:

Experience & fit
Have you supported TLDs like ours before? How many are you operating today?

Growth & reach
How many registrars are live? How quickly can new ones be onboarded?

Flexibility
Can you support eligibility rules, premium tiers, or bespoke policies?

Reliability & security
What are your uptime SLAs, incident response targets, and security controls?

Commercial clarity
How is pricing structured, and what’s included vs charged as add-ons?

Neutrality
Do you also operate registrars or TLDs, and how are conflicts managed?

How TLDz helps beyond the shortlist

The Selector gets you from universe → shortlist. From there, TLDz supports applicants by:

• Aligning backend choices with your business model and launch strategy

• Running weighted, side-by-side comparisons

• Assessing performance, registrar reach, and price-to-value

• Advising on contract terms, SLAs, exit rights, and continuity

• Ensuring your backend supports long-term growth, not just delegation

You stay focused on the what. We optimise the how.

Ready to shortlist?

• Access RSP Selector

• Talk to TLDz – book a fit-check call

Whether you’re launching a .brand, a generic gTLD, or a community-driven TLD, we’ll help you put the right technical foundation in place,  and keep it aligned as the 2026 round approaches.

Summary of RSP Evaluation List (Source ICANN)