Establish a Contractual Relationship
To establish your business relationship with Verisign, e-mail all required forms and supporting documentation to the Customer Affairs Office.
NOTE: All supporting documentation, including Registrar's Registration Agreement, Dispute Policy and Corporation Formation documents, must be provided in English.
Registry-Registrar Agreements (Required)
To offer .com, .net and/or .name, you will first be required to enter into a Registry-Registrar Agreement with Verisign for each TLD. The links to the relevant agreements below are for reference only as the Verisign Customer Affairs Office will forward the required contracts to you electronically.
Name Store Activation Agreement (Required)
To offer .tv and/or .cc, you will be required to enter into a Name Store Merchant and Name Store Activation Agreement. To obtain copies of these agreements, contact the Verisign Customer Affairs Office.
Corporate Formation Documents (Conditional)
Depending on the outcome of the Authentication process described in Step 2 above, Verisign may require you to provide copies of corporate formation documents to verify the legal entity with which VeriSign, Inc., is entering into a contract. The corporate name used on all forms must match the name used for ICANN accreditation. ccTLDs such as .tv and .cc do not require ICANN-accreditation.
Foreign Corrupt Practices Act Form (Required)
Registrars are required to complete and return the FCPA form to certify that the registrar will comply with the applicable laws and requirements under the Foreign Corrupt Practices Act. The Customer Affairs Office will forward the required form electronically.
Registrar Information Form (Required)
Please complete the Registrar Information Form and submit the information to establish your account. Your business information must match your ICANN accreditation information. ccTLDs such as .tv and .cc must match your legally registered name. You will also need the following technical information: Web server name, Whois server name, SSL Common 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).
Verisign, Inc.’s Handling of Personal Data
As the registry operator for the .com, .net, .name, .tv and .cc top level domains (the “Registry TLDs”), Verisign’s policies regarding the collection, use, and disclosure of personal data submitted to Verisign by registrars for the Registry TLDs can be found in the Registrar Personal Data notice, including the purposes for which Personal Data submitted to Verisign by registrars for the Registry TLDs is collected, the intended recipients (or categories of recipients) of such Personal Data, and the mechanism for access to and correction of such Personal Data.
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. The minimum Payment Security amount is based on your forecasted domain registrations, however there is no maximum amount you can provide. 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 across all TLDs.
Registrars must demonstrate full and correct operation of client systems within the Operational Test and Evaluation (OT&E) environment before connecting to the 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 complete it until Verisign has established your account.
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:
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 your EPP software. You will also need to secure a license for the use of RSA cryptographic algorithms through RSA Data Security, Inc.
Testing and Evaluation
You will receive your user IDs and passwords to the OT&E environment when Verisign has established your account. Your information pack 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.