VeriSign & Thawte Digital Certificates

Prices (limited time only)

We has excess inventory of VeriSign & Thawte SSL digital certificates and we are ready to provision your orders now.

Type	Vendor Price (US$)	Our Price (US$)	Savings (20% Saving)*
SSL VeriSign (128 bit capability)	895	716	149
SSL VeriSign (40 bit capability)	349	279	69
SSL Thawte (40 56 128 bit capability)	125	100	25
* Additional savings available for quantities of 10 or more.

For more information, please send an email to support@aboutdomains.com.

Why Do I Need One?

if you are running an e-commerce site, you need to worry about:

• Authentication: The low cost of establishing and running a Web site makes it all too easy to create illegitimate sites that appear to be operated by established organizations. Your customers must be assured that they are in fact doing business with you
• Confidentiality: When sensitive information is transmitted “in the clear,” without proper security and encryption, hackers can intercept the transmissions .You must keep such information private and secure.  Such information includes credit card and personal information submitted by customers, as well as propriety code and information transmitted in the form of documents and email.
• Data integrity: The content of a transaction can be not only intercepted, but also altered en route, either maliciously or accidentally. Communication between you and your customers must be protected from alteration in transmission on the Internet.
• Audit Trail: A person must not be able to deny that he or she sent a secured communication or made an online purchase.

You can solve these issues by using a SSL Server ID.

 

How SSL Certificates Work

Digital certificates for your Web site (or “Server IDs”) is a digital credential that enables your customers to verify your site’s authenticity and to securely communicate with it.

Server IDs take advantage of the state-of-the-art Secure Sockets Layer (SSL) protocol, developed by Netscape. SSL has become the standard for authenticating Web sites to Web browser users, and for encrypting communications between browser users and Web servers. Because SSL is built into all major browsers and Web servers, simply installing a Server ID, enables SSL capabilities.

SSL server authentication allows users to confirm the receiving Web server’s identity. SSL-enabled client software, such as a Web browser, can automatically check that a server’s certificate and public ID are valid and have been issued by a certificate authority.

An encrypted SSL connection requires that all information sent between a client and a server to be encrypted by the sending software and decrypted by the receiving software, protecting private information from interception over the Internet. In addition, all information sent over an encrypted SSL connection is protected with a mechanism for detecting tampering—that is, for automatically determining whether the data has been altered in transit. This means that users can confidently send private data to a Web site, trusting that it is kept it private and confidential.

The Server ID process works as follows:

1. A customer contacts your site and accesses a page that is secured by a Server ID (indicated by a URL that begins with “https:” instead of just “http:” or by a message from the browser).
2. Your server responds, automatically sending the customer your site’s digital certificate, which authenticates your site.
3. Your customer's Web browser generates a unique “session key” to encrypt all communications with the site. The user’s browser encrypts the session key itself with your site’s public key so only your site can read the session key.
4. A secure session is automatically established in seconds. Depending on the browser, the customer may see a key icon at the bottom of the screen becoming whole or a padlock closing, indicating that the session is secure.

 Top

Server IDs and Public-Key Cryptography

Encryption is not new. Historically, most private messages were kept secret with a single unique code (or key) for both encrypting and decrypting messages.  Single key cryptography works as follows:

If Susan wants to send you a secret message:

1. You have to first create a secret code
2. You have to send Susan a copy of your secret code
3. Susan encrypts her message with your secret code
4. You are then able to decrypt the message with your secret code

Unfortunately, this method has several problems:

1. You must find a secure method of getting your secret key to Susan. If the secret key is intercepted, all of your communications are compromised.
2. You need to trust Susan. You must be sure that she is not a double agent or, she may read your other private messages.
3. If you have an organization with people who need to exchange secret messages, you will either need to have thousands (if not millions) of secret keys, or you will need to rely on a smaller number of keys, which opens the door to compromise.

The solution is using the more advanced public-key cryptography. Rather than using the same key to both encrypt and decrypt information, a Server ID uses a matched pair of keys that uniquely complement each other. When a key pair is generated for your business, your “private key” is installed on your server; nobody else has access to it. When your “public key encrypts a message” only your “private key” can decrypt it. Thus, your matching “public key,” can be freely distributed as part of your Server ID. Customers or correspondents who want to communicate with you privately can use the public key in your Server ID to encrypt information before sending it to you. Only you can decrypt the information, because only you have your “private key.”