.insurance

API commandsExtensionsRestrictionsIDN

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.

AddDomainModifyDomainRenewDomainDeleteDomainTransferDomainRestoreDomain

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

• The transfer is submitted to the registry and the losing registrar is automatically notified by them.
• The losing registrar sends an email to the owner (and optionally admin) contact, informing about the transfer; this may include options to approve and/or deny the transfer. If neither explicitly approved nor denied, the transfer will be automatically finalized after 5 days.

Transfer Notes

• A .insurance domain transfer must be initiated with a so-called authorisation code, (auth-code) which can be obtained from the current registrar through the owner/admin contact of the domain.
• Ensure that your respective domain does not have a lock-status (clientTransferProhibited and/or serverTransferProhibited). This can be seen in WHOIS.
• If the domain has a client-side transfer lock, the owner can ask the current registrar to have the lock removed.

These procedures only apply for domain transfers between registrars. For internal transfers between resellers, please consult our documentation about internal transfers/usertransfers.

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-TOKEN	Provide 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!
• Domain-based Message Authentication, Reporting and Conformance (DMARC) required
• encryption required for web access, mail exchange and file transfer
• Security Requirements for .insurance can be found via security requirements with the full list being available via 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.

Afrikaans	AFR
Albanian	ALB
Arabic	ARA
Aragonese	ARG
Armenian	ARM
Assamese	ASM
Asturian	AST
Avestan	AVE
Awadhi	AWA
Azerbaijani	AZE
Balinese	BAN
Baluchi	BAL
Basa	BAS
Bashkir	BAK
Basque	BAQ
Belarusian	BEL
Bengali	BEN
Bhojpuri	BHO
Bosnian	BOS
Bulgarian	BUL
Burmese	BUR
Carib	CAR
Catalan	CAT
Chechen	CHE
Chinese	CHI
Chuvash	CHV
Coptic	COP
Corsican	COS
Croatian	SCR
Czech	CZE
Danish	DAN
Divehi	DIV
Dogri	DOI
Dutch	DUT
English	ENG
Estonian	EST
Faroese	FAO
Fijian	FIJ
Finnish	FIN
French	FRE
Frisian	FRI
Gaelic	GLA
Georgian	GEO
German	GER
Gondi	GON
Greek	GRE
Gujarati	GUJ
Hebrew	HEB
Hindi	HIN
Hungarian	HUN
Icelandic	ICE
Indic	INC
Indonesian	IND
Ingush	INH
Irish	GLE
Italian	ITA
Japanese	JPN
Javanese	JAV
Kashmiri	KAS
Kazakh	KAZ
Khmer	KHM
Kirghiz	KIR
Korean	KOR
Kurdish	KUR
Lao	LAO
Latvian	LAV
Lithuanian	LIT
Luxembourgisch	LTZ
Macedonian	MAC
Malay	MAY
Malayalam	MAL
Maltese	MLT
Maori	MAO
Moldavian	MOL
Mongolian	MON
Nepali	NEP
Norwegian	NOR
Oriya	ORI
Ossetian	OSS
Panjabi	PAN
Persian	PER
Polish	POL
Portuguese	POR
Pushto	PUS
Rajasthani	RAJ
Romanian	RUM
Russian	RUS
Samoan	SMO
Sanskrit	SAN
Sardinian	SRD
Serbian	SCC
Sindhi	SND
Sinhalese	SIN
Slovak	SLO
Slovenian	SLV
Somali	SOM
Spanish	SPA
Swahili	SWA
Swedish	SWE
Syriac	SYR
Tajik	TGK
Tamil	TAM
Telugu	TEL
Thai	THA
Tibetan	TIB
Turkish	TUR
Ukrainian	UKR
Urdu	URD
Uzbek	UZB
Vietnamese	VIE
Welsh	WEL
Yiddish	YID

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.