From TLDinfo
Jump to: navigation, search


RRPproxy is the Reseller Portal for ISPs, Registrars & Domain Investors. Domains, Hosting & More ...

IDN capable: No
Handle Updates: Yes
Registration Period: 1-10 years
Autorenew Grace Period: 35 days
Deletion Timeframe: 35 days after expiration date
Registration System: realtime
WHOIS-Privacy: No
Registry: Registry
Dispute Policy: Policy


Zone Info

Zone Use

.INSURANCE is the top level domain for insurances and can only be registered by insurance companies.


  • Minimum: 3
  • Maximum: 63
  • Letters and numbers
  • Hyphens ("-"), however not at the beginning or directly in front of the TLD

Domain Registration

command                                   = AddDomain
domain                                    =
ownercontact0                             = [owner handle]
admincontact0                             = [admin contact]
techcontact0                              = [tech contact]
billingcontact0                           = [billing contact]
nameserver0                               = [nameserver1]
nameserver1                               = [nameserver2]
X-CONTACTVERIFICATION-NAME                = [FULL CONTACT NAME]  (forename and lastname has to be separated with a comma)
X-CONTACTVERIFICATION-COUNTRY             = [Country]  (in ISO-Code)
X-CONTACTVERIFICATION-PHONE               = [Phone Number]
X-CONTACTVERIFICATION-MAIL                = [E-Mail]

All extensions are mandatory!

X-CONTACTVERIFICATION - Data must be additional contact data of two full time employees from the organisation. The contacts will be validated by Symantec and should be informed.
These must be two natural persons, including all information like E-Mail and phone number of these persons! The information will not be published in Whois.

X-CONTACTVERIFICATION-NAME - First and Last name must be separated by "," and must be in order First name, Last name

X-CONTACTVERIFICATION-SPECIALINSTRUCTIONS - Required. Based on the order type, you must include the following information. While the string format is not validated, you should label and separate each piece of information with a comma or semi-colon. This Field MUST begin with the Category.

  • Category - select one: Carrier, SP (Service Provider), Assn(Association), Govt(Government Agency), Agent/Agency, Broker/Brokerage.
  • Primary Government Regulatory Authority Name - the government agency with which the organization is registered.
  • Primary Government Regulatory Authority ID Number - the ID number provided by the named government regulatory authority.
  • Human Resources Contact - include the name, telephone number and email address of someone in the HR department or someone who performs this role for the registrant organization.
  • Registrant's Manager - include the name, telephone number and email address of someone who can verification that the registrant contact has the authority to register these domains for the registrant organization.

Further details are also available in the .INSURANCE FAQ.

Attention.png Incomplete or incorrect data may cause a failed validation, this might result in extra costs for revalidation!

Would you like to have instant access to RRPproxy and more than 300 domain extensions? Sign-up here for free ...

Domain Modification


Registrant changes for .INSURANCE domains can be done online via api or webinterface.

command       = ModifyDomain
domain        =
ownercontact0 = [new owner handle]
token         = 

Deletion Process

.INSURANCE Domains can be deleted online through the Delete Command.

command = DeleteDomain
domain  =
token   = 


  • Registrant organization must be in insuranceing sector
  • Domainname must be in touch with organization
    • Qualified Registrants Registrant Eligibility Policy
      • The following for-profit and not-for-profit businesses or organizations are initially eligible to register domain names in .INSURANCE:
        3.1 State, regional and provincial insurances that are chartered and supervised by a government regulatory authority;
        3.2 Savings associations that are charted and supervised by a government regulatory authority;
        3.3 National insurances that are chartered and supervised by a government regulatory authority;
        3.4 Associations whose members are primarily comprised of entities identified above in 3.1, 3.2 or 3.3;
        3.5 Groups of associations whose members are primarily comprised of associations identified above in 3.4;
        3.6 Service providers that are principally owned by or predominantly supporting regulated entities identified above in 3.1, 3.2 or 3.3. (if approved by the Registry Operator Board); and
        3.7 Government regulators of chartered and supervised insurances or savings associations or organizations whose members are primarily comprised of such government regulators (if approved by the Registry Operator Board).
      • Insurance holding companies are not eligible as they do not fit the definition of a insurance nor do they provide insuranceing services. If the insurance holding company believes they need to be listed in the registration, they can for example be listed as the admin contact. Please do not submit any requests in this format as they will be rejected.
  • DomainPinLock is required as multi factor authentication and will be set on AddDomain.
    It is NOT possible to deactivate DomainPinlock. Instead of SMS, E-Mail authentication will be used, the token will be sent to the registrant's email address. Changes to the domain can only be performed, when a valid token is provided!
  • .INSURANCE domains must use .INSURANCE nameservers (e.g.
  • DNSSEC required
  • Domain-based Message Authentication, Reporting and Conformance (DMARC) required
  • possibility to add domains without nameservers
  • Policy overview
Attention.png Please carefully review the .INSURANCE Registrant Eligibility Policy before submitting requests to avoid inconveniences for all involved in the registration process and most importantly your customer. If the eligible insuranceing entity provides these types of services itself along with its insuranceing services then the registration is permissible. If however these services are provided by separate legal entities that are not eligible for domains in .INSURANCE (e.g., mortgage broker, equipment leasing company, investment firm), then the registration is not permissible.


  • .INSURANCE Transfers can either be done through the RRPproxy WebInterface or API.
command = TransferDomain
domain  =
action  = request
auth    = .....
  • After the transfer has been requested, our backend system sends a confirmation email to the Owner/Admin-C according to the WHOIS of the respective domain. In order to initiate the transfer successfully it is important, that this email is confirmed.
  • After confirmation the transfer is initiated through the official registry and the losing registrar will receive the transfer request.
  • The losing registrar will also send an email to the Owner/Admin-C. allowing him/her to deny the transfer. If you do not respond to the email of the losing registrar, then the transfer will get processed successfully after 5 days.
Attention.png If the Email-Address in the WHOIS is invalid, then the transfer cannot be processed.If this is the case, then kindly contact your current registrar and ask him to update the WHOIS information accordingly.

Transfer notes

  • A .INSURANCE Domain Transfer must be initiated with a so-called Authorisation Code, which can be obtained from the current registrar through the owner or Admin-C of the domain.
  • Ensure that your respective domain does not have a lock-status (REGISTRAR-LOCK or HOLD). This can be seen in the WHOIS.
    If the domain is locked, then the owner can demand that the domain will be unlocked.
  • Please note that we are only allowed to initiate a gTLD transfer after confirmation of the "ICANN Form of Authorization" by the current registrant. The policies can be viewed under
  • After a successful transfer of the domain, it will be transfer locked from the registry for a period of 60 days.

Transfer time

A transfer takes 5 days to complete.

Personal tools

new gTLDs
New Users