Quick Start Guide
fTLD on Twitter

New to .INSURANCE? Use this Quick Start Guide to learn the basic steps required to begin using your new domain name. Whether you intend to use your domain name now or later for your website or email, this Quick Start Guide covers the key steps you will need to follow to leverage the security features of your domain name and promote your new online presence. The Resources listed below go into greater detail about the Security Requirements—with Guides for both an Executive or Technical audience—and include a Planning and Communications Guide designed especially for marketing and communications teams. The Implementation Planning Checklist is a tool designed to help your domain name implementation team think about all the key steps involved in launching your new online presence. With this Quick Start Guide, you can jump right into setting up your domain name for your website and/or email!

To get started, click the option below that best describes how your company intends to use its .INSURANCE domain name or download a PDF Version of the full Quick Start Guide:

My company will use our .INSURANCE domain name to host our primary website.

Can be either hosted internally or with a web- or cloud-based provider. Information about the Security Requirements is available in the Technical Guide.

  1. Authoritative name servers must be in the .INSURANCE zone – Requirement #28
  2. DNSSEC deployed at each zone and sub-zone – Requirement #23
  3. Obtain a public key certificate (also known as a digital or identity certificate) – Requirement #25
  4. Publish a valid DMARC record and SPF and/or DKIM records – Requirement #26
  5. TLS/Encryption Standards – Requirements #25 & #29
  6. Aliasing (e.g., CNAME, DNAME, MX) – Requirement #27

Information about the Security Requirements is available in the Technical Guide.

  1. Follow the steps in 1(A) above, except in step 4 you only need to publish a valid DMARC record and set to p=reject – Requirement #26.

My company will point our .INSURANCE domain name to our existing domain name and we will not use .INSURANCE for email.

Information about the Security Requirements is available in the Technical Guide.

  1. Redirection (i.e., URL forwarding) must be made from HTTPS version of your .INSURANCE domain name before resolving to your existing domain name – Requirement #30
    1. For example, you may wish to temporarily or permanently redirect https://www.companyname.insurance to https://www.companyname.com
  2. Authoritative name servers must be in the .INSURANCE zone – Requirement #28
  3. DNSSEC deployed at each zone and sub-zone – Requirement #23
  4. Obtain a public key certificate (also known as a digital or identity certificate) – Requirement #25
  5. Publish a valid DMARC record (p=reject) – Requirement #26
  6. TLS/Encryption Standards for Web Connections – Requirements #25 & #29

Information about the Security Requirements is available in the Technical Guide.

  1. Aliasing (e.g., CNAME, DNAME, MX) – Requirement #27
  2. Authoritative name servers must be in the .INSURANCE zone – Requirement #28
  3. DNSSEC deployed at each zone and sub-zone – Requirement #23
  4. Obtain a public key certificate (also known as a digital or identity certificate) – Requirement #25
  5. Publish a valid DMARC record (p=reject) – Requirement #26
  6. TLS/Encryption Standards for Web Connections – Requirements #25 & #29

My company will not use our .INSURANCE domain name at this time and instead wants to hold it to protect our brand.

  1. Domain name remains inactive (not resolving on the internet) and is not subject to fTLD’s Security Requirements.
  2. fTLD domain names are inactive by default and you may request certain domain statuses to be set by your registrar to further protect your domain name. See Client Status Codes available here: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

 

Resources on how to activate your .INSURANCE domain

fTLD has developed the following resources to assist in your domain planning and
implementation:

Question on the Security Requirements – compliance@fTLD.com

General Inquiries – fTLD@fTLD.com