What services does an RSP provide?
An RSP runs the technical backend named in its evaluated and contracted scope. That scope can include:
Shared Registration System (SRS) / EPP
The registry database and protocol registrars use to register, renew, transfer, and manage domains.
RDAP registration data service
The definitive service for gTLD registration data. WHOIS is now legacy and is retained only where a Registry Agreement or compatibility need calls for it.
Additional registry services
Authoritative DNS, DNSSEC, data escrow coordination, monitoring, and operational support may be provided by the RSP or another qualified provider, depending on the applicant's model and evaluated scope.
Applicants should compare the official ICANN scope, the proposed architecture, responsibilities, service targets, and commercial agreement—not assume every provider has the same bundle.
ICANN's RSP evaluation program
ICANN runs the RSP evaluation program to assess the technical, operational, financial, and security capabilities stated in each application. Scope matters: the official list shows whether a provider has cleared the Main evaluation and any additional service evaluations.
Provider status and scope can change as the program progresses, so applicants should verify the official ICANN list before deciding. ADG has cleared the Main RSP evaluation and serves TLD operators from Indonesia; any additional service scope should be confirmed against the current list and the proposed agreement.
RSP vs registry operator: what's the difference?
These two roles are distinct but closely related:
| Registry Operator | Registry Service Provider (RSP) | |
|---|---|---|
| ICANN relationship | Holds the Registry Agreement | No direct ICANN contract |
| Accountability | Accountable to ICANN for TLD | Accountable to registry operator |
| Policy role | Sets domain policy for TLD | Implements policy, not sets it |
| Technical role | Owns the TLD rights | Runs the technical systems |
| Business role | Commercial/branding strategy | Infrastructure operations |
A registry operator can be technical (building their own systems) or non-technical (relying entirely on an RSP). Most new gTLD operators use an RSP because the technical requirements are significant — building ICANN-compliant DNS, EPP, WHOIS/RDAP, DNSSEC, and data escrow from scratch takes years and millions of dollars in infrastructure investment.
How to choose the right RSP
Not all RSPs are the same. Key evaluation criteria:
1. ICANN evaluation status: Non-negotiable — confirm the RSP is on ICANN's current evaluated list.
2. DNS infrastructure quality: Node count, geographic distribution, SLA guarantees, DDoS protection capacity.
3. References: Which active TLDs does the RSP operate? Talk to existing customers.
4. Contract terms: What happens if you want to migrate to another RSP? Is there a data portability guarantee?
5. Local support: If your TLD serves a regional market, is the RSP accessible in your time zone with staff who understand local regulations?
6. Pricing model: Per-domain fees vs. flat-rate fees — which model fits your TLD's projected zone size?
ADG offers a free discovery call to help TLD applicants evaluate their options before committing to an RSP agreement.
Frequently asked questions
Can I change my RSP after delegation?
Yes, but it's operationally complex. RSP migration involves transferring zone data, SRS data, registrar EPP connections, and DNSSEC keys — all while maintaining 100% uptime. ICANN requires a migration plan that ensures no registrant impact. Most registry operators stay with their initial RSP for stability.
What is a shared RSP vs a dedicated RSP?
A shared RSP operates infrastructure used by multiple TLD operators simultaneously (multi-tenancy). A dedicated RSP provisions exclusive infrastructure for a single TLD. Most RSPs offer shared infrastructure for cost efficiency; dedicated infrastructure is available for high-volume TLDs or those with special security/compliance requirements.
How long does RSP onboarding take?
Technical setup time depends on data readiness, registrar integration, DNS and DNSSEC configuration, and ICANN testing schedules. ADG agrees the activation plan, responsibilities, and target dates with the operator after the scope and dependencies are confirmed.