Revision as of 18:24, 25 July 2019 (view source) WikiAdmin (Talk | contribs) (Created page with "{{Infobox nTLD | name = .INSURANCE | image =250px | introduced = 2019 | category = Business, Finance | registry = fTLD Registry | idn capable = Unkno...")		Latest revision as of 21:21, 29 April 2024 (view source) Timo (Talk | contribs) (→‎TLD specific)
Line 159:		Line 159:
	</pre>		</pre>
		+	=== Restrictions ===
		+
		+	* Registrant organization must be in insurance sector
		+	* Domain name must be directly related with organization name
		+	* 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 is required
		+	* Domain-based Message Authentication, Reporting and Conformance (DMARC) required
		+	* Encryption required for web access, mail exchange and file transfer
		+
		+	Full list of [https://www.ftld.com/docs/fTLD-2016-Security-Requirements.pdf .insurance security requirements]
		+
		+	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.
	= Addons =		= Addons =

---

Latest revision as of 21:21, 29 April 2024

.INSURANCE domain is more than a really great marketing tool. Get a .INSURANCE domain to quickly inform potential customers as to who and what you are, differentiating you from your competitors and across the internet.

.INSURANCE
Overview
Introduced	2019
Category	Business, Finance
Registry	fTLD Registry
IDN Capable	Unknown
Dispute Policy	ICANN Rules
Webpage	Register .INSURANCE
Legal Information
Legal	Registry Policies

Contents 1 Registry 2 Periods 3 API 3.1 Domain Registration 3.2 Domain Transfer 3.3 Delete Domain 3.4 Restore Domain 3.5 Ownerchange 4 TLD specific 4.1 Authorization code 4.2 Restrictions 5 Addons 6 RegistrarOC 6.1 Restore Process

[edit] Registry

TLD	-
Registry	CentralNic
Dispute Policy	Rules
Registrar	1api GmbH
WHOIS-Server	whois.centralnic.net
WHOIS-Update	Real-Time
Min. Characters	1
Max. Characters	63
Character Set	Letters and numbers Hyphens ("-"), however not at the beginning or directly in front of the TLD IDN: allowed
Limitations	Registrant Contacts: Required: 1 / Maximum: 1 Admin Contacts: Required: 1 / Maximum: 1 Tech Contacts: Required: 1 / Maximum: 1 Billing Contacts: Required: 1 / Maximum: 1
{{{Possible Extensions}}}
IDN capable	Yes
Restore capable	Real-Time
Handle Updates	Supported
Registration System	Real-Time
Allowed number of NS	0 to 13
Registry Nameservercheck	No
Host IP-Addresses Type	IPv4 / IPv6
Hosts managed as	Object
Root Nameserver Update	every 15min
SEC DNS Interface	DS data interface
Transferclass	Pull
Transfer Periods	1Y
Transfer Authcode required	Yes
Transfer Real-Time	No
Transfer Pending Period	5 days
Transfer Expire Action	ACK
Transfer ACK by	Registrar
Transfer NACK by	Registrar
Transfer Lock	Yes
Owner Change by	ICANN-TRADE

[edit] Periods

{{{Possible Extensions}}}
Registration Periods	1-10 years
Add Grace Period	0 days
Accounting Period	-5 days
Finalization Period	1 day
Failure Period	44 days
Payment Period	-61 days
Deletion Restorable Period	30 days
Deletion Hold Period	5 days
Explicit Renewals	Yes
Renewal Periods	1-9 years

[edit] API

[edit] Domain Registration

Domains can be registered in Real-Time with the API AddDomain command.

command = AddDomain
domain  = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)

OPTIONAL

auth = (TEXT) | (NULL)
period = (PERIOD)
transferlock = 0 | 1 | (NULL)

[edit] Domain Transfer

The transfer has to be initiated by the gaining registrar and can be requested with the API TransferDomain command.
A valid Authorization Code must be provided to initiate a transfer successfully. You may obtain the authorization code from the losing registrar.
As soon as a domain transfer has been initiated it can either be approved ("ACK") by Registrar or denied ("NACK") by Registrar. If the registry receives neither a denial ("NACK") nor an approval ("ACK") the transfer will be ACKed after 5 days.

command = TransferDomain
domain = (DOMAIN)

REQUIRED

auth = (TEXT)

OPTIONAL

period = (PERIOD)
transferlock = 0 | 1 | (NULL)
action = REQUEST | APPROVE | DENY | CANCEL | USERTRANSFER

[edit] Delete Domain

Domains can be deleted with the API DeleteDomain command.
There is a Deletion Restorable Period of 30 days and a following Deletion Hold Period of 5 days.

command = DeleteDomain
domain = (DOMAIN)

[edit] Restore Domain

Restores can be processed in realtime. A restore is possible within 30 days upon deletion. Please use the command RestoreDomain.

command = RestoreDomain
domain = (DOMAIN)

OPTIONAL

subuser = (TEXT)
renewalmode = (NULL) | (TEXT)

[edit] Ownerchange

All contact information with the exception of registrant Name, Firstname and Organisation can be updated through the ModifyDomain command.
In order to change the owner you have to request a trade with the TradeDomain command. This can be done through our web interface or through our API:

command = TradeDomain
domain = <DOMAIN>
ownercontact0 = <CONTACT>

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

ownercontact0 = (CONTACT)

[edit] TLD specific

[edit] Authorization code

There are special requirements regarding the format of the authorization code. Please consider the following restrictions, if you want to assign a new authorization code to a domain:

• Minimum 8 characters
• having at least one (1) numeric,
• one (1) alphabetic, and
• one (1) special character

You may generate a valid random auth code by adding this parameter to the ModifyDomain command:

command = ModifyDomain
domain = (DOMAIN)

REQUIRED

generaterandomauth = 1

[edit] Restrictions

• Registrant organization must be in insurance sector
• Domain name must be directly related with organization name
• 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 is 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

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.

[edit] Addons

[edit] RegistrarOC

Restore Process

To restore a domain as a RegistrarOC customer, you simply have to execute the RestoreDomain command. HEXONET directly forwards the restore request to the registry, which performs the restore in real-time. As soon as the restore is complete, the domain will get assigned to your account with the original domain data.