0

I'm looking to get some quick, informal feedback about some copy we may use in our UI.

If you're familiar with SSL certificates, can you read the copy below and let me know your thoughts?

Copy: "Build trust with your customers—apply a custom SSL certificate"

closed as off-topic by dennislees, Madalina Taina, locationunknown, DarrylGodden, Ken Mohnkern Jul 12 at 17:37

This question appears to be off-topic. The users who voted to close gave these specific reasons:

  • "Questions about Site Reviews are off-topic because questions here are expected to be relevant for a variety of people in the same situation. Reviewing a site, flow or interface only helps one person at a specific time. Instead try to ask a focused question about a particular aspect of the design that solicits solutions, not opinions." – dennislees, Ken Mohnkern
  • "Questions about Implementation are off-topic because this site is for User Experience design questions, not questions around how to implement these designs. Therefore, questions around the use of programs like Photoshop or languages such as CSS or JavaScript are off topic." – Madalina Taina, DarrylGodden
If this question can be reworded to fit the rules in the help center, please edit the question.

  • This falls under the category of site review, and should be closed as the answers will be primarily subjective are only really valuable to the person asking the question. – dennislees Jul 12 at 2:35
1

Meaningless

TL;DR Every SSL certificate is custom at the most basic level. And beyond that, virtually nobody knows or cares.

Every SSL certicicate is "custom" in that it references the domain name, and possibly other web site/company specific data. But beyond those basics, which are, at least minimally, required, by the nature of a functioning SSL certificate, what else matters? An end-user looking at the site may notice a different color or whatever for a higher-level certification, but most people don't even notice that - or may notice but have no idea what it means. Anything else would be buried inside the details of the certificate - and almost nobody (except security professionals) looks at the details of a certificate unless the browser presents it as an error.

Personally, I've migrated wherever possible from Thawte and other high-level certificates to Let's Encrypt and nobody I know as an ordinary web user knows the difference.

Not the answer you're looking for? Browse other questions tagged or ask your own question.