com-logonet-logo
Become a Domain Name Registrar

Verisign IDN TLDs

ICANN accredited registrars may add Verisign’s IDN TLDs to their domain name portfolios using this process. The registrar onboarding process has several requirements. For assistance or questions, please contact the Verisign Customer Affairs Office at +1 703 925 6999 or send an email.

Step 1: ICANN Accreditation / Requirements (Required)

Your business must be ICANN-accredited before you can become a registrar for the new generic top level domains (gTLDs). Registrars who wish to offer Verisign’s IDN TLDs under ICANN’s New gTLD Program must enter into the 2013 version of the Registrar Accreditation Agreement (RAA) and meet other ICANN requirements. Go to the ICANN website to start the ICANN accreditation process or contact ICANN to enter into the 2013 version of Registrar-Accreditation Agreement ("RAA") if you are already accredited but are operating under an older version of the RAA. Verisign has no control over how long the ICANN accreditation process may take.

Step 2: Authentication (Conditional)

Next, if you have not completed the authentication process with Verisign previously, Verisign’s vendor will contact you to request documents required to validate your business as well as your authority to represent and act on behalf of your company, an ICANN-accredited registrar.

STEP 3: Verisign Certification (Required)

After you establish an account, you may complete the next steps simultaneously: provide financial information and determine technical readiness. Use the tabs below to proceed.

Establish a Contractual Relationship & Create Your Registrar Account with Verisign

To offer one or more of the new gTLDs, you will first be required to enter into a Non-Disclosure Agreement, after which Verisign Customer Affairs Office will forward the required contracts to you electronically.

Registrar Information Form (Conditional)

If you have not already completed a Registrar Information form, or if you need to update your account information with Verisign, you will be required to complete a Registrar Information Form. You will need the following technical information: Web server name, Whois server name, and no more than three subnets in Classless Inter-Domain Routing Protocol (CIDR) format, up to a total of 96 hosts (/26 = 64 hosts, /27 = 32 hosts, /28 = 16 hosts, /29 = 8 hosts, /30 = 4 hosts, /31 = 2 hosts, /32 = 1 host).

To establish an account with Verisign, email the Registrar Information Form to the Customer Affairs Office.

Financial Requirements (Required)

Verisign requires registrars to establish a payment security based on expected monthly registration volume across all TLDs. The Payment Security allows Verisign to provide you with available credit in our Shared Registration Systems. If you expect a considerable increase in your monthly transaction volume, you must re-evaluate the amount of your payment security and adjust it accordingly. For more information on the Payment Security requirement, contact the Customer Affairs Office.

NOTE: You may start this process before you receive your user IDs and passwords.

Technical Requirements

Registrars must demonstrate full and correct operation of client systems within the Operational Test and Evaluation (OT&E) environment before connecting to the Verisign Shared Registration System (SRS). You may begin development of your client applications before you receive your user IDs and passwords, but you will not be able to integrate with the Verisign SRS until your account has been established.

SSL Certificates

Verisign requires that each server that communicates with the SRS has a 40- or 128-bit SSL Certificate installed. Verisign accepts the following SSL Certificates:

Geotrust

  • RapidSSL
  • RapidSSL Wildcard
  • QuickSSL
  • QuickSSL Premium
  • True BusinessID
  • True BusinessID MultiDomain
  • True BusinessID Wildcard

GoDaddy

  • Starfield Standard SSL

Symantec

  • Secure Site (40bit)
  • Secure Site Pro (128bit)

Thawte

  • SSL 123
  • SSL Web Server
  • SGC SuperCerts
  • Wildcard SSL

Extensible Provisioning Protocol (EPP) SDK

To develop the client end to the SRS, you must implement EPP software. Verisign has developed EPP SDKs and guides to help you develop your client application.

If you choose to develop your own EPP implementation, it must be based on RFC-5730, the published protocol specification. You will need to acquire and incorporate an implementation of the Secure Sockets Layer (SSL) protocol into their EPP software. You will also need to secure a license for the use of RSA cryptographic algorithms through RSA Data Security, Inc.

You will receive your user IDs and passwords to the OT&E environment when Verisign has established your account. Your informational packet will include testing information to complete this process. When you are ready to demonstrate technical operation and qualify for access to the production SRS, contact Verisign Customer Affairs Office. For assistance with testing, contact Customer Support.