Assign this task

 


 

WHY THIS IS IMPORTANT

With a Digital Identity Certificate your .BANK or .INSURANCE domain will resolve to HTTPS, a requirement of the .BANK and .INSURANCE space, ensuring all data is secure in transit. *HTTP sites in the .BANK and .INSURANCE domains will not be accessible in most major browsers (like Google Chrome) due to a technical control called HSTS (HTTP Strict Transport Security); see below for more information.

GET HELP

  • Webhosting Companies  .BANK | .INSURANCE
  • Check with Your Registrar
  • Certificate Authority (e.g.)
    • Let’s Encrypt
    • Comodo
    • DigiCert
    • EnTrust
    • GlobalSign
    • IdenTrust

ASK fTLD  CHAT  |  EMAIL


 
ADDITIONAL REQUIREMENT DETAIL

Registrants must have a public key certificate (also known as a digital identity or TLS certificate) in place to meet the HTTPS-only requirement. Registrants may wish to use a wildcard certificate (e.g., *.domainname.BANK | *.domainname.INSURANCE) which allows a public key certificate to be used across single-level subdomains.

As .BANK and .INSURANCE are on the HSTS preload list, domains that are not HTTPS compliant will not be accessible via browsers following this list (like Google Chrome). As a global HSTS security policy becomes increasingly common, additional browsers are expected to block sites that are not HTTPS compliant.


 

Mark Requirement Complete and Submit to fTLD for Review

 

IMPLEMENTATION HUB