Software & Apps Apps 54 54 people found this article helpful Signed and Self-Signed Certificates by Jennifer Kyrnin Freelance Contributor Jennifer Kyrnin is a professional web developer who assists others in learning web design, HTML, CSS, and XML. our editorial process LinkedIn Jennifer Kyrnin Updated on December 01, 2019 Pixabay/CCO Apps Best Apps Payment Services Tweet Share Email Security is a critically important factor in the success of any website. This is especially true for sites that need to collect PIA, or "personally identifiable information," from visitors. Think about a site that requires you to enter a social security number, or more commonly, an e-commerce site that you need to add credit card info to in order to complete your purchase. On sites like these, security is not only expected from those visitors, it is essential to success. When you're building an e-commerce site, one of the first things you'll need to set up is a security certificate so that your server data will be secure. When you set this up, you have the option of creating a self-signed certificate or creating a certificate approved by a certificate authority. Let's take a look at the differences between these two approaches to website security certs. Similarities Between Signed and Self-Signed Certificates Whether you get your certificate signed by a certificate authority or sign it yourself, there is one thing that is exactly the same on both: Both certificates will generate a site that cannot be read by third-parties. The data is sent over an HTTPS connection, or SSL, and will be encrypted regardless of whether the certificate is signed or self-signed. In other words, both types of certificates will encrypt the data to create a secure website. From a digital security perspective, this is step 1 of the process. Why You Would Pay a Certificate Authority A certificate authority tells your customers that this server information has been verified by a trusted source and not just the company that owns the website. Basically, there is a 3rd party company that has verified the security information. A commonly used Certificate Authority is Verisign. Depending upon which CA is used, the domain is verified and a certificate is issued. Verisign and other trusted CAs will verify the existence of the business in question and the ownership of the domain to provide a bit more security that the site in question is legitimate. The problem with using a self-signed certificate is that nearly every web browser checks that an HTTPS connection is signed by a recognized CA. If the connection is self-signed, this will be flagged as potentially risky and error messages will pop up encouraging your customers to not trust the site, even if it is, indeed, secure. Using a Self-Signed Certificate Since they provide the same protection, you can use a self-signed certificate anywhere you would use a signed certificate, but some places work better than others. Self-signed certificates are great for testing servers. If you're creating a website that you need to test over an https connection, you don't have to pay for a signed certificate for that development site (which is likely to be an internal resource). You just need to tell your testers that their browser may pop up warning messages. You can also use self-signed certificates for situations that require privacy, but people might not be as concerned about. For example: Username and password formsCollecting personal but non-financial PIAOn forms where the only users are people who know and trust you, like on a company intranet What it comes down to is trust. When you use a self-signed certificate, you are saying to your customers, "Trust me—I am who I say I am." When you use a certificate signed by a CA, you are saying, "Trust me—Verisign agrees I am who I say I am." If your site is open to the public and you are trying to do business with them, the latter is a much stronger argument to make. If You're Doing E-commerce, You Need a Signed Certificate It is possible your customers will forgive you for a self-signed certificate if all they use it for is to log in to your website, but if you're asking them to input their credit card or PayPal information, then you really need a signed certificate. Most people trust the signed certificates and won't do business over an HTTPS server without one. So if you're trying to sell something on your website, invest in that certificate. It's part of the cost of doing business and being engaged in online selling.