Secure gTLD

Bruce Morton
Attribution: Photo is a screen capture from Artemis.net

Attribution: Photo is a screen capture from Artemis.net

As a follow to my post on new gTLDs, here is an interesting request for a gTLD called .secure.

Artemis Internet is planning to provide secure domain names. Security will be provided through human verification, security policies, and enforcement. The .secure gTLD would be available to any organization or individual. The users would have to follow a strict code of conduct including rigorous identity screening, two factor authentication, meet a minimum set of security practices, and end-to-end encryption of most traffic.

The Artemis CTO says, “We have a chance to create a neighborhood on the Internet where security is required, and users know that. We have the ability since we’re starting from scratch to have a floor.”

This could be a great implementation for a new gTLD. As I said before, the requests for the gTLDs must be assessed and approved and there is more than one request for .secure. We’ll see what happens.

Bruce Morton
Bruce Morton
Director, Certificate Technology & Standards

Bruce Morton has worked in the public key infrastructure and digital certificate industry for more than 15 years and has focused on SSL and other publicly trusted certificates since 2005. He has been an active member of the CA/Browser Forum that released guidelines for extended validation (EV) certificates and Baseline Requirements for SSL certificates. Bruce oversees the governance and compliance of Entrust’s publicly trusted PKI.

0 Comments

Add to the Conversation