IT.COM

Name Selection Poll for Root Certificate brand

Spaceship Spaceship
Watch

Which brand names would you prefer for producing (free) domain certificates?


Rob Monster

Founder of EpikTop Member
Epik Founder
Impact
18,389
We previously announced a search for a great brand name for an online service for sourcing domain certificates. The thesis is that there will eventually be innovative alternatives to the likes of LetsEncrypt that empower more people to secure their sites with robust technology. That search was described here:

https://www.namepros.com/threads/ssl-root-certificate-authority-ca-brand-name.1158491/

In the meantime, we have had some great domain candidate submissions. In order to select a winning name, we welcome your input on name selection through poll and discussion as we make plans to co-create another tool that helps make the pie bigger.

As for the list of brand prospects, we used every slot allowed in the poll software. There were many good ones left out unfortunately, but it is still a long list from some very thoughtful submitters who I look forward to highlighting among the top contenders to the extent they choose to be identified!
 
10
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
FullEncrypt certainly is a nice (and powerful) name and all, but I feel it's more suitable in the context of hard disk encryption. In the context of digital certificates, especially standing up a Root CA as Epik intends to, I feel DNEncrypt is a much better fit. If FullEncrypt is used, it implies that without it, you only have partial encryption. In the realm of digital certificates, partial encryption doesn't exist. You either have it, or you don't. Its' not something you could go into your workplace and say, "I just installed Epik's new Root CA cert. called FullEncrypt and now I'm fully encrypted."

DNEncrypt is generic but descriptive enough to let the end-user know that their connection to a domain name (more accurately a server) will be encrypted - period. All underlying negotiated encryption protocols are transcended now and in the future. The upside to having an Epik DNEncrypt certificate installed, is that it can added to the existing line of Epik's security-related offerings such as DNProtect. No need to reinvent the wheel - just add more spokes. :)
...
IMO of course, and I do believe Full Encrypt is a good name, just not in the context of digital certificates.

I understand you, but DN does not seem ideal to me (for this context).

If "Let's Encrypt" name is good (yes, in my opinion and your), Full Encrypt is good too.

Also, "Web" and "Seal" words do not seem ideal to me. (Also, potential trademark issue.)
 
Last edited:
1
•••
Well, if you want to challenge the big boys out there you'll need to start with a better brand name they currently have (not just in this particular case but for any new startup in any niche).
Personally I don't understand what Rob is trying to achieve with these contests and polls, but if you really want to setup a new venture, better go out there and privately purchase the best name you find and afford.
Asking the opinion of 40, 50, 100 people from different backgrounds, with different education levels and different interests to vote for the brand name of my future venture, well I for one, not quite a fan of it. If you would have asked 100 of the world's best branding experts, that would have been quite a different story.
You just can't pick your startup new brand name based on what 100 (more or less) domainers vote for. Just my opinion of course, Rob is a very smart guy and he surely know better than myself how to conduct his own branding research.
I beg to differ. I think it is logical to have a poll and seek the opinion of the people 'specialized' in the domain branding field ( of course, it is a open forum and not all are exactly specialists). It gives a good 360 degree perspective. It also helps to identify issues which could have been overseen ( TM issues, etc).
Lastly and most importantly, it helps build the community in terms of learning and sharing perspectives and helps each of us grow.
Also the past experience of such polls, i guess have been successful in finding good names, potential features and connections for these projects. Also has been a good and insightful experience for domainers.
Lets just enjoy the experience. Everyone has something to gain and nothing much to loose :)
You say it as if the audience is just some random folks. While there are indeed some of the world's best branding experts here, who envision and eventually sell names eventually used by businesses worldwide.

There are advantages and disadvantages to this process. What makes me laugh is that nobody else asked or discussed who the target end user is for the brand. That's the most important thing as from that you can eliminate a lot of names and possibly create a few other cool ones.

I hate saying this .. but it's also unfortunately true that NamePros members are not all "branding experts" .. it's just an sad fact that the vast majority of new domainers fail at domaining specifically because they lack the marketing, branding and language skills required to build a profitable portfolio. Beyond that .. even some of the best domainers then might not have the required knowledge or information on the specific niche and intended market to understand the domain characteristics and traits that would make the ideal brand.

Also, if it were me, the poll result would only be about 10% of it .. it's the debate and pro/cons that are much more important. However, with this being an open part of the forum that Google can index, then it's not ideal because anything negative against a domain will remain there long after the poll ends .. there would likely be a lot more relevant and helpful critical feedback if the discussion/debate were behind closed doors.

All that said .. I think as these polls go on, @Rob Monster and his team is going to focus less and less on the poll results. At the moment one of the very few names I actually thought was usable is in the lead .. but there seems to be strong trademark issues .. so obviously Rob will quickly look into to it to be sure either way, and then eliminate it as a choice if it's a potential problem. That's one thing where this thread can be very helpful.

Another important point I mentioned a couple of pages ago, regarding domains with industry abbreviations and tech terms .. if the ultimate LCD (Lower Common Denominator in terms of encryption/tech vocabulary) of the target market is found to not be very tech savvy, then many domains unfortunately can't be considered from the start.

For example, does the intended client think the certificates they need to keep their website secure is linked to their domain, or the hosting service, or webpages themselves? It's not about what it actually is, it's what the target-audience perceives. That's why SSL is used in most of the branding for such certificates, even if certificates can not be "SSL" .. it's because the term SSL is actually used as a brand at this point .. and not just any brand, but at the generic industry umbrella term like "Bluetooth" or "DVD", etc.

It's for this reason why many companies try to choose brands that are completely generic. However, based on previous choices, it seems Rob prefers keeping at least one word industry specific (non-generic). Which actually is still a good thing if your brand is pretty set in what it's going to be and the majority of the intended target audience is familiar with the word components that make up the brand.

The key for such "contests" to be effective is for there to be direction and feedback as the process moves along. There hasn't been much of that in this contest .. and we still don't even know who the intended target audience is .. so the feedback, debate and lists of pros/cons aren't going to be as relevant as they could be. Hopefully a bit more precision and clarity will be given this week as Rob returns from his conference. :)
 
3
•••
0
•••
It was clear even before the poll:
OK .. sorry if I missed it .. so then by all means, please give us the profile of the targeted client.
(Or more ideally, please quote where that info was clearly given)
 
Last edited:
0
•••
You need to click on the arrow, it is going to bring you to the thread :xf.wink:

(I don't mean the "profile of the targeted client", but that should have been obvious from the start)
 
Last edited:
0
•••
You need to click on the arrow, it is going to bring you to the thread :xf.wink:
(I don't mean the "profile of the targeted client", but that should have been obvious from the start)

I read the thread .. and given the varied range of opinions and feedback, I'd say it wasn't very clear or obvious .. but if it's obvious to you, then please enlighten the rest of us! :)
 
0
•••
The first poll title says:

Does the market need more alternatives for free SSL certificates?

The product is aimed at the same audience which is using Let's Encrypt – tech savvy people (who use it knowingly) and everyone else (who use it because their hosting provider is giving this option for their website), and of course all web hosting providers who have to be dependent on LE right now. The second category may have no clue, but the first and the third clearly understand that its not good to go without choices, so they'll obviously embrace the alternatives, the more the better. (Would you like to live in a world, with only one domain registrar?)
 
1
•••
That's a good guestimate .. and what I might have assumed myself .. :) .. but looking at a lot of the technical-based domains that made it into the list, it seems like the "everyone else" group isn't really a factor or consideration.

Is the product going to be free, freemium or paid? If there will be no free/freemium model then competing against Let's Encrypt isn't even a factor and maybe we don't need to worry so much about the non-technically savvy (or at least not as much). Or will it be more focused on creating a service to re-license to other registrars/hosting companies who would in turn offer the service for free .. or at a price?

Ultimately even for a paid service, I think the growing need for a trust/security certificate for ALL websites means the name needs to make sense to the "everyone else" group .. but again .. the inclusion of many of the more technical domains in the list points to the "everyone else" group not being relevant.

Also a little confusing because in the first thread he said he didn't want to be SSL specific ... but then he includes an SSL domain in the list!? lol

Or maybe possibly it's that Rob doesn't see that type of name as being an obstacle ... but ultimately I think the list was pretty quick coffee-induced list with the safety of knowing there would be at least one final round of elimination (whether via another pool, or just internally with himself and a few people he trusts). OR .. MUCH more likely .. this is simply a project based on a quick idea .. and he's using this process not just to find a brand .. but also to actually flesh out what the specifics and details of final product is actually going to be? (crawl .. walk .. run ... lol) ... Wouldn't be the first time! :)
 
2
•••
I think you guys are somewhat overthinking this. Not every brand screams this is what I am about and alot of times a more open vessel is desired as opposed to something very standard and boring.

Its not simply the name its what you do with it is my point. I have seen names I would never look twice at or are downright weak or dull purchased for end user pricing and used well. We all have. There is no accounting for user TASTE when using a logical argument only. A great name is helpful for success but opinions on what is a great name are vast and varied. And the name ultimately does not guarantee success the effort behind it does.

I am sure a great choice will be made by Rob, as mentioned,these threads are great for discussion but certainly not the deciding factor. They are more for us to debate and learn than anything else.
 
4
•••
I think you guys are somewhat overthinking this. Not every brand screams this is what I am about and alot of times a more open vessel is desired as opposed to something very standard and boring.
Its not simply the name its what you do with it is my point. I have seen names I would never look twice at or are downright weak or dull purchased for end user pricing and used well. We all have. There is no accounting for user TASTE when using a logical argument only. A great name is helpful for success but opinions on what is a great name are vast and varied. And the name ultimately does not guarantee success the effort behind it does.
I am sure a great choice will be made by Rob, as mentioned,these threads are great for discussion but certainly not the deciding factor. They are more for us to debate and learn than anything else.

I agree with everything you said .. and in fact .. it's actually my point .. lol .. if the end game and end user were more detailed/refined/specific, then we would at least have a more relevant discussion debate as to the merits of each name .. because at this point there's a lot of wasted time guessing (when there doesn't need to be).
 
Last edited:
2
•••
FullEncrypt certainly is a nice (and powerful) name and all, but I feel it's more suitable in the context of hard disk encryption. In the context of digital certificates, especially standing up a Root CA as Epik intends to, I feel DNEncrypt is a much better fit. If FullEncrypt is used, it implies that without it, you only have partial encryption. In the realm of digital certificates, partial encryption doesn't exist. You either have it, or you don't. Its' not something you could go into your workplace and say, "I just installed Epik's new Root CA cert. called FullEncrypt and now I'm fully encrypted."

DNEncrypt is generic but descriptive enough to let the end-user know that their connection to a domain name (more accurately a server) will be encrypted - period. All underlying negotiated encryption protocols are transcended now and in the future. The upside to having an Epik DNEncrypt certificate installed, is that it can added to the existing line of Epik's security-related offerings such as DNProtect. No need to reinvent the wheel - just add more spokes. :)

IMO of course, and I do believe Full Encrypt is a good name, just not in the context of digital certificates.

What are your thoughts on EncryptSpace? Like you said it is not the website that is encrypted but the conversation between servers i.e. the layer or space between the two parties is encrypted and thus safe. Disclaimer - I am biased as I own EncyptSpace.com :D
 
0
•••
What are your thoughts on EncryptSpace? Like you said it is not the website that is encrypted but the conversation between servers i.e. the layer or space between the two parties is encrypted and thus safe. Disclaimer - I am biased as I own EncyptSpace.com :D

Hi there! Purely IMO, "Encrypt" yes, but "space" kind of leaves a first impression of space on a hard disk/drive. For example, using BitLocker to encrypt your primary partition. I don't have the first impression of encrypting traffic or communication between end-points. :)
 
2
•••
DNCertify
DNCert(s)
DNCertificates

A suite of .com tailored brands specifically for domain certificates, aligned with Epik's recent DNProtect product.
 
1
•••
Double DN Usage can be confused, imo.
(The brand names must be different, not similar.)
 
1
•••
Double DN Usage can be confused, imo.
(The brand names must be different, not similar.)
You obviously sumbitted FullEncrypt, as you've posted it a bunch.

Competing with Let'sEncrypt, FullEncrypt or any "encrypt" keyword combo doesn't create confusion with the current giant in this specific space? Seriously doubt that.
 
Last edited:
2
•••
No, usage of "Full" will not be confusing with "Let's"; it would be with "Lite" etc, starting with L.
But, "DNSomething" with "DNProtect" can be confusing.
"Encrypt" word (as a verb or a name (abbreviation of Encryption)) is not problem, it is descriptive and ideal; but "DNSomethings" seem not ideal, imo.

So, I suggest(ed) FullEncrypt, and imo it is very ideal; all-in-one!
All the best!
 
Last edited:
1
•••
That's why SSL is used in most of the branding for such certificates, even if certificates can not be "SSL" .. it's because the term SSL is actually used as a brand at this point

Fully agree with you @Ategy.com. SSL has long been deprecated (since 1999 according to https://www.ssl.com/faqs/faq-what-is-ssl/) but here we are in 2019 and its still the most common way for referring to the SSL\TLS certificates.

Here is another quote from https://www.websecurity.digicert.com/en/in/security-topics/what-is-ssl-tls-https

"TLS (Transport Layer Security) is just an updated, more secure, version of SSL. We still refer to our security certificates as SSL because it is a more commonly used term, but when you are buying SSL from Symantec you are actually buying the most up to date TLS certificates with the option of ECC, RSA or DSA encryption."

No matter how advanced or updated the technology gets, seems like SSL is been branded in consumer mindset very strongly.

And if Rob changes his mind on SSL inclusion I still have 2 very strong candidates:

SSLCloak.com
Like the Cloak of Invisibility. Will hide your data from prying eyes :)

SSLified.com
Could potentially create a new lingo for SSL certificates -> "Get SSLified with us and ensure privacy and protection for you and your customers!"

Cheers!
 
0
•••
As per Rob

So, looking ahead, we think it is likely that we will need to become our own CAA root authority. However, this will not happen as "Epik", but rather as a stand-alone brand similar to Komodo, Thawte, or other SSL root authority. We now need to select a great brand name for a SSL cert brand.

It says all about end user and brand specifications .
 
0
•••
As per Rob

So, looking ahead, we think it is likely that we will need to become our own CAA root authority. However, this will not happen as "Epik", but rather as a stand-alone brand similar to Komodo, Thawte, or other SSL root authority. We now need to select a great brand name for a SSL cert brand.

It says all about end user and brand specifications .
See note just sent about SSL. The SSL tech is being replaced by TLS, which will eventually be replaced by something else. As such, SSL is not something to include in the brand..
Rob made this note regarding "SSL" as a keyword in a note later in the original discussion thread regarding this project..
 
Last edited:
2
•••
You can create free certificate for yourself or for you clients, but if they don't pass through one of 3 cartel companies, then Firefox or Chrome may say this certificate is not real, this site is not secure, I don't allow you to visit it. Sometimes no ssl works better, because then the browser wouldn't block access by saying this site is not secure. Maybe things changed recently.
 
2
•••
Rob made this note regarding "SSL" as a keyword in a note later in the original discussion thread regarding this project..
I am not at all saying brand should contain SSL. I just said it says all about the end user and overall objective of the brand name.
 
2
•••
Currently, if you use Epik's premium landing pages, you will notice that Epik enrolls a digital certificate for your domain name (DN) for free using Let'sEncrypts' intermediate (or issuing) certificate authority (CA).

Let'sEncrypt's intermediate certificate authority (CA) or "issuing CA" is called "Let'sEncrypt Authority X3 ".

Let'sEncrypt Authority X3 is NOT a Root CA, rather it get's it's ability to issue (sign) certificates from Digital Signature Trust Company, who runs the Root CA called DST X1.

Epik has been issuing a TON of free certs lately from LetsEncrypt's CA (and subsequently the Root CA, DST X1) that Epik thought it'd be a great idea to become independent of these two CAs. I agree with this idea.

So in the end, which name from the list above best replaces "DST X1" and "Let'sEncrypt Authority X3".

I am confident that my suggested name is perfectly suited, and here is what an Epic certificate would look like if DNEncrypt is selected and issued a certificate to the DN "TheBitten.com". (a name I own)

@Rob Monster
@Abdullah Abdullah


upload_2019-10-21_10-38-1.png
 
Last edited:
4
•••
I am confident that my suggested name is perfectly suited, and here is what an Epic certificate would look like if DNEncrypt is selected and issued a certificate to the DN "TheBitten.com". (a name I own)

@Rob Monster
@Abdullah Abdullah


Show attachment 132448
I like your confidence. Going by your comments even RootAuth.com, TrustCert.com and CertAuth.com seem to fall the same category and, should be the most preferred.
 
1
•••
I like your confidence. Going by your comments even RootAuth.com, TrustCert.com and CertAuth.com seem to fall the same category and, should be the most preferred.

The name "RootAuth" wouldn't leave a lot of room for expansion as the only function it could serve is being a Root CA. What about any intermediate or issuing CA's? Those would no longer be "root". :) "TrustCert" is borderline TM last I checked. "CertAuth" is an abbreviation for the technology being used - IMO, not a brand.
 
Last edited:
2
•••
Is this fair: to call the vote via another thread and multi-messages?
Don't please.
 
2
•••
Back