RRPproxy Homepage
RRPproxy Homepage

.insurance

API commands

Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.

Domain Registration

(API Command reference » AddDomain)
  • Registrant completes application on .insurance website
  • fTLD issues registration token to registrant.
  • The registrant/registrar can register the domain name on RRPProxy with the fTLD-Token: X-ALLOCATION-TOKEN = [fTLD Registration Token]
Exception
command = AddDomain
domain = yourdomain.insurance
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
X-ALLOCATION-TOKEN = (TEXT)

Domain Modification

(API Command reference » ModifyDomain)
Exception
command       = ModifyDomain
domain        = yourdomain.insurance
ownercontact0 = (CONTACT)
token = (TEXT)

Domain Renewal

(API Command reference » RenewDomain)
Command
command    = RenewDomain
domain     = yourdomain.insurance
period     = (INT)
expiration = (INT)

Domain Deletion

(API Command reference » DeleteDomain)
Exception
command = DeleteDomain
domain  = yourdomain.insurance
token = (TEXT)

Domain Transfer

(API Command reference » TransferDomain)
Command
command = TransferDomain
domain = yourdomain.insurance
action = REQUEST
auth = (TEXT)

Transfer procedure

  • 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.

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 http://www.icann.org/transfers/
  • After a successful transfer of the domain, it will be transfer locked from the registry for a period of 60 days.

Auth-Codes

The format for auth info requires a minimum length of 8 characters and a maximum length of 32 characters.

Additionally, auth info must contain at least one of each of the following three character types:

  • Alphabetic characters: a-z; A-Z
  • Numeric characters: 0-9
  • Special characters: !;<=$%?&@[()]*^+-,'-{.|/}:~

Domain Restore

(API Command reference » RestoreDomain)
Command
command = RestoreDomain
domain  = yourdomain.insurance

Domain Extensions

X-ALLOCATION-TOKENProvide a token that has to be issued by the registry for the registration of a premium domain name.

Domain Restrictions

  • Registrant organization must be in insurance 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 .BANK:
      • 3.1 State, regional and provincial banks 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 banks 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 banks 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 bank nor do they provide banking services. If the bank 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. ns1.insurancename.insurance)
  • DNSSEC required
  • Domain-based Message Authentication, Reporting and Conformance (DMARC) required
  • encryption required for web access, mail exchange and file transfer
  • full list of .insurance security requirements
  • possibility to add domains without nameservers

Please carefully review the .insurance Registrant Eligibility Policy and Security Requirements before submitting requests to avoid inconveniences for all involved in the registration process and most importantly your customer. If the eligible banking entity provides these types of services itself along with its banking 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.

Supported IDN Scripts

The following IDN scripts are supported by .insurance.
Provide the LANGUAGE TAG corresponding to your desired IDN within the AddDomain command as X-IDN-LANGUAGE extension.

AfrikaansAFR
AlbanianALB
ArabicARA
AragoneseARG
ArmenianARM
AssameseASM
AsturianAST
AvestanAVE
AwadhiAWA
AzerbaijaniAZE
BalineseBAN
BaluchiBAL
BasaBAS
BashkirBAK
BasqueBAQ
BelarusianBEL
BengaliBEN
BhojpuriBHO
BosnianBOS
BulgarianBUL
BurmeseBUR
CaribCAR
CatalanCAT
ChechenCHE
ChineseCHI
ChuvashCHV
CopticCOP
CorsicanCOS
CroatianSCR
CzechCZE
DanishDAN
DivehiDIV
DogriDOI
DutchDUT
EnglishENG
EstonianEST
FaroeseFAO
FijianFIJ
FinnishFIN
FrenchFRE
FrisianFRI
GaelicGLA
GeorgianGEO
GermanGER
GondiGON
GreekGRE
GujaratiGUJ
HebrewHEB
HindiHIN
HungarianHUN
IcelandicICE
IndicINC
IndonesianIND
IngushINH
IrishGLE
ItalianITA
JapaneseJPN
JavaneseJAV
KashmiriKAS
KazakhKAZ
KhmerKHM
KirghizKIR
KoreanKOR
KurdishKUR
LaoLAO
LatvianLAV
LithuanianLIT
LuxembourgischLTZ
MacedonianMAC
MalayMAY
MalayalamMAL
MalteseMLT
MaoriMAO
MoldavianMOL
MongolianMON
NepaliNEP
NorwegianNOR
OriyaORI
OssetianOSS
PanjabiPAN
PersianPER
PolishPOL
PortuguesePOR
PushtoPUS
RajasthaniRAJ
RomanianRUM
RussianRUS
SamoanSMO
SanskritSAN
SardinianSRD
SerbianSCC
SindhiSND
SinhaleseSIN
SlovakSLO
SlovenianSLV
SomaliSOM
SpanishSPA
SwahiliSWA
SwedishSWE
SyriacSYR
TajikTGK
TamilTAM
TeluguTEL
ThaiTHA
TibetanTIB
TurkishTUR
UkrainianUKR
UrduURD
UzbekUZB
VietnameseVIE
WelshWEL
YiddishYID

Get more information of "IDN tables", which represent permitted code points (letters) allowed for Internationalised Domain Name registrations in particular registries on IANA Repository of IDN Practices.

Wedomains :)